Bugzilla Keyword Standardization Proposal

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bugzilla Keyword Standardization Proposal

Marc Schifer

We in QA have been discussing ways to help improve our workflows and provide some standardization across the teams in how we use Bugzilla. As part of this process we have come up with a proposal to make a small change to the definition of qawanted keyword and the addition of a new keyword qaurgent

Please read the proposal linked below and give us your feed back.

https://wiki.mozilla.org/QA/qawanted_proposal

Marc S.

_______________________________________________
dev-planning mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-planning
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Keyword Standardization Proposal

Alexander Keybl
Sounds good to me. Will bring consistency across the products w/r/t qawanted. I also appreciate the ability to nominate a priority within your queue through qaurgent - thanks.

-Alex

On Jun 25, 2013, at 2:58 PM, Marc Schifer <[hidden email]> wrote:

>
> We in QA have been discussing ways to help improve our workflows and provide some standardization across the teams in how we use Bugzilla. As part of this process we have come up with a proposal to make a small change to the definition of qawanted keyword and the addition of a new keyword qaurgent
>
> Please read the proposal linked below and give us your feed back.
>
> https://wiki.mozilla.org/QA/qawanted_proposal
>
> Marc S.
>
> _______________________________________________
> dev-planning mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-planning

_______________________________________________
dev-planning mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-planning
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Keyword Standardization Proposal

Axel Hecht
In reply to this post by Marc Schifer
On 6/25/13 11:58 PM, Marc Schifer wrote:
> We in QA have been discussing ways to help improve our workflows and provide some standardization across the teams in how we use Bugzilla. As part of this process we have come up with a proposal to make a small change to the definition of qawanted keyword and the addition of a new keyword qaurgent
>
> Please read the proposal linked below and give us your feed back.
>
> https://wiki.mozilla.org/QA/qawanted_proposal
>
> Marc S.
>
Sounds very reasonable.

I only have one nit, qaurgent doesn't read as "qa urgent" to me. maybe
use qa-urgent? Not sure if that had negative effects on queries. Oddly
enough, I don't have that parsing problem with qawanted. Maybe a
cultural thing of 'au' being a common thing in German. I wouldn't know
of a word where it'd be split across syllables.

Axel
_______________________________________________
dev-planning mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-planning
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla Keyword Standardization Proposal

marcussaad
My thoughts on this proposal:

When joining the community as a developer, learning how the keywording process works was quite confusing and intimidating. The fear of flagging something wrong and making people waste their time was something that freaked me out. I strongly agree with this proposal when it tackles ambiguity. By making things clearer, we make it better.
Now that I'm moving to QA, I'll go through that process again, and this proposal fixes many of the issues I had in my head already.

As Axel said, "qaurgent" is also confusing for a pt-br speaker and also for other languages as we use "ua, ue, ui" in several words. My eyes (or brain?) keeps trying to swap the letters to make something that is familiar to me. Adopting "qa-urgent" would not follow the pattern (if that is a must, we could also change qawanted to "qa-wanted"), but it's way more readable.

Third and last, it will be need to raise awareness on every team so that proper use of these new mechanisms are being used properly. IMO, the key to success here is to have the widest adoption possible.

~msaad