Open ghost opened 4 years ago
It's based off this project's starting code: https://github.com/sahat/hackathon-starter#license
They're MIT License, I suppose that means this project is also MIT?
From what I found, it's possible to fork an MIT-licensed project and re-distribute under a (A)GPL license:
MIT licensed software can be re-licensed as GPL software, and integrated with other GPL software, but not the other way around.
https://en.wikipedia.org/wiki/MIT_License
Also:
If not sure, you could send an email to the FSF licensing@fsf.org
What would I get with an (A)GPL license that wouldn't be available via MIT? Thanks for the help on this by the way.
AGPL requires that if I make a change.....even if I only run it on my own server, I still have to submit it back to you. MIT doens't require that.
On Mon, Dec 30, 2019 at 2:54 PM mayeaux notifications@github.com wrote:
What would I get with an (A)GPL license that wouldn't be available via MIT?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mayeaux/nodetube/issues/34?email_source=notifications&email_token=AAAGV5NPJWSR2LNIDK2MNILQ3J3ZRA5CNFSM4KBKOGCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH3MGRA#issuecomment-569819972, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGV5PIA364KBKFKS3XVSTQ3J3ZRANCNFSM4KBKOGCA .
-- Anthony Ettinger http://anthony.ettinger.name anthony@ettinger.name +1 (831) 406-1123
I'm happy with the MIT license that's up right now. What do you think @chovy I think it should be fine for now hey?
up to you. I like MIT because I'm not commiting myself to submitting my local changes. I had a dev get all upset with me and ban me from his repo because I added tracking code to my version. and because it was client side he said I was "publishing" it.
(A)GPL gives people the piece of mind that the project won't become proprietary 'overnight'. MIT is good for businesses and people that don't plan to give back their change to the community. (A)GPL on the other hand mostly benefits the people. I've decided for myself to always contribute only to (A)GPL-licensed projects since I only care about regular people, the masses.
@chovy:
AGPL requires that if I make a change.....even if I only run it on my own server, I still have to submit it back to you. MIT doens't require that. I like MIT because I'm not commiting myself to submitting my local changes.
sorry but this is incorrect:
The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program's users, under the GPL.Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you.
https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic
Wouldn't someone just be able to fork the project and maintain it that way if an MIT license ever monetized their software? I'll continue to look into this, right now I'm more focused on bringing some attention to the project but I'll make a decision before 1k stars for sure.
The project needs a license. Have you decided which one you're gonna pick? Hopefully AGPL v3?