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.
Contents
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:
|
ROS Android |
|
|
|
ROS Controls |
|
|
|
ROS Core |
|
|
|
ROS Drivers |
|
|
|
ROS Geographic Information |
|
|
|
ROS GitBuildPackage (GBP) |
|
|
|
ROS Infrastructure |
|
|
|
ROS Java |
|
|
|
ROS Manipulation |
|
|
|
ROS Interactive Manipulation |
|
|
|
ROS Perception |
|
|
|
ROS Planning |
|
|
|
ROS Robots |
|
|
|
ROS Simulation |
|
|
|
ROS Visualization |
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.
