From Fedora Project Wiki
m (1 revision(s))
(fix formatting for mw)
Line 5: Line 5:
== Important Account Signups ==
== Important Account Signups ==


1. Obtain a bugzilla account in Red Hat's Bugzilla
# Obtain a bugzilla account in Red Hat's Bugzilla
* https://bugzilla.redhat.com/bugzilla/createaccount.cgi
#* https://bugzilla.redhat.com/bugzilla/createaccount.cgi
* Fedora's bugs are tracked in Red Hat's Bugzilla
#* Fedora's bugs are tracked in Red Hat's Bugzilla
1. Obtain a [[Infrastructure/AccountSystem|  Fedora Account]]  
# Obtain a [[Infrastructure/AccountSystem|  Fedora Account]]  
* This is necessary to obtain additional permissions in bugzilla needed to triage bugs
#* This is necessary to obtain additional permissions in bugzilla needed to triage bugs
* It is necessary that the e-mail address used for your Bugzilla and Fedora accounts are the same
#* It is necessary that the e-mail address used for your Bugzilla and Fedora accounts are the same
1. After successfully obtaining a Fedora account, view the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs group]  and apply to the group by clicking the '''Apply!''' button.
# After successfully obtaining a Fedora account, view the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs group]  and apply to the group by clicking the '''Apply!''' button.
1. If you can commit to being a regular triager for the current release cycle, add your name to the [[BugZappers/ActiveTriagers|  Active Triagers]]  page.
# If you can commit to being a regular triager for the current release cycle, add your name to the [[BugZappers/ActiveTriagers|  Active Triagers]]  page.
* This is a simple reference so that package maintainers know who the triagers are
#* This is a simple reference so that package maintainers know who the triagers are
* It also gives us a rough idea who is triaging bugs in which components
#* It also gives us a rough idea who is triaging bugs in which components
{{ Template:message/notice | This does mean certain components are reserved. If you are unfamiliar with a component and someone is very active there, it is probably a good idea to pick a different component.
{{ Template:message/notice | This does mean certain components are reserved. If you are unfamiliar with a component and someone is very active there, it is probably a good idea to pick a different component.
}}
}}
Line 20: Line 20:
== Communication ==
== Communication ==


1. Join the fedora-test-list
# Join the fedora-test-list
* All announcements and conversations about bug triage happen on this list
#* All announcements and conversations about bug triage happen on this list
* https://www.redhat.com/mailman/listinfo/fedora-test-list
#* https://www.redhat.com/mailman/listinfo/fedora-test-list
1. Valuable communication and real time help happen in the chat channels on IRC.
# Valuable communication and real time help happen in the chat channels on IRC.
* Two useful channels to join are: #fedora-qa and #fedorabot on Freenode
#* Two useful channels to join are: #fedora-qa and #fedorabot on Freenode
* Once you are all setup and ready to go drop by and say hello on #fedora-qa
#* Once you are all setup and ready to go drop by and say hello on #fedora-qa
* #fedora-qa is also a good place to get help if you are having problems with the sign-up process
#* #fedora-qa is also a good place to get help if you are having problems with the sign-up process
* See [[Communicate/IRCSetup| ]]  and [[Communicate/IRCHowTo| ]]  for more information on using IRC
#* See [[Communicate/IRCSetup| ]]  and [[Communicate/IRCHowTo| ]]  for more information on using IRC
1. Obtain wiki edit access
# Obtain wiki edit access
* The Fedora Project Wiki (which is what you are reading from right now) is a useful place to store and retrieve information.
#* The Fedora Project Wiki (which is what you are reading from right now) is a useful place to store and retrieve information.
* Obtaining wiki edit access gives you the ability to contribute too.
#* Obtaining wiki edit access gives you the ability to contribute too.
* See WikiEditing for information to obtain wiki edit access--note this username and password are separate from your Fedora Account username and password.
# Attend a [[BugZappers/Meetings|  Bug Triage Meeting]] .
1. Attend a [[BugZappers/Meetings|  Bug Triage Meeting]] .


[[Category:BugTriage]]
[[Category:BugTriage]]

Revision as of 01:35, 27 May 2008

Joining the BugZappers

Important Account Signups

  1. Obtain a bugzilla account in Red Hat's Bugzilla
  2. Obtain a Fedora Account
    • This is necessary to obtain additional permissions in bugzilla needed to triage bugs
    • It is necessary that the e-mail address used for your Bugzilla and Fedora accounts are the same
  3. After successfully obtaining a Fedora account, view the fedorabugs group and apply to the group by clicking the Apply! button.
  4. If you can commit to being a regular triager for the current release cycle, add your name to the Active Triagers page.
    • This is a simple reference so that package maintainers know who the triagers are
    • It also gives us a rough idea who is triaging bugs in which components
This does mean certain components are reserved. If you are unfamiliar with a component and someone is very active there, it is probably a good idea to pick a different component.

Communication

  1. Join the fedora-test-list
  2. Valuable communication and real time help happen in the chat channels on IRC.
    • Two useful channels to join are: #fedora-qa and #fedorabot on Freenode
    • Once you are all setup and ready to go drop by and say hello on #fedora-qa
    • #fedora-qa is also a good place to get help if you are having problems with the sign-up process
    • See and for more information on using IRC
  3. Obtain wiki edit access
    • The Fedora Project Wiki (which is what you are reading from right now) is a useful place to store and retrieve information.
    • Obtaining wiki edit access gives you the ability to contribute too.
  4. Attend a Bug Triage Meeting .