You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Xavier Hanin <xa...@gmail.com> on 2007/05/23 11:44:08 UTC
Branding Guide clarification (was Re: to brand or not to brand?)
On 5/23/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> On 5/22/07, Xavier Hanin <xa...@gmail.com> wrote:
> > Mmm, it's still not completely clear. Is the phrase "However, the
> > Public Relations Committee MUST review any releases by affiliated
> > organizations or groups to ensure they comply with these branding
> > guidelines." referring to press release announcing the podling only,
> > or to all press releases? Since it seems it's not allowed to issue
> > press releases announcing the release, I'd think it's for press
> > releases that reference the podling. And that's what my article will
> > do, reference the podling.
>
> I think the gist is in the term "Press release". I think a press
> release is something other than an article. A press release is
> something like "Foo is adopting Apache Ivy in its product line and
> providing professional support for it." and send it across the wire,
> i.e. an announcement.
>
> This is of course something different than "This is how you manage
> your Java project dependencies using Apache Ivy, currently undergoing
> incubation at the Apache Incubator." which is published on
> theserverside.com and/or infoq.
It makes sense, indeed. But I think it would be nice to have something in
the branding guide more clearly understandable.
So, maybe I should ask the question to the PRC, and open a JIRA issue to put
their answers or some examples in the branding guide?
Xavier
Re: Branding Guide clarification (was Re: to brand or not to brand?)
Posted by robert burrell donkin <ro...@gmail.com>.
On 5/26/07, Martijn Dashorst <ma...@gmail.com> wrote:
> On 5/26/07, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> > Do you have a suggestion as to how it should read?
>
> I would shift a bit within the sentences, so that the things that are
> permitted get their own section. something like the following:
>
> [...]
> 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. The ASF will not issue any
> press releases for any podling at this stage. However, the Public
> Relations Committee MUST review any press releases by affiliated
> organizations or groups to ensure they comply with these branding
> guidelines.
like the wording but not sure that this is quite right
by definition only the PRC can issue official press releases for
apache. so, if a podling wants a press release then they need to talk
to the PRC.
the main issue was with third parties issuing press releases on behalf
of the podling or pre-empting the decision making process at apache.
few PR departments seem to understand the open source space.
IMHO these issues could be solved just by asking that the apache PRC
has a chance to check all PR activity by third parties related to
podlings before it's public but the majority opinion at the time was
that stronger measures were needed.
> A Podling can conduct informal PR activities without having to go
> through the PRC. Examples of informal PR activities are media
> outreach, blog publicity, technical articles, etc. The article may use
> Apache <Podling> in such articles, provided the incubation status is
> mentioned: "Apache Foo, currently incubating at the Apache Software
> Foundation, can be used to bar the foo. In this article we will show
> how to use Foo to accelerate the development of bars and..."
> [...]
wording is fine
IMHO informal and unofficial PR is great - the main problem is
accuracy. accurate PR work sympathetic PR is no problem at all. apache
isn't good at PR and we have real issues correcting inaccurate PR
which is pushed by a professional department. the press tends to
believe corporations, not apache.
> Of course, I am very open to suggestions to make this better, shorter
> or completely different.
>
> > The prohibition is on 'formal' press releases surrounding the fact
> > that it incubated - but it's certainly okay to write articles and
> > stuff - just make sure that it says it's under incubation, blah, blah.
>
> That is what I figured. Thanks for the clarification.
+1
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Branding Guide clarification (was Re: to brand or not to brand?)
Posted by Martijn Dashorst <ma...@gmail.com>.
On 5/26/07, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> Do you have a suggestion as to how it should read?
I would shift a bit within the sentences, so that the things that are
permitted get their own section. something like the following:
[...]
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. The ASF will not issue any
press releases for any podling at this stage. However, the Public
Relations Committee MUST review any press releases by affiliated
organizations or groups to ensure they comply with these branding
guidelines.
A Podling can conduct informal PR activities without having to go
through the PRC. Examples of informal PR activities are media
outreach, blog publicity, technical articles, etc. The article may use
Apache <Podling> in such articles, provided the incubation status is
mentioned: "Apache Foo, currently incubating at the Apache Software
Foundation, can be used to bar the foo. In this article we will show
how to use Foo to accelerate the development of bars and..."
[...]
Of course, I am very open to suggestions to make this better, shorter
or completely different.
> The prohibition is on 'formal' press releases surrounding the fact
> that it incubated - but it's certainly okay to write articles and
> stuff - just make sure that it says it's under incubation, blah, blah.
That is what I figured. Thanks for the clarification.
Martijn
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Branding Guide clarification (was Re: to brand or not to brand?)
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 5/23/07, Martijn Dashorst <ma...@gmail.com> wrote:
> It may be on purpose that the wording is vague and open for debate.
> This way you get away with a lot, and when things go wrong, you get to
> point and slap people on the wrists :)
Ha - you give us too much credit.
Do you have a suggestion as to how it should read?
The prohibition is on 'formal' press releases surrounding the fact
that it incubated - but it's certainly okay to write articles and
stuff - just make sure that it says it's under incubation, blah, blah.
-- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Branding Guide clarification (was Re: to brand or not to brand?)
Posted by Xavier Hanin <xa...@gmail.com>.
On 5/23/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> On 5/23/07, Xavier Hanin <xa...@gmail.com> wrote:
> > It makes sense, indeed. But I think it would be nice to have something
> in
> > the branding guide more clearly understandable.
>
> > So, maybe I should ask the question to the PRC, and open a JIRA issue to
> put
> > their answers or some examples in the branding guide?
>
> It may be on purpose that the wording is vague and open for debate.
> This way you get away with a lot, and when things go wrong, you get to
> point and slap people on the wrists :)
>
> Maybe a rewording might make us not so fluent in the English language
> (and more specifically: the 'legal' English lingo) more confident and
> knowledgable in these policies/rules/guidelines.
>
> I think a JIRA with 'This needs more clarification' would suffice
> (pointing at the document and this discussion). This way it won't get
> lost in the ongoing discussions.
I've created a JIRA issue:
https://issues.apache.org/jira/browse/INCUBATOR-65
Thanks,
Xavier
Martijn
>
> --
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.6 contains a very important fix. Download Wicket now!
> http://wicketframework.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
Re: Branding Guide clarification (was Re: to brand or not to brand?)
Posted by Martijn Dashorst <ma...@gmail.com>.
On 5/23/07, Xavier Hanin <xa...@gmail.com> wrote:
> It makes sense, indeed. But I think it would be nice to have something in
> the branding guide more clearly understandable.
> So, maybe I should ask the question to the PRC, and open a JIRA issue to put
> their answers or some examples in the branding guide?
It may be on purpose that the wording is vague and open for debate.
This way you get away with a lot, and when things go wrong, you get to
point and slap people on the wrists :)
Maybe a rewording might make us not so fluent in the English language
(and more specifically: the 'legal' English lingo) more confident and
knowledgable in these policies/rules/guidelines.
I think a JIRA with 'This needs more clarification' would suffice
(pointing at the document and this discussion). This way it won't get
lost in the ongoing discussions.
Martijn
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org