This is my test case example of how a triage community tracker bug
can work. Whether or not its going to work as I expect is an open
question. Here's how I see it working. Community members can add
comments to this bug to nominate existing bugreports as 'easyfix.'
I as the bug owner on this bug, and anyone else with editting rights
to this bug, will look over the comments and add bugsreport numbers to
the bugblocking list for the tracker bug.
The goal here is to try to use community effort to put all the bugs
that should be classified as easyfix in one place. Hopefully if we can
make it easier for the technically competent people to find the
easyfix bugs, they will be more willing to spend time actually fixing
Easyfix is a valid bugreport keyword and is defined here:
Marks bugs that are trivial easy-to-understand fixes that
anyone could implement. For example fix URL or dependencies in spec
I interpret the keyword definition to mean, bug reports that come with
patches that need review or states a very trivial problem that another
community member with more technical ability than the reporter can
build a patch for.
Steps to getting a bug nominated as a blocker for this tracker:
1) do your best to troll bugzilla and search for lingering bugreports
that are trivial or have a submitted patch. I would suggest
concentrating on older inactive reports than brand new ones.
2) drop into #fedora-bugs on the freenode irc network and take a few
minutes to see there are people there who agree that the bug you found
is really an 'easyfix.' You might even find someone who can fix it and
submit a patch if you can't build a patch yourself. Patches are really
the goal. If you do get a new patch built and submit to the orginal
bug report its probably wise to stop here and give the developer a
little time to review your patch. More likely than not, you will need
to give the developer a little feedback, and you might even have to
patch your patch....all in a days work. the #fedora-bugs channel is
going to be a good resource if you are new at fixing trivial patches.
3) Once you have convinced a few people that the bug should be
nominated easyfix, submit a comment to this bugreport with the bug
number for the bug you think is an 'easyfix' along with a very brief
4)Comments to this bug will be reviewed, and a portion of those
comments will turn into blocking bugs for this tracker which can
easily be queried.
Again please be aware that trying to get easyfix bugs patched and
those patches reviewed quickly is really my intention for this bug.
When searching for trivial bugs, its important that you make an effort
to attempt to build the patch yourself or conjule someone into
building the patch. The #fedora-bugs irc channel is there as a
resource to help you learn how to be more effective. And its perfectly
understandable if a bug seems trivial but still beyond your specific
technical abilities due to a code language barrier or other
constraint. Hopefully this public tracker bug will make it easier to
match up trivial problems with community volunteers.
Could we get a few queries posted on the main bugzilla web page for:
'All Fedora Core bugs at NEEDINFO or below in status'
'All Fedora Core bugs unchanged for more than 30 days'
'All Fedora Core bugs made in the last 24 hours'
just so we can more quickly get to things w/o all having to make the
same defined searches.
Yes, a place to list some useful queries would be...keen
But i'm not sure it needs to be the bugzilla main page.
I was thinking the fedora website should have a triage guide section
and triage's mainpage could better represent a useful toolbox for triage
and things like important notices.
I might mock up something as a layout sketch in the wiki, or maybe my
blog that isn't being used for anything.
Also...maybe we need to have yet another mailing list fedora-triage.
I'd hate to do all our longwinded, but very much needed, discussions
about triage policy in bugzilla comments :->
I think things like the queries Seth is suggesting make a lot of
sense. Perhaps just add them to the footer with the other preset
queries ("My bugs") rather than everyone having to make a custom saved
query to get it there....
Or perhaps, instead of cluttering that for everyone, just add
documentation to the Wiki (as much as I hate working with Wikis, I
can't believe I just said that ;-) covering how to add saved queries
including some useful example queries. That way, people who want to
triage can easily get them, and the rest don't have them in the way
(and bugzilla doesn't have to be modified)
Check out the triage page that Jef setup at fedora.us.
I added some suggested triage keywords.
I've also sent a request into the bugzilla master @ red hat to see
about either 1. adding triage field, 2. opening up the whiteboard or
3. opening up the keywords.
CLOSED->CRACKROCKMONKEY would be a useful new resolution to have
added. Perhaps dkl can investigate the feasibility of such an
addition. That would be very useful IMHO
Real easy bug to solve is
Just need to remove 3 times a ".o" from /etc/init.d/pcmcia
Trivial cosmetic bug with patch here:
When adding easyfix bugs, scroll down below to the bugzilla field
Bug 109188 depends on:
And add the bug ID's to the list there. Those are the bug IDs that
the tracker is tracking. Hope this helps.
OK Mike added my own report and the one of Dax to the Bug depends on
list. Now hope they get fixed soon ;-)
Testing xml-rpc api using bugtool.
Hopefully with triage comments and canned queries then we should be able to use bugtool/bugzuki for a lot of this.
Not much activity going on here lately :-( . Are the listed bugs going
to be solved before FC 2.0?
I have no idea if they WILL be solved. But I'm working my way through
the backlog of bugs that have been pre-marked for triage and marking
them up. The goal is to get things marked with keywords or closed
where appropriate to make it easier for developers to find the bugs
the can fix quickly. Bugzilla editting rights to fedora contributors
just recently got the kinks worked out. If you want to help out with
please sign up for the triage mailing list at
and read the very small number of initial messages sitting in the
archive. I plan to communicate with people interested in helping with
triage in a significant way via the mailinglist
This bug can be marked as solved as it was fixed in the recent update
Adding Tracking keyword
Triaging the distribution bugs in NEW state :)
Not sure what to do about this one, there's a keyword that folks can add that is
trivial to search for. Is this bug useful anymore with that?
Should this bug remain open? As Jon points out there is a keyword "EasyFix"
which makes a lot more sense than this tracking bug which does not appear to
have been used for a few years.
Will close in 30 days if no response.
No response. Closing.