On 14/12/2018 21:15, Craig Russell wrote: > Hi Julian, > > I've read this thread and I'm afraid I don't understand the problem you're > trying to solve. > > For wide-reach public information we already have committ...@apache.org > > For wide-reach private information we already have memb...@apache.org > > For wide-reach private information that will reach pmc members who are not > foundation members, while not spamming apache foundation members who are not > members of any pmc, we have the existing pmcs@ alias. > > Perhaps it would help me if you give an example of a communication that would > require a different recipient list. I'm really stumped. > > The specific example that spawned this thread (from a different thread) was a > request for hi-res logos. Would committers@ not work for this?
Not really. We try to keep committers@ limited to mail we expect every committer to need to read. While the pmcs alias isn't perfect, I'm of the view that we need to send mails like the logos mail rarely enough that the pmcs alias is good enough. Mark > > Craig > >> On Dec 13, 2018, at 4:20 AM, Julian Foad <julianf...@apache.org> wrote: >> >> Bertrand Delacretaz wrote: >>> I read the quoted text but don't understand exactly what it is that >>> you are suggesting, an example would probably help. >> >> Example -- the one that started this thread: >> * somebody wants to ask every project for its best project logo (a public >> matter); >> * they write "Dear PMCs ..." to all projects' *private* mailing lists. >> >> Problem and assumptions: >> * the request really ought to go to the project communities; >> * the initiator (I'm guessing / generalizing) thinks the PMCs are >> appropriate representatives of their communities AND knows an easy way to >> email all the PMCs AND possibly has a fear of addressing a wider audience >> than PMC members; >> * the request goes to the private lists, more or less by accident as result >> of the foregoing, especially as a result of one particular obvious-looking >> address*; >> * the initiator may not even realize that's where their message went. >> >> Solution: >> * make it more difficult to email all projects' private lists and easier to >> email all projects' public lists; >> * despite some people's reservations, contacting dev lists does seem to be >> the consensus; see 2b below; >> * make it more clear what any obvious-looking address* is actually for. >> >> PRIMARY PROPOSAL: >> >> 1a. drop the existing four-letter obvious-looking address* >> - because its name is misleading which (I think) leads people to mis-use it. >> >> 1b. create an easier way to email all the projects about a public matter >> - introduce an obvious-looking address* that contains '-public', that goes >> to all dev lists; more details in my earlier mail; >> >> Additional proposals: >> >> 2a. document some guidelines on how to mass-email dev lists without >> upsetting recipients, as have been noted elsewhere in this thread. >> >> 2b. add a way to contact all PMCs about a private matter, >> - perhaps an obvious-looking address* that contains '-private' >> - ONLY if needed: this might be sufficiently rare as to not be needed; >> >> (* By request, to try to reduce spam, I'm deliberately obfuscating the >> "obvious-looking address". I'm sorry that that makes it harder to follow. >> See start of thread for plain disclosure.) >> >> -- >> - Julian >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> > > Craig L Russell > Secretary, Apache Software Foundation > c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo > <http://db.apache.org/jdo> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
