I've done my best to assign appropriate maintainers.
Listed multiple individual maintainers and also included the internal
mailing list to ensure the load is distributed in the event of build
failures.
Related to:
fetchrobotics/fetch_msgs#16
fetchrobotics/fetch_robots#57
fetchrobotics/fetch_gazebo#97
fetchrobotics/fetch_demos#3
fetchrobotics/fetch_tools#15
fetchrobotics/fetch_open_auto_dock#3
fetchrobotics/power_msgs#11
fetchrobotics/robot_controllers#41
For the new maintainers- worth following the 9 repos which the research customers depend on, it's easy to loose track when they report issues.
I've given @erelson documentation (I can't link to it as I've lost access to the private repo.) which explains the release process, and gave @narora1 a tutorial a while ago. I can be reached on whatsapp or username at bostondynamics.com email address (same format at fetch) if needed.
I've done my best to assign appropriate maintainers.
Listed multiple individual maintainers and also included the internal mailing list to ensure the load is distributed in the event of build failures.
Related to:
For the new maintainers- worth following the 9 repos which the research customers depend on, it's easy to loose track when they report issues.
I've given @erelson documentation (I can't link to it as I've lost access to the private repo.) which explains the release process, and gave @narora1 a tutorial a while ago. I can be reached on whatsapp or username at bostondynamics.com email address (same format at fetch) if needed.