<br><br><div><span class="gmail_quote">On 18/09/2007, <b class="gmail_sendername">Richi Plana</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 2007-09-18 at 10:59 +0200, Alexander Larsson wrote:<br>> > The bug was filed on 2007-06-08 (over 3 months ago) by J H Ettle and<br>> > added my +1 to it on 2007-08-29. Is Alexander missing? Is there a
<br>> > co-maintainer who should be available?<br>><br>> I don't know what help a co-maintainer for fedora would do. What we need<br>> are more people to look at bugs, come up with patches that fix them and
<br>> post them upstream, where I can review and commit them. This will then<br>> instantly come back to fedora (beacuse we track upstream closely).<br>><br>> Unfortunately, not many people seem interested in doing this work. :(
<br><br>Either that or bugzilla needs a better way to allocate tasks.<br><br>Having worked as a software developer for quite some time, I know how<br>many developers would rather just work on a problem rather than try to<br>
validate bug reports and gather missing information. Personally, I would<br>rather work on bugs that either interest me really well, or are provided<br>in a format that allows me to work on the problem immediately.<br><br>
Unfortunately, qualifying bug reports (finding dupes, going back to the<br>reporter for missing information) can only be done by people who know<br>exactly what real problems are and what's needed to resolve them.</blockquote>
<div><br>This is simply untrue. I am currently about halfway through a bug triage of all Fedora 7 kernel bugs and am doing so solely on the basis of one page from the wiki which the kernel team put together. I know nothing of kernel code but I do know having had a few pointers from people in the know what information to request under what circumstances. If I can do that for the kernel I'm sure the same goes for any application.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I know this is something that requires discipline and structure ...<br>something that doesn't always go hand-in-hand with the nature of
<br>volunteer work, but it's something that has to be addressed in order for<br>bugs to be proactively addressed (rather than wait for someone to bring<br>it up on a mailing list). As FOSS endeavors grow (and the number of
<br>users increase), there's got to be ways to improve on volunteer<br>bug-fixing.<br><br>Any ideas?<br><br>I've always wondered if the assignment of tasks can be round-robin'd (or<br>pick some better way of scheduling tasks that's completely and really
<br>fair, ;) ) assuming we had a couple of more volunteers.<br><br></blockquote></div>I think you just need to dive right into bugzilla and whatever component interests you then start with that. Bug triage is quite rewarding and people actually feel a little loved. Surely there is nothing like the hurt and pain of an un-answered bug report?
<br><br>Cheers<br>Chris<br clear="all"><br>-- <br><a href="http://www.chruz.com">http://www.chruz.com</a>