Gentoo Archives: gentoo-dev

From: Svyatogor <svyatogor@g.o>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] Email Overload; Make summaries and bugs for test requests
Date: Wed, 27 Aug 2003 09:19:06
Message-Id: 20030827124042.275ba6ef.svyatogor@gentoo.org
In Reply to: [gentoo-dev] Email Overload; Make summaries and bugs for test requests by Jason Wever
1 Why do I have a feeling this is another "great proposal" which everyone
2 agreed with but didn't bother to go further and suggest it's
3 implementation? Can someone update me on the status? Probably a GLEP is
4 required, then I could right it.
5
6 On Mon, 18 Aug 2003 16:24:36 -0400
7 Jason Wever <weeve@g.o> wrote:
8
9 > Hi All,
10 >
11 > Since our -dev mailing list is now receiving an enormous amount of
12 > traffic each day, I'd like to suggest bringing/bring back up the
13 > summaries idea previously mentioned a few months ago. Due to the fact
14 > that we all have limited time to work on Gentoo, and we can't spend
15 > all of it reading the 50+ emails on -dev every day (not to mention
16 > other list(s) we may be on).. So please, if a thread ends up resulting
17 > in something devs need to read(i.e. policy changes), please make a
18 > summary email.
19 >
20 > Also, for sparc, if you want us to test something, it is *HIGHLY
21 > SUGGESTED* that you make a bug for it and CC the sparc team on it
22 > <sparc@g.o>. As I've mentioned in the above paragraph about
23 > email overload, it's easy for your test request to get lost in the
24 > shuffle(especially if it's at the top of the 50+ emails to read).
25 > This will guarantee the best response from the team. If you want to
26 > do whatever with your ebuild(s) in the test request by a certain date,
27 > please indicate that in the bug.
28 >
29 > Thanks,
30 > --
31 > Jason Wever
32 > Gentoo/Sparc Team Lead
33 >
34
35
36 --
37 Let the Force be with us!
38 Sergey Kuleshov <svyatogor@g.o>
39 Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg