Entry tags:
The June Clean-Up-The-Little-Stuff Hackathon
So, the other day I took a look at our number of open bugs (currently 689) and resolved bugs (currently 1948) and realized: it was time for a hackathon!
For this one, since Mark's time is really constrained this month and Fu will be doing most of the review/commit work in addition to her other duties, we're going to concentrate on whacking the little stuff: the effort-minor bugs, the half-an-hour fixes, the small UI tweaks, the little bits of code cleanup, etc. This isn't to say that you can't do the bigger stuff if you want, just that the priority for this month should be blazing through all the small, quickly-fixed pieces. (If we were a different kind of project, someone would be using the phrase "low-hanging fruit" right about now.) We also welcome, and in fact encourage, people to be doing code review of others' patches as well as code work.
My goal is to get the open count under 600 open bugs by June 30. (This will also mean that we'll surpass 2000 resolved bugs, too. Which will be awesome.)
To help keep track, I'll be posting regular progress reports! If you've been thinking about picking up a bug or two, now's the time to do it. And if you're working on something huge, why not take an afternoon and knock out some little things?
We've got Bugzilla searches for unassigned effort-minor bugs and unassigned from-suggestions bugs (many of which are quick hits too).
Let's get cracking; I totally know we can knock those numbers down like whoa if we really give it a shot. :)
For this one, since Mark's time is really constrained this month and Fu will be doing most of the review/commit work in addition to her other duties, we're going to concentrate on whacking the little stuff: the effort-minor bugs, the half-an-hour fixes, the small UI tweaks, the little bits of code cleanup, etc. This isn't to say that you can't do the bigger stuff if you want, just that the priority for this month should be blazing through all the small, quickly-fixed pieces. (If we were a different kind of project, someone would be using the phrase "low-hanging fruit" right about now.) We also welcome, and in fact encourage, people to be doing code review of others' patches as well as code work.
My goal is to get the open count under 600 open bugs by June 30. (This will also mean that we'll surpass 2000 resolved bugs, too. Which will be awesome.)
To help keep track, I'll be posting regular progress reports! If you've been thinking about picking up a bug or two, now's the time to do it. And if you're working on something huge, why not take an afternoon and knock out some little things?
We've got Bugzilla searches for unassigned effort-minor bugs and unassigned from-suggestions bugs (many of which are quick hits too).
Let's get cracking; I totally know we can knock those numbers down like whoa if we really give it a shot. :)
no subject
I think it's maybe because of the missing sharer_id argument? I managed to have them work by adding
&sharer_id=2
at the end of the url.no subject
no subject
no subject
no subject
no subject
no subject
Useful resources:
http://wiki.dwscoalition.org/notes/Category:Getting_Started
http://wiki.dwscoalition.org/notes/Dev_Getting_Started
http://wiki.dwscoalition.org/notes/Dreamhack_Getting_Started
("Dreamhacks" are our hosted development environments, provided free of charge, for anyone who's hacking on the DW code. It saves you the trouble of installing the code yourself and needing to have your own server.)
no subject
no subject
no subject
no subject
no subject
http://bugs.dwscoalition.org/show_bug.cgi?id=2280
We've contacted the forum owner and know of what exception to tell people to add until it's implemented in code.
no subject
no subject
(And yes, wander through Bugzilla and find something that you like. *g*)