From Fedora Project Wiki
(drop the 'obtain wiki access' bit, as it had no links, and anyone with a FAS account has 'wiki access'...)
(→‎Important Account Signups: clarify after Oleg was confused)
Line 8: Line 8:
#* 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
#* Note that this is all you need to start ''reporting'' bugs, but if you also want to triage, then you will also need to...
# Obtain a [[Account_System|  Fedora Account]]  
# Obtain a [[Account_System|  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
#* It is necessary that the e-mail address used for your Bugzilla and Fedora accounts are the same
# 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. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient.
# 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. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient.  After your approval, you will have additional permissions in the system which will allow you to triage bugs.
# 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

Revision as of 19:30, 24 February 2009

Joining the BugZappers

Important Account Signups

  1. Obtain a bugzilla account in Red Hat's Bugzilla
  2. Obtain a Fedora Account
    • 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. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient. After your approval, you will have additional permissions in the system which will allow you to triage bugs.
  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. See IRCSetup and IRCHowTo for more information on using IRC
    • The main IRC channels to join are: #fedora-bugzappers - where team members discuss things - and #fedorabot - where you will see automated messages when new bugs are filed (among other things)
    • Once you are all setup and ready to go drop by and say hello on #fedora-bugzappers
    • #fedora-bugzappers is also a good place to get help if you are having problems with the sign-up process
  3. Attend a Bug Triage Meeting. Details on the time and location of meetings are on that page