This document defines the scope and governance of the Community Group (CG).
Mission: The Event Camera Community Group's mission is to increase adoption of event camera sensors and their use cases in aerial robotic systems using the open source ROS 2 stack. The ECWG leverages embedded hardware such as the AMD Kria KV260, AMD Kria KD240, NVIDIA Jetson Orin Nano series, NVIDIA Jetson Orin NX series, and Raspberry Pi 4/5 to test proof-of-concept software leveraging event camera sensors.
Scope: The ECWG scope software focuses on the ROS 2 stack, third-party ROS 2 packages, and the Prophesee Metavision SDK. The primary hardware focus is on widely available embedded arm64 boards to include the Jetson Nano Orin/Orin NX, AMD Kria KV260/KD240, and Raspberry Pi 4/5.
This Community Group owns and maintains the following Subprojects. Its meetings and membership are largely focused on the direction, design, and work on the projects.
The following subprojects are owned by the Community Group:
-
Establishing awareness and presence of the ECWG in the wider robotics community
- Description: Establish official OSRF ROS event Camera Community Group and documentation
- Status: Soft launch TBD 🚧
-
Event Camera Driver for Nvidia Jetson Orin
- Description: Working on kernel module, DKMS, and the Nvidia camera core development library interface to get an event camera working on the Jetson Orin Nano/Orin NX via MIPI CSI interface
- Repositories
- linux-sensor-drivers
- Status: In development 🚧
-
Docker Image for Metavision SDK (AMD Kria development using Ubuntu)
- Description: Make the Prophesee metavision repo and dependencies for the Kria embedded kit (event markers demo) easier to install via Kria Docker
- Respositories:
- kria-docker
- Status: In development 🚧 (Need CI/CD through jenkins/gitlab etc)
-
Metavision Embedded Markers Example Adapt to ROS 2
- Description: Adapt the existing pose markers example from Prophesee to a ROS 2 package
- Repositories:
- metavision-event-markers
- Status: Compiles and runs (AMD Kria KV260), needs debian package hosting 🏁
-
Evaluation of Existing Simulation Tooling
- Description: Look into existing simulation tooling for event sensors (gazebo, isaac sim, etc)
- Status: Community Notes Merged 🏁
-
Non-profit Exploratory/Market research into Event perception product fit
- Description: Look into non-profit status and research event perception solution
- Status: On hold ❌
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
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.
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.
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.
- Regular WG Meeting: bi-weekly on Wednesday, 0800 UTC
- Meetings through Google Meet, coordinated via email
- Artifacts updated will include meeting minutes, transcribing of the meeting.
Discord, Google Meet
{{Is any project management software/site used to track work for this Community Group? How can new members discover the highest impact tasks they could take on? GitHub Projects, ZenHub, etc.}}
Community Group members may act in one or more of the following roles:
- Member
- Prerequisite: Attend at least one out of the last three Community 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 Community Group
- Lead
- TSC member or their delegate
- Responsible for organizing and moderating Community 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 Community 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.
