sebb wrote: > On Thu, 13 Dec 2018 at 12:20, Julian Foad <julianf...@apache.org> wrote: > > 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. > > The address is an alias which forwards to all the project private lists. > There is an equivalent alias for all the podling private lists [...]
Are you for or against proposal 1a? I'm trying to push you (or anyone) for a direct answer because I would like us to reach some closure on this. > > 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; > > However not all projects have a single dev@ list; some may not have one at > all. > This will make it trickier to create and maintain the aliases. As I wrote previously, "This would be "dev@" for Apache Subversion and probably for most projects, while any project could potentially use a public list that is separate from their dev list if they wished (although I vaguely recall recommendations to keep both kinds of discussions together for the sake of community over code)." All projects must have a public mailing list even if it not named 'dev@'. Are you for or against proposal 1b? The details can be worked out afterwards. > > Additional proposals: > > > > 2a. document some guidelines on how to mass-email dev lists without > > upsetting recipients, as have been noted elsewhere in this thread. > > +1 > > > 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; > > This currently exists (see above); but perhaps the alias could be renamed. Well, yes -- that's pretty much the basis of the entire proposal. Are you for or against proposal 2b, or do you not know if it is really needed? (It seems to me it's safest/easiest to rename/replace what exists, rather than debate removing it.) > If it is decided to have public and private aliases for the > projects/podlings, then the existing short aliases could be changed to > return a bounce message giving details of the new aliases. That sounds like a good addition to ease the transition. - Julian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
