openstack/governance
Code Issues Proposed changes

Use opendev for repository links

Browse Source 
Update the :repo: shorthand role to use opendev instead of cgit links
in project team pages.

Make sure that the other content under the reference/ directory is
updated to use :repo: instead of cgit links (except the one in
pti/javascript.rst which should really point to the NPM package).

Change-Id: I1009ba2a0f8d0fd1dab26f05241903b71c63e4fb
This commit is contained in:
Thierry Carrez 2019-05-10 15:48:31 +02:00
parent 173df219ac
commit 6d0cf799c1
5 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/conf.py
View File

@ -47,7 +47,7 @@ todo_include_todos = True
# Define shorthand roles for making links to common destinations. # Define shorthand roles for making links to common destinations.
extlinks = { extlinks = {
'repo': ('https://git.openstack.org/cgit/%s', ''), 'repo': ('https://opendev.org/%s', ''),
} }
# Add any paths that contain templates here, relative to this directory. # Add any paths that contain templates here, relative to this directory.

3
reference/charter.rst
View File

@ -136,8 +136,7 @@ teams (see
:doc:`/resolutions/20141128-elections-process-for-leaderless-programs`). An :doc:`/resolutions/20141128-elections-process-for-leaderless-programs`). An
email must be sent to the ``openstack-discuss at lists.openstack.org`` mailing email must be sent to the ``openstack-discuss at lists.openstack.org`` mailing
list announcing the change in leadership. A patch must also be submitted to the list announcing the change in leadership. A patch must also be submitted to the
OpenStack `governance repository :repo:`openstack/governance` repository updating the project's
<http://git.openstack.org/cgit/openstack/governance>`_ updating the project's
PTL information in ``projects.yaml``, which must be approved by the TC in order PTL information in ``projects.yaml``, which must be approved by the TC in order
for the appointed candidate to officially assume PTL responsibilities. for the appointed candidate to officially assume PTL responsibilities.

2
reference/pti/javascript.rst
View File

@ -180,4 +180,4 @@ logic needed should go into reno.
.. _NPM package scripts: https://docs.npmjs.com/misc/scripts .. _NPM package scripts: https://docs.npmjs.com/misc/scripts
.. _ESLint: http://eslint.org .. _ESLint: http://eslint.org
.. _eslint-config-openstack: http://git.openstack.org/cgit/openstack/eslint-config-openstack .. _eslint-config-openstack: https://www.npmjs.com/package/eslint-config-openstack

6
reference/service-project-naming.rst
View File

@ -11,9 +11,9 @@ Project Naming Process
---------------------- ----------------------
The Technical Committee reviews the incoming project proposals through the The Technical Committee reviews the incoming project proposals through the
`openstack/governance <http://git.openstack.org/cgit/openstack/governance/>`_ :repo:`openstack/governance` repository with an update to the
repository with an update to the ``doc/source/reference/projects.yaml`` file. ``doc/source/reference/projects.yaml`` file. TC members should review
TC members should review the patches with these guidelines. the patches with these guidelines.
Project Name Guidelines Project Name Guidelines
----------------------- -----------------------

7
reference/tags/vulnerability_managed.rst
View File

@ -100,8 +100,8 @@ Requirements
since it is by necessity a group of constrained size and some since it is by necessity a group of constrained size and some
of its processes simply can't be scaled safely. Finally, the of its processes simply can't be scaled safely. Finally, the
results of the review, audit, or threat analysis must results of the review, audit, or threat analysis must
be proposed as a gerrit review in the security-analysis_ repository. be proposed as a gerrit review in the :repo:`openstack/security-analysis`
and accepted by the OpenStack Security Group (OSSG). Acceptance repository and accepted by the OpenStack Security Group (OSSG). Acceptance
by the OpenStack Security Group (OSSG) of the documentation does by the OpenStack Security Group (OSSG) of the documentation does
not constitute a third party approval unless the OpenStack Security not constitute a third party approval unless the OpenStack Security
Group (OSSG) agrees in advance to acting as a third party approver. Group (OSSG) agrees in advance to acting as a third party approver.
@ -116,9 +116,6 @@ Requirements
disclosure, and also decreases the chance of creating additional disclosure, and also decreases the chance of creating additional
work for the VMT issuing errata later. work for the VMT issuing errata later.
.. _security-analysis: https://git.openstack.org/cgit/openstack/security-analysis/
Tag application process Tag application process
======================= =======================