In the Drupal community we tend to talk about committing code to our public spaces (drupal.org, GitHub, etc.) in terms of "contributing" and "contributions", and while much of it can be seen in that altruistic light, there are actually very strong business reasons for publishing your code and/or attempting to get your code changes committed to the open source project that you are working on.
Some of the business reasons for public publishing we'll explore will include:
- The power of peer review. With enough eyes, all bugs are shallow, and with only a few eyes the stupidity knows no depths!
- Fork you! The costs associated with "hacking" both Drupal core and contrib modules and base themes.
- Take my code, please! Cost savings from committing patches.
- Professionals publish or perish. Using open source contributions as marketing and lead generation.
- Developers are people, seriously. And like most people, they like recognition. Contributing to an open source project, and having their code used by a broad community, can be inspiring and motivating in a way that client work never can. In short, open source contributions help with recruiting and retention.
- Integrating contributions into your client engagements.
This session will look at U.S. government and military documents that espouse the adoption of Drupal within the federal government and explore how Zivtech has used open source contributions as a cornerstone in growing their businesses. You will hopefully walk away convinced that open source isn’t just good, it’s good business.