| 1 |
On Sun, 2006-06-25 at 05:54 +0200, Marius Mauch wrote: |
| 2 |
> On Sat, 24 Jun 2006 22:30:31 -0500 |
| 3 |
> Lance Albertson <ramereth@g.o> wrote: |
| 4 |
> |
| 5 |
> > Donnie Berkholz wrote: |
| 6 |
> > |
| 7 |
> > > I propose that all need-to-know announcements and decisions be |
| 8 |
> > > posted to a separate, moderated (or restricted posting) |
| 9 |
> > > gentoo-dev-announce list to ensure that no developers lose track of |
| 10 |
> > > what really matters. Hopefully, this will also help to give more |
| 11 |
> > > focus to discussions on gentoo-dev because the goal will be to get |
| 12 |
> > > a real decision to send to gentoo-dev-announce. |
| 13 |
> > |
| 14 |
> > Outside if this being more centered around dev-only announcements, |
| 15 |
> > could the current -announce list suffice? I'd hate to need to |
| 16 |
> > subscribe to yet-another-announcement-list (or make our |
| 17 |
> > developers/users). Our -announce list certainly has the historical |
| 18 |
> > presence where the most of our user-base would see something. I guess |
| 19 |
> > if this isn't the case, then I don't see a problem with the new list. |
| 20 |
> |
| 21 |
> The main problem with -announce is that noone has a clue how to get |
| 22 |
> stuff posted there, similar situation as with the frontpage. |
| 23 |
> Not really convenient if you have to bug people just to get a hint who |
| 24 |
> to bribe to get stuff posted. |
| 25 |
|
| 26 |
If you need something posted somewhere, bug PR. Even if they don't have |
| 27 |
access or don't know who needs to do what, we'll find out. It's really |
| 28 |
our job to know who does this stuff, and it means we'll know for the |
| 29 |
next time someone asks. |
| 30 |
|
| 31 |
-- |
| 32 |
Chris Gianelloni |
| 33 |
Release Engineering - Strategic Lead |
| 34 |
x86 Architecture Team |
| 35 |
Games - Developer |
| 36 |
Gentoo Linux |
Archives