This is a follow-up from a session we held at the 2015 technical operations offsite. It's by no means complete but is a starting point for (re)organizing the tags used for #operations-related work. This follows efforts initially made during the Phabricator move (T1147) as well as a Labs-specific effort earlier this year (T89270).
The current status quo, mostly established due to legacy (imported Bugzilla projects, RT queues and initial Phabricator experimentation) is:
- A couple of team/purple tags (operations, Labs)
- A few project/blue tags (such as Traffic and NetOps)
- Lots of random/inconsistent yellow tags, often technology-specific (e.g. Varnish)
The goal here is to:
- Subdivide #operations work into multiple areas and assign project/blue tags to them, to make them more manageable and triage-able (especially with work boards)
- Move away from technology-specific tags that are often misused or may become legacy (what does "Puppet" mean? what are we going to do with the "Varnish" tag if we switch to another software for our caching proxies?)
To that end, we've assessed the situation as follows:
Team tags:
- operations (keep as is)
- Labs (keep as is)
- DC-Ops (new, will be tagged along all of the ops-$site + procurement tagged tasks)
Existing project tags (keep as is):
- Traffic
- NetOps
- hardware-requests
- ops-eqiad, ops-codfw, ops-ulsfo, ops-esams
- ops-access-requests
- procurement
- OTRS
- dumps-generation
New project tags:
- DBA (convert the old yellow "Database" tag, adjust its description)
- media-storage (convert the old yellow "Swift" tag)
- Monitoring (convert from yellow)
- Mail (convert from yellow)
- pybal (convert from yellow)
- ops-security (new)
- Packaging (new)
- Domains (convert from yellow)
- DNS (rename from Wikimedia-DNS, clarify relationship with "domains")
New umbrella tags:
- Incidents (for all Incidents, superset or possibly replacement for Incident-YYYYMMDD-Description tags)
(please help to complete the list)