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

Open
xied75 opened this Issue Apr 5, 2016 · 16 comments

Comments

@xied75
Contributor

xied75 commented Apr 5, 2016

Dear Team,

Given the whole .NET world is now MIT, any chance this great lib could also change to that?

@christophwille

This comment has been minimized.

Show comment
Hide comment
@christophwille

christophwille Apr 5, 2016

Member

This is currently also discussed in pull request #101

Member

christophwille commented Apr 5, 2016

This is currently also discussed in pull request #101

@McNeight

This comment has been minimized.

Show comment
Hide comment
@McNeight

McNeight Apr 6, 2016

Contributor

The following PRs were originally merged without MIT license assignment, and the checked PRs now have MIT license assignment from the author:

Contributor

McNeight commented Apr 6, 2016

The following PRs were originally merged without MIT license assignment, and the checked PRs now have MIT license assignment from the author:

@hultqvist

This comment has been minimized.

Show comment
Hide comment
@hultqvist

hultqvist Apr 6, 2016

Contributor

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.

Contributor

hultqvist commented Apr 6, 2016

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.

@McNeight

This comment has been minimized.

Show comment
Hide comment
@McNeight

McNeight Apr 6, 2016

Contributor

Peter,

Inget behov av rättsliga åtgärder. Tack för att svara, och tack för ditt bidrag.

-Neil

Contributor

McNeight commented Apr 6, 2016

Peter,

Inget behov av rättsliga åtgärder. Tack för att svara, och tack för ditt bidrag.

-Neil

@christophwille

This comment has been minimized.

Show comment
Hide comment
@christophwille

christophwille Apr 7, 2016

Member

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!

Member

christophwille commented Apr 7, 2016

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!

@Mailaender

This comment has been minimized.

Show comment
Hide comment
@Mailaender

Mailaender Apr 7, 2016

Contributor

Yeah sure, although I guess my contributions are somehow insignificant.

Contributor

Mailaender commented Apr 7, 2016

Yeah sure, although I guess my contributions are somehow insignificant.

@McNeight

This comment has been minimized.

Show comment
Hide comment
@McNeight

McNeight Apr 14, 2016

Contributor

I would like to merge the following PRs once we have an MIT license assignment from the original author, and the checked PRs now have MIT license assignment from the author:

Contributor

McNeight commented Apr 14, 2016

I would like to merge the following PRs once we have an MIT license assignment from the original author, and the checked PRs now have MIT license assignment from the author:

@konstantingolovanov

This comment has been minimized.

Show comment
Hide comment
@konstantingolovanov

konstantingolovanov commented Apr 17, 2016

Yes sure.

@konstantingolovanov

This comment has been minimized.

Show comment
Hide comment
@konstantingolovanov

konstantingolovanov Apr 17, 2016

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 would like to merge the following PRs once we have an MIT license assignment from the original author:
#18 by @hempels (5 lines in 1 file)
#69 by @Ezghoul (2 lines in 1 file)
#74 by @konstantingolovanov (26 lines in 1 file)
#76 by @bbenoist (2 lines in 1 file)
#83 by @depend86 (64 lines in 1 file)
#84 by @kkguo (2 lines in 1 file)
#85 by @pldg (5 lines in 1 file)
#86 by @creker (7 lines in 2 files)
#93 by @bastianeicher (102 lines in 6 files)
#96 by @aviranco (34 lines in 1 file)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

konstantingolovanov commented Apr 17, 2016

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 would like to merge the following PRs once we have an MIT license assignment from the original author:
#18 by @hempels (5 lines in 1 file)
#69 by @Ezghoul (2 lines in 1 file)
#74 by @konstantingolovanov (26 lines in 1 file)
#76 by @bbenoist (2 lines in 1 file)
#83 by @depend86 (64 lines in 1 file)
#84 by @kkguo (2 lines in 1 file)
#85 by @pldg (5 lines in 1 file)
#86 by @creker (7 lines in 2 files)
#93 by @bastianeicher (102 lines in 6 files)
#96 by @aviranco (34 lines in 1 file)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 3, 2016

I certify that Google owns, and I have sufficient rights to contribute, all
source code and related material for pull request 85 by @pldg intended to
be compiled or integrated with the source code for the #develop open source
product (the "Contribution"). My Contribution is licensed under the MIT
License.

On Sun, Apr 17, 2016 at 11:48 AM, konstantingolovanov <
notifications@github.com> wrote:

Yes, certainly.

15.04.2016, 01:56, "Neil McNeight" notifications@github.com:

