Josh Berkus wrote:
> 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."
Yup, thats exactly what I experienced when I started a TODO list for the
PHP project. A few developers wanted to get direct access, others use me
as their proxy and then others do not care about the list at all. But it
has been very helpful to the community to hear whats going on. It has
let to some people joining the development or suggesting possible
implementation options and more importantly it has reduced the work load
of the release managers. This is not a task that requires a lot of
technical know how and is therefore a great way for some non C hacker to
contribute to the project.
regards,
Lukas