From: Donnie Berkholz <dberkholz@gentoo.org>
To: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [Fwd: [gentoo-dev-announce] New gentoo-dev-announce list]
Date: Sat, 21 Jul 2007 00:41:42 -0700 [thread overview]
Message-ID: <46A1B8B6.5070601@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1838 bytes --]
Here's the policy I wrote for -dev-announce. As mentioned elsewhere, the
automatic copy-to-dev isn't yet working so people need to send to both
lists. Reply-To is currently forced to -dev, but that may change as per
Chris's thread "New lists and their usage."
Useful input appreciated.
Thanks,
Donnie
-------- Original Message --------
Subject: [gentoo-dev-announce] New gentoo-dev-announce list
Date: Wed, 18 Jul 2007 11:55:53 -0700
From: Donnie Berkholz <dberkholz@gentoo.org>
Reply-To: gentoo-dev@lists.gentoo.org
To: gentoo-dev-announce@gentoo.org
gentoo-dev-announce is now open. The goal of this list is to make it
easy to follow changes that may be pertinent to Gentoo contributors.
This is intended to be a LOW-TRAFFIC announce-only list of development
topics, so we hope subscribers won't feel the need to filter it away
from their Inbox.
Acceptable Types of Announcements
- Policy or process changes that affect developers.
- Infrastructure changes that affect developers.
- Tools changes that affect developers.
- Schedule changes
Unacceptable Types of Announcements
- Package removal or addition. This should go on a general -announce
list because it affects all users.
- Discussion
- Anything else not mentioned above
Some List Details
- gentoo-dev-announce is OPTIONAL for project contributors, although
highly recommended.
- In the future we may auto-subscribe new developers to this list.
They may choose to unsubscribe themselves thereafter.
- All announcements here will also be delivered to gentoo-dev. So if
you follow gentoo-dev religiously you don't need to subscribe to
gentoo-dev-announce.
- Replies on gentoo-dev-announce go to gentoo-dev. gentoo-dev-announce
is a moderated list.
Thanks,
Donnie
P.S. -- Description borrowed from fedora-devel-announce
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2007-07-21 7:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46A1B8B6.5070601@gentoo.org \
--to=dberkholz@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