Ühel kenal päeval, L, 07.01.2017 kell 14:18, kirjutas Rich Freeman: > On Sat, Jan 7, 2017 at 2:05 PM, Mart Raudsepp <l...@gentoo.org> > wrote: > > > > > > If gentoo-dev feel the need to set Reply-To in my place, then > > gentoo- > > dev-announce should do the same and not throw my mail into > > /dev/null, > > but into some regular moderation rules after setting the Reply-To > > itself then. > > > > Not all replies to gentoo-dev-announce should go to gentoo-dev. Some > belong on gentoo-project, or maybe even gentoo-nfp or some other less > common list. Hence the need to set a reply-to.
1) It is called gentoo-DEV-announce; there is gentoo-announce for the other stuff already. 2) It could keep an existing reply-to and set the default if none is set, instead of just making the mail disappear with no notice of any kind for spam reasons 3) I still haven't seen my announce mails after setting a Reply-To, so I assume there's manual moderation anyways. > Perhaps it should just be called gentoo-announce, though it is mostly > aimed at developers. Such a gentoo-announce list exists. Mostly has the GLSAs. > In the past people used to send stuff like this > to -core, but that led to a lot of over-use of -core which is private > to devs only. Now -core is only used very rarely and for the sorts > of > things it was intended for (exchanging phone numbers at conferences, > etc), so in that it was a pretty big success and it makes us more > open. Thanks for the history lesson. It is interesting you know that stuff about that this was on -core prior to -dev-announce, considering you became a developer in December 2007, while gentoo-dev-announce was created in July 2007 and the last rites have went there since then. (And I have sent last rites since early 2007 at least). Though I'm pretty sure this information about last rites to -core is wrong, but my memory fades and my old -core is archived up somewhere offline :D
