Seems mostly focused on using open source, rather than contributing to open source, but the general concept can be applied to contributions as well: If you need

Seems mostly focused on using open source, rather than contributing to open source, but the general concept can be applied to contributions as well: If you need to convince your supervisor to contribute code to open source, it's best to find out how this is good for the business. For example, suppose your company uses some open source component Widget and did some internal work to enhance it. Now you want to contribute that work back to the community. What does the business gain from this? If someone changes Widget and your extension is internal, then it might break. But if your extension is part of the open source repo - along with integration tests - now anyone working on Widget will make sure that it still works with the extension. It's a bit cynical, but the end result is more open source contributions.