3 ms·
You have to be the market leader, then the other 149 other software providers will implement it in order to take part of your market. One (costly) thing I lear
by smoyer 5y ago
You have to be the market leader, then the other 149 other software providers will implement it in order to take part of your market.
One (costly) thing I learned a couple times as an entrepreneur is that it's almost impossible for a small company to make a market but they can sometimes move a market. In the same way, you might not be able to make the standard (the fact that you refer to it as "our OSS interop protocol" is telling) but you might be able to coordinate an industry group that starts with something small and grows it to what you'd like it to be.
Warning: This takes an extraordinary amount of time (I've been part of RFCs that took 4-5 years for complex protocols).
- openthc 5y ago> "our OSS" OUR as in the Royal OUR: my team + some small but visible external contributors + some external non-visible contributors + some businesses paying to improve the model + some sending direct email PRs. I'm not sure what other word to use to describe a fledgling community that I'm part of besides "our".
- smoyer 5y agoSorry about that assumption ... I took the initial "We" in your question to be one of 150 organizations and extended that to the OSS API.