On Tuesday 22 April 2003 10:26 am, Dan Armak wrote:
> The points you and other people make in this thread are known and
> acknowledged by us. We are busily working towards a setup that solves these
> problems.

A lot of the unrest within the community and a lot of the annoyances the dev 
team has to deal with are the result of the community at large not knowing 
enough about what the dev team is doing.

Possibly they've already thought of and considered what I'm about to say, but 
I have no way of knowing. ;-)

I think making the closed dev team mailing list (only slightly) less opaque is 
the way to solve this problem, and that doing so would help out both the 
developers and the community.

Here are my ideas:

1) Recruit one or more non-developers from the community and give them 
read-only access to the closed development list. Their job is to write a 
condensed summary of what's being discussed. (perhaps like KernelTraffic)

1.1) Possibly require them to remove any names from the summary.
1.2) Possibly require them to summarize only topics, not the discussion 
content.
1.3) Possibly require them to submit their summary for review.
1.4) They could post the summary to gentoo-dev

This option, I think, would go a long way towards eliminating a lot of the 
opacity that people complain about and that causes a lot of the 
out-of-control mailing list threads. Plus it costs the developers very 
little.

2) Open the archives of the closed developer list after, say, one month.

3) And, finally, just for completeness, and not because I think it's a good 
idea: allow anyone to subscribe, but not post, to the closed developer list.

Evan

--
gentoo-dev@g.o mailing list