-
Notifications
You must be signed in to change notification settings - Fork 3
Draft REP for ros2log new CLI development.
#20
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Tomoya.Fujita <Tomoya.Fujita@sony.com>
|
@gbiggs since this is 1st REP 🥇 ??? aligned with new process https://reps.openrobotics.org/rep-0001-2025/, i probably may miss something in this. if you find anything missing here, please let us know 🙇 |
Signed-off-by: Decwest <fumiyaonishi1016@gmail.com>
|
according to https://reps.openrobotics.org/rep-0001-2025/#step-3-move-the-rep-to-draft-rep-status, what i need to do is to allocate the REP number and assign it on this PR. then after the approval, we can merge this draft REP and proceed to discussion https://reps.openrobotics.org/rep-0001-2025/#step-4:-discuss-the-draft-rep |
Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com>
Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com>
|
according to https://github.com/ros-infrastructure/rep/pulls, i say next REP number is going to be |
This is standard REP for
ros2lognew CLI enhancement, related to ros2/ros2cli#1148after this PR is merged, it requires discussion and feedback via OpenRobotics ROS Discourse to refine the REP, see more details for https://reps.openrobotics.org/rep-0001-2025/#step-4:-discuss-the-draft-rep.