public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo-dev-announce list
Date: Mon, 26 Jun 2006 13:10:23 -0700	[thread overview]
Message-ID: <44A03F2F.3090408@gentoo.org> (raw)
In-Reply-To: <1151349060.11622.63.camel@cgianelloni.nuvox.net>

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

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).

Thanks,
Donnie


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-06-26 20:18 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
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 [this message]
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=44A03F2F.3090408@gentoo.org \
    --to=spyderous@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