On Sat, Aug 05, 2006 at 01:00:24PM -0700, Josh Berkus wrote:
> Neil, all:
>
> > If people are interested in the status of a patch, I think it's
> > fine for them to email the person who's volunteered to work on it.
>
> The problem I would like to see resolved is that there is currently
> no accurate way to determine who is working on a patch except by
> comprehensive -hackers, -patches, and -performance archive reading.
True.
> This is a little daunting for people who just joined the community,
> or who are users just wanting to know if someone is working on a
> feature they want.
>
> I doubt that any TODO system would have 100% participation, and I
> know that it would depend on having some non-hacker volunteers
> updating the information on behalf of developers who didn't want to
> use it. However, I think that getting those volunteers is entirely
> possible (for example, PWN is inculding a weekly patch list and it's
> not much more effort to check off those patches against a web-based
> TODO list). If the system reflected 70% of current development
> activity, then I think it would be a big improvement over the
> current "read 100% of the mail archives for three mailing lists back
> one year to find out what's going on."
This thing is why I've been continuing the patches review on
PostgreSQL Weekly News :)
Cheers,
D
--
David Fetter <david@fetter.org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter
Remember to vote!