| 1 |
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 |
>> Outside if this being more centered around dev-only announcements, |
| 14 |
>> could the current -announce list suffice? I'd hate to need to |
| 15 |
>> subscribe to yet-another-announcement-list (or make our |
| 16 |
>> developers/users). Our -announce list certainly has the historical |
| 17 |
>> presence where the most of our user-base would see something. I guess |
| 18 |
>> if this isn't the case, then I don't see a problem with the new list. |
| 19 |
> |
| 20 |
> The main problem with -announce is that noone has a clue how to get |
| 21 |
> stuff posted there, similar situation as with the frontpage. |
| 22 |
> Not really convenient if you have to bug people just to get a hint who |
| 23 |
> to bribe to get stuff posted. |
| 24 |
|
| 25 |
Those are issues that can be delt with. I wondered if this was one of |
| 26 |
the reasons behind the idea. If we need to work out a better process, |
| 27 |
just let us know :) I don't recall someone asking us lately about it. I |
| 28 |
don't know all the specifics, but I know we can fix it or make it work. |
| 29 |
|
| 30 |
-- |
| 31 |
Lance Albertson <ramereth@g.o> |
| 32 |
Gentoo Infrastructure | Operations Manager |
| 33 |
|
| 34 |
--- |
| 35 |
GPG Public Key: <http://www.ramereth.net/lance.asc> |
| 36 |
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 |
| 37 |
|
| 38 |
ramereth/irc.freenode.net |
Archives