community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <>
Subject Re: [reporter] Confusing PMC/Committeer/Committee/LDAP report format
Date Wed, 21 Oct 2015 12:27:02 GMT
On Wed, Oct 21, 2015 at 7:52 AM, Mike Kienenberger <> wrote:
> Rich already made it clear what would be the best improvement and gave
> a specific example, but I'll put it in generic terms.
> Show the current count of the PMC members and committers.
> Show the last PMC addition and date.
> Show the last committer addition and date.
> That's also all I'm looking for as PMC Chair of MyFaces.   I don't
> need this report to tell me if the info came from LDAP or
> committee-info as they should always be the same.  If they are out of
> sync, then you can add section with the details for identifying and
> fixing that if you think that's important, but that's not the point of
> the reporter tool.   The point of the report also isn't to tell the
> board the exact day someone was added, it is to give the board an idea
> how often the community is growing.  Let's not worry about making the
> board report template so accurate and precise and in-depth that it
> stops being useful due to too much information.
> I ended up going through and rewriting the membership section for the
> MyFaces October report by hand, defeating the point of using the
> reporter tool to write the boilerplate section for me.


I'd suggest that the reporter tool and Whimsy roster tool provide
pointers to each other, where the latter focuses on the differences.
I'm working slowly on making the roster tool read/write so that it can
be used instead of the Perl scripts and editing committee-info.txt
directly.  The idea is that adding an existing committer to the PMC
should be a matter of a few mouse clicks.

Examples (currently read-only):

- Sam Ruby

View raw message