OT Free Software 3424

I work for a company that uses free software extensively to support internal systems.

We produce some free software because we really needed it for our own purposes. Releasing it more widely has already had several useful effects:

1. Others have provided some testing buttistance, as different "use cases" have tortured parts of the software that we wouldn't have, thereby making it more reliable, even for us.

2. Others have added features. Some of dubious value to us, others that were interesting.

3. The "goodwill" effects are quite valuable. Since we're clearly contributing to a relevant community, that community takes our needs quite seriously.

And that doesn't touch on other things...

4. An alternative would have been to buy something with a proprietary license. But that would either force us into one of three scenarios:

a) Buying a VERY EXPENSIVE product from "Brand O" b) Buying a QUITE EXPENSIVE product from "Brand I" c) Buying some really risky product from someone else that nobody has ever heard of. {aside: Brands "O" and "I" are the first letters of names of software companies that you have doubtless heard of...}

Those options would involve either paying a pile of money in licensing fees, or paying out a smaller pile, and living in fear of changes in the vendor's prospects.

5. We're not in the business of selling software. We have no sales people with skill in that. We have no processes in place for managing sales of licenses.

Selling software licenses is a remarkably challenging business that isn't a "core competency" for other than a relative handful of firms.

It may be that no one of these considerations would be sufficient to justify sponsoring free software projects. But as the reasons mount up, the value does leap out. -- Despite the high cost of living, it remains very popular.