And if you’re trying to maintain an open ecosystem, use GPL.
GreyEyedGhost@lemmy.ca 1 week ago
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.
futatorius@lemm.ee 6 days ago
nous@programming.dev 1 week ago
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.
idunnololz@lemmy.world 1 week ago
From what i understand if you wrote it you can just license the public version via GPL and license the private version what ever you want since you own it.
futatorius@lemm.ee 6 days ago
Even then. some employment contracts try to take the piss and claim ownership of anything you produce while you’re employed. Clauses like that are unenforceable in many jurisdictions, but I’ve taken the liberty of redlining them before signing the contract. That means another half-day wating for Legal to look at it, but it’s worth it for the removal of ambiguity about what I intend to do. By the way, I’ve never had an offer withdrawn for doing that.
kuberoot@discuss.tchncs.de 1 week ago
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.
idunnololz@lemmy.world 1 week ago
In my case, the repository does not allow pull requests so it’s fine.
nous@programming.dev 1 week ago
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.
bpev@lemmy.world 1 week ago
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.