I can't speak for the PostgreSQL team (well, is there such a thing?), but
in general, it doesn't quite work this way.
You usually start out as a user, find out the development environment,
etc, etc, use it for your project, then you find that there are few things
about a project that really make you itch. Then you scratch that itch, and
hopefully send your patch to the team. :)
On Fri, 22 Jun 2001, P. Dwayne Miller wrote:
> If someone was interested in joining the development team, where would
> they...
>
> - Find a description of the open source development process used by the
> PostgreSQL team.
>
> - Find the development environment (OS, system, compilers, etc)
> required to develop code.
>
> - Find an area or two that needs some support.
>
>
> Thanks
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>
>
