I understand it's quite early for you now. I can assure oyu, we have looked at all the licenses you mentioned.
They all care about the business of sharing code and not the business of making money. This more of a general problem or merely lack of alternatives, is what the blog post is all about.
I understand what you're saying, but I promise that the creation of another open source license isn't the solution.
It WILL Strictly limit usage of your code, to the point that open sourcing it won't make much of a difference. You won't get the goodwill, you won't get the patches, it's just a bad idea. It makes it difficult for everyone else, and doesn't help you.
If you want something that forces people to contribute back, I'd suggest a dual-license, like you point out MySQL does with GPL/Proprietary. That way if they go GPL, they'll contribute back code, if they go Proprietary, they'll give you money. Either way, you win.
Comments
I understand it's quite early for you now. I can assure oyu, we have looked at all the licenses you mentioned. They all care about the business of sharing code and not the business of making money. This more of a general problem or merely lack of alternatives, is what the blog post is all about.
I understand what you're saying, but I promise that the creation of another open source license isn't the solution.
It WILL Strictly limit usage of your code, to the point that open sourcing it won't make much of a difference. You won't get the goodwill, you won't get the patches, it's just a bad idea. It makes it difficult for everyone else, and doesn't help you.
If you want something that forces people to contribute back, I'd suggest a dual-license, like you point out MySQL does with GPL/Proprietary. That way if they go GPL, they'll contribute back code, if they go Proprietary, they'll give you money. Either way, you win.