"2 Things to Measure and Improve Open Source Community Sustainability"

Haven& #39;t written on @COSSMedia for a while, but this topic has been in my head for many months.

Some snippets of thoughts...(thread) https://coss.media/2-things-to-measure-and-improve-open-source-community-sustainability/">https://coss.media/2-things-...

There are plenty of metrics you can track--stars, forks, PRs/MRs, etc--but more data doesn’t necessarily mean clearer insight.

I propose two second-order metrics to track to build a sustainable OSS community:
-PRs/MRs reviewer breakdown
-Leaderboard of different interactions

Why? Because...

PRs/MRs reviewers breakdown speaks to Ownership.

Leaderboard of different community interactions speaks to Incentive.

Both are important elements that drive sustainability.

Here& #39;s an example comparison between @thekonginc & @apache_pulsar of reviewers breakdown.

Key takeaway: @sonicaghi & @subnetmarco (who created Kong) aren& #39;t doing much reviews any more; that& #39;s good thing! Pulsar, a younger project, is on its way to gaining that balance.

Here& #39;s an example comparison between @thekonginc & @apache_pulsar of 90-day interactions leaderboard.

This view helps visualize interactions frequency and who& #39;s doing what -- useful for both internal management & external community building, if you are building a COSS company.

I hope you found this thread useful.

I used #ApacheSuperset and a tutorial written by @mistercrunch to crawl & visualize this data.

Please check out the full post for my complete thinking. https://abs.twimg.com/emoji/v2/... draggable="false" alt="🙏" title="Folded hands" aria-label="Emoji: Folded hands"> https://coss.media/2-things-to-measure-and-improve-open-source-community-sustainability/">https://coss.media/2-things-...