MIT License

Question

MIT License

weepy opened this issue 6 years ago · 20 comments

Would you consider releasing this project under MIT or similar ?

Answer 1 · 2018-11-17T09:46:14.000Z

Not at the moment, but I will considering it. If you have a use-case that requires MIT I'm certainly open to hearing it :)

Answer 2 · 2018-11-17T10:45:25.000Z

I have an iOS app that needs wav file support. Don’t want to oss it for obvious reasons :-) Don’t worry if it’s a hassle I’m sure other wave file libs out there.

…

On Sat, 17 Nov 2018 at 09:46, Adam Stark ***@***.***> wrote: Not at the moment, but I will considering it. If you have a use-case that requires MIT I'm certainly open to hearing it :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAADNFoMHxR02gUqSrE-PLCQ1UE_nHHkks5uv9rngaJpZM4YmeJc> .

Answer 3 · 2021-05-20T13:01:51.000Z

Hi @adamstark,

great library! Just wanted to check this old thread if you are still considering changing to MIT? It's not possible to use this library in any closed-source application since GPL infects the whole project.

Johannes

Answer 4 · 2022-01-06T14:21:50.000Z

Hi,

How about using LGPL v2.1 instead of GPLv3 ? it allows you to keep the project open source (and must still be open source if modified) however you can still link against it as long as it's dynamically linked and can be quite literally replaced via a copy-paste

I've linked here an TL;DR on what it does:
https://tldrlegal.com/license/gnu-lesser-general-public-license-v2.1-(lgpl-2.1)

Answer 5 · 2022-01-06T15:08:54.000Z

I think actually that's also the case with GPLv3 (you can link against if the source isn't changeD).

…

On Thu, Jan 6, 2022 at 3:22 PM Robin ***@***.***> wrote: Hi, How about using LGPL instead of GPLv3 ? it allows you to keep the source open source (and must still be open source if modified) however you can still link against it as long as it's dynamically linked and can be quite literally replaced via a copy-paste I've linked here an TL;DR on what it does: https://tldrlegal.com/license/gnu-lesser-general-public-license-v2.1-(lgpl-2.1) — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGNGWJLAEWT3L2AD6WILUUWQQRANCNFSM4GEZ4JOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 6 · 2022-01-06T15:37:37.000Z

Hi all, I have been re-considering my use of GPLv3 for a while now. This library would be top of my list for giving a more permissive licence. I'm not totally sure how it works with changing a library licence when people have already contributed to it. By default their contributions are provided under the licence of the repository, so I think i need to confirm with them first...

@mynameisjohn
@Sidelobe
@MatthieuHernandez
@Abhinav1997
@helloimmatt
@BenjaminHinchliff
@emiro85

Do you approve of moving this repository (AudioFile) and therefore your contributions to a MIT licence?

Thanks,
Adam

Answer 7 · 2022-01-06T15:41:39.000Z

If I could ask you each to comment here rather than just adding a reaction so it is a bit clearer that would be great :)

Answer 8 · 2022-01-06T15:53:28.000Z

I’m fine with it.

Answer 9 · 2022-01-06T20:21:03.000Z

I'm good with whatever you decide - thank you for the great work

Answer 10 · 2022-01-06T20:23:08.000Z

Fine for me as well.

Answer 11 · 2022-01-06T20:30:25.000Z

Absolutely fine with me switching over to MIT license 👌

Answer 12 · 2022-01-06T21:10:51.000Z

Fine with me too - thanks for checking.

Answer 13 · 2022-01-07T19:38:10.000Z

All good go for it. Thanks for checking with me as well :)

Answer 14 · 2022-01-13T16:12:20.000Z

@MatthieuHernandez - any thoughts? :)

Answer 15 · 2022-01-14T14:02:01.000Z

I'm still wondering what I'm doing here 😆 but yes I totally agree with that. Sorry for my late reply.

Answer 16 · 2022-01-14T14:48:16.000Z

Thanks @MatthieuHernandez - you are listed in the collaborator list for the repo. I wasn't totally sure how as I didn't see a commit but assumed it was a contribution somewhere or a contribution to a contribution? Either way, thanks for confirming!

Thanks to everyone else for confirming too - I'll get to this in the next few days

Adam

Answer 17 · 2022-01-14T15:23:30.000Z

@adamstark I just checked and it turns out I reviewed and approved a pull request 2 years ago.

Answer 18 · 2022-01-14T15:24:20.000Z

Yes, that sounds right - I knew it was something like that :) Thank you!

Answer 19 · 2022-01-15T17:58:32.000Z

It's done! AudioFile is now licensed under the MIT licence :)

Thanks all.

Answer 20 · 2022-01-15T18:43:11.000Z

If anyone is interested, I wrote a little about my thinking behind doing this (as well as lots of people asking me to, of course): https://twitter.com/mostlynoise/status/1482417156033814532