Re: J-C oversight

[Sam Ruby <ru...@apache.org>]

Greg Stein wrote:
> 
> The information overload is very well characterized by a reference
> somebody made recently to a Jakarta report to the board. See Attachment D
> in the March minutes:
> 
>     http://www.apache.org/foundation/records/minutes/2003/board_minutes_2003_03_19.txt
> 
> The most recent report defers much of the report to the Jakarta
> newsletter. It doesn't summarize the state for the Board, and it doesn't
> provide any insight into community issues, interactions, legal issues, or
> forward thoughts of the PMC. We have this *massive* amount of code and a
> *huge* community, and the PMC is not able to effectively report on what is
> happening.
> 
> Is it just me? Maybe. But as a Director, I'm supposed to be able to review
> this stuff and know whether Jakarta is going well/poorly. I have never
> felt that I have enough information to really know that. And the scary
> part is that I'm one of the more informed Directors -- I'm subscribed to
> the Jakarta PMC list (along with one or two other Directors). The rest?
> Scrappy info.

If I recall correctly, this report was approved as submitted.  You 
certainly could have raised issues at the time, but instead it was 
accepted by unamimous consent... only to be brought up later as an issue 
on the general@commons mailing list.

I personally think that having the information online, continuously 
updated, and available for review to all is a good thing.

One way or another, the root issue is information overload.  One could 
certainly immagine a four paragraph update for each row in the following:

http://gump.covalent.net/log/xref.html

- Sam Ruby