mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
Split the maintainer role into two types to make it easier to grow the bench without asking new contributors to commit to a specific component up front. Code Owners keep their existing scoped responsibility for a category, while Reviewers help across the project without ownership of any specific area. Both are full maintainers, share the @PX4/dev-team GitHub team, and have the same write access and voting rights. Rename the Active Maintainers table to Code Owners with no change to the current roster. Add an empty Reviewers table so future nominations land in their own PRs. Update the contributor docs to describe the two types, cover both in the recruitment and onboarding flow, and note the promotion path from Reviewer to Code Owner. Signed-off-by: Ramon Roche <mrpollo@gmail.com>
1.3 KiB
1.3 KiB
Community
This page may be out of date. See the latest version.
Welcome to the PX4 Community!
:::tip We pledge to adhere to the PX4 code of conduct, which aims to foster an open and welcoming environment. :::
This section contains information about how you can meet with the community and contribute to PX4:
- Dev Call - Discuss architecture, pull requests, impacting issues with the dev team
- Maintainers - Maintainer roles, types, and how to become one
- Support - Get help and raise issues
- Source Code Management - Work with PX4 code
- Documentation - Improve the docs
- Translation - Translate using Crowdin
- Terminology/Notation - Terms and symbols used in the docs
- Licenses - PX4 and Pixhawk licensing