@arrowcircle says that the number of project management boards on GitHub should be reduced. He also says that we need to define concrete requirements for the demo canvas mock-up starting with the exact list of nodes; we agreed to model a trivial tailsitter containing the following nodes:
- one FMU
- four ESC
- two servos
- one airspeed sensor
The exact subjects and services are TBD.
@arrowcircle should look at the ROS Computational Graph documentation to better understand the concept of real-time distributed pub-sub:
- https://en.wikipedia.org/wiki/Robot_Operating_System#Computation_graph_model
- http://wiki.ros.org/ROS/Concepts#ROS_Computation_Graph_Level
- http://wiki.ros.org/rqt_graph
It is hard to organize our activities because we still don’t know what the specific objectives are. @ivodre is going to help us here. He is willing to invest up to 15 hrs/week (best case) into this project but the duration of this commitment is unknown. We are unable to determine what is the required minimum level of involvement from his side as a product owner so we are a little in the blind but hopefully things will clear up in the near future. Ivo will be asking questions via Slack until he has a clear picture of what we are trying to do, I will make sure to accommodate. While @tsc21 & @arrowcircle are working on the demo, @ivodre will be learning the background and then working on formulating the plan & requirements.
Regarding the PX4 summit: @tsc21 is hesitant to commit to anything citing conflicting personal arrangements so at the moment we are going to avoid stating anything related to Yukon but will keep our options open; hopefully the organizers will be flexible enough to admit late replanning.
The next conversation will take place on Wednesday during the regular weekly dev call.