From: Richard Freeman <rich@thefreemanclan.net>
To: gentoo-dev@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Getting -project started
Date: Wed, 18 Jul 2007 13:50:54 -0400 [thread overview]
Message-ID: <469E52FE.3060605@thefreemanclan.net> (raw)
In-Reply-To: <pan.2007.07.18.12.23.56@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Duncan wrote:
>
> According to the bug on -project (which I was CCed to), both it and dev-
> announce have been created.
>
> New developers are announcements. The primary announcement should
> therefore go to dev-announce, x-posted to dev, with followups going to
> -project, since the followups are neither announcements nor dev-technical
> and thus don't belong on either dev-announce or dev.
>
> Similarly here, the additions-removals initial post should go on dev-
> announce (x-posted to dev, of course, as anything there should be, so
> those that choose to can read only dev), with replies sent to dev.
> Additions-removals doesn't get many replies, but last-rites mails are in
> the same category and do. Replies to last-rites are dev material.
>
> ...
>
> That's my take on it, anyway.
>
[crossposting to -project to facilitate moving this thread over]
As usual, good ideas. One thing I'd say is that just because everything
isn't 100% figured it there is no reason not to start using the new
lists. And we can all try to be patient if somebody posts to the wrong
lists while things are being worked out. I'm sure practices will evolve
as makes sense.
Let's hope this initiative works out well! If the need for moderation
is mooted I think everybody will be happy!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGnlL9G4/rWKZmVWkRAoCzAKCw+FWM05K3bE5vm25zrmtijH2cNwCgztVh
x2b59MY1CxMuOHdKWN6zBUQ=
=T45h
-----END PGP SIGNATURE-----
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4101 bytes --]
prev parent reply other threads:[~2007-07-18 17:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 7:04 [gentoo-dev] Getting -project started Petteri Räty
2007-07-17 7:13 ` Kumba
2007-07-17 7:28 ` Robin H. Johnson
2007-07-18 3:12 ` Robin H. Johnson
2007-07-18 3:28 ` Philip Webb
2007-07-18 3:59 ` Kumba
2007-07-18 11:41 ` [gentoo-dev] " Duncan
2007-07-18 17:49 ` Joe Peterson
2007-07-18 18:20 ` Richard Freeman
2007-07-18 21:51 ` Robin H. Johnson
2007-07-20 2:11 ` Ryan Hill
2007-07-20 2:15 ` lnxg33k
2007-07-20 5:17 ` Robin H. Johnson
2007-07-20 18:50 ` Duncan
2007-07-20 19:14 ` George Prowse
2007-07-20 19:20 ` lnxg33k
2007-07-20 19:29 ` Dale
[not found] ` <pan.2007.07.20.20.03.24@cox.net>
2007-07-22 19:11 ` Ryan Hill
2007-07-22 22:47 ` Duncan
2007-07-20 3:24 ` Duncan
2007-07-17 7:49 ` [gentoo-dev] " Wernfried Haas
2007-07-17 7:54 ` Petteri Räty
2007-07-17 8:08 ` Wernfried Haas
2007-07-17 7:56 ` Robin H. Johnson
2007-07-17 10:00 ` Ciaran McCreesh
2007-07-17 10:26 ` Roy Marples
2007-07-17 13:13 ` George Prowse
2007-07-17 13:44 ` Roy Marples
2007-07-17 13:50 ` Kumba
2007-07-17 17:30 ` Joe Peterson
2007-07-17 19:43 ` Roy Marples
2007-07-18 12:23 ` [gentoo-dev] " Duncan
2007-07-18 17:50 ` Richard Freeman [this message]
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=469E52FE.3060605@thefreemanclan.net \
--to=rich@thefreemanclan.net \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@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