Source code licensing seems to be a sensitive topic, and I have my own opinions, but I'd rather just be frank and ask the group: What are the best open source licensing options to build a business on?<p>I benefit greatly from open source - standing on the shoulders of giants and all that - and I want to contribute useful tooling back to the community. I enjoy making my projects available for others to use freely. At the end of the day, I'm selfish - I care about feeding my kids, owning a house, putting my kids through school, etc., which is all very expensive.<p>I don't want to work for someone else all my life, which means starting a software business, and licensing is a key issue here.<p>How do I balance:
1. Sharing my work with the community in a way that benefits everyone
2. Ensure that I can profit off of my work (e.g. prevent Amazon et al from simply hosting my software as a SaaS offering, like they did with elasticsearch)<p>The most palatable option I see is a more restrictive license for commercial users, a more permissive license for non-commercial users. Thoughts?
Some random thoughts on a complex topic:<p>Why do you want to open source your project? Is there a business reason? There should be, even if you're an open source advocate. You could also choose to donate money you made to a project, volunteer, etc.<p>Who is going to use the open source version of you software?<p>As for the license, non-commercial always rubs me the wrong way. Whatever you do, just don't pretend that is open source. Trying to get good PR or community contributions for something that only you can profit from under the guise of open source is super sleazy. I think if you're going that route it's better to just make it freemium and not even bother releasing the source.<p>That aside, the license really depends on your strategy. Start with what you are trying to achieve, concretely, not "sharing with the community".<p>You could also consider open-core.