[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Fedora Bug Day: Aprl 07 2004: I'm not quite dead...



..in fact.. I'm feeling better.
What: Fedora Bug Day: 
To every bug..turn turn turn...
there is a resolution...turn turn turn...
and a time for cobweb cleaning in the bugzilla. 

Or in plain but misspelled english, Let's spend a little time over the
next 24 or so hour period, digging into bugzilla and trying to help
clean out some of the bugreports that are cluttering up Fedora bugzilla
in an effort to make it marginally easier for developers to navigate the
'zilla and find reports that need fixing.  Several types of bugreports
are screaming for community invovlement:
1) duplicates bug reports for problems already resolved that can be 
cleaned out
2) bug reports about potentially real problems that need more
information and/or confirmation before developers can make head way
3)sundry other situations
 
Who:
pretty much anyone with a web browser and a bugzilla.redhat.com and/or a
bugzilla.fedora.us account, and want to contribute to the fedora
development process.  Users of all skill levels can make a positive
impact on keeping bugzilla's bug reports better organized for developers
via Fedora Triage effort by learning how to be a package shepherd of
sorts:

Alan Cox I think said it best:
"Track the bugs in your favorite package/component:
* try to make a few minutes everyday to look through the new bugs filed
  in the last day for the package you want to watch.
* Sign up for the upstream mailing lists and bug tracking system, so you
  can more effectively be able to move bugs reported to Fedora upstream
  where they are more likely to be fixed."

And to put a finer point on it Warren Togami adds:
"Most projects don't have anything like an effective bug tracker of
their own. Because of that, what we need are volunteers to serve as
liaison to upstream projects. They should be members of those upstream
mailing lists and pay attention to news/patches/security alerts there.
Such helpers if they are diligent would be like assistants to the
package maintainers, and learn things as they go as well as gain trust
in the process"

Where: #fedora-bugs channel on freenode irc network

How: 
Come to the #fedora-bugs channel on the freenode irc network tomorrow
and be a part of the discussion. Go to bugzilla.redhat.com and try to
find a Fedora Core bugreport that you think is should be closed out, get
the attention of one of the triagers or developers sitting in channel
waiting in a grip of white knuckle anticipation to discuss with you
whether the bug should be closed or not. ( difficulty of trying to flag
someone down to talk to in channel might be a little time sensitive,
please be patient and don't be discouraged if someone doesn't respond
right away ) Use the bug day opportunities to start down a path of
contributing to fedora development by becoming a package shepherd, or
general fedora triager. 
 
Huh:  No Clue What I'm talking about when I say the phrase Fedora
Triage?
Take a quick look at the fedora-triage-list archives:
https://lists.dulug.duke.edu/pipermail/fedora-triage-list/
These messages should hopefully tell you what its all about in more
detail:
http://tinyurl.com/ywma3 - Summary of my vision for Fedora Triage
http://tinyurl.com/23alw - My short term goals and long term plan

-jef"damn..its Wednesday already"spaleta  




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]