Stakeholders are the people that care about the project you are working on—the ones who make sure you have what you need to get it done. Traditionally, in open source software, the only stakeholders have been a project’s contributors and users. However, that is changing. As more and more people get paid to work on open source software, the stakeholders are not always obvious and not necessarily involved in day-to-day operations. For example, the VP of R&D at a large company might fund five developers to work on your project every year. Do you know who they are? Do you know what information they need to be able to continue to justify this annual investment? Do you know how to keep them apprised of your community’s health and any needs you might have?
Whether it’s a project you lead or a project you are invested in, it’s important to know your stakeholders and communicate regularly with them. Stormy Peters explains how to identify key project stakeholders in open source software projects and details the information you should review with them to ensure their needs (and yours) are met. You’ll leave with a proven list of things to include in your next stakeholder review.
Stormy Peters is a senior manager for community leads at Red Hat. Passionate about open source software, Stormy educates companies and communities on how open source software is changing the software industry. Previously, Stormy was vice president of developer relations at the Cloud Foundry Foundation, led developer relations at Mozilla, was executive director of the GNOME Foundation, and worked at OpenLogic, where she set up the OpenLogic Expert Community. She is a compelling speaker who engages her audiences during and after her presentations. Stormy holds a BA in computer science from Rice University.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com