Hi, Looking a bit deeper at one of the reports:
• Releases (from list votes/results): 3 (—) • Median days between releases: 32.5 (↗↗) • New contributors: 21 (↗↗) • Unique committers: 41 (↗↗↗) • Commits: 513 (↗↗) • Issues opened/closed: 87/54 (→/→) • PRs opened/merged: 642/521 (↗↗/↗↗↗) • Median PR time-to-merge (days): 0.6 (↗↗) • Bus factor proxy (contributors to reach 50% / 75% of commits): 3 / 7 (↘↘/↘) • Mailing list msgs (dev@): 730 (↗↗) • Unique posters (dev@): 49 (↗↗↗) • Reviewer diversity (eff.#, sampled): 5.74 (↘↘) • PR author diversity (eff.#, sampled): 8.91 (↘↘) • Unique reviewers (sampled): 20 (↗↗↗) • Unique PR authors (sampled): 20 (↗↗↗) That looks mostly good. The project is active and growing quickly, with a strong release cadence, a steady inflow of contributors, and active participation on the mailing list . One possible thing to watch for is the concentration of contributions (see bus factor and declining diversity scores), which could possibly signal an over-reliance on a small group of contributors despite overall broad activity. This could potentially suggest that they are not adding committers as frequently as needed, or perhaps there are some vendor issues, but there may be other reasons for this. I'd need to look more into the project to work that out. From that, a report could be something like: We continues to release updates regularly and is bringing in new contributors and committers. Development is active, with frequent commits and pull requests, and reviews are handled quickly. The mailing list also sees a lot of participation from a variety of community members. The podling is working to involve more people by mentoring new contributors during reviews and inviting more community members to join discussions. These steps should help increase our reviewer pool and reduce the project's dependence on a select group of individuals. And another: • Releases (from list votes/results): 0 (—) • Median days between releases: — (—) • New contributors: 2 (—) • Unique committers: 9 (↗) • Commits: 58 (↘) • Issues opened/closed: 13/16 (↘↘/↘) • PRs opened/merged: 89/59 (↘/→) • Median PR time-to-merge (days): 1.4 (↗↗) • Bus factor proxy (contributors to reach 50% / 75% of commits): 2 / 3 (→/↘↘) • Mailing list msgs (dev@): 200 (↘) • Unique posters (dev@): 3 (—) • Reviewer diversity (eff.#, sampled): 2.41 (—) • PR author diversity (eff.#, sampled): 3.53 (↘) • Unique reviewers (sampled): 4 (—) • Unique PR authors (sampled): 8 (↗) This project has a lot less activity, but again, it’s the trends that are important, not the levels. The project needs to focus on releases, and overall development activity is trending downward. Of more concern is that dev@ participation remains low and the bus factor risk is high, with most commits concentrated among a few individuals. I would guess that project activity is more on GitHub than the dev mailing list, but I would need to check that. From that, a report could be something like: We did not make a release during this period, and although development continues, overall commit and issue activity have slowed slightly. Growth in new contributors has been modest, and most work remains concentrated among a small set of committers and reviewers. Corrective actions we are considering include releasing a new version in the next quarter, improving contributor onboarding, and mentoring to broaden participation and strengthen community engagement. Kind Regards, Justin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
