Repository navigation
Conversation
Filling in more motivation and notes talking with cottsay fill in test cases more completely rep-2015: specify generic binary package name transformation and reverse resolution (#31) Signed-off-by: Federico Rossi <federico.rossi@creativa77.com.ar> Rename to 159:2026 Signed-off-by: Tully Foote <tullyfoote@intrinsic.ai>
tfoote
force-pushed
the
rosdistro_extension
branch
from
September 17, 2026 04:31
642e13e to
01c4eed
Compare
gbiggs
requested changes
Sep 17, 2026
| date: 2026-01-04 | ||
| Requires: REP-0141, REP-0143 | ||
| # Maybe supercedes versus requires one of the above Depends on results | ||
| Created: 2038-08-19 |
| title: ROS Distribution Extnsions | ||
| author: Tully Foote <tullyfoote@intrinsic.ai> | ||
| PMC Sponsor: None | ||
| PMCs: Infrastructure, ROS |
Contributor
There was a problem hiding this comment.
I wonder if just Infra is enough for this one.
| REP: 159 | ||
| title: ROS Distribution Extnsions | ||
| author: Tully Foote <tullyfoote@intrinsic.ai> | ||
| PMC Sponsor: None |
Contributor
There was a problem hiding this comment.
You need a sponsor before this can be a draft.
| --- | ||
| layout: post | ||
| REP: 159 | ||
| title: ROS Distribution Extnsions |
Contributor
There was a problem hiding this comment.
Suggested change
| title: ROS Distribution Extnsions | |
| title: ROS Distribution Extensions |
Rather than a generic "extensions", I think this would be better explicitly stating what the REP enables.
| layout: post | ||
| REP: 159 | ||
| title: ROS Distribution Extnsions | ||
| author: Tully Foote <tullyfoote@intrinsic.ai> |
Contributor
There was a problem hiding this comment.
Make sure all authors are in CODEOWNERS.
| ## Motivation | ||
|
|
||
| The goal of this extension is to enable projects to collaborate together more easily. | ||
| I will flesh out two primary use cases. |
Contributor
There was a problem hiding this comment.
Suggested change
| I will flesh out two primary use cases. | |
| We will flesh out two primary use cases. |
Comment on lines
+308
to
+323
| ## How to use the template | ||
|
|
||
| Follow these steps to use the template and begin drafting your proposed REP. | ||
|
|
||
| 7. Add the full URL to all relevant discussion threads on the Open Robotics Discourse to the `Discussion` field. | ||
| Do not use link shorteners. | ||
| If no discussion thread yet exists, use `Pending` for this field, but remember to update the field with the discussion thread links once they become available, or your REP will not be accepted. | ||
| 12. Fill in the `Supersedes` field, if your REP will make one or more existing Finalized REPs obsolete. | ||
| 13. Write the Abstract, Motivation, Specification, Rationale, and any other necessary sections for your REP. | ||
| Replace all the existing text from the original file with your own. | ||
| 14. Create a pull request against the [REPs repository](https://github.com/openrobotics/reps) to add your REP as a draft. | ||
|
|
||
| Other than the Header, which must be in [RFC 2822](https://datatracker.ietf.org/doc/html/rfc2822.html) format, all content in the REP’s source Markdown file must comply with the [GitHub Flavored Markdown Specification](https://github.github.com/gfm/). | ||
| Within the file, lines must not be wrapped, and each sentence must start on a new line (i.e. each sentence is on its own line). | ||
| This is necessary to ensure pull request diffs are sufficiently readable. | ||
|
|
Contributor
There was a problem hiding this comment.
Suggested change
| ## How to use the template | |
| Follow these steps to use the template and begin drafting your proposed REP. | |
| 7. Add the full URL to all relevant discussion threads on the Open Robotics Discourse to the `Discussion` field. | |
| Do not use link shorteners. | |
| If no discussion thread yet exists, use `Pending` for this field, but remember to update the field with the discussion thread links once they become available, or your REP will not be accepted. | |
| 12. Fill in the `Supersedes` field, if your REP will make one or more existing Finalized REPs obsolete. | |
| 13. Write the Abstract, Motivation, Specification, Rationale, and any other necessary sections for your REP. | |
| Replace all the existing text from the original file with your own. | |
| 14. Create a pull request against the [REPs repository](https://github.com/openrobotics/reps) to add your REP as a draft. | |
| Other than the Header, which must be in [RFC 2822](https://datatracker.ietf.org/doc/html/rfc2822.html) format, all content in the REP’s source Markdown file must comply with the [GitHub Flavored Markdown Specification](https://github.github.com/gfm/). | |
| Within the file, lines must not be wrapped, and each sentence must start on a new line (i.e. each sentence is on its own line). | |
| This is necessary to ensure pull request diffs are sufficiently readable. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is being actively prototyped and developed and we have our first demonstrations of source based extensions working. And are working on binary support.
I'm proposing this to be added as a draft now to increase visibility and enable broader community discussion and feedback now that we're confident that the overall concept can work.