Another question is how to address different ROS2 user groups/domains packages are used in, applications packages are used in w.r.t. recommendations for quality related activities. (A lot of recommendations are just reasonable for the industrial domain.)
Recommendations could e.g. be coupled to the ROS industrial package “software status”: Experimental, DEVELOPMENTAL, PRODUCTION. (industrial_moveit is e.g. EXPERIMENTAL.) This would allow to recommend activities with relation to the development state of a package.
ADDITION:
In my experience it is especially challenging to define activity recommendations w.r.t to the application software is used in. The higher level SW design and the idiomatic level can be heavily impacted by this. Developing a good approach which enables iterative migration to avoid the need for major re-factoring of software is challenging. We can probably discuss about this challenge in the upcoming “ROS Quality Assurance Working Group meeting - April 2018”?