Closed zachdaniel closed 3 years ago
I approve of changing to any open-source license, including MIT or LGPL, and further relinquish copyright of my contributed code to @zachdaniel.
Hi Daniel,
I agree with changing the licence of the project to MIT licence.
Best regards, Dan
On Fri, Jan 8, 2021, 20:59 Frank Dugan III notifications@github.com wrote:
I approve of changing to any open-source license, including MIT or LGPL, and further relinquish copyright of my contributed code to @zachdaniel https://github.com/zachdaniel.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/zachdaniel/git_ops/issues/45#issuecomment-756937723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADVG22SSQ45DW3BQP7ITXTSY5IYBANCNFSM4V2Z4WHQ .
Sorry, on holiday. Just saw this. You have my permission to use my code under the MIT license.
EDIT: Had to check to see what code I contributed. Changing a single line in the README haha
Awesome! Thanks @benwoodward. Apologies for interrupting your vacation.
@zachdaniel Permission granted to switch from GPL to MIT.
Thanks so much!
(To normalize it all into one place) Permission granted to switch license from GPL to MIT.
@zachdaniel I am happy to relicense my contributions as MIT. Go forth and share.
Thank you everyone for timely responses and making this happen. Hope you all have a great 2020!
Thank you everyone for timely responses and making this happen. Hope you all have a great 2020!
Classic off by one error.
Lol, just shows how much I wish this last year wasn't real.
Hey everyone! I'm reaching out because you're a contributor on my
git_ops
project on GitHub. The project can be found here: https://github.com/zachdaniel/git_ops. I've been notified that the license is actually much less permissive than we'd expect. Specifically, it is very unpermissive. Technically this means its a legal issue for those using it in their closed source work projects. However, this license is not in the spirit of what the creators intended. For ethical reasons, it is my responsibility to reach out to each contributor and confirm that they are okay with their work being relicensed under the MIT software license, which is extremely permissive. If those users would then like to update to the latest version of git_ops with that new license (once it is published) then all is well with the world and no one needs to worry.Some names may already be checked off, which means that I received confirmation from them through various media. If I was able to contact them by email, their email is not included here for their own privacy.
If we can't get ahold of @benwoodward we can undo his changes until we hear from him (or permanently if we never do): https://github.com/zachdaniel/git_ops/commit/97db3b5fa65405485c62bc936416d07b90f84dcd