Assigning bug to 'me' practice for triagers

[John Vivirito]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I have only recently actively working on bug triaging. I have taken
> the habit, in most case, on an incomplete report, to assign the bug
> on me, as this is suggested to do on:
> https://wiki.ubuntu.com/Bugs/HowToTriage#head-65e5a5e189e28e52756baa61c7cd13b0f8121738
> This is/was making sense to me. The assignee, is the one taking care
> of a bug, RIGHT NOW. As the bug triager is trying to get more
> information before have it ready to be examined by a competent
> developer (confirmed state as I see it), it make sense to have it
> assigned to him. This way, searching for unassigned bug, become a
> reasonable way to find bugs that needs some action on them. It took
> me a number of reading at https://wiki.ubuntu.com/DebuggingUbiquity
> to realize that this is not permitted on Ubiquity: "Please do not
> assign ubiquity bugs to anyone unless you're a ubiquity developer or
> you manage a ubiquity developer." In fact, this message was
> initiated based on extract of Colin Watson, on a parted bug:
> "Unassigning Paul from this bug, unless he actually plans to write
> the code necessary to fix this.". On this particuliar bug, I felt
> relieved, because the reporter was quite annoyed at the way I was
> triaging his bug. I have received a number of such comments, that I
> should not assign a bug to myself as a bug triager. So this email is
> a request to make sure 'HowToTriage bugs's suggestion to assign to
> oneself is right. And if so, see in what case/packages, this would
> be considered bad practice.
> -- http://www.fastmail.fm - Faster than the air-speed velocity of an
> unladen european swallow
Only assign a bug to the person that is gonna fix it. A good way to do
this is to not assign a bug to someone unless that person says to.
Maintainer/ Developer isnt always the person to add patches or fixes.
Triager is not always the person thats gonnd fix the bug a triager is
the user that asks for info, marks dups and so on for the developer.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFQhAwqig4QTwcPCoRAmq6AJ9vIkyZHG2C85EpixGgzHBtAiKqHQCbBpRk
h2hOGw1qScVkFoPGKt3EpPg=
=JZX6
-----END PGP SIGNATURE-----