4 ms·
I have a side project in data management that I have worked on for years (https://www.Didgets.com https://www.Didgets.com) and it is finally reached the point w
by didgetmaster 4y ago
I have a side project in data management that I have worked on for years (https://www.Didgets.com https://www.Didgets.com) and it is finally reached the point where it is an MVP with real value. I have considered adopting an open source license for it, but there are so many to choose from (I read somewhere that there are over 100 accepted kinds of OSS licenses).
Stories like this one make me nervous about choosing the wrong one. Once you let the genie out of the bottle, there is no putting it back in. You can change the license for future versions, but some big company has the right to fork your code at that point and bury you with their superior resources.
How do you choose a good license without shooting yourself in the foot?
- demonshreder 4y agoAGPLv3 or GPLv3 is a good choice to ensure that all changes stay out in the open. Then the competition becomes who can change the code faster and reach more customers.
- didgetmaster 4y ago>Then the competition becomes who can change the code faster and reach more customers. That is not very reassuring advice for a small developer who has limited resources. By opening your source code, you have just given up any head start you might have over the competition. They now have access to every line of code you spent hours agonizing over to get it right. Now they can out market you and leverage their vast resources to steal away any of your potential customers.