> On Jul 13, 2026, at 6:12 AM, Bowen, Rich <[email protected]> wrote:
>
>
>
>> On Jul 13, 2026, at 8:56 AM, Dave Fisher <[email protected]> wrote:
>>
>> 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?
>
> I assume you mean adding PMC growth and committer growth separately? Yeah,
> that would probably make more sense. But getting the new committer data has
> always been a bit tricksy, since the only data that I can reliably find is
> icla dates, which is *often* the same thing, but not always. Is that data
> that I can get via an API call somewhere that I don’t know about?
Yes, it is a tricky bit of code in the reporter. There is an ldap pubsub feed
that needs to be processed. You have to notice the change in the PMC’s
committer list. You could ask Infra about how to use that and what credentials
you would need.
> Related to that, I run reports for a couple of dozen projects that I care
> about $WorkHat, which calculates who is likely to be the *next* committer, if
> the project is paying attention. I’d like to provide that report, somehow, to
> PMCs, but it’s potentially sensitive, in much the say way that new committer
> votes can be sensitive. I’d need to figure out how to auth that to only
> members of those PMCs. That’s on my To Do list.
You can send from an @apache.org address to private@pmc. Or you can make your
site an asfquart app, use MFA, and you will get project/pmc auth as part of the
framework. You could look into the recent CAP work by Infra as an example.
>
>>
>> 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.
>
> I went pawing through the complete svn log for dist.apache.org (`svn log
> https://dist.apache.org/repos/dist/release/`
> <https://dist.apache.org/repos/dist/release/%60>) this weekend, and I think
> that might be another way to get this data, but having a simpler source of
> that info available via an API call would be fantastic.
We’ve done that too, it’s hit or miss. For ATR we started watching changes to
pick up non-ATR releases, changes to KEYS files, and release archival. In
addition to an api we’ve started a mailing list that will begin to have all
releases - [email protected] - it only has ATR ones at the moment.
Best,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
