Add repository for the User Committee's ops tags team

As discussed[0] at the summit, the ops tags team[1] of the user
committee[2] will conduct its initial development of tags
in a git repository using the gerrit process while the
discussions around where they will eventually end up (both
file-wise and display-wise) are conducted.

This patch adds a blank repo and standard ACLs to
achieve this objective.

[0] https://etherpad.openstack.org/p/YVR-ops-tags
[1] https://wiki.openstack.org/wiki/Operations/Tags
[2] https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups

Change-Id: I2daf3569f7973c7a0ff750fc31f0778d6ccaeb09

gerrit/acls/stackforge/ops-tags-team.config

@@ -0,0 +1,11 @@
+[access "refs/heads/*"]
+abandon = group ops-tags-team-core
+label-Code-Review = -2..+2 group ops-tags-team-core
+label-Workflow = -1..+1 group ops-tags-team-core
+
+[receive]
+requireChangeId = true
+requireContributorAgreement = true
+
+[submit]
+mergeContent = true

gerrit/projects.yaml

@@ -2003,6 +2003,8 @@
   description: Openstackdroid is an Android application to access OpenStack clouds
 - project: stackforge/openvz-nova-driver
   description: OpenVz driver for Nova
+- project: stackforge/ops-tags-team
+  description: Work of the User Committee's Ops Tags Team.
 - project: stackforge/os-ansible-deployment
   description: Ansible playbooks for deploying OpenStack.
   groups:

zuul/layout.yaml

@@ -6362,6 +6362,11 @@ projects:
       - name: merge-check
       - name: noop-jobs
 
+  - name: stackforge/ops-tags-team
+    template:
+      - name: merge-check
+      - name: noop-jobs
+
   # note that these jobs use an in-repo script for execution
   # in order to cater for differing requirements per branch
   - name: stackforge/os-ansible-deployment