Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review revisions rep-2004 #243

Merged
merged 1 commit into from
Mar 24, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions rep-2004.rst
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,9 @@ Requirements to be considered a 'Level 1' package:

#. **Platform Support:**

#. Must support all tier 1 platforms for ROS 2, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_
#. Must support all target platforms for the package's ecosystem.

* For ROS 2 this means supporting all tier 1 platforms, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_

If the above points are satisfied then a package can be considered 'Level 1'.
Refer to the detailed description of the requirements below the chart for more information.
Expand Down Expand Up @@ -250,7 +252,7 @@ The chart below compares Quality Levels 1 through 5 relative to the 'Level 1' re
- ✓
- ✓
- ✓
-
-
* - 3.iv
- ✓
- ✓
Expand Down Expand Up @@ -501,7 +503,9 @@ Requirements to be considered a 'Level 2' package:

#. **Platform Support:**

#. Must support all tier 1 platforms for ROS 2, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_
#. Must support all target platforms for the package's ecosystem.

* For ROS 2 this means supporting all tier 1 platforms, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_

If the above points are satisfied then a package can be considered 'Level 2'.
Refer to the detailed description of the requirements following the Quality Level 1 section above for more information.
Expand Down Expand Up @@ -548,7 +552,9 @@ Requirements to be considered a 'Level 3' package:

#. **Platform Support:**

#. Must support all tier 1 platforms for ROS 2, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_
#. Must support all target platforms for the package's ecosystem.

* For ROS 2 this means supporting all tier 1 platforms, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_

If the above points are satisfied then a package can be considered 'Level 3'.
Refer to the detailed description of the requirements following the Quality Level 1 section above for more information.
Expand Down Expand Up @@ -588,7 +594,9 @@ Requirements to be considered a 'Level 4' package:

#. **Platform Support:**

#. May support all tier 1 platforms for ROS 2, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_
#. Must support all target platforms for the package's ecosystem.

* For ROS 2 this means supporting all tier 1 platforms, as defined in `REP-2000 <https://www.ros.org/reps/rep-2000.html#support-tiers>`_

Any package that does not claim to be 'Level 3' or higher is automatically 'Level 4'.
Refer to the detailed description of the requirements following the Quality Level 1 section above for more information.
Expand All @@ -597,7 +605,7 @@ Quality Level 5
^^^^^^^^^^^^^^^

Packages in this category cannot even meet the simple 'Level 4' requirements, and for that reason should not be used.
All packages should have at least a declared license or set of licenses and should include copyright statements in each file.
'Level 5' has no requirements, but we still strongly recommend all packages have a license and copyright statement, ideally in each file.

Repository Organization
^^^^^^^^^^^^^^^^^^^^^^^
Expand Down