We agree Mark. What I talked with Josh about is our interest in getting
Slony in use with some organizations in an enterprise capacity as well as
ensuring that commercial support is available (hence our workshop on Slony
at OSCON). Our plan is that once we have these details sewn up we can
directly pitch case studies of Slony's use with adequate customer and
support service references. Then we'd like to pursue product reviews.
The first step is to get this in production in our organization and then we
can think more about the press strategy.
As always, we are happy to be quoted in PostgreSQL releases and listed as an
enterprise user and contributor. We would just request review of how our
organization and it's employees are mentioned.
Best,
Heather
--
Heather D. Carle
Director of Communications
Afilias
Tel: +1.215.706.5700 x114
Fax: +1.215.706.5701
E-mail: hcarle@afilias.info
http://www.afilias.info
-----Original Message-----
From: pgsql-advocacy-owner@postgresql.org
[mailto:pgsql-advocacy-owner@postgresql.org]On Behalf Of Marc G.
Fournier
Sent: Thursday, August 12, 2004 2:59 PM
To: Josh Berkus
Cc: pgsql-advocacy@postgresql.org
Subject: Re: [pgsql-advocacy] Time to work on Press Release 8.0
On Thu, 12 Aug 2004, Josh Berkus wrote:
> Marc,
>
>> Also, the PR should be focused around what we are releasing, not side
>> projects ... Slony-I isn't part of this release, and, IMHO, isn't
>> appropriate as part of the PostgreSQL Server press release ... they
should
>> be doing their own Press Release for that. Focus on what *we* are
>> releasing, not what another project is releasing ...
>
> Afilias didn't want to do a Slony press release, which is why I want to
> mention it in passing in the main release. Along with several other
> add-ons.
IMHO, it detracts from what we are announcing ... ... but if nobody else
feels the same way, go for it ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
