Обсуждение: pgaccess.org - invitation for a working meeting
Hello everybody, I personally had enough discussions during the last few days. I want to thank everybody who expressed their opinion and to remind you all that we started as a small group of four people who actively use and patch pgaccess now, asked by Teo to see what we can do about bringing our patches together. I do not feel like moderating a pgaccess war. My opinion is that some of the last postings are by people who have not followed the whole discussion from the start, and also some go into problems - too distant for the current fragile day. With this message I would like to invite all people who have fresh patches (newer than one year) and all people who are interesting in working and/or supporting pgaccess now (during the next few weeks) to send a signal during the weekend. And all the rest to be quite for a while. I want on Monday to proceed and to merge at least the code we produced in our company with the latest pgaccess that can be found and with the code of Chris and Bartus. And to see if and how we (Chris, Bartus, Boyan, Teo and myself, plus all active people who send a signal) can work together. I think it is clear that pgaccess is for PostgreSQL, that nobody wants to take it away or to kill it. After we do this small step next week and 'show some code' to Peter Eisentraut, we can think how is best to make it available for the PostgreSQL users. And how to continue. I think some of you want too much from a half asleep project. Let it wake up, let is see on which earth it is. And let it then decide. Thanks, Iavor -- www.pgaccess.org
Iavor Raytchev wrote: > I want on Monday to proceed and to merge at least the code we produced in > our company with the latest pgaccess that can be found and with the code of > Chris and Bartus. > > And to see if and how we (Chris, Bartus, Boyan, Teo and myself, plus all > active people who send a signal) can work together. > > I think it is clear that pgaccess is for PostgreSQL, that nobody wants to > take it away or to kill it. > > After we do this small step next week and 'show some code' to Peter > Eisentraut, we can think how is best to make it available for the PostgreSQL > users. [ Just catching up.] I think we have a few options. You can maintain both your current pgaccess source and previous version CVS (if you wish) using the PostgreSQL CVS tree. Any changes you commit will be released automatically as part of PostgreSQL. You will have commit privileges for PostgreSQL CVS so you will have control over the changes. (The jdbc group already does this successfully.) Others PostgreSQL developers will also have access to the source tree and hopefully will make changes to keep pgaccess in sync with backend changes. You would not be required to get approval for the patches you apply, but we do ask you to restrict your changes to the pgaccess subdirectory unless you discuss non-pgaccess changes on hackers. Another options is to return to the old way we did it, where I grabbed the most recent pgaccess version when it was released and updated the PostgreSQL CVS. The choice is yours. Also, we can make our ftp distribution and mailing lists available if they would be of value to you. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
Folks, If I might just say ... I think it's phenominal that somebody has started working on the PGAccess code again and I really look forward to testing (and documenting!) your work. If you don't read the Novice list, new Postgres users have been dying for a PGAccess update for the last year. Your contribution will be widely appreciated by Postgres users everywhere. -Josh BerkusPostgreSQL/Techdocs Writer
Thanks Josh, Good, encouraging words. There are two mailing lists - please feel free to make them popular - developers@pgaccess.org users@pgaccess.org Both are run on qmail/ezmlm, for help send a blank e-mail to - developers-help@pgaccess.org users-help@pgaccess.org The lists are not moderated. Please, ONLY people who develop or would like to develop subscribe to 'developers'. On 'users' we'll be happy to read what people expect form pgaccess. There will be bugzilla soon on bugzilla.pgaccess.org The current stage is - we are about the merge the three major (known) patches to pgaccess done by Bartus, Chris and Boyan with the latest known version of pgaccess. Tacho (tacho@verysmall.org) will be the release engineer in the beginning. This should happen this week or so (Chris is about to submit his work). To repeat again - we all use, like and admire PostgreSQL. And pgaccess. The only reason to set up a separate community for it is because we believe that it needs a bit more air. pgaccess has no meaning outside PostgreSQL. We do not try to steal it or take it over,... One day I should write a page how the whole things started, so that I do not have to explain it every time. All best to everyone, Iavor PS Josh, testing and documenting are two good activities. What we urgently need is a dedicated release engineer - Tacho will do this in the beginning but he can not promise long term commitment. And Teo is busy right now. > -----Original Message----- > From: Josh Berkus [mailto:josh@agliodbs.com] > Sent: Mittwoch, 05. Juni 2002 17:35 > To: Bruce Momjian; Iavor Raytchev > Cc: Tom Lane; Thomas Lockhart; Stanislav Grozev; Ross J. Reedstrom; > Nigel J. Andrews; Marc G. Fournier; Constantin Teodorescu; Cmaj; Boyan > Filipov; Boyan Dzambazov; Bartus. L; Brett Schwarz; pgsql-hackers > Subject: Re: [HACKERS] pgaccess.org - invitation for a working meeting > > > Folks, > > If I might just say ... I think it's phenominal that somebody has > started working on the PGAccess code again and I really look forward to > testing (and documenting!) your work. > > If you don't read the Novice list, new Postgres users have been dying > for a PGAccess update for the last year. Your contribution will be > widely appreciated by Postgres users everywhere. > > -Josh Berkus > PostgreSQL/Techdocs Writer
Iavor Raytchev wrote: > pgaccess has no meaning outside PostgreSQL. We do not try to steal it or > take it over,... One day I should write a page how the whole things started, > so that I do not have to explain it every time. I have not heard --- where are you going to keep the master CVS? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026