Re: Press Release Party - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: Press Release Party
Date
Msg-id 200404230933.36570.josh@agliodbs.com
Whole thread Raw
In response to Re: Press Release Party  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Press Release Party  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-advocacy
Peter,

> Another feature of a press release is that those in whose name it is
> made know what they are committing to.  If only, say, three people know
> what is going to be announced, then you can make the announcement in
> the name of those three people, but not in the name of "the PostgreSQL
> project".  Otherwise you're just lying.

Well, no, actually.    You've never worked with the PR department of a real
company, have you?

> > Not everybody is involved in every patch that gets added to the code;
> > not everyone will be involved in every press release.
>
> You're wrong.  Everyone has a chance to review every patch and discuss
> every patch in public before it is released.

Precisely.   "has a chance".  This is that chance, so either participate or
don't.   And if you choose not to participate, then don't complain later that
you didn't get your say.

--
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-advocacy by date:

Previous
From: Alexey Borzov
Date:
Subject: Re: What can we learn from MySQL?
Next
From: "scott.marlowe"
Date:
Subject: Re: What can we learn from MySQL?