The Membership

The membership collectively sets the overall project direction.

Members 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, design and maintain the infrastructure, make releases, and everything else.

Community members that have been contributing to Nura in a meaningful way for six months or longer and intend to do so in the future can apply to become a member!

Responsibilities

Members must stay active in the community. To reflect this, members are required to renew membership every two years.

Note

The renewal process is not yet implemented, but expected to not differ significantly from the application process.

Benefits

All members have access to the following benefits

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

  • Access to Nura’s Nextcloud.

  • Access to Nura’s instance of La Suite Docs.

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

  • Economic support at events where a big part of the membership 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 membership.

  • Possibility to attend the Team Meetings.

  • Rights to merge contributions in Nura repositories.

GitLab Permissions

Members have approval and merge rights for all branches and repositories under the Nura repositories, and should follow the code review and merge guidelines.

Attention

Force push is disabled for master and stable branches in pmaports

Note

If the team grows, and we include a greater share of non-developers, it is expected that those people can contribute to the project and receive all the other benefits. But for security reasons, they might not get merge rights.

Becoming a member

People who have been contributing to Nura or closely related similar free software projects for the past six months may apply to become a member. 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 member, please follow this process:

  • Open an issue in this repository.

  • Two people from the current membership need to endorse you. It is strongly recommended having discussed the endorsement with them before opening the issue.

  • Once the endorsers confirm their endorsement in the issue, any member of the Board might start the voting process by emailing the assembly. Then:

    • For the next two weeks, any member can raise issues about the application with any Board member in private, or replying to the email.

    • If no member raises an objection within the two weeks following the admission request. Members might proceed with the Onboarding by creating an onboarding issue.

    • If any one member raises an objection, the acceptance of the new member will be voted in the next general assembly.

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