On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
On 5/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Tuesday 22 May 2007 17:21, Xavier Hanin wrote:
> > So, any recommendation or link?
>
> All public announcements should be run through the PRC, to ensure accuracy.
> So, I suggest th
On 5/26/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 5/26/07, Justin Erenkrantz <[EMAIL PROTECTED]> 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 followin
On 5/26/07, Justin Erenkrantz <[EMAIL PROTECTED]> 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 pres
On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> 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 a
On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 5/23/07, Xavier Hanin <[EMAIL PROTECTED]> 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
On 5/23/07, Xavier Hanin <[EMAIL PROTECTED]> 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 brand
On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> 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
On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> 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 announc
As a lurker on PRC, I've never seen an article sent for review. I
don't think its necessary. Paul
On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
Mmm, it's still not completely clear. Is the phrase "However, the
Public Relations Committee MUST review any releases by affiliated
organizations
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
On Tuesday 22 May 2007 20:50, Martijn Dashorst wrote:
> I just read it and it seems to me that the technical article Xavier is
> trying to publish would not need to be passed to the PRC.
Better safe than sorry... ;o)
Cheers
Niclas
-
I just read it and it seems to me that the technical article Xavier is
trying to publish would not need to be passed to the PRC.
In my understanding this falls in the category of informal pr
activities, as long as the article is not intended as a press release
announcing the Podling.
But I alway
I'm pretty sure you already read it. But in case you don't, see
http://incubator.apache.org/guides/branding.html
Gilles
> -Original Message-
> From: Xavier Hanin [mailto:[EMAIL PROTECTED]
> Sent: mardi 22 mai 2007 14:28
> To: general@incubator.apache.org
> Subjec
On 5/22/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Tuesday 22 May 2007 17:21, Xavier Hanin wrote:
> Hi,
>
> I'm currently preparing an article on Ivy, and I'd like to know if
> it's better to talk about Apache Ivy, or simply Ivy. The rules about
> branding are still not clear for me, sorry
On Tuesday 22 May 2007 17:21, Xavier Hanin wrote:
> Hi,
>
> I'm currently preparing an article on Ivy, and I'd like to know if
> it's better to talk about Apache Ivy, or simply Ivy. The rules about
> branding are still not clear for me, sorry if I missed an obvious
> link.
>
> So, any recommendatio
Yes, the advice is completely right.
Paul
On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
It makes sense, thanks!
Xavier
On 5/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> As I understand it, you need to call it Apache Ivy on first reference,
> and mention prominently that it is "curre
It makes sense, thanks!
Xavier
On 5/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
As I understand it, you need to call it Apache Ivy on first reference,
and mention prominently that it is "currently undergoing incubation at
the Apache Software Foundation" (or something like that).
- Brett
On
As I understand it, you need to call it Apache Ivy on first reference,
and mention prominently that it is "currently undergoing incubation at
the Apache Software Foundation" (or something like that).
- Brett
On 22/05/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
On 5/22/07, Xavier Hanin <[
On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
...I'm currently preparing an article on Ivy, and I'd like to know if
it's better to talk about Apache Ivy, or simply Ivy. The rules about
branding are still not clear for me, sorry if I missed an obvious
link
IMHO it'd be good to say "Ap
Hi,
I'm currently preparing an article on Ivy, and I'd like to know if
it's better to talk about Apache Ivy, or simply Ivy. The rules about
branding are still not clear for me, sorry if I missed an obvious
link.
So, any recommendation or link?
Xavier
--
Xavier Hanin - Independent Java Consultan
20 matches
Mail list logo
