Skip to content
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

Relicense under 3-clause BSD #610

Closed
untitaker opened this issue Mar 26, 2017 · 8 comments
Closed

Relicense under 3-clause BSD #610

untitaker opened this issue Mar 26, 2017 · 8 comments
Assignees

Comments

@untitaker
Copy link
Member

@untitaker untitaker commented Mar 26, 2017

As per #253 a portion of contributors has given me permission to relicense vdirsyncer under any OSI license. I want to switch to the 3-clause BSD for 0.16.

Contributors that have not commented on #253 are by @beli3ver and @benjaminfrank as far as I can tell (other contributions are one-line typo fixes). Would you be fine with your contributions being relicensed under the 3-clause BSD license?

@ghost
Copy link

@ghost ghost commented Mar 26, 2017

@WhyNotHugo
Copy link
Member

@WhyNotHugo WhyNotHugo commented Mar 26, 2017

Any reason to pick the 3-clause BSD over MIT or ISC?

@untitaker
Copy link
Member Author

@untitaker untitaker commented Mar 26, 2017

@WhyNotHugo
Copy link
Member

@WhyNotHugo WhyNotHugo commented Mar 26, 2017

Oh, sorry, I though of the 2-clause. I got them all mixed up.

As far as I'm concerned, I'm okay with any of the MIT/BSD/ISC licenses.

@untitaker
Copy link
Member Author

@untitaker untitaker commented Mar 26, 2017

Ah sorry, I thought you also signed the generic OSI-compatible waiver. Thanks for confirming.

@WhyNotHugo
Copy link
Member

@WhyNotHugo WhyNotHugo commented Mar 27, 2017

Nope, I hadn't. 😛

@untitaker
Copy link
Member Author

@untitaker untitaker commented Mar 27, 2017

@benjaminfrank could you please leave a short comment on whether you approve of your contribution (the .plist file for vdirsyncer) being relicensed under the 3-clause BSD license? Thanks!

@untitaker
Copy link
Member Author

@untitaker untitaker commented Apr 6, 2017

Since @benjaminfrank didn't respond and technically I can relicense MIT code to 3-clause BSD without the copyright holder's consent, I will presumably do that tomorrow. However, I will exclude the contrib folder from the pypi distribution, partially due to the unrelated reason of minimizing tarball size.

@untitaker untitaker self-assigned this Apr 6, 2017
@untitaker untitaker closed this in 7aa0ea2 Apr 7, 2017
@untitaker untitaker removed the ready label Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants