Switch to MIT license #264
Comments
Sure. My contribution isn't even copyrightable (just a file extension change). |
BTW, your LICENSE says to check AUTHORS file for the list of contributors, but there is no such file in the repo. Probably makes sense to remove that note. |
When the new license takes effect we'll have the AUTHORS thing out, we'll link to https://github.com/tony/tmuxp/graphs/contributors |
Good action! I agree. |
I have no problem with this. Thanks for keeping us all in the loop. |
I am fine with it. |
I'm fine with this as well.
…On Sat, May 27, 2017, 10:11 PM anatoly techtonik ***@***.***> wrote:
I am fine with it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#264 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABYq8xKlgSp_vGzBt5utf9GHUa2Fw4Wxks5r-QHpgaJpZM4NohGZ>
.
|
I agree, thanks! |
fine for me |
Ok for me. |
Ok for me too |
Ok with me |
|
I'm ok with it. |
I agree
…On May 28, 2017 6:10 AM, "Martin Bukatovič" ***@***.***> wrote:
I'm ok with it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#264 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AApIXNFwDUwgmwYEmVilIsuJNwQQXw5rks5r-Tn2gaJpZM4NohGZ>
.
|
OK for me. |
Ok for me. |
Ok for me too :) |
I agree. |
Ok by me. |
Same here, I agree. |
fine with me |
Fine with me.
Domas
…On Tue, May 30, 2017 at 4:47 PM, Greg Back ***@***.***> wrote:
fine with me
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#264 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHRtB6XjIFE866SlNsDyMCxKlZwGOxZks5r_B3UgaJpZM4NohGZ>
.
|
I'm OK with this! |
This is fine with me! |
We're almost there. @kmactavish @roxit @raine @cryptojuice @sehe @Omeryl, do you agree to licensing your contributions under MIT license? If so, reply here that it's Ok! |
Good with me. |
OK! |
Fine! |
@roxit, @cryptojuice, @Omeryl, can you take a look at this issue? |
@tony I don’t believe I have any code in the repository. The only thing I recall writing is a typo fix to the README. Therefore, do whatever you need. |
thank you @Omeryl ! |
This issue has been automatically marked as stale because it has not had This bot is used to handle issues where the issue hasn't been discussed or |
Thank you for updating this issue. It is no longer marked as stale. |
@cryptojuice @roxit : You okay with relicensing your contributions to MIT? If so, please reply here. Only two more to go! |
Here is @roxit and @cryptojuice's commits: @roxit: acd882c (doc update), 992a50c (loading detached) @cryptojuice 2ea1366 (typo) Last call If there's no response, this license change can't wait forever, I may revert them and/or rewrite them licensed under MIT. |
This reverts commit 992a50c, a BSD-licensed commit blocking #264, conversion to MIT. See also: #264 (comment)
One of the code changes from @roxit, @cryptojuice's weren't revertable (findable) from master, so it looks like we're good to do the switch! #363 merged. Updating LICENSE now. |
1.4.0 is released. We're MIT. |
Woot!
…On Sun, Mar 11, 2018, 6:30 PM Tony Narlock ***@***.***> wrote:
1.4.0 is released.
We're MIT.
|
Nice! (but it took 10 months...wow. I wonder if asking permission was really necessary, besides being a nice thing to do) |
I'd like to switch the license to something even more permissive than BSD 3-clause (MIT).
Sorry for causing the ping, but wanted to get it out of the way.
If you're ok with it, please reply with a note that you agree for your code contribution(s) to tmuxp to be released under the MIT license.
The text was updated successfully, but these errors were encountered: