From Fedora Project Wiki

(Dumped Susan's great email)
(Format fixes)
Line 5: Line 5:
 
also make sure they have the ability to close the related bug in
 
also make sure they have the ability to close the related bug in
 
bugzilla.
 
bugzilla.
 +
 
Here's how:
 
Here's how:
1. get a bugzilla account if you do not have one.  https://bugzilla.redhat.com/
+
# get a bugzilla account if you do not have one.  https://bugzilla.redhat.com/
2. make sure the email you list in bugzilla matches the email you list in fas
+
# make sure the email you list in bugzilla matches the email you list in fas
3. request sponsorship to the fas group fedorabugs
+
# request sponsorship to the fas group fedorabugs
4. ask stickster to approve fedorabugs and ask sparks to start
+
# ask stickster to approve fedorabugs and ask sparks to start assigning you bugs :)
assigning you bugs :)
+
# starting fixing and closing bugs.
5. starting fixing and closing bugs.
 
  
 
You do NOT need to own the bug to close it.  When it is closed the
 
You do NOT need to own the bug to close it.  When it is closed the

Revision as of 00:11, 13 May 2009

Some of this is triage work - not a bug or filed in the wrong place. Some is fixing the doc at the source - usually git (or shouldn't be a filed bug)

So - I would suggest that anyone who has write to a doc in git should also make sure they have the ability to close the related bug in bugzilla.

Here's how:

  1. get a bugzilla account if you do not have one. https://bugzilla.redhat.com/
  2. make sure the email you list in bugzilla matches the email you list in fas
  3. request sponsorship to the fas group fedorabugs
  4. ask stickster to approve fedorabugs and ask sparks to start assigning you bugs :)
  5. starting fixing and closing bugs.

You do NOT need to own the bug to close it. When it is closed the assignee and the person that opened the bug will be notified, along with anyone else on the cc list. They will have the option to reopen the bug if they have more information or do not believe it should have been closed.

Do try to be polite and helpful when closing the ancient ones. It is ok to close as the doc is end of life but it is also nice to point out the link to the current version and encourage more review and reporting as needed.