4e5c0fac7a
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.5 KiB
Weekly Community Q&A Call (Previously "Dev Call")
This page may be out of date. See the latest version.
The PX4 dev team and community come together to discuss any topic of interest to the community, ranging from sorting out issues to satisfying your curiosity.
Who should attend?
- Code Owners
- Reviewers
- Test team lead
- Dronecode members
- Community members (you!)
:::tip The Community Q&A call is open to all interested community members.
This is a great opportunity to meet the team and contribute to the ongoing development of the platform. :::
What gets discussed?
We publish a forum post per meeting a week before the call on PX4 Discuss - weekly-dev-call and track the agenda write down the discussion for the day. We welcome any topics that you, as a community member may have questions about / want to discuss!
Please add your topics for discussion to the agenda before the meeting begins, by replying to the meeting note. This will help you formulate your questions more clearly, and allow us to think about them in advance.
Schedule
- TIME: Wednesday 17h00 CET (subscribe to calendar)
- Join the call: https://discord.com/invite/BDYmr6FA6Q