Skip to content
This repository has been archived by the owner on Feb 2, 2024. It is now read-only.

License confirmation? #2

Closed
pombredanne opened this issue May 1, 2022 · 13 comments
Closed

License confirmation? #2

pombredanne opened this issue May 1, 2022 · 13 comments

Comments

@pombredanne
Copy link

I see that the license is declared as "(MIT OR GPLv3)" but the original from @stephenliberty at https://github.com/stephenliberty/excel-builder.js was under GPL v3 and had some code under MIT, making it "GPL AND MIT" but not a "GPL or MIT" choice?
I see this was introduced by 7b92d44

What was the rationale for the license change? was @stephenliberty involved and gave its OK?

Thank you for your answer!

@ghiscoding
Copy link
Owner

ghiscoding commented May 1, 2022

he really has both in his License folder so that's the rational

EDIT
I remember seeing something somewhere from the author that he had dual license, and here it is

Note
his website is no longer available but we can use the webtime archive to see it at this link, then scroll to the bottom of the page and you will see the licenses
https://web.archive.org/web/20160907051738/http://excelbuilderjs.com/index.html

image

@pombredanne
Copy link
Author

pombredanne commented May 1, 2022

@ghiscoding Thanks for the quick reply!

he really has both in his License folder https://github.com/stephenliberty/excel-builder.js/tree/master/License so that's the rationale

I saw this too, but I think that the copyright in https://github.com/stephenliberty/excel-builder.js/blob/master/License/MIT.txt is from @Stuk "Copyright (c) 2009 Stuart Knightley" and jszip which is bundled in the compiled version and is under an MIT license.... and it seems highly unlikely (to me) that @Stuk MIT applies otherwise as a choice of license for the overall package?

@ghiscoding
Copy link
Owner

I follow more what the author of lib wrote on his own website (only available from the web archive) and I think the way I have it displayed is valid for that reason. I can add it to the readme if that's any helpful but I'm not planning to change the description of the license since I am following what the author wrote

@pombredanne
Copy link
Author

I follow more what the author of lib wrote on his own website (only available from the web archive) and I think the way I have it displayed is valid for that reason. I can add it to the readme if that's any helpful but I'm not planning to change the description of the license since I am following what the author wrote

oh, I did not knew there was a statement from upstream! do you have a URL?

@pombredanne
Copy link
Author

just saw your above ...let me check

@pombredanne
Copy link
Author

ok, this looks good:

License
Dual - MIT and GPLv3. Use whatever is appropriate in your project.

means clearly (even though it says "and") that this is a choice of MIT OR GPLv3.

I think you should clarify this in the readme as this is rather ambiguous otherwise :)

@pombredanne
Copy link
Author

@ghiscoding Thank you ++ for doing the research!
So you did not relicense anything, but just clarified the licensing documentation along the lines of @stephenliberty statements! 👍

@stephenliberty
Copy link

Hi -

Short version - the GPLv3 / MIT dual is compatible with libraries that are MIT licensed. Read in on https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses (search for MIT, it's described under the Expat License section). In the case of the packed MIT license, the name was a copy/pasta error (whoops, ten years ago now?) from the jszip library. @Stuk doesn't have anything to do with that project beyond providing a library for it.

The project was dual licensed because, at the time, there was a lot of hubub about what license type to use. I settled on dual licensing because I wanted to allow strong GPLv3 projects (ones that rejected MIT/X11/etc.. I can't remember why they did that..) to be able to use this.

Honestly, I'm beyond surprised that this little library is still being used today, but feel free to fix that license file/README/whatever with the appropriate names.

@pombredanne
Copy link
Author

@stephenliberty thank you ++ for the confirmation!

Honestly, I'm beyond surprised that this little library is still being used today, but feel free to fix that license file/README/whatever with the appropriate names.

good code dies hard 🙇

@ghiscoding
Copy link
Owner

ghiscoding commented May 1, 2022

@stephenliberty wow a confirmation from the author itself, how cool is that? 😃 For a long time I wanted to thank you for all of the hard work that you have done in creating this library, I thought that you had left GitHub scene but I'm happy to be able to thank you today after all these years. Indeed your library was the best at the time and is still quite useful and used by many.

Honestly, I'm beyond surprised that this little library is still being used today, but feel free to fix that license file/README/whatever with the appropriate names.

Since I have your blessing, I will replace in the coming days to the MIT license which is a more permissive license to use.
Thanks for all of what you've done, if you have a link for donation, I can also add it to the readme and I'll do a donation myself. 🤝

@pombredanne
Copy link
Author

@ghiscoding I am psyched and in awe that by bugging you on a mundane license issue we have such a great outcome and so quickly 🙇 ... you both rock!

@stephenliberty
Copy link

stephenliberty commented May 1, 2022

Yeah - I think just dropping the GPLv3 portion is the right way to go. Legally, it's a a LOT easier to do that than to change to a different license or anything because you don't need to contact every other author that has ever touched anything in the codebase. And I am still around, just not working on this. The small story is that I was just getting a lot of emails from people asking for help, some nasty ones about "why did you do this when you could have done that", bots trying to break into my account, etc. It was just a lot of work to try and keep everything going and improve upon, while at the same time I was dealing with depression and other personal issues.

There are parts of me that would really enjoy picking this back up, but I've stopped programming as a 'hobby' - three kids and a farm will do that to you. Gotta have enough time in the day to pet your turkeys and geese, ya know? Hah. Glad this work has helped ya'll - feel confident in making changes as you see fit. Especially tests. Oh my word did this thing need proper tests.

Anyway, no donation - if you've got family or a good friend, just give one of them a call and see how they're doing. It's silly, but in this world it sorta feels like that's the most valuable currency of all - your time.

ghiscoding added a commit that referenced this issue May 4, 2022
- the original license was a dual license (MIT or GLPv3), we just received original author's blessing to change it to MIT only which is more permissive.
- closes issue #2
@ghiscoding
Copy link
Owner

Alright I made the following changes

  • delete previous GPLv3 License from the project
  • replace Stuart's name with Stephen's name
  • renamed the License/MIT.txt to LICENSE.md and moved it to the root of the project.

You can double-check the new LICENSE.md file and a new version v2.1.7 of excel-builder-webpacker was released with the new license.

Thanks everyone for chiming in, feel free to write back if there's problems in any of the changes.
Cheers

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants