Merge pull request #21252 from ros/tfoote-rosdep-sources

Define which sources are valid for rosdep keys

CONTRIBUTING.md

@@ -65,6 +65,59 @@ Guidelines for rosdep rules
   * Keep everything in alphabetical order for better merging.
   * No trailing whitespace.
 
+### Expected Rosdep Sources
+
+Keys in the rosdep database are required to come from packages contained in the following repositories only.
+
+#### Ubuntu
+
+* Ubuntu Repositories: Main, Universe, or Multiverse
+* ROS Sources: https://wiki.ros.org/Installation/Ubuntu/Sources
+
+#### Debian
+
+* Debian Repositories: Main, Universe, or Multiverse
+* ROS Sources: https://wiki.ros.org/Installation/Ubuntu/Sources
+
+#### Fedora
+
+* Fedora Project Repositories: release or updates
+
+#### RHEL/CentOS
+
+* CentOS Repositories: base, extras, centos-sclo-rh, or updates
+* Fedora Project Repositories: epel
+
+#### MacOS
+
+TODO
+
+#### Gentoo
+
+* Gentoo Portage Repository (e.g. `rsync://rsync.us.gentoo.org/gentoo-portage`)
+* ROS-Overlay: `https://github.com/ros/ros-overlay`
+
+If the ebuild you are referencing is not in either of those locations, please
+file a PR into ROS-Overlay to add it and any needed dependencies to the tree.
+
+#### Arch Linux
+
+Packages must be in the official Archlinux core, extra, or community repositories at the time they are contributed.
+
+Packages in the AUR may not be added directly.
+Work has been proposed to add a separate installer for AUR packages [ros-infrastructure/rosdep#560](https://github.com/ros-infrastructure/rosdep/issues/560).
+
+#### Alpine Linux
+
+* Alpine Linux requires the [`edge`](https://wiki.alpinelinux.org/wiki/Edge#Upgrading_to_Edge) release and [`testing`](https://wiki.alpinelinux.org/wiki/Aports_tree#testing) aports branch.
+
+#### pip
+
+For pip installers they are expected to be in the main pypi index.
+
+#### 
+
+
 ### Python 3 rules
 
 When adding rules for python 3 packages, create a separate entry prefixed with `python3-` rather than `python`