[Documentation] [TitleIndex] [WordIndex

If you find an issue with ROS or ROS-related software, or you wish to request a feature, please use the appropriate issue-tracking system to file a ticket:

On a wiki page for a package or stack there should be a link at the bottom pointing to where to file tickets.

Below is a list of common organizations on GitHub for ROS packages.

ROS GitHub Organizations

There are several GitHub organizations which host many of the core ROS packages. Below you will find a list of the most common ones with a quick description of their focus:

logo

ROS Android
Android apps based on ROSJava. Also see ROS Android PR2 and Link to Play Store

logo

ROS Controls
Controllers and interfaces for hardware

logo

ROS Core
Core ROS libraries and tools such as standard messages, the build system catkin, the ROS clients roscpp and rospy, actionlib, pluginlib, nodelet, etc

logo

ROS Drivers
Drivers for sensors and other hardware

logo

ROS Geographic Information
Packages for managing geographic information within ROS

logo

ROS GitBuildPackage (GBP)
Git Build Package style repositories for the release pipeline.

logo

ROS Infrastructure
Foundational tools for ROS ecosystem such as package release (bloom), build farm scripts, documentation generators. Most of these are backend, non-user facing repositories.

logo

ROS Java
The Java ROS client library and tools

logo

ROS Manipulation
Packages relating to manipulation and the manipulation pipeline.

logo

ROS Interactive Manipulation
Packages relating to interactive manipulation and the manipulation pipeline.

logo

ROS Perception
Tools for perception and vision

logo

ROS Planning
Navigation and path planning related packages including navigation and moveit

logo

ROS Robots
Packages to support robots which do not have their own organization. See also PR2 and Turtlebot

logo

ROS Simulation
Simulators for use in ROS

logo

ROS Visualization
Graphical tools to visualize data including rviz and rqt.

A historical list of institutions that have contributed to ROS is available on the repositories page.

It is not required that if you are doing something related to one of these categories that your package be in one of the organization. And every choice of where to put a packages is always a judgement call for most packages could be multiply categorized. The goal of using these organizations is to facilitate maintenance so grouping software by developer communities is often the best way to decide where to host a package.

Guidelines for administering organizations

These are general guidelines for anyone administering a repository with ROS code.

  • All package maintainers should have administrative access to the repositories in which they maintain packages to enable them to process tickets and do their role.
  • All package maintainers should be publicly visible as members of the organization.
  • The main point of contact for the organization should be listed as a public member.

Guidelines for administering ros-* organizations on GitHub

In addition to the general guidelines for administering an organization on GitHub listed above. If the organization is using the ROS name in the ros-* format:

  • The ROS Platform Manager should also be in the Owners group to facilitate handoff's between maintainers should there be a gap.

2017-10-21 12:26