Trusted Contributors

Trusted Contributors (TC) 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!

Responsibilities

Trusted Contributors must stay active in the community. Inactive TCs might get removed after a year of inactivity or earlier at their request.

Benefits

All Trusted Contributors team have access to the following benefits

  • A @postmarketos.org inbox, or redirection to your personal one.

  • Access to postmarketOS’s nextcloud.

  • Access to postmarketOS’s instance of https://github.com/suitenumerique/docs[La Suite Docs].

  • On request, an account on the :postmarketos.org matrix server.

  • Economic support at events where a big part of the team assembles, e.g: accommodation for the classic post-FOSDEM planning hackathon.

  • Your desired name and nick, together with a description of your interests will be featured on the website!

  • You will be added to an internal chat with the rest of the team members.

  • Possibility to attend the Team Meetings.

GitLab Permissions

TCs have approval and merge rights for all branches and repositories under the postmarketOS repositories, with the following exceptions:

  • stable branches of pmaports (v24.06 etc.)

  • master branch of pmbootstrap

  • homepage

  • cast.postmarketos.org.git

  • postmarketos.org.git

  • build.postmarketos.org (bpo)

Becoming a Trusted Contributor

People who have been contributing to postmarketOS or closely related similar free software projects for the past six months may apply to become a Trusted Contributor (TC). We have a broad interpretation of “contribution” to encourage not only developers to apply. If you have been spending significant time triaging issues, providing community support, doing outreach by going to conferences and doing talks, improving documentation and/or creating artwork, we would be very happy to have you apply!

Application Process

To become a TC, please follow this process:

  • Open an issue in this repository.

  • Two people from the Trusted or Core Contributors need to endorse you. It is strongly recommended to have discussed the endorsement with them before opening the issue.

  • Once the endorsers confirm their endorsement in the issue, any member of the Core Contributors might start the voting process by following the instructions.

  • Everybody from the Core Contributors needs to approve / gets a chance to veto the new contributor. This is done exclusively for governance reasons.

  • Once all Core Contributors have approved the application, or if one week has passed and there is no veto, any Core Contributor might proceed with the Onboarding by creating an onboarding issue.

TIP

Give reviews/feedback on merge requests - even though you cannot approve, you can still help folks out!

TIP

Be active in chat and gitlab issues, helping other users or going to events and spreading the word.

Further reading