Working on bugs
Christopher Antila
crantila at fedoraproject.org
Wed Apr 30 01:50:52 UTC 2014
-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBCgAGBQJTYFcAAAoJEAWCcTQ3FNFMTTEQAJL4yriuxSBS5QrCFQ48Q357
AiCIQtlfX4mzeuanyBF+UcrtmEii2qaaH2subwcvta+hejJtj9IcpF9Ew6hXqLRT
+aWNGZbpjsG9HbfQRtxTWtwo5orXpgBmr8rYlyK3qdsUM7F1oUSzN2mn349kifG0
64hbsbV0zNvHRk/GpjZiaoEpOCn67D2EidTENUSJJMRSgAdyJRZ1uolkXlB97NAj
Nq0OcxtQsEZKu47MJBFsCCAnUA14Ogos9WA+POIyOEzkUJjoWx8EnF++OjlGEaqc
0oVDtF04jbwgRLMSCCY4o8HF5QNRY3hWFgLAP8dzQmGEYcabEj/ZS2bJMy4+nHsd
UMxmMQRlWHy+dtNlCmBBlHzKDN7eYjNJN1PWneft5h7uYFRdl7rw/lLMSAZwIVq6
uyX4OEINRVKG5shJ9GjTxl6gu8CJ0U+Cj6v17XUKuQB/LIOupbC8HQKnl5M0daTY
7RCwN36o7LF7/3Qo12Is5/eY0GsFExMdpNgUDnnBpJ638RU0cGa/XoHGVsfvldlj
foMr60/hefcYuxyja5oHhKYnAxTLJWzdqiwRhwb/6cwrA2dWWsK96IzIzpKWUY8l
a3g1qiJBzrq7vj4WYvS8Zo2yDpW+20DAk37yrYHy/E9KEUs8w3c3xs4lgBc9FNZw
MiFsuasy6zOD2OfjtszR
=WU9d
-----END PGP SIGNATURE-----
More information about the docs
mailing list