Abusing the OSS and Community model
Many OSS projects seem to be going through a recurring cycle these days:
1. Build the core product with a small team
2. Build a community and enhance the community version of the product
3. Finally, with a long-term business model in mind, they build a commercial version
I call this the MySQL business model although I may not be strictly correct in my assumptions. However, this is basically using the community to build the basic product and add significant differentiating features to the commercial version. Strictly speaking, not a bad business model. But in my opinion, this is like gaming the community system by using it when needed but providing more goodies in the commercial product.
Dana Blankenhorn's blog about OrangeHRM paints this scenario. However, this is no different from a bunch of other product companies that are doing the same thing.
1. Build the core product with a small team
2. Build a community and enhance the community version of the product
3. Finally, with a long-term business model in mind, they build a commercial version
I call this the MySQL business model although I may not be strictly correct in my assumptions. However, this is basically using the community to build the basic product and add significant differentiating features to the commercial version. Strictly speaking, not a bad business model. But in my opinion, this is like gaming the community system by using it when needed but providing more goodies in the commercial product.
Dana Blankenhorn's blog about OrangeHRM paints this scenario. However, this is no different from a bunch of other product companies that are doing the same thing.






Comments