Groups and Teams¶

As a free and open-source software (FOSS) project, anyone can contribute to postmarketOS by submitting patches and taking part in discussions. There are a wide range of contributions that come from all corners of our amazing community. You too can contribute!

All creatures welcome. Make sure to follow the Code of Conduct.

Groups¶

Members who have special responsibilities are organized into the following groups, with a specific set of responsibilities.

Core Contributors¶

The Core Contributors are the most involved with the project. They set the overall project direction, design and maintain the infrastructure, make releases, and everything else. The group is currently limited to a maximum of 8 people to keep it effective. We currently don’t have a formal process for becoming a Core Contributor. However if you are already a Trusted Contributor and have a very good reason, then talk to us and we can consider it.

Trusted Contributors¶

Trusted Contributors work on day-to-day things across the project including development, code reviews, merging changes, triaging issues, community support, outreach by going to conferences and doing talks, improving documentation and/or creating artwork. Community members that have been contributing to postmarketOS in a meaningful way for six months or longer and intend to do so in the future can apply to become a Trusted Contributor!

Active Contributors¶

Active Contributors can’t merge changes themselves, but otherwise do much of what Trusted Contributors do. They usually focus on the specific devices they are interested in.

Teams¶

postmarketOS is also organized into Teams, which are built around a singular topic or purpose.

Testing Team¶

Given the breadth of hardware postmarketOS supports, extensive testing is important to prevent regressions: the Testing Team tests changes before they’re released ensuring they’re as reliable as possible.

Code of Conduct Team¶

By following our Code of Conduct, we establish a baseline of civil and professional collaboration. In case people behave unacceptably (join our channels and insult others, post spam, etc.) we enforce the CoC with the CoC Team.

The CoC Team is not a last resort and it is typically best to contact them sooner than later so they can help prevent issues from escalating. Getting in touch doesn’t mean that severe action will be taken, and more often than not they can resolve issues peacefully.

The Board¶

The board is responsible for approving expenses in our Open Collective as well as budgets when executing projects.

Infrastructure Team¶

The Infrastructure Team administrates postmarketOS servers and services running on them.

Members: Luca, Oliver, Clayton