[Practitioner Guide]: Demonstrating Value

Practitioner Guide Topic (1 - 3 words)

Demonstrating Value

Primary Metrics (2 - 4 metrics)

Why is this topic important? How will this help people improve their open source project and / or community? Who will benefit from this guide?

Are you a maintainer struggling to justify your continued time working on an OSS project? Or are you an end-user trying to determine if you should use or support a project? Or how about a business trying to map your employee's contributions to internal initiatives? These struggles are prevalent throughout the ecosystem and often boil down to ineffectively conveying the "value" and "risks" of a project.

Some relevant topics include:

Why communicating a project's value & risks is essential for project growth and long-term sustainability.
Strategies projects can adopt to better surface their value & risks.
Several unconventional methods for end-users and vendors to evaluate their contributions.
Highlight new non-code opportunities for people to get involved.

How would you like to see this guide developed?

I have the experience and time available to write the first draft

Additional Notes

This is based on a talk that @mrbobbytables gave at KubeCon: Why is this so hard? Conveying the Business Value of Open Source. That link contains the slides and video of the talk.

chaoss / wg-data-science