I'm kind of the only one working on that component, and roc agrees that I should have the required privileges to set blocking flags on that component... To state the obvious, my bugzilla user name is firstname.lastname@example.org. Thanks!
We can't do component-level permission granting for the blocking flag. We can give you access to set the blocking2.0 flag in general, but it'll be Bugzilla-wide. Also, need roc or some other driver (generally it's beltzner/damons/shaver/etc.) to approve this in the bug.
roc, if you agree, can you please vouch for me here?
I approve, but I may not be high enough level for this. Beltzner, will you approve?
Yeah, it's fine. I would give Ehsan the usual spiel about how with the authority comes the responsibility (don't approve risky things, only block on real blockers), and the tacit understanding that product drivers are always willing to give a second opinion ... but he knows that already ;)
The following changes have been made to the user account email@example.com: The account has been added to the mozilla-next-drivers group.
Assignee: nobody → reed
Status: NEW → RESOLVED
Last Resolved: 8 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Thanks! I'll make sure to not misuse my new powers. :-)
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.