got it, thanks.
Thanks everyone for attending today!
Video: https://www.youtube.com/watch?v=cio-5RkllzA
Notes: https://docs.google.com/document/d/1UXWaEkT6ji0Z0uTtJJSni5Y6fiopM9qOOzv4ldeNaAM/edit#
For the next 4 weeks we’ll be focusing on stability and QA for WG-owned projects leading into Foxy, there is no new feature work planned for this period.
At the end of this coming month, around the time of the Foxy release, we are planning to do a different sort of meeting on 5/22 to prioritize big feature work and decide what new directions we want to take in aiming at G-turtle.
The next meeting will be 5/8
Hello everyone!
We will be canceling the 5/22 Tooling Working group meeting tomorrow at 9 am pacific time. (Sorry for the late notice!)
The “prioritize big feature work and new directions” discussion will happen in the next meeting on 6/5 instead.
Thanks everyone for your continued interest and I look forward to seeing you at the next meeting ON Foxy launch day!
Hey all,
I just realized we’ve been a little quiet on Discourse! The meeting is continuing as planned today at 9 am pacific (half an hour).
As always you can find the notes/agenda here https://docs.google.com/document/d/1UXWaEkT6ji0Z0uTtJJSni5Y6fiopM9qOOzv4ldeNaAM/edit#
This one is our “big ideas day”, we plan to discuss what the high level goal is for the WG going toward the next ROS 2 release, and dig down into what projects we want to take on based on that.
- https://chime.aws/1558235226
- Meeting ID: 1558 23 5226
Great meeting today everyone!
Recording: https://www.youtube.com/watch?v=AmbQ-X1o6Dc
High level - we discussed where we’d like to go with how we run the working group, and what we work on. We seem to have settled on taking backlog management as one primary responsibility. For the projects that we monitor, though we may not have enough developers to implement everything, we would like to present a very clear, prioritized, and up-to-date backlog to invite contributions, and direct our own development.
Additionally, Adam gave us an overview of his investigation into rosbag2 performance, which is looking extremely valuable. This is one of the areas that will be very important moving forward in ROS 2.
Lastly, we will not have a meeting on July 3 because most of us have the day off work for the 4th of July weekend. We’re considering a new recurring time for the WG anyways (Tuesday or Wednesday, probably), keep an eye out here for a survey to inform what we choose.
I am really interested in statistics which AWS team’s been working on with big effort. Is this feature related and discussed in this Tooling WG. if that so, i’d like to join. but it is kinda hard to join from the pacific time… no pressure, i do understand someone needs to take that burden anyway.
I did go through the record quickly,
Diagnostics with topic statistics.
about statistics, i will be in tough via github.
Hi @tomoyafujita, yes some of the work on topic statistics has been discussed in the Tooling WG meeting, and one of the libraries involved belongs to the WG. I would like to help you some meetings, but like you said it is difficult to schedule when including North America, Europe, and Asia. One idea - we could have a “breakout session” for this specific topic, I have been interested in trying to schedule some more of these. If most of the interest is in US and Japan time for a particular session, then we could find a reasonable time. Let’s keep thinking about this.
1 Like
To update this thread about the meeting status, we have the “rosbag2 performance” breakout meeting coming up in a few hours 2020-07-10T16:00:00Z It’s on the ROS events calendar and uses the same Chime room as the usual Tooling WG meetings.
The last meeting ended up not happening due to July 4 holiday in the US - the next meeting will happen as regularly scheduled on July 17. The main topic of discussion will be “How best to manage and present the roadmap/backlog for the working group?” - we’d like to continue encouraging more contribution to these projects, and making these priorities as clear as possible should help. So, that meeting may end up being largely backlog triage.
that makes sense to me, anyway i will try to participate in the next WG.
Hey all, just a reminder that tomorrow’s meeting is on as scheduled - 2020-07-17T16:00:00Z
The primary focus for the meeting will be WG backlog management. We have not done very well so far at keeping the backlog clean and usable, so we’ll be discussing process for keeping it in shape, and triage as many tickets as we can get to.
Top priorities within this focus are 1) surfacing bug reports and 2) collecting rosbag2 performance issue tickets
Cheers!
1 Like
Thanks everybody for attending Friday’s meeting.
The recording can be found at https://youtu.be/7VTuLuNA7Ok
The notes at https://docs.google.com/document/d/1UXWaEkT6ji0Z0uTtJJSni5Y6fiopM9qOOzv4ldeNaAM/edit#
Summary:
- We mainly discussed management of the WG backlog, beginning to get a better handle on identifying and clarifying the most important issues.
- Based on the success of the rosbag2 performance breakout - we would like to schedule alternating meetings to discuss/present specific topics relevant to the WG. We will use the entire time of the existing meetings to focus on the backlog and housekeeping. This way we have enough time to get to everything.
In the interest of clearly communicating roadmap and priorities to the community - here is the WG backlog. The “Backlog” column is a relative indicator of what the WG has identified as top priorities https://app.zenhub.com/workspaces/ros-2-tooling-working-group-5dc4f36af1b75b0001fb7c8d/board?repos=159832509,215937578,220127671,215920213,216100324,217394247,218648031,215863494,215879926,127306752,227492521,216679256,255456651&showPRs=false
Additionally we wanted to present the following “bounty list” of important items - these do not have a commitment by the WG to start work before the next meeting. Any interested parties, please comment directly on the tickets 
* https://github.com/ros2/rosbag2/issues/437 (enhancement - allow passing arbitrary configuration to the storage implementation - specificallly to allow for configuring SQLite to start)
* https://github.com/ros2/rosbag2/issues/424 (enhancement - cache a specified amount of recording time rather than number of messages)
* https://github.com/ros2/rosbag2/issues/39 (usability - clean up files if rosbag2 exits before recording any messages)
2 Likes
I’ve put up the last WG meeting from last week in the usual place: https://www.youtube.com/watch?v=W-bHv7JN5Qs
We discussed starting regularly scheduled breakout sessions. I did not personally get any materials prepared for tomorrow, and have not had any proposals for a different conversation, so we will not have a meeting tomorrow. Anybody who does have a topic they’d like to discuss in a dedicated WG meeting, please let us know here or propose it on the running document https://docs.google.com/document/d/1UXWaEkT6ji0Z0uTtJJSni5Y6fiopM9qOOzv4ldeNaAM/edit#
See you on 8/14
Hello all, the regularly-scheduled meeting will be happening at 0900PST.
One topic of conversation from the last few meetings was having an alternating time to potentially accommodate more time zones. Rather than make recommendations, I’m going to put it as an open-ended question: is there a time anyone would like to suggest? Ideally it would not be in the middle of the night for US Pacific Time. I would be happy to experiment with this and try something else out - it could be on any weekday, it does not have to be Friday.
And hello again! We will be holding a breakout session next week at the regularly scheduled time to discuss the multi-machine/remote launching design doc https://github.com/ros2/design/pull/297
Meeting notes from this morning can be found, as always, at https://docs.google.com/document/d/1UXWaEkT6ji0Z0uTtJJSni5Y6fiopM9qOOzv4ldeNaAM/edit#
And the videosare at https://www.youtube.com/playlist?list=PLpUh4ScdBhSMSX5vJTPtTJb9PPU04yCbD
2 Likes
Just a reminder that we’ll be meeting 2020-09-04T16:00:00Z to discuss the remote launch proposal! We’ll set aside some time at the beginning for reading, though you may want to familiarize yourself with it beforehand as well.
Cheers and see you then.
Hey everyone, sorry for the late notice but here’s today’s (9/11) meeting link: https://chime.aws/7281583054
Thanks everyone for attending today - you’ll be able to find the video later at the usual channel.
We have a topic for next week’s breakout session, and that is “Minimal C++ ROS2 Variant”, a followup to discuss the contents of this REP proposal https://github.com/ros-infrastructure/rep/pull/231
The goal of the discussion will be to try and shake out some of the tricky issues, like
- How do we think about test packages in such a variant - some of these are python, even though all the feature code is C/C++
- How do we think about build tools in such a variant - we want to target cross-compilation, so the build tools run on one platform, but the output code on another