On Mon, 2006-06-26 at 13:10 -0700, Donnie Berkholz wrote:
> Chris Gianelloni wrote:
> > - Create a new list ("gentoo-core-announce" ?)
> > Reading: dev-only
> > Posting: dev-only, reply-to set to gentoo-core
> > This is the reference list of things (policy, decisions and discussions
> > in progress) all developers must know about.
>
> Agree with -(core|dev)-announce.
>
> > - Keep -core and -dev, as non-required reading
>
> Agree, but with the caveat that devs must still be at least subscribed
> to -core even if they choose not to read it. This way, you could have a
> -dev-announce that also refers to something private on -core if need be.
>
> > Now, do we really need it to be -core-announce? Not really. In fact,
> > at one point we'd come up with both a -core-announce and a
> > -dev-announce, with -core-announce being for more sensitive information.
>
> I'm having a tough time thinking of sensitive information that all devs
> must know about (i.e., that would qualify for -core-announce).Same here, which was why we eventually dropped to only a single announce list in our discussions. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
