This document defines the scope and governance of the SMACC Working Group (SMACC WG).

Mission: The SMACC Working Group's mission is to advance the current state of the art in robotic applications, by utilizing the SMACC state machine library for ROS and ROS2.

We will be focused on…

• The creation of new SMACC state machine examples that demonstrate advanced autonomy capabilities.
• The creation of new SMACC clients that will enable the utilization of SMACC on platforms with different peripherals.
• Improvements to the core SMACC library, bug-fixes, new features, etc.
• Improving the documentation of the library.
• Surveying the community interest in using SMACC for particular use cases in ROS 2 and Gazebo.
• Producing demonstrations with real robots that utilize SMACC to meet their application requirements.

Meeting will generally happen once a month or more often. Meetings will be announced on ROS Discourse and minutes will be kept.

• Proposal for the SMACC Working Group
• Rolling Agenda and Minutes

• Meeting invite group: smacc-wg@googlegroups.com
• Working Group Github repo: SMACC_WG
• Discourse tag: wg-smacc

Backlog management is performed using Github Issues & Projects on the following repos:

• SMACC Repository for ROS1
• SMACC2 Repository for ROS2
• SMACC Working Group Repository

Working Group members may act in one or more of the following roles:

• Member
  • Prerequisite: Attend at least one out of the last three Working Group meetings
  • Responsible for triaging issues
• Reviewer
  • All reviewers are members
  • Prerequisite: Proven track record of high-quality reviews to WG Subprojects
  • Responsible for reviewing pull requests
• Approver
  • All approvers are reviewers
  • Prerequisite: Proven track record of high-quality contributions and reviews to WG Subprojects
  • Responsible for approving and merging pull requests
  • Responsible for vetting and accepting new projects into the Working Group
• Lead
  • TSC member or their delegate
  • Responsible for organizing and moderating working group meetings
  • Responsible for posting meeting materials (minutes, recordings, etc.)
  • Responsible for breaking ties

To become a member or change role, create an issue in this repository using the appropriate issue template. Such applications are accepted upon unanimous agreement from Approvers, and are typically based on the applicant's history with the subprojects of the Working Group.

The Lead role cannot be applied for, as it is an appointee of the ROS 2 TSC.

Changes to this document will be made via Pull Request. The PR will be merged on unanimous agreement from Approvers.