HI Rich, This is cool. Some thoughts.
1) On the Community Growth Tab new PMCs dominate the list. Would it make sense to have two lists? 2) Tooling is working on a catalog feature for the ATR Beta. In a few months we can likely hook you up with better data. I’ll note that if you are using the zzz/find file then you are using a method that mostly counts release artifacts where many PMC’s projects like Airflow Providers and OpenOffice release dozens or hundreds of artifacts in a single release. It might be interesting to count only source and binary convenience separately. Best, Dave > On Jul 13, 2026, at 4:17 AM, Brian Proffitt <[email protected]> wrote: > > This looks really sharp, Rich. Please let me know if you need any help > with this project, since metrics is still part of $dayjob. > > Peace, > BKP > > Brian Proffitt > VP, Marketing & Publicity > VP, Conferences > > On Sun, Jul 12, 2026 at 1:05 PM Rich Bowen <[email protected]> wrote: >> >> Hi, folks, >> >> One of the pillars of community health is the ability to *measure* it, in >> some meaningful way. As a director, as well as a PMC member, or a potential >> contributor, I always wanted some kind of high-level dashboard to see how a >> project is doing. Are the lists active? Are there more than a handful of >> people participating in the discussion? In the code? >> >> For a while we had the Kibble dashboards. (I wonder if Kibble would do >> better in this AI-coding era than it did under the previous reality, but I >> guess that is a discussion for another time.) And I miss having that little >> bit of insight. >> >> This weekend I put together this - >> https://boxofclue.com/comdev-metrics/index.html - which does very high-level >> metrics around several data sources: >> >> * Git/SVN - is the project producing code? >> * Mailing lists - is the community talking to each other? >> * Community growth - Is the project adding members? >> * Releases - Is the project releasing software? >> >> This is primarily for myself, but if anyone thinks that this would be a >> service to our larger community, and fall under our mandate as the Community >> Development PMC, I’d be delighted to shove it into a ComDev repo. The code >> is here - https://github.com/rbowen/comdev-metrics >> >> The basics are documented in README.md, and what I want to do next is in >> PLAN.md. DATA_SOURCES.md describes where the data is coming from. >> >> It’s Python. It runs once a week, and takes a little over an hour, and about >> 6000 Github API calls, for the initial run, but subsequent runs only fetch >> the most recent activity, and use caches for everything else. It generates >> HTML/JSON/Javascript, so the result is static files that can be published to >> any web server. We could put them on projects.apache.org/metrics >> <http://projects.apache.org/metrics> for example, if that seems useful. >> >> Feedback welcome. Do we want to provide this as a ComDev service? What >> additional metrics would be useful to you, as a PMC member or a Director? >> Would projects find this helpful in their quarterly reporting? >> >> —Rich >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
