Recently in reps Category

NOTE: for discussion, please use the ros-developers list

REP 3: This REP defines target platforms for each ROS Distribution Release. We define platforms to include both operating system releases (Ubuntu Lucid) as well as major language releases (e.g. Python 2.5). The target platforms represent the set on which all stable, released stacks are expected to work. Exceptions can be made for stacks that are intentionally platform-specific.

REP 10: REP 10 outlines the ros-developers voting guidelines. These guidelines serve to provide feedback or gauge the "wind direction" on a particular proposal, idea, or feature. They don't have a binding force. REP 10 is a direct copy of PEP 10 by Barry Warsaw. The Author field of this document has been updated to reflect responsibility for maintenance.

The following REPs have been posted for comment.

• REP 2: Scope of REPs, REP Stacks
• REP 100: ROS Stack Separation
• REP 102: ROS Install Target

To join in on the discussion, please sign up for ros-developers. You can also browse the archives.

ROS was started less than three years ago and much has changed in that short period of time. Now, with over 30 institutions contributing public, open source repositories and over 40 different robots supporting ROS, we recognize that we must make additional efforts to incorporate community feedback into the ongoing development of ROS.

We are adopting a new "ROS Enhancement Proposal" (REP) process to enable members of the community to propose, design, and develop new features for ROS and its core libraries. Thanks to the efforts of the Python community and it's PEP process, we were able to quickly bootstrap this new process.

The process is fairly straightforward. Anyone in the community can author a REP and circulate it to the ros-developers list. An index of REPs is stored in REP 0*, which defines the REP process.

We will soon circulate several REPs for public comment to provide information on current work with ROS. We will also circulate process- and information-type REPs to help better define the REP process.

We invite members of the community to review REP 1 and put together their own REPs for consideration.

* REP 1 is mostly a search-and-replace of PEP 1, so much credit to Barry Warsaw, Jeremy Hylton, David Goodger.