ROS Quality Assurance Working Group Feb. 2019 Meeting Notes

Quality Assurance
1

Agenda:

  1. Actions from last meeting (Adam)
  2. Update on the QA Dashboard implementation (Matt Droter)
  3. Discuss next iteration initiatives
    1. Energize Continuous Integration
    2. Quality Hub
    3. Formalize the code ownership process
    4. Onboarding process for core and non-core community members
  4. Presentation of a code analysis tool Phys (John-Paul Ore)

Actions from last meeting:

  1. The action was for me to contact Dirk Thomas and ask him to recommend some ROS 2 repositories to run a pilot for code review. Dirk suggested these repositories:
    1. ament/ament_lint
    2. ros2/rcl
    3. ros2/rclcpp
    4. ros2/ros2cli

Update on the QA Dashboard:

  1. Matt Droter provided an update to the group on the ongoing work to implement the QA Dashboard. Nicolas Limpert and Matt Droter are working on the Buildfarm integration. The prototype of the dashboard is available in this link: https://git-afsantos.github.io/haros/#dashboard

This year initiatives:

  1. 2019 initiatives were discussed briefly:
    1. Energize Continuous Integration
    2. Quality Hub
    3. Formalize the code ownership process
    4. Onboarding process for new comers

Phys:

  1. John-Paul Ore presented Phys(https://unl-nimbus-lab.github.io/phys/) to the group. The link to slides below: https://unl.box.com/s/4g5guvflnp5soixrmfvs2mb4zdyurr60

Actions from the meeting:

  1. Gijs to raise PRs for ROS2 repositories
  2. Adam to ask Andrzej Wasowski to summarize the scope and intent of “Energize Continuous Integration” and circulate it to the group in preparation for next meeting.
2 Likes