Gentoo Archives: gentoo-dev

From: Robert Buchholz <rbu@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] ML changes
Date: Fri, 13 Jul 2007 00:20:29
Message-Id: 75C450B6-4E1C-4AE0-9424-8BD6B88F8AA8@gentoo.org
In Reply to: RE: [gentoo-dev] ML changes by Chrissy Fullam
1 Am 13.07.2007 um 00:43 schrieb Chrissy Fullam:
2 > The -dev mailing list would be the list for development discussion.
3 > The
4 > reason it does not replace -core is because it would still be open
5 > to be
6 > viewed by the public.
7 > Many devs have stated that they do not wish to read -dev presently
8 > due to
9 > the quantity of off topic emails, or at least those that are not
10 > productive.
11 > These devs would be able to continue to read -dev and reduce the
12 > volume of
13 > email to wade through to only those pertinent to the topic at hand.
14 > Non-devs would still subscribe and post, but those posts must first be
15 > approved by ANY developer.
16 ...
17 > The -project mailing list would be the place for the unmoderated and
18 > potentially off topic correspondence. I don't think anyone is
19 > married to the
20 > name. It also is a required list for a dev to join.
21
22 Isn't that two solutions for one problem?
23
24 Creating the -project list is a way to discuss off-topic non-technical
25 stuff on a place other than -dev. Why would we need to enforce
26 moderation
27 on the -dev list along with that?
28
29 I have to second the voices that a lot of user mails are productive.
30 I did
31 not do any stats, but I feel that most mails to -dev are currently by
32 Gentoo
33 devs anyway, so it will not seriously reduce the amount of mail in
34 total.
35
36 As far as the usually fast technical discussions are concerned, my
37 problem
38 here is that users are in practical kept out of the discussion by the
39 mere
40 delay of their mails. We might experience double replies, users writing
41 replies which get dumped -- because someone else already wrote the
42 same mail 30 minutes ago and it did not get approved until he wrote
43 his mail.
44 If you ever spent 30 minutes figuring out a problem in Mac OS X and
45 filing
46 a decent bug report on their bug tracker just to find out it gets DUPed,
47 but you could not know before because the search is not public, you know
48 what I am talking about.
49
50 My imagination of this would be:
51 Create the project list for open discussion and restrict the
52 *topic* range, not the *participant* range of this list.
53 We can evaluate whether the SNR did improve enough after some time.
54
55 Regards,
56
57 Robert
58
59 --
60 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] ML changes Ned Ludd <solar@g.o>