| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Learning curves and such (was Re: pgFoundry) |
| Date: | 2005-05-17 19:50:59 |
| Message-ID: | 2047.1116359459@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> It also seems that, once you get it up and running, any worthwhile dev
>> management system is going to actually take less time / effort to
>> maintain than, say, maintaining manually concocted todo lists and
>> coordinating development via a mailing list.
> This is true or at least, this is my experience but you are not going to
> convince many people of that.
The Postgres project has been exceedingly successful while using email
lists as the primary means of communication/organization. I for one
am disinclined to tinker with such a fundamental aspect of the way that
the community operates. If we try to substitute a bug tracker for the
mailing lists, I think we'll be making a very basic change in the
community's communication structure, and not one for the better.
>> Call me a normaliser, but even if the maintenance cost is higher, I
>> think it's worth it to have a centralised, authoratitive, organised
>> repository for dev task data.
> I agree.
Since the development community is neither centralised nor organized,
why would you expect such a repository to have anything to do with
what actually happens?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-05-17 20:03:40 | Re: Learning curves and such (was Re: pgFoundry) |
| Previous Message | Joshua D. Drake | 2005-05-17 18:56:32 | Re: Learning curves and such (was Re: pgFoundry) |