You point out a valid use-case. I think they fall into a couple of different categories: 1) Developers build OSS components that solve a larger business need f

You point out a valid use-case. I think they fall into a couple of different categories: 1) Developers build OSS components that solve a larger business need for the organization. The fact they could modularize it and make it generic enough for open consumption is intrinsic motivation on part of the developer. In this case the "somebody" who is paying them doesn't really care about the OSS, just that they solve the larger task. 2) People build OSS projects on their own time, while working for someone else. 3) Someone is contracted or paid to build a solution for someone. Turns out it would be great OSS, and is given away for free afterwards. The contracting party is essentially paying for the development. 4) Then theres the case you point out. Where people pay others to explicitly build OSS, which I could be wrong but I don't see that happening that often, outside of maybe Redhat or something.