Hello,
I saw from this week's Docs Meeting logs that there was a discussion about the number of open bugs in BZ. I would like to help reduce this number but first I would welcome some guidance about the etiquette around picking bugs to work on. I have read the wiki page Fixing Documentation Bugs [1] and it says I should choose a bug, assign it to myself and update its status to ASSIGNED. Almost all of the open Fedora documentation bugs list a named Assignee, even those with status NEW and not ASSIGNED. Does BZ automatically list an Assignee for new bugs, based on the Product and Component? Is it OK to assign to myself any bug ticket with status NEW? What are the accepted practices here?
Thanks, Simon
[1] https://fedoraproject.org/wiki/Fixing_documentation_bugs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Simon:
On 29 April 2014 22:24:24 Simon Clark wrote:
I saw from this week's Docs Meeting logs that there was a discussion about the number of open bugs in BZ. I would like to help reduce this number but first I would welcome some guidance about the etiquette around picking bugs to work on. I have read the wiki page Fixing Documentation Bugs [1] and it says I should choose a bug, assign it to myself and update its status to ASSIGNED. Almost all of the open Fedora documentation bugs list a named Assignee, even those with status NEW and not ASSIGNED. Does BZ automatically list an Assignee for new bugs, based on the Product and Component? Is it OK to assign to myself any bug ticket with status NEW? What are the accepted practices here?
Thanks for volunteering to help!
You're right about how Bugzilla automatically assigns someone to a bug when it's submitted. In Fedora Docs, I think we try to be proactive, so you're probably safe in assigning yourself to a bug that interests you. When you make this change, Bugzilla will notify the previous assignee by email, which should prompt them to complain if they choose. You may also wish to comment on the bug, saying that you intend to fix it, and asking if anybody else has started thinking about or writing a fix.
Basically, as long as a guide's maintainer is aware of what you're doing (or should reasonably be aware), you can make any changes you wish. We can always use git to undo or revise the changes, if required.
Have fun!
Christopher
On Tue, 2014-04-29 at 21:50 -0400, Christopher Antila wrote:
Hi Simon:
On 29 April 2014 22:24:24 Simon Clark wrote:
I saw from this week's Docs Meeting logs that there was a discussion about the number of open bugs in BZ. I would like to help reduce this number but first I would welcome some guidance about the etiquette around picking bugs to work on. I have read the wiki page Fixing Documentation Bugs [1] and it says I should choose a bug, assign it to myself and update its status to ASSIGNED. Almost all of the open Fedora documentation bugs list a named Assignee, even those with status NEW and not ASSIGNED. Does BZ automatically list an Assignee for new bugs, based on the Product and Component? Is it OK to assign to myself any bug ticket with status NEW? What are the accepted practices here?
Thanks for volunteering to help!
You're right about how Bugzilla automatically assigns someone to a bug when it's submitted. In Fedora Docs, I think we try to be proactive, so you're probably safe in assigning yourself to a bug that interests you. When you make this change, Bugzilla will notify the previous assignee by email, which should prompt them to complain if they choose. You may also wish to comment on the bug, saying that you intend to fix it, and asking if anybody else has started thinking about or writing a fix.
Basically, as long as a guide's maintainer is aware of what you're doing (or should reasonably be aware), you can make any changes you wish. We can always use git to undo or revise the changes, if required.
Have fun!
Christopher
Hi Christopher,
Thanks for the explanation.
Simon