| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Duncan wrote: |
| 5 |
> |
| 6 |
> According to the bug on -project (which I was CCed to), both it and dev- |
| 7 |
> announce have been created. |
| 8 |
> |
| 9 |
> New developers are announcements. The primary announcement should |
| 10 |
> therefore go to dev-announce, x-posted to dev, with followups going to |
| 11 |
> -project, since the followups are neither announcements nor dev-technical |
| 12 |
> and thus don't belong on either dev-announce or dev. |
| 13 |
> |
| 14 |
> Similarly here, the additions-removals initial post should go on dev- |
| 15 |
> announce (x-posted to dev, of course, as anything there should be, so |
| 16 |
> those that choose to can read only dev), with replies sent to dev. |
| 17 |
> Additions-removals doesn't get many replies, but last-rites mails are in |
| 18 |
> the same category and do. Replies to last-rites are dev material. |
| 19 |
> |
| 20 |
> ... |
| 21 |
> |
| 22 |
> That's my take on it, anyway. |
| 23 |
> |
| 24 |
|
| 25 |
[crossposting to -project to facilitate moving this thread over] |
| 26 |
|
| 27 |
As usual, good ideas. One thing I'd say is that just because everything |
| 28 |
isn't 100% figured it there is no reason not to start using the new |
| 29 |
lists. And we can all try to be patient if somebody posts to the wrong |
| 30 |
lists while things are being worked out. I'm sure practices will evolve |
| 31 |
as makes sense. |
| 32 |
|
| 33 |
Let's hope this initiative works out well! If the need for moderation |
| 34 |
is mooted I think everybody will be happy! |
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 37 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 38 |
|
| 39 |
iD8DBQFGnlL9G4/rWKZmVWkRAoCzAKCw+FWM05K3bE5vm25zrmtijH2cNwCgztVh |
| 40 |
x2b59MY1CxMuOHdKWN6zBUQ= |
| 41 |
=T45h |
| 42 |
-----END PGP SIGNATURE----- |
Archives