In my mind, you’re either an OSS person who “goes viral” and maybe gets picked up or a large “thank you” contrib to your “buy me a coffee” bucket.. or you’re actually trying to make a product but need to “market test” on the old (but hardly ever used anymore) “shareware” concept. Free market testing and occasional PRs is not a proper path to IPO or venture capital. It’s just that you didn’t realize it when you set out, or you did and you’re “meta gaming” the lifecycle.
With a (to be invented?) license that allows pivoting, I reckon it can be the kind of thing that happens, and is a potential known to any product with that license.
I just don’t see it being popular.
- bugs that are actually free support
- feature requests for things that some company needs, but won't pay them to create
- pull requests you can't accept, need to review, etc.
(I have contributed OSS in a minor way via a few original projects. I don’t run a business. I don’t have a dog in this fight. But imo ..)
If you start an OSS project, get contributions, then the thing becomes a hit, and then when money comes knocking on the door — investors want returns as it happens — and you then suddenly realize that you wanted a business after all. Then you will run into then “no good license” issue if you still want the help of free OSS patches, workers, and OSS monicker but need to protect business interests.
One the other hand, you can start with intent of making a business from your OSS project, and give non-transferable non-commercial license grants (of a foundational subset e.g. a single node graph db) to whoever wants to see or help you with the code. This scenario is (ianal) supported by existing commercial licenses. However this -may- limit the free flow of code and love and care by non-stakeholders of your commercial endeavor. I am not sure if anyone has ever tried this.