4 ms·
If you want people to use it, use MIT or Apache 2.0. It sounds like you want to limit how people can use it so they can't put their own restrictions on it - whi
by version_five 3y ago
If you want people to use it, use MIT or Apache 2.0. It sounds like you want to limit how people can use it so they can't put their own restrictions on it - which would suggest a GPL license. But then people won't want to use it so it sort of defeats the purpose.
Imo GPL is good for finished products that you don't want being closed up and sold commercially, but are useful on their own. Like LaTeX or Pandoc. If that describes your project, maybe it will work.
For components that go into some bigger project, GPL is way to onerous a restriction as you're forcibly selecting the license of the finished project, so people will just not bother using your component.
- hoofhearted 3y agoAwesome! Thank you for the insight and advice. I am trying to accomplish as you described, without being greedy. Our finished project isn’t the money maker itself, and benefits the frontend community as a whole. I’m planning on following simple Laravel/Vercel strategy of revenue if the momentum keeps growing. I feel that we can build optional hosted service offerings around our own open source product, and if someone doesn’t trust us or want to use us, they can just freely host it themselves like open source should be :) The current content editors on the market seemed to have gotten a whiff of WordPress’ revenue, and started closing themselves off to their own platforms in the last few years. The end result is that it really has staggered innovation for us frontend devs, and some of the best options for building user docs for your app is to stand up and expensive siloed Wordpress instance.
- hoofhearted 3y agoCan I modify the language in the license to say “don’t do bad things” if I go with Apache 2.0 or MIT?