[gentoo-dev] Email Overload; Make summaries and bugs for test requests

[gentoo-dev] Email Overload; Make summaries and bugs for test requests

[Jason Wever]

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hi All,

Since our -dev mailing list is now receiving an enormous amount of
traffic each day, I'd like to suggest bringing/bring back up the summaries
idea previously mentioned a few months ago.  Due to the fact that we all
have limited time to work on Gentoo, and we can't spend all of it reading
the 50+ emails on -dev every day (not to mention other list(s) we may be
on).. So please, if a thread ends up resulting in something devs need to
read(i.e. policy changes), please make a summary email.

Also, for sparc, if you want us to test something, it is *HIGHLY
SUGGESTED* that you make a bug for it and CC the sparc team on it
<sparc@gentoo.org>. As I've mentioned in the above paragraph about email
overload, it's easy for your test request to get lost in the shuffle
(especially if it's at the top of the 50+ emails to read).  This will
guarantee the best response from the team.  If you want to do whatever
with your ebuild(s) in the test request by a certain date, please indicate
that in the bug.  

Thanks,
-- 
Jason Wever
Gentoo/Sparc Team Lead

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Email Overload; Make summaries and bugs for test requests

[Svyatogor]

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

Great idea! Often (espesially after a few days of inactivity) I don't
have time to read all the threads and just delete the ones I'm not
particularly interested in. However, you never know what a certain
discussion might end up with. So I'd love to have a summary for those
threads which actualy do end up with some decision.

On Mon, 18 Aug 2003 16:24:36 -0400
Jason Wever <weeve@gentoo.org> wrote:

> Hi All,
> 
> Since our -dev mailing list is now receiving an enormous amount of
> traffic each day, I'd like to suggest bringing/bring back up the
> summaries idea previously mentioned a few months ago.  Due to the fact
> that we all have limited time to work on Gentoo, and we can't spend
> all of it reading the 50+ emails on -dev every day (not to mention
> other list(s) we may be on).. So please, if a thread ends up resulting
> in something devs need to read(i.e. policy changes), please make a
> summary email.
> 
> Also, for sparc, if you want us to test something, it is *HIGHLY
> SUGGESTED* that you make a bug for it and CC the sparc team on it
> <sparc@gentoo.org>. As I've mentioned in the above paragraph about
> email overload, it's easy for your test request to get lost in the
> shuffle(especially if it's at the top of the 50+ emails to read). 
> This will guarantee the best response from the team.  If you want to
> do whatever with your ebuild(s) in the test request by a certain date,
> please indicate that in the bug.  
> 
> Thanks,
> -- 
> Jason Wever
> Gentoo/Sparc Team Lead
> 


-- 
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Email Overload; Make summaries and bugs for test requests

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

On Tue, 2003-08-19 at 04:03, Svyatogor wrote:
> Great idea! Often (espesially after a few days of inactivity) I don't
> have time to read all the threads and just delete the ones I'm not
> particularly interested in. However, you never know what a certain
> discussion might end up with. So I'd love to have a summary for those
> threads which actualy do end up with some decision.

Definitely a great idea.  May I propose that we start the subjects with
SUMMARY: then th rest of the thread subject, so we can easily pick them
out from the mess.

-- 
Chris Gianelloni
Developer, Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Email Overload; Make summaries and bugs for test requests

[Svyatogor]

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

Why do I have a feeling this is another "great proposal" which everyone
agreed with but didn't bother to go further and suggest it's
implementation? Can someone update me on the status? Probably a GLEP is
required, then I could right it.

On Mon, 18 Aug 2003 16:24:36 -0400
Jason Wever <weeve@gentoo.org> wrote:

> Hi All,
> 
> Since our -dev mailing list is now receiving an enormous amount of
> traffic each day, I'd like to suggest bringing/bring back up the
> summaries idea previously mentioned a few months ago.  Due to the fact
> that we all have limited time to work on Gentoo, and we can't spend
> all of it reading the 50+ emails on -dev every day (not to mention
> other list(s) we may be on).. So please, if a thread ends up resulting
> in something devs need to read(i.e. policy changes), please make a
> summary email.
> 
> Also, for sparc, if you want us to test something, it is *HIGHLY
> SUGGESTED* that you make a bug for it and CC the sparc team on it
> <sparc@gentoo.org>. As I've mentioned in the above paragraph about
> email overload, it's easy for your test request to get lost in the
> shuffle(especially if it's at the top of the 50+ emails to read). 
> This will guarantee the best response from the team.  If you want to
> do whatever with your ebuild(s) in the test request by a certain date,
> please indicate that in the bug.  
> 
> Thanks,
> -- 
> Jason Wever
> Gentoo/Sparc Team Lead
> 


-- 
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]