From Fedora Project Wiki
mNo edit summary |
(→Learn More About Triage: change Goals link to "components" - making redirect) |
||
Line 42: | Line 42: | ||
* Come to Triage Team [[BugZappers/Meetings| meetings]] -- everyone is welcome! | * Come to Triage Team [[BugZappers/Meetings| meetings]] -- everyone is welcome! | ||
<!--* Check out our [[BugZappers/OfficeHours| OfficeHours]] -- someone will be there to help out.--> | <!--* Check out our [[BugZappers/OfficeHours| OfficeHours]] -- someone will be there to help out.--> | ||
* [[BugZappers/ | * [[BugZappers/components|Component list]] - tracks progress and has pre-formatted queries to produce bug lists | ||
* [[BugZappers/Tools| Tools]] | * [[BugZappers/Tools| Tools]] | ||
* [[BugZappers/HouseKeeping | Regular Release Processes]] | * [[BugZappers/HouseKeeping | Regular Release Processes]] |
Revision as of 15:54, 24 February 2009
Fedora Bug Zappers
Who Are We?
Fedora Common Bugs | ||
---|---|---|
Fedora 8 | Fedora 9 | Fedora 10 |
- Our primary mission is to track down and shoot Fedora bugs in bugzilla.redhat.com . We also strive to be a bridge between users and developers that aids in fixing and closing bugs
- See if you qualify :-)
Contributing roles in the Bug Zappers Project
Getting Involved
- Stop by #fedora-bugzappers and #fedorabot on freenode
- Join the fedora-test-list@redhat.com mailing list.
- See Joining for detailed information on account signups and getting access
Start Triaging Bugs!
Learn More About Triage
- Come to Triage Team meetings -- everyone is welcome!
- Component list - tracks progress and has pre-formatted queries to produce bug lists
- Tools
- Regular Release Processes
- Stock Responses
Recent Presentations
- FUDCon Boston--June 21, 2008