Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add MIT licence #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Add MIT licence #246

wants to merge 1 commit into from

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented May 8, 2025

We don't have a licence is this repo, which means some people cannot contribute.

I suggest we add MIT licence, which was recently used for buildmaster-config: https://github.com/python/buildmaster-config/blob/main/LICENSE.txt

To continue, please could everyone listed below leave a comment to confirm you are happy to licence your past contributions to this repo under MIT?

@hugovk hugovk marked this pull request as draft May 8, 2025 15:56
@zware
Copy link
Member

zware commented May 8, 2025

Does checking your own box (shown as an edit by the correct user) count as agreement? Either way, I do so confirm for myself.

@zooba
Copy link
Member

zooba commented May 8, 2025

Can we MIT it, or should we use the Python license?

It looks like the CLA bot is active on this repo, which implies that contributions have been under Apache 2.0 or Academic Free License v3 (from https://www.python.org/psf/contrib/contrib-form/) and says that we either keep it under those licenses or a license "approved by a unanimous vote of the PSF board" (which I assume is only the Python license right now?).

@Yhg1s
Copy link
Member

Yhg1s commented May 8, 2025

👍 for any license

@di
Copy link
Member

di commented May 8, 2025

Confirmed!

@carljm
Copy link
Member

carljm commented May 8, 2025

Confirmed that I'm fine with my contributions being licensed under either MIT or Python license.

@AlexWaygood
Copy link
Member

I am also fine with my work being under either the Python license or the MIT license!

@Wulian233
Copy link
Contributor

I'm fine!

@encukou
Copy link
Member

encukou commented May 9, 2025

MIT it!

I am fine with my work here being under the MIT license, or any other OSI Approved License.

@ice-tong
Copy link
Contributor

LGTM!

@hugovk
Copy link
Member Author

hugovk commented May 13, 2025

Can we MIT it, or should we use the Python license?

It looks like the CLA bot is active on this repo, which implies that contributions have been under Apache 2.0 or Academic Free License v3 (from python.org/psf/contrib/contrib-form) and says that we either keep it under those licenses or a license "approved by a unanimous vote of the PSF board" (which I assume is only the Python license right now?).

Good point, looks like the CLA bot first triggered on this repo on 18th July 2023 (#51 (comment)).

Limiting to before this date at https://github.com/python/release-tools/graphs/contributors gives these contributors:

  • ambv
  • benjaminp
  • berkerpeksag
  • birkenfeld
  • carljm
  • di
  • ezio-melotti
  • larryhastings
  • ned-deily
  • pablogsal
  • serhiy-storchaka
  • vstinner
  • Yhg1s
  • zooba

I expect everyone there has already signed the CLA, or can do. I'll open another PR to use the PSF licence instead and ask Łukasz/Ee to confirm these have indeed already signed in the CLA DB.

Thanks anyway everyone!

@hugovk hugovk mentioned this pull request May 13, 2025
14 tasks
@hugovk
Copy link
Member Author

hugovk commented May 13, 2025

I expect everyone there has already signed the CLA, or can do. I'll open another PR to use the PSF licence instead and ask Łukasz/Ee to confirm these have indeed already signed in the CLA DB.

Or we do need confirmation that past commits can be licensed under PSF, but the list is much smaller. Take 2: #249!

@hugovk hugovk closed this May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants