public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: Alexey Borzov <[email protected]>
Cc: Omar Kilani <[email protected]>
Cc: [email protected]
Subject: Re: [pgsql-advocacy] Alternate PostgreSQL.org Design
Date: Sat, 13 Nov 2004 00:01:03 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
On Friday 12 November 2004 23:42, Marc G. Fournier wrote:
> On Fri, 12 Nov 2004, Peter Eisentraut wrote:
> > Josh Berkus wrote:
> >>> OK, fair enough. Now can someone explain how we can put out a
> >>> release evrery 8-12 months with 200-300 changes, some very complex,
> >>> and we can't get a group together to update a web site?
> >>
> >> Because a lot less people are working on the web site, and none of
> >> them are paid to do so?
> >
> > We put out regular releases long before (some) people started getting
> > paid for their work. If now we're only getting work done if someone's
> > getting paid for it, we're in trouble.
>
> I agree ... IMHO, its like docs ... its not something ppl want to do,
> since they have a perception that its not as "cool' as orking on the code
> ...
>
I don't think it is just the coolness factor. It is easier to justify needing
to hack database code to your boss/professor/manager than it is to justify
hacking on the website. Same is true for a great many third party apps like
ODBC/JDBC/PhpPgAdmin/etc... All of these things help you solve another
problem. The current website, while not award winning, is functional enough
that enough people can get work done without haveing to chip in.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
view thread (59+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [pgsql-advocacy] Alternate PostgreSQL.org Design
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox