| 1 |
Donnie Berkholz wrote: |
| 2 |
|
| 3 |
> Agree, but with the caveat that devs must still be at least subscribed |
| 4 |
> to -core even if they choose not to read it. This way, you could have a |
| 5 |
> -dev-announce that also refers to something private on -core if need be. |
| 6 |
> |
| 7 |
>> Now, do we really need it to be -core-announce? Not really. In fact, |
| 8 |
>> at one point we'd come up with both a -core-announce and a |
| 9 |
>> -dev-announce, with -core-announce being for more sensitive information. |
| 10 |
> |
| 11 |
> I'm having a tough time thinking of sensitive information that all devs |
| 12 |
> must know about (i.e., that would qualify for -core-announce). |
| 13 |
|
| 14 |
I'd rather not create a -core-announce. The amount of times those types |
| 15 |
of things come up on the list are rare. It would be easier to have an |
| 16 |
standard subject heading (maybe ANNOUNCEMENT:) that people can use in |
| 17 |
their filters. If devs start abusing it, then we'll vote them off the |
| 18 |
island :) |
| 19 |
|
| 20 |
-- |
| 21 |
Lance Albertson <ramereth@g.o> |
| 22 |
Gentoo Infrastructure | Operations Manager |
| 23 |
|
| 24 |
--- |
| 25 |
GPG Public Key: <http://www.ramereth.net/lance.asc> |
| 26 |
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 |
| 27 |
|
| 28 |
ramereth/irc.freenode.net |
Archives