Firefox OS/BlockerFlags

< Firefox OS
Revision as of 13:25, 1 February 2015 by Lakrits (talk | contribs) (Lakrits moved page FirefoxOS/BlockerFlags to Firefox OS/BlockerFlags: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling of its name is consistent with the content...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Blocker Flags for Users

Summary

This page shows to add/remove blocker flags for a given user.

Blocker flag management is important: People who have the ability to flip that flag are able to make go/no-go decisions for the product.

History tl;dr: Damon Sicore was driving the "Kilimanjaro" initiative which had a "Basecamp" goal, which introduced the idea of a Bugzilla flag that is project-wide. That means that the flag applied *across* the Product field options in Bugzilla. A project field was created for B2G (Firefox OS) once it transitioned from Github's issue tracking system to Bugzilla, called blocking-b2g. Most people are familiar with the flag's use since that point.

Mechanics: The ability to edit project flags is enabled by adding a Bugzilla user the "kilimanjaro-drivers" group. Bugzilla users with the "editusers" privilege in Bugzilla can add/remove people from this group.

HOWTO