{BAIXRI} Mobile AR VR Community Group for {Robotics Official} {Bellande Technologies Official}

Mission: The Mobile AR VR Working Group's mission is to to build the architecture of mobile robotics build that is

Scope: The Scope of this working group will be to inovate and create new libraries, api, packages that is widely used by every researcher from industies and universities

Communication Channels

• Ronaldson Bellande Linkedin: https://www.linkedin.com/in/ronaldson-bellande-5b9699178
• BAI&XRI Center Linkedin Page: https://www.linkedin.com/company/bellande-application-ui-ux-research-innovation-center
• Ronaldson Bellande GIthub: https://github.com/RonaldsonBellande
• Email: ronaldsonbellande@gmail.com
• Discord Group: https://discord.gg/KBwqcPdx2H
• Google Group: https://groups.google.com/g/mobilevrar-application-uiux-community-group
• Email Group: mobilevrar-application-uiux-community-group@googlegroups.com
• Google Meeting Calender: https://calendar.google.com/calendar/u/0/embed?src=c_3fc5c4d6ece9d80d49f136c1dcd54d7f44e1acefdbe87228c92ff268e85e2ea0@group.calendar.google.com&ctz=UTC
• Google Meeting Link: https://meet.google.com/sim-yvox-ksr?authuser=0&hs=122&ijlm=1713929631349

Resources

• Google Calendar: https://calendar.app.google/fsqC1XNE294JdiFVA
• Notes and Presentation: https://github.com/Application-UI-UX/BAI-XRI-Mobile-AR-VR-PowerPoint-Notes

Subproject List

• BAI&XRI ROS/ROS2 Mobile Catkin Modules Build Development Tools

  • Description: ROS/ROS2 Mobile Catkin Modules Build Development Tools
  • Repositories
    • Mobile Catkin Modules Build Development Tools

• BAI&XRI ROS/ROS2 Mobile Message Service Generator

  • Description: ROS/ROS2 Mobile Message Service Generator
  • Repositories
    • Mobile Message Service Generator

• BAI&XRI ROS/ROS2 Mobile Catkin Gradle Plugins

  • Description: ROS/ROS2 Mobile Catkin Gradle Plugins
  • Repositories
    • Mobile Catkin Gradle Plugins

• BAI&XRI ROS/ROS2 Mobile Implementation Core

  • Description: ROS/ROS2 Mobile Implementation Core
  • Repositories
    • Mobile Implementation Core

Standards for subprojects

Subprojects must meet the following criteria (and the WG agrees to maintain them upon adoption).

• Build passes against ROS 2 master
• The ROS 2 standard linter set is enabled and adhered to
• If packages are part of nightly builds on the ROS build farm, there are no reported warnings or test failures
• Quality builds are green (address sanitizer, thread sanitizer, clang thread safety analysis)
• Test suite passes
• Code coverage is measured, and non-decreasing level is enforced in PRs
• Issues and pull requests receive prompt responses
• Releases go out regularly when bugfixes or new features are introduced
• The backlog is maintained, avoiding longstanding stale issues

Adding new subprojects

To request introduction of a new subproject, add a list item to the "Subprojects" section and open a Pull Request to this repository, following the default Pull Request Template to populate the text of the PR.

PR will be merged on unanimous approval from Approvers.

Subproject changes

Modify the relevant list item in the "Subprojects" section and open a Pull Request to this repository, following the default Pull Request Template to populate the text of the PR.

PR will be merged on unanimous approval from Approvers.

Deprecating subprojects

Projects cease to be useful, or the WG can decide it is no longer in their interest to maintain. We do not commit to maintaining every subproject in perpetuity.

To suggest removal of a subproject, remove the relevant list item in the "Subprojects" section and open a Pull Request in this repository, following instructions in the Pull Request Template to populate the text of the PR.

PR will be merged on unanimous approval from Approvers.

If the repositories of the subproject are under the WG's GitHub organization, they will be transferred out of the organization or deleted at this time.

Governance

• Ronaldson Bellande

Meetings

• Regular WG Meeting: 6:00 PM EST

  • The meetings be announced in Discourse, Discord as well as our Bellande Application & UX/UI Research Innovations Center

  • The Meeting will be video will be posted in BR&SRI Youtube channel

Backlog Management

The Working group management will be working in the Bellande Application & UX/UI Research Innovations Center and Where thr working group will be displayed and tracked will be Bellande Application & UX/UI Research Innovations Center

Membership, Roles and Organization Management

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

• Member
  • Ronaldson Bellande
  • Responsible for triaging issues
• Reviewer
  • Ronaldson Bellande
  • Prerequisite: Proven track record of high-quality reviews to WG Subprojects
  • Responsible for reviewing pull requests
• Approver
  • Ronaldson Bellande
  • 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
  • Ronaldson Bellande
  • 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.

Modifying this governance document

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