38
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jan 2026
38 points (93.2% liked)
Open Source
44676 readers
348 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
How about LGPL
It does not promote freedom as much as gpl.
You can always publish your code under gpl now and add a note that you are open to relicense your work. You can then later add the L to gpl or switch to MIT if you want to.
You can not switch from MIT to GPL.
My first packages were gpl. Then I got to know MIT and thought, wow, that is real freedom! Following that, I published my code under MIT until someone told me that gpl promotes freedom. If a project uses MIT, i may contribute but I won't be the main author.
MIT is much better than proprietary. sometimes MIT is much more favorable than gpl. E.g. If you are a company and want to collaborate with others, you release your base code under MIT and anyone can just not release their additional contribution but everyone contributes to the base code.