-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add design document for ROS 2 Access Control Policies #246
Add design document for ROS 2 Access Control Policies #246
Conversation
If there is no more feedback, perhaps we could merge on this, that reflects the current state, so that we can open a new PR to extend the design to account for proposals on composing nodes and contexts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some wording suggestions.
Content seems reasonable.
@jacobperron , thanks for the wording suggestions. They all looked fine to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good reflection of where things stand today.
The change to the CSS is unrelated to the SROS article and I think would be best to pull out into a separate PR to review. |
Co-Authored-By: Kyle Fazzari <[email protected]>
Co-Authored-By: Daniel Wang <[email protected]>
Co-Authored-By: Jacob Perron <[email protected]>
90fd411
to
23726b4
Compare
I've rebased the PR and opened the syntax highlighting changes to its own PR: #253 |
Thanks for splitting out the PR. LGTM |
As currently used for SROS 2.