Craig Russell wrote: > For wide-reach public information we already have committ...@apache.org
I'm going to accept this as the Best Answer, combined with Bertrand's "send a URL", and will reply as such to future shouldn't-be-private mails. The should-be-public topics that inspired me to write this proposal were: - please send us your project logos - about your project joining Kibble demo projects - project, please promote ApacheCon It seems like committers@ is basically good enough for those. It may not be ideal, but it exists. It's not quite right for the follow-up to Kibble: the team wanted to contact just the projects that had signed up for the Kibble demo. We provided no very easy way to contact the PMCs publicly, because we don't require that each project designates a specific list (or lists) for that purpose. That doesn't seem right. We are making it easy to do the wrong thing (contact PMCs privately) and hard to do the right thing. I still think we should be concerned about that. It seems to me that ASF policy pretty much requires there to be a way to contact each project publicly. At the moment, there is, but it's not easily/automatically discoverable or clearly designated for the purpose. As for renaming the all-private-lists alias that doesn't sound like it's private, I still think that's a good simple obvious idea but with pretty much no support for it expressed here I will not pursue it. As for the writing of guidelines about how to mass-email politely: that no longer seems critical, as the "send a URL" method probably accomplishes most of that by itself. Thanks, everyone, for weighing in. Thanks, - Julian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
