-
Notifications
You must be signed in to change notification settings - Fork 977
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
MIT License? #103
Comments
This is currently also discussed in pull request #101 |
The following PRs were originally merged without MIT license assignment, and the checked PRs now have MIT license assignment from the author:
|
Do the listed PR contain enough to qualify for copyright and thus need the assignments. Looking at my own contribution (i changed the case in a few filenames) can't possibly reach verkshöjd(can't bother to translate) to be covered by copyright. Although if you want me to take any legal action I will happily contact a lawyer and pass on the bill to you. |
Peter, Inget behov av rättsliga åtgärder. Tack för att svara, och tack för ditt bidrag. -Neil |
Good morning, I am the "all things administrative red tape guy" on the SharpDevelop team. Some background on why we now want to (finally) take SharpZipLib to MIT - and action items. @McNeight has joined as the new maintainer for SharpZipLib, and in the process of discussing with the old maintainers @jfreilly and @davidpierson somewhat obviously the license topic came up (and I can tell everybody that it was/is a pain to me too just by looking at the inbox on how many questions I got over the years just on license clarification). Now, SharpZipLib started out of part of SharpDevelop, and with SharpDevelop we required JCAs (please see https://github.com/icsharpcode/SharpDevelop/wiki/Joining-the-Team). We want to get to exactly the same point with SharpZipLib, and so we want to go the following route:
About the PR part: usually in SharpDevelop we had the notion of "more than five lines" that needed a JCA. Which for the PRs @McNeight listed applies only to a few then, however, we would love that everyone adds the MIT paragraph to their past contributions (comment to the original PR). For documentation purposes and, basically, we want to be a good OSS community citizen as always. Once that is done, we will have a contributing.md that reflects the "joing the team" document of SharpDevelop. Read: PRs come with that paragraph for documentation purposes (we want to do away with the paperwork (even digital)). @Mailaender, @hypersw, @ermshiperete and @hultqvist: could you please amend your past PRs with I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License. All others mentioned by @McNeight - not strictly required but we would love you to do that too. Thank you in helping us make the license of SharpZipLib easy & palatable to an even broader audience! |
Yeah sure, although I guess my contributions are somehow insignificant. |
Yes sure. |
I certify that I own, and have sufficient rights to contribute, all source code and related material for pull request #74 by @konstantingolovanov intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License. 15.04.2016, 01:56, "Neil McNeight" notifications@github.com:
|
I certify that Google owns, and I have sufficient rights to contribute, all On Sun, Apr 17, 2016 at 11:48 AM, konstantingolovanov <
|
I certify that Renaissance Learning Inc owns, and I have sufficient rights to contribute, all source code and related material for pull request #18 by @hempels intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License. |
I certify that I own, and have sufficient rights to contribute, all source code and related material for pull request #84 by @kkguo intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License. |
I certify that I own, and have sufficient rights to contribute, all source code and related material for pull request #69 by @Ezghoul intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License. |
Shouldn't the change in license also be reflected on http://icsharpcode.github.io/SharpZipLib/ ?
It is somewhat confusing to see different info on https://github.com/icsharpcode/SharpZipLib
|
I think so.I want to use this library, but it's license policy confused. So I cannot use this library on MIT License. |
Hello, any news on the license question in regards of the License Change on the http://icsharpcode.github.io/SharpZipLib/ page to the github provided license? |
Hi - This looks like a great library and I would like to use it. However, as @SOesterreicher mentioned, http://icsharpcode.github.io/SharpZipLib/ is still showing that the licence as GPL.
Thank you. |
Good day.I confirm that it is definitly MIT license.Thanks.--Отправлено из мобильной Яндекс.Почты23.10.2018, 05:37, "brendonferris" <notifications@github.com>:Hi - This looks like a great library and I would like to use it.
However, as @SOesterreicher mentioned, http://icsharpcode.github.io/SharpZipLib/ is still showing that the licence as GPL.
Is it now possible to update http://icsharpcode.github.io/SharpZipLib/ to show that it is MIT?
Can you confirm that it is definitely MIT now (and there are no outstanding licensing issues)?
Thank you.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
|
Great - thank you for the confirmation. |
I certify that I own, and have sufficient rights to contribute, all source code and related material for |
MIT License forever--Sent from Yandex.Mail for mobile30.12.2019, 23:39, "nils måsén" <notifications@github.com>:Closed #103.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
|
Dear Team,
Given the whole .NET world is now MIT, any chance this great lib could also change to that?
The text was updated successfully, but these errors were encountered: