Merge "Use opendev for repository links"

doc/source/conf.py

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

reference/charter.rst

@@ -136,8 +136,7 @@ teams (see
 :doc:`/resolutions/20141128-elections-process-for-leaderless-programs`). An
 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
-OpenStack `governance repository
-<http://git.openstack.org/cgit/openstack/governance>`_ updating the project's
+:repo:`openstack/governance` repository updating the project's
 PTL information in ``projects.yaml``, which must be approved by the TC in order
 for the appointed candidate to officially assume PTL responsibilities.
 

reference/pti/javascript.rst

@@ -180,4 +180,4 @@ logic needed should go into reno.
 
 .. _NPM package scripts: https://docs.npmjs.com/misc/scripts
 .. _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

reference/service-project-naming.rst

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

reference/tags/vulnerability_managed.rst

@@ -100,8 +100,8 @@ Requirements
    since it is by necessity a group of constrained size and some
    of its processes simply can't be scaled safely.  Finally, the
    results of the review, audit, or threat analysis must
-   be proposed as a gerrit review in the security-analysis_ repository.
-   and accepted by the OpenStack Security Group (OSSG).  Acceptance
+   be proposed as a gerrit review in the :repo:`openstack/security-analysis`
+   repository and accepted by the OpenStack Security Group (OSSG).  Acceptance
    by the OpenStack Security Group (OSSG) of the documentation does
    not constitute a third party approval unless the OpenStack Security
    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
    work for the VMT issuing errata later.
 
-.. _security-analysis: https://git.openstack.org/cgit/openstack/security-analysis/
-
-
 Tag application process
 =======================