Updated REP links (backport #6016) (#6027)

Signed-off-by: Alejandro Hernandez Cordero <[email protected]>
Co-authored-by: Alejandro Hernández Cordero <[email protected]>

Author: mergify[bot]

source/Concepts/Advanced/About-Build-System.rst

@@ -46,7 +46,7 @@ Parsing of the :term:`package.xml` files is provided by ``catkin_pkg`` (as in RO
 
    package.xml
        Package manifest file which marks the root of a :term:`package` and contains meta information about the :term:`package` including its name, version, description, maintainer, license, dependencies, and more.
-       The contents of the manifest are in machine readable XML format and the contents are described in the |REPs| `127 <http://www.ros.org/reps/rep-0127.html>`_ and `140 <http://www.ros.org/reps/rep-0140.html>`_, with the possibility of further modifications in future |REPs|.
+       The contents of the manifest are in machine readable XML format and the contents are described in the |REPs| `127 <https://reps.openrobotics.org/rep-0127/>`_ and `140 <https://reps.openrobotics.org/rep-0140/>`_, with the possibility of further modifications in future |REPs|.
 
 So anytime some |package| is referred to as an :term:`ament package`, it means that it is a single unit of software (source code, build files, tests, documentation, and other resources) which is described using a :term:`package.xml` manifest file.
 

source/Glossary.rst

@@ -21,10 +21,10 @@ Glossary of terms used throughout this documentation:
        A single unit of software, including source code, build system files, documentation, tests, and other associated resources.
 
    REP
-        ROS Enhancement Proposal.
+        Robotics Enhancement Proposal.
         A document that describes an enhancement, standardization, or convention for the ROS community.
         The associated REP approval process allows the community to iterate on a proposal until some consensus has been made, at which point it can be ratified and implemented, which then becomes documentation.
-        All REPs are viewable from the `REP index <https://www.ros.org/reps/rep-0000.html>`_.
+        All REPs are viewable from the `REP index <https://reps.openrobotics.org/>`_.
 
    VCS
        Version Control System, such as CVS, SVN, git, mercurial, etc...

source/How-To-Guides/Ament-CMake-Documentation.rst

@@ -65,7 +65,7 @@ Compiler and linker options
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 ROS 2 targets compilers which comply with the C++17 and C99 standard.
-Newer versions might be targeted in the future and are referenced `here <https://www.ros.org/reps/rep-2000.html>`__.
+Newer versions might be targeted in the future and are referenced `here <https://reps.openrobotics.org/rep-2000/>`__.
 Therefore it is customary to set the corresponding CMake flags:
 
 .. code-block:: cmake

source/How-To-Guides/Installing-on-Raspberry-Pi.rst

@@ -2,7 +2,7 @@ ROS 2 on Raspberry Pi
 =====================
 
 ROS 2 is supported on both 32 bit (arm32) and 64 bit (arm64) ARM processors.
-However, you can see `here <https://www.ros.org/reps/rep-2000.html>`__ that arm64 receives Tier 1 support, while arm32 is Tier 3.
+However, you can see `here <https://reps.openrobotics.org/rep-2000/>`__ that arm64 receives Tier 1 support, while arm32 is Tier 3.
 Tier 1 support means distribution specific packages and binary archives are available, while Tier 3 requires the user to compile ROS 2 from source.
 
 The fastest and simplest way to use ROS 2 is to use a Tier 1 supported configuration.
@@ -14,7 +14,7 @@ Ubuntu Linux on Raspberry Pi with binary ROS 2 install
 
 Ubuntu for Raspberry Pi is available `here <https://ubuntu.com/download/raspberry-pi>`__.
 
-Make sure to confirm that you have selected the correct version as described in `REP-2000 <https://www.ros.org/reps/rep-2000.html>`__.
+Make sure to confirm that you have selected the correct version as described in `REP-2000 <https://reps.openrobotics.org/rep-2000/>`__.
 
 You can now install ROS 2 using the normal binary installation instructions for Ubuntu Linux.
 
@@ -30,7 +30,7 @@ After flashing the OS, `install Docker <https://docs.docker.com/engine/install/d
 The official ROS 2 Docker images can be found `here <https://hub.docker.com/_/ros/tags>`__.
 
 You may choose from ros-core, ros-base, or perception.
-See `here <https://www.ros.org/reps/rep-2001.html>`__ for more information on these variants.
+See `here <https://reps.openrobotics.org/rep-2001/>`__ for more information on these variants.
 
 Fetch and run an image:
 

source/How-To-Guides/Migrating-from-ROS1/Migrating-CPP-Package-Example.rst

@@ -328,7 +328,7 @@ Require a newer version of CMake so that ``ament_cmake`` functions work correctl
 
    cmake_minimum_required(VERSION 3.14.4)
 
-Use a newer C++ standard matching the version used by your target ROS distro in `REP 2000 <https://www.ros.org/reps/rep-2000.html>`__.
+Use a newer C++ standard matching the version used by your target ROS distro in `REP 2000 <https://reps.openrobotics.org/rep-2000/>`__.
 If you are using C++17, then set that version with the following snippet after the ``project(talker)`` call.
 Add extra compiler checks too because it is a good practice.
 

source/How-To-Guides/Migrating-from-ROS1/Migrating-CPP-Packages.rst

@@ -32,8 +32,8 @@ Require a newer version of CMake
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 ROS 2 relies on newer versions of CMake than used by ROS 1.
-Find the minimum version of CMake used by the ROS distribution you want to support in `REP 2000 <https://www.ros.org/reps/rep-2000.html>`__, and use that version at the top of your ``CMakeLists.txt``.
-For example, `3.14.4 is the minimum recommended support for ROS Humble <https://www.ros.org/reps/rep-2000.html#humble-hawksbill-may-2022-may-2027>`__.
+Find the minimum version of CMake used by the ROS distribution you want to support in `REP 2000 <https://reps.openrobotics.org/rep-2000/>`__, and use that version at the top of your ``CMakeLists.txt``.
+For example, `3.14.4 is the minimum recommended support for ROS Humble <https://reps.openrobotics.org/rep-2000/#humble-hawksbill-may-2022-may-2027>`__.
 
 .. code-block::
 

source/How-To-Guides/Migrating-from-ROS1/Migrating-Package-XML.rst

@@ -5,7 +5,7 @@ Migrating your package.xml to format 2
    :depth: 2
    :local:
 
-ROS 2 requires ``package.xml`` files to use at least `format 2 <https://ros.org/reps/rep-0140.html>`__.
+ROS 2 requires ``package.xml`` files to use at least `format 2 <https://reps.openrobotics.org/rep-0140/>`__.
 This guide shows how to migrate a ``package.xml`` from format 1 to format 2.
 
 If the ``<package>`` tag at the start of your ``package.xml`` looks like either of the following, then it is using format 1 and you must migrate it.
@@ -29,7 +29,7 @@ Migrate from format 1 to 2
 --------------------------
 
 Format 1 and format 2 differ in how they specify dependencies.
-Read the `compatibility section in REP-0140 <https://www.ros.org/reps/rep-0140.html#compatibility>`__ for a summary of the differences.
+Read the `compatibility section in REP-0140 <https://reps.openrobotics.org/rep-0140/#compatibility>`__ for a summary of the differences.
 
 Add ``format`` attribute to ``<package>``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/How-To-Guides/Releasing/Index-Your-Packages.rst

@@ -28,7 +28,7 @@ If the ROS packages in your repository have different licenses, create a ``LICEN
 
 Give your packages REP 144 compliant names
 ------------------------------------------
-Packages released into a ROS distribution must have names that comply with `REP 144 <https://www.ros.org/reps/rep-0144.html>`__.
+Packages released into a ROS distribution must have names that comply with `REP 144 <https://reps.openrobotics.org/rep-0144/>`__.
 Read the full REP to understand the rules.
 If one of your ROS package names doesn't comply, then change the name before continuing.
 
@@ -79,7 +79,7 @@ Here's how to fill out each item:
 * YOUR-BRANCH-NAME: This is the git branch on your repository from which you will release your package into this ROS distribution.
   This is commonly one of: ``main``, ``master``, or the name of the ROS distribution itself.
   For example, the `rosidl repository <https://github.com/ros2/rosidl>`__ uses the branch ``rolling`` to hold changes to be released into ROS Rolling.
-* YOUR-STATUS: This is a status from the list in `REP 141 <https://www.ros.org/reps/rep-0141.html#distribution-file>`__.
+* YOUR-STATUS: This is a status from the list in `REP 141 <https://reps.openrobotics.org/rep-0141/#distribution-file>`__.
   You likely want either ``maintained`` or ``developed``.
 
 Open a pull request to ros/rosdistro

source/How-To-Guides/Releasing/Release-Team-Repository.rst

@@ -61,7 +61,7 @@ Create a new release repository
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro <https://github.com/ros/rosdistro>`_ adding a ``source`` entry for your repository (e.g. https://github.com/ros/rosdistro/pull/39513).
-The review process for the rosdistro database will ensure your repository and packages conform to the `REP 144 package naming conventions <https://www.ros.org/reps/rep-0144.html>`_ and other requirements before release.
+The review process for the rosdistro database will ensure your repository and packages conform to the `REP 144 package naming conventions <https://reps.openrobotics.org/rep-0144/>`_ and other requirements before release.
 Once your package name has been approved and merged, fill in the `Add New Release Repositories issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_repository.md&title=Add+new+release+repositories>`_ issue template
 if you don't have a release repo for your project yet.
 

source/How-To-Guides/Releasing/Releasing-a-Package.rst

@@ -20,7 +20,7 @@ Releasing a Package
 **Releasing a package makes your package available on the public ROS 2 buildfarm.**
 This will:
 
-* Make your package available to be installed via package managers (e.g. ``apt`` on Ubuntu) for all supported Linux platforms in a ROS distribution as described in `REP 2000 <https://ros.org/reps/rep-2000.html>`_.
+* Make your package available to be installed via package managers (e.g. ``apt`` on Ubuntu) for all supported Linux platforms in a ROS distribution as described in `REP 2000 <https://reps.openrobotics.org/rep-2000/>`_.
 * Allow your package to have API documentation automatically generated.
 * Make your package part of the `ROS Index <https://index.ros.org>`_.
 * (Optionally) Allow you to have automatic CI run for pull requests in your repository.