I would like to merge the following PRs once we have an MIT license
assignment from the original author:
#18 by @hempels (5 lines in 1 file)
#69 by @Ezghoul (2 lines in 1 file)
#74 by @konstantingolovanov (26 lines in 1 file)
#76 by @bbenoist (2 lines in 1 file)
#83 by @depend86 (64 lines in 1 file)
#84 by @kkguo (2 lines in 1 file)
#85 by @pldg (5 lines in 1 file)
#86 by @creker (7 lines in 2 files)
#93 by @bastianeicher (102 lines in 6 files)
#96 by @aviranco (34 lines in 1 file)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#103 (comment)

ghost commented May 3, 2016

I certify that Google owns, and I have sufficient rights to contribute, all
source code and related material for pull request 85 by @pldg intended to
be compiled or integrated with the source code for the #develop open source
product (the "Contribution"). My Contribution is licensed under the MIT
License.

On Sun, Apr 17, 2016 at 11:48 AM, konstantingolovanov <
notifications@github.com> wrote:

Yes, certainly.

15.04.2016, 01:56, "Neil McNeight" notifications@github.com:

I would like to merge the following PRs once we have an MIT license
assignment from the original author:
#18 by @hempels (5 lines in 1 file)
#69 by @Ezghoul (2 lines in 1 file)
#74 by @konstantingolovanov (26 lines in 1 file)
#76 by @bbenoist (2 lines in 1 file)
#83 by @depend86 (64 lines in 1 file)
#84 by @kkguo (2 lines in 1 file)
#85 by @pldg (5 lines in 1 file)
#86 by @creker (7 lines in 2 files)
#93 by @bastianeicher (102 lines in 6 files)
#96 by @aviranco (34 lines in 1 file)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#103 (comment)

@hempels

This comment has been minimized.

Show comment
Hide comment
@hempels

hempels May 9, 2016

Contributor

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.

Contributor

hempels commented May 9, 2016

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.

@kkguo

This comment has been minimized.

Show comment
Hide comment
@kkguo

kkguo May 11, 2016

Contributor

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.

Contributor

kkguo commented May 11, 2016

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.

@Ezghoul

This comment has been minimized.

Show comment
Hide comment
@Ezghoul

Ezghoul Jul 27, 2016

Contributor

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.

Contributor

Ezghoul commented Jul 27, 2016

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.

@McNeight McNeight modified the milestones: post 1.0, 1.0 Aug 14, 2016

@ReinoutW

This comment has been minimized.

Show comment
Hide comment
@ReinoutW

ReinoutW Jan 2, 2017

Shouldn't the change in license also be reflected on http://icsharpcode.github.io/SharpZipLib/ ?
It still reads:

License
The library is released under the GPL with the following exception:

Linking this library statically or dynamically with other modules is making a combined work based on this library. Thus, the terms and conditions of the GNU General Public License cover the whole combination.

As a special exception, the copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.

Note The exception is changed to reflect the latest GNU Classpath exception. Older versions of #ziplib did have another exception, but the new one is clearer and it doesn't break compatibility with the old one.

Bottom line In plain English this means you can use this library in commercial closed-source applications.

It is somewhat confusing to see different info on https://github.com/icsharpcode/SharpZipLib

License

This software is now released under the MIT License. Please see issue #103 for more information on the relicensing effort.

Previous versions were released under the GNU General Public License, version 2 with an exception which allowed linking with non-GPL programs.

ReinoutW commented Jan 2, 2017

Shouldn't the change in license also be reflected on http://icsharpcode.github.io/SharpZipLib/ ?
It still reads:

License
The library is released under the GPL with the following exception:

Linking this library statically or dynamically with other modules is making a combined work based on this library. Thus, the terms and conditions of the GNU General Public License cover the whole combination.

As a special exception, the copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.

Note The exception is changed to reflect the latest GNU Classpath exception. Older versions of #ziplib did have another exception, but the new one is clearer and it doesn't break compatibility with the old one.

Bottom line In plain English this means you can use this library in commercial closed-source applications.

It is somewhat confusing to see different info on https://github.com/icsharpcode/SharpZipLib

License

This software is now released under the MIT License. Please see issue #103 for more information on the relicensing effort.

Previous versions were released under the GNU General Public License, version 2 with an exception which allowed linking with non-GPL programs.

@ntjtomohide

This comment has been minimized.

Show comment
Hide comment
@ntjtomohide

ntjtomohide Jan 17, 2017

I think so.I want to use this library, but it's license policy confused. So I cannot use this library on MIT License.

ntjtomohide commented Jan 17, 2017

I think so.I want to use this library, but it's license policy confused. So I cannot use this library on MIT License.

@SOesterreicher

This comment has been minimized.

Show comment
Hide comment
@SOesterreicher

SOesterreicher Dec 15, 2017

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?
Thanks in advance.

SOesterreicher commented Dec 15, 2017

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?
Thanks in advance.

@piksel piksel added this to To do in v1.0 via automation Jul 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment