Kent Olsson wrote:
Please, give the list a proper answer in this topic! This is important,
though it is boring with bugs! :-)))
Just to relate some experience of open source with Acegi Security (www.acegisecurity.org), of which I am project lead, I have found the addition of issue tracking very valuable. Whilst I had initial hesitation, as a project grows it's liberating being able to direct the community to a particular tool to log bugs or feature suggestions. The reason is that it acts as a managed list of tasks, which I can go and deal with as and when I get time. The alternative is to track everything manually, or respond instantly, which is possible in the beginning of an open source project but simply doesn't scale in line with the community. Qooxdoo is an incredible framework, and it *will* scale (assuming we can get tabs to wrap as per my earlier email) ;-) so it's perhaps worthwhile to put issue tracking in place. Core developers need to remember that not every issue needs to be answered or addressed. Many issues are marked as "won't fix" or "cannot duplicate" or "not enough information". It doesn't require extra time overall. I've found it actually saves me time overall, as I can devote specific days to resolving issues (and I get a lot more done on such days than spending a little bit of time resolving issues every day).

Issue tracking also gives one other major benefit in that the list doesn't need to be bombarded with code contributions and patches constantly. Again, these are fine initially but as you get a few hundred and then thousand on this list, people will start to become frustrated with it. Issue tracking gives a single place where people can be sent to obtain the latest version of some code (like split pane or logging consoles), and only after the code "settles down" can it (eventually) be entered into CVS.

In relation to the Qooxdoo domain name, I personally would transfer the name to Sebastian at the earliest opportunity. Think of it as a donation for a generous contribution to the open source community. It's good to take the initiative, but it's important that critical resources like domain names are held by whoever is the project lead of the day.

Cheers
Ben


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to