Proprietary Projects That Benefitted From Becoming Open?

redmoss asks: "The company I work for has a server-based system that we use for a wide variety of tasks: checking in customers, maintaining customer information, etc. We have had the programmer of this system working with us many years to bring it to its current level. I have approached him about open-sourcing/GPL'ing his system; he agrees with the idea in principle, but is not convinced that it would benefit him. He asked me to provide examples where opening a proprietary system has benefitted the programmer/owner. Perhaps some of you know of such cases and can point me to examples?" It should be noted that benefits from moving a project into the open may not be measured entirely in monetary units. Sometimes increased reliability of a service is worth more than an extra $1000 in sales at the end of the quarter. So can anyone out there name projects that have benefitted by opening up their source?

Comments

It very well depends on the stage of the product

[bonzoesc]

If the product is in an early stages of development, but still has enough features and codebase already present, it will benefit from Open Source. Linux was in the early stage of development when Linus released it for comments and additions, and look now.

On the other hand, if it is already at the end of it's functional lifetime, like StarOffice, releasing it publicly will probably result in its' cannibalization (sp?) and it will not evolve as quickly as competing products.

For the most part, if the product has few competitors, especially open-source competitors, it will do well as Open Souce. If a better Open Source app is already available, your product will not change much by Open-Sourcing it, unless it's far better than the alternative.

Tell me what makes you so afraid
Of all those people you say you hate