Ops Tags Team
Moderators: Tim Bell, Jonathan Proulx, Subbu Allamaraju, Tom Fifield
A team to define tags for ops, allowing users to make better decisions by providing useful information about OpenStack software projects.
- Induct and coordinate volunteers to achieve the objectives of the team.
- Manage the process for adding new tags in the ops:* namespace.
- Manage any disputes related to ops:* tag value assignment
- Continuously assess ops:* tag values as projects change.
- Conduct the ops:* tag assessment for new projects as they are released.
- email@example.com - can help think of tags, organise meetings, and also validate tags against projects
- firstname.lastname@example.org - would like to contribute mainly on how to map some tags to software development metrics
How To Join
- Put your name above, subscribe to the OpenStack Ops Mailing List and participate in threads that have [tags] in the subject line,
- Make a contribution directly to the ops-tags-team repository: http://git.openstack.org/cgit/openstack/ops-tags-team
- Review proposed tags at https://review.openstack.org/#/q/status:open+project:openstack/ops-tags-team,n,z
Ops Tags team meets approximately monthly on IRC, in addition to meetings at the summits and at mid-cycle ops events - stay tuned to the OPS ML for announcements.
- Meetings slots are every second Thursday at 1400 UTC in #openstack-meeting on freenode (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150702T1400 )
Previous meeting nodes:
What are Tags?
- Explained at a high level in http://ttx.re/the-way-forward.html
- When applied to a project, Tags are comprised of a name (eg "Ops:Deployment-Widespread", "Ops:Config-Recipes-Available", "Ops:Packaged"), a value (eg "92%", "yes", "Ubuntu, Redhat and SUSE") and if applicable a description of why the project has that value.
- Particularly, any tag that is not a 'perfect' result should have a bug report or some other information on steps to fix it
- All tags are advisory only. They're RFC-style: IETF, not IEEE :)
- Tags should easily facilitate caveats. Eg due to 2011 Tohoku earthquake, SmartTraveller lists Japan as still fine to visit, but has a sub-note saying "Fukushima area: do not travel" (http://smarttraveller.gov.au/zw-cgi/view/Advice/Japan ). For example, for a tag related to neutron, maybe neutron itself is fine but there might be some special thing about the linuxbridge driver that is important to note.
- Early tags we're starting with should be simple and non-controversial. There is great potential to define more subjective tags, however these should be left until after the first set are completed.
- The lack of a particular tag should not be a barrier to someone using the code
How To Dispute a Tag Application
If you feel a tag managed by this team has been applied wrongly, please email the OpenStack Ops Mailing List with [tags] in the subject line to state the reasoning. If you feel uncomfortable having this discussion on a mailing list, or feel that escalation is required, please email email@example.com or any of the user committee members