Add docs on "Becoming a Flathub Team Member"

Author: bbhtt

docs/03-for-team-members/02-becoming-a-team-member.md

@@ -0,0 +1,114 @@
+# Becoming a Flathub Team Member
+
+Flathub, as a centralized application repository, relies on a dedicated
+team of mainly volunteer contributors to maintain the quality, security,
+and consistency of the repository.
+
+These contributors are generally responsible for tasks including, but
+not limited to:
+
+* Reviewing new application submissions.
+* Reviewing moderation requests, such as permission changes.
+* Triaging and responding to issues or queries from application
+  developers.
+* Updating, adopting maintenance of, or contributing to Flatpaks when
+  necessary.
+* Auditing existing applications to ensure compliance with current
+  Flathub guidelines and best practices.
+
+As Flathub continues to grow, the associated workload also increases.
+So, expanding the contributor base helps distribute this workload more
+effectively and improves sustainability for the project overall.
+
+## Team Membership Process
+
+Please open an issue in <INSERT META REPO> linking relevant activity
+and/or contributions and wait for at least one existing project members
+to approve the request and grant the necessary permissions.
+
+Please note that all approval requests are evaluated on a case-by-case
+basis and may take additional factors into consideration and may be
+denied.
+
+## Membership Criteria
+
+### Reviewer Team
+
+Members in the Reviewer Team are primarily responsible for reviewing,
+approving and merging new submissions.
+
+Criteria:
+
+* Past examples of performing non-trivial application submission
+  reviews, with at least 3 successful reviews within the last 1 month
+  that resulted in accepted submissions.
+* Familiarity with review policies and Flathub requirements.
+
+### Trusted Maintainer Team
+
+Members of the Trusted Maintainer Team are granted access to all
+Flathub submission repositories, including relevant access to the
+developer portal in the website.
+
+They are primarily responsible for assisting with the maintenance and
+continuity of Flatpaks in situations where the original maintainer is
+unavailable or unresponsive.
+
+Criteria:
+
+* Experience maintaining at least 2 Flatpaks in Flathub GitHub
+  repositories.
+* Past examples of assisting with package adoption, co-maintenance, or
+  maintenance efforts with adherence to proper maintenance practices.
+* Familiarity with Flatpak, Flathub workflows, and related tooling.
+
+### Build Moderation Team
+
+Members of the Build Moderation Team are responsible for reviewing build
+and moderation requests, approving or denying them as appropriate, and
+providing clarification or follow-up when developers raise questions.
+
+Criteria:
+
+* Membership in either the Reviewer Team or Trusted Maintainer Team for
+  a reasonable period of time.
+* Familiarity with moderation policies and Flatpak permission system.
+
+### `flathub-infra` repositories
+
+Most of the tooling and infrastructure used by Flathub is maintained in
+the `flathub-infra` organisation.
+
+Access to the repositories there is granted based on demonstrated
+contributions to the relevant project for a reasonable period of time
+through all of pull requests, reviews, issue triaging, and familiarity
+with the associated project and its workflows.
+
+Access will initially be limited to the triage or write permission and
+may later be expanded based on requirements and continued maintenance
+activity.
+
+### `shared-modules` repository
+
+This repository contains manifests for commonly used Flatpak modules
+that can be consumed as a git submodule.
+
+Write access is granted to contributors willing to maintain one or
+more modules in the repository and the access may be revoked if the
+contributor no longer maintains the relevant modules or if those modules
+are removed from the repository.
+
+## Revocation of Team Membership
+
+In the event of prolonged inactivity, team membership may be revoked.
+
+Inactivity is defined as the absence of any meaningful activity in the
+relevant GitHub repositories or namespaces for a period exceeding one
+year.
+
+Before revocation, the concerned member must be notified through a
+GitHub issue in the <INSERT META REPO> and must be given up to one
+month to respond or resume activity.
+
+Existing members may also request voluntary removal from the team by
+following the same process.