Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E81E55E.40001@shanecurcuru.org>
Date: Tue, 27 Sep 2011 11:01:50 -0400
From: Shane Curcuru <asf@shanecurcuru.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Press requests
References: 
 <CAP-ksoi+4y59EKAYYzOKy8054B-j+VBqMtHKdRw2Oj241+AUBA@mail.gmail.com>
 <4E7D38AB.9090207@shanecurcuru.org>
 <CAMDRyTd8xq8-22i+nDyc2rjr1_VewZe8WYVKsAsHCSNN76s7Ag@mail.gmail.com>
In-Reply-To: 
 <CAMDRyTd8xq8-22i+nDyc2rjr1_VewZe8WYVKsAsHCSNN76s7Ag@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 9/27/2011 7:12 AM, Donald Harbison wrote:
> Thanks Shane.
>
> To be clear, Apache policy on podling branding[1] states:
>
> "*Podling has been approved for incubation, podling has launched public
> mailing lists, and podling has dropped code into repository*: A podling*MUST
> * now be called *Apache "Podling-Name"* (see
> Naming<http://incubator.apache.org/guides/branding.html#Naming>
> below).
> A podling and affiliated persons can issue press releases that reference the
> podling, but cannot issue press releases with the specific intent of
> announcing the Podling. Podling can conduct informal pr activities, such as
> media outreach, blog publicity, etc. The ASF will not issue any press
> releases for any podling at this stage. However, the Public Relations
> Committee *MUST* review any releases by affiliated organizations or groups
> to ensure they comply with these branding guidelines."
>
> So there is no requirement to run our blogs or media outreach efforts
> through Apache press office before posting, correct?

Correct - now that infra has created a blogs.a.o for the podling, you're 
free to use that directly to communicate to the larger world as the 
podling sees fit.  Indeed, I agree we need a committed group of 
volunteers to push content to that blog more regularly, so we can better 
tell our own story (instead of having others tell it).

The issue with coordinating with press@ is partly about any official 
"press releases" (i.e. on newswires) and mostly any coordination or 
responses with journalists or third party major technology blogs.

- Shane
>
> The statement about press releases by affiliated organizations is clear
> enough.
> *
> *
> /don
>
> [1] http://incubator.apache.org/guides/branding.html
>
> On Fri, Sep 23, 2011 at 9:55 PM, Shane Curcuru<asf@shanecurcuru.org>  wrote:
>
>> I'd recommend that folks contact the Apache press team in the future if
>> there are articles in the press that the project has issues with (or, things
>> we'd like to highlight in @TheASF or the Foundation blog):
>>
>>   http://www.apache.org/press/
>>
>> press@apache.org is a privately archived list, and has people with
>> experience with most of the major technology journalists and bloggers out
>> there who cover open source.  It's usually more effective to work with
>> press@ on material corrections to news stories than trying to work with
>> journalists you don't know personally.
>>
>> - Shane
>>
>>
>