| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Iavor Raytchev <iavor(dot)raytchev(at)verysmall(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Constantin Teodorescu <teo(at)flex(dot)ro>, Cmaj <cmaj(at)freedomcorpse(dot)info>, Boyan Dzambazov <boyan(dot)dzambazov(at)verysmall(dot)org>, "Bartus(dot) L" <bartus(dot)l(at)bitel(dot)hu>, Stanislav Grozev <stanislav(dot)grozev(at)cees(dot)org>, Boyan Filipov <boyan(dot)filipov(at)verysmall(dot)org> |
| Subject: | Re: pgaccess |
| Date: | 2002-05-09 16:23:16 |
| Message-ID: | 3CDAA274.F4109A6A@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
...
> It is not important where it is - it is important (for us) to put a small
> organization around the thing that can make collecting all patches possible.
pgaccess is currently in the pgsql cvs tree, and is welcome to stay
there. Some of us have commit privileges, and y'all may want to have
someone else with privs also once you are organized and it is clear how
best to proceed. If you need web resources that can be arranged too, as
can a dedicated mailing list.
gborg is another way to organize, and of course www.pgaccess.org is a
way too. It partly depends on how you see the future of pgaccess. If it
stays tightly coupled to pgsql, then perhaps it may as way stay
organized with pgsql.
Regards.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2002-05-09 16:34:58 | Issues tangential to win32 support |
| Previous Message | Barry Lind | 2002-05-09 16:21:51 | Re: PG+Cygwin Production Experience (was RE: Path to PostgreSQL |