Actually, the tools of the ASF are taking care of that. And that needs to be planned.
And I understand why we have to tread carefully, as it is one way to state something as the Apache Way and talking about facilitating open source projects and holding them up it. While I do accept and understand the various viewpoints about projects independence, it is the ASF that provides the tools and umbrella that protects these. The ASF getting something in return (e.g. a few mails from the ASF to its contributors in its projects) from the projects is also reasonable, understandable and acceptable when GRC is in place. And yes, effectiveness should be measured each time. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Apr 20, 2015 at 9:46 PM, Rich Bowen <[email protected]> wrote: > > > On 04/20/2015 10:44 AM, Pierre Smits wrote: > >> Hi All, >> >> Up to now, we have relied on a few contributors to communicate the >> messages >> regarding ApacheCon and on the trickle-down approach via the private ML of >> our projects. Shouldn't we be reaching out directly (and systematically) >> to >> all our contributors by mailing directly to the user and dev MLs of our >> project? We thereby reach a greater audience with thus potentially >> achieving a bigger success. >> > > Who is "we" in this paragraph? > > I have taken the approach of passing the message to the PMCs, and > delegating to them whether they care enough to promote the message. I don't > personally want to take on the task of mailing 200+ dev@ lists, and 200+ > users@ lists, but if you wish to do that, I don't think we'll say no. > However, tread carefully, since we historically take a dim view of what > might be perceived as spam, if it were sent out to all of those lists in > one go. > > If you know of an effective way to reach everyone in our extended > community, I'd love to hear it. > > > -- > Rich Bowen - [email protected] - @rbowen > http://apachecon.com/ - @apachecon >
