From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Lamar Owen <lowen(at)pari(dot)edu> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Learning curves and such (was Re: pgFoundry) |
Date: | 2005-05-18 21:19:55 |
Message-ID: | 20050518211955.GV30011@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Lamar Owen (lowen(at)pari(dot)edu) wrote:
> On Tuesday 17 May 2005 01:41, Josh Berkus wrote:
> > > > To put it much more bluntly: PostgreSQL development (both the process
> > > > and the codebase) has one of the steepest learning curves around,
>
> > You haven't looked at the OpenOffice.org code. <wince>
>
> Yes, I have. Yes, it's steeper.
That seems rather odd to me. I havn't really looked at the
OpenOffice.org code very much but generally I've found the PostgreSQL
code to be pretty well commented and generally well thought-out. I've
also found the acceptance, understanding and hand-holding of the
PostgreSQL developers to be *better* than I've found in other
communities (such as the Linux kernel...) that I've developed and have
had code included in.
I havn't actually gotten anything real into PostgreSQL *yet*, but I've
been spending a fair bit of time on implementing support for SQL Roles
and have had alot of help developing the approach for best implementing
it (thanks Tom!) and help with stupid questions (what's a tuple?) from
a couple developers on IRC (thanks Neil! thanks Andrew!).
So, no, I don't think the barrier to entry is all that steep, and it's
certainly not *too* steep by any means.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-18 21:28:19 | Re: pg_dump and using schema problem |
Previous Message | Tom Lane | 2005-05-18 21:15:09 | Two-phase commit issues |