this post was submitted on 25 May 2025
96 points (96.2% liked)
Technology
70365 readers
3880 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you want to put an idea out there, permissive licenses are the most likely to promote it. Any individual or organization can use it without restrictions (or restrictions that aren't unpalatable to most). So if what you're trying to promote is an idea, a technique, or a standard, this type of license allows it to have the greatest reach.
People seem to forget that most of the open source language library code out there is written by people working for companies, being sponsored by companies or writing it so they can use it where they work. Some might start out as hobbiest projects but if it survives and grows it eventually will be sponsored in some form. Even if indirectly by some guy that wants to use it where he works.
From what i understand if you wrote it you can just license the public version via GPL and license the private version that you wrote for your job what ever you want since you own it.
This assumes you wrote the project without company tools and on your free time.
If you license your project under GPL, and somebody submits some code (like through a pull request) that ends up in the library you use, you are now also bound by the GPL license, meaning you also have to publish the source of any derivatives.
The way to avoid it is to use something like a CLA, requiring every contributor to sign an agreement giving you special rights to their code, so you can ignore the GPL license in relation to the code they wrote. This works, but is obviously exploitative, taking rights to contributions while giving out less.
It also means if somebody forks the project, you can't pull in their changes (if you can't meet GPL terms, of course), unlike with MIT, where by default everybody can make their own versions, public or private, for any purpose.
Though it's worth noting, if you license your code under MIT, a fork can still add the GPL license on top, which means if you wanted to pull in their changes you'd be bound to both licenses and thus GPL terms. I believe this is also by design in the GPL license, to give open-source an edge, though that can be a bit of a dick move when done to a good project, since it lets the GPL fork pull in changes from MIT versions without giving back to them.
In my case, the repository does not allow pull requests so it's fine.
The company you work for will likely not like that. Needs a special case license to be drawn up would probably need to involve lawyers and cost far more then is worth the hassle. Vastly easier just to give it a MIT license.
You can always use your own code however you want. However, if your project starts to get contributions from other people, that's where it can start to become more muddy.