From: | Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bugzilla (Was: What do you want me to do?) |
Date: | 2003-11-11 14:01:35 |
Message-ID: | 200311111931.35793.shridhar_daithankar@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tuesday 11 November 2003 19:19, Peter Eisentraut wrote:
> Andrew Dunstan writes:
> > Seriously, I have wondered if it might be a good idea to assemble a
> > small "hit team" that would take some high profile open source projects
> > and make sure they worked with Postgres. Bugzilla would be the most
> > obvious candidate, but there are certainly others. I suspect that could
> > be quite productive, though.
>
> Good thought, but a hit team is not the right answer, because any project
> that would have been "hit" in this way will just go bad again the moment
> its database layer is changed. What would work better are "consultants":
> people that hang around on the other project's mailing lists, offer advise
> on database layer modelling and implementation, do clean up tasks, check
> regularly if everything works with the PG development branch, be there
> when the developers of that other project have a question. I've been
> doing a bit of that, and my sensation is that most developers of
> database-backed applications are dying to have people like that at their
> disposal.
So forming a new group is quite beneficial?
I think so too.. I have been planning to do that for dbmail and egroupware
but haven't got around it..
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-11-11 14:10:54 | Re: bugzilla (Was: What do you want me to do?) |
Previous Message | Peter Eisentraut | 2003-11-11 13:49:38 | Re: bugzilla (Was: What do you want me to do?) |