From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo-dev-announce list
Date: Sun, 25 Jun 2006 05:54:03 +0200 [thread overview]
Message-ID: <20060625055403.108e746e@sven.genone.homeip.net> (raw)
In-Reply-To: <449E0357.8060705@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On Sat, 24 Jun 2006 22:30:31 -0500
Lance Albertson <ramereth@gentoo.org> wrote:
> Donnie Berkholz wrote:
>
> > I propose that all need-to-know announcements and decisions be
> > posted to a separate, moderated (or restricted posting)
> > gentoo-dev-announce list to ensure that no developers lose track of
> > what really matters. Hopefully, this will also help to give more
> > focus to discussions on gentoo-dev because the goal will be to get
> > a real decision to send to gentoo-dev-announce.
>
> Outside if this being more centered around dev-only announcements,
> could the current -announce list suffice? I'd hate to need to
> subscribe to yet-another-announcement-list (or make our
> developers/users). Our -announce list certainly has the historical
> presence where the most of our user-base would see something. I guess
> if this isn't the case, then I don't see a problem with the new list.
The main problem with -announce is that noone has a clue how to get
stuff posted there, similar situation as with the frontpage.
Not really convenient if you have to bug people just to get a hint who
to bribe to get stuff posted.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-25 3:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 3:06 [gentoo-dev] gentoo-dev-announce list Donnie Berkholz
2006-06-25 3:30 ` Lance Albertson
2006-06-25 3:54 ` Marius Mauch [this message]
2006-06-25 4:01 ` Lance Albertson
2006-06-26 18:47 ` Chris Gianelloni
2006-06-25 5:35 ` Donnie Berkholz
2006-06-25 3:32 ` Ned Ludd
2006-06-25 5:38 ` Donnie Berkholz
2006-06-26 19:10 ` Chris Gianelloni
2006-06-26 20:10 ` Donnie Berkholz
2006-06-26 23:36 ` Lance Albertson
2006-06-27 11:29 ` Simon Stelling
2006-06-28 1:56 ` Ned Ludd
2006-06-27 11:57 ` Chris Gianelloni
[not found] ` <20060625190022.GE13449@elladan.wh-og.hs-niederrhein.de>
2006-06-25 22:18 ` Donnie Berkholz
2006-06-27 7:32 ` Stuart Herbert
2006-06-27 11:20 ` Enrico Weigelt
2006-06-27 11:29 ` Stuart Herbert
2006-06-27 11:24 ` Simon Stelling
2006-06-27 11:32 ` Stuart Herbert
2006-06-27 16:16 ` Donnie Berkholz
2006-07-01 18:00 ` [gentoo-dev] " Ryan Hill
2006-07-01 20:01 ` Donnie Berkholz
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:09 [gentoo-dev] " Donnie Berkholz
2007-06-21 21:16 ` Mike Doty
2007-06-21 21:33 ` Jim Ramsay
2007-06-21 21:37 ` Mike Doty
2007-06-21 21:55 ` Jim Ramsay
2007-06-21 22:10 ` Chris Gianelloni
2007-06-21 21:38 ` Joe Peterson
2007-06-22 1:34 ` Kumba
2007-06-22 2:06 ` Seemant Kulleen
2007-06-22 9:24 ` Thomas Raschbacher (Gentoo)
2007-06-22 3:02 ` Daniel Ostrow
2007-06-22 10:59 ` Ferris McCormick
2007-06-22 11:26 ` Wernfried Haas
2007-06-23 8:12 ` Alec Warner
2007-06-24 12:46 ` Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060625055403.108e746e@sven.genone.homeip.net \
--to=genone@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox