Jump to content

Team members: Difference between revisions

From postmarketOS Wiki
TC: add @longnoserob
Remove TC info, now in apply-for-tc repo
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The postmarketOS team consists of ''Core Team'' and ''Trusted Contributors''. This page lists related permissions and responsibilities, mostly with a focus on the git repositories.
{{note|Who the Core Contributors, Trusted Contributors, etc. are is now listed at https://postmarketos.org/team/. Here is some remaining information that we probably want to move other to the other page eventually.}}


== Core Team ==
== Core Contributors ==
=== Responsibilities / Permissions ===
=== Responsibilities / Permissions ===
==== GitLab ====
==== GitLab ====
Line 13: Line 13:
* Creating Releases and Service Packs
* Creating Releases and Service Packs
* Making releases of pmOS projects (pmbootstrap, tinydm, ...)
* Making releases of pmOS projects (pmbootstrap, tinydm, ...)
=== Members ===
* @calebccff (Caleb Connolly)
* @craftyguy (Clayton Craft)
* @dylanvanassche (Dylan Van Assche)
* @Newbyte (Stefan Hansson)
* @pabloyoyoista (Pablo Correa Gómez)
* @PureTryOut (Bart Ribbers)
* @ollieparanoid (Oliver Smith)
* @z3ntu (Luca Weiss)


=== Voting ===
=== Voting ===
Line 30: Line 20:
== Trusted Contributors ==
== Trusted Contributors ==


See also: [https://postmarketos.org/blog/2023/12/03/how-to-become-tc/ How to become a Trusted Contributor], [https://postmarketos.org/blog/2024/01/28/how-to-become-tc2/ Part 2]
All this information is now available in https://gitlab.postmarketos.org/postmarketOS/apply-for-trusted-contributor
 
== Active Contributors ==
 
The community plays a big role in the project. Device maintainers and active community members are able to get [https://docs.gitlab.com/ee/user/permissions.html Reporter] access on repositories relevant to their work. This is managed in a case-by-case basis, and requires having worked in postmarketOS for at least several months.


=== Responsibilities / Permissions ===
You can find the complete list in [https://gitlab.postmarketos.org/groups/group/active-contributors/-/group_members gitlab].
==== GitLab ====
 
Have approval and merge rights for all branches and repositories, with the following ''exceptions'':
=== Expectations ===
* stable branches of pmaports (v21.06 etc.)
* homepage
** apkbrowser.git
** cast.postmarketos.org.git
** postmarketos.org.git
* bpo


=== Members ===
Reporter access on GitLab includes a bunch of "project manager" type permissions, like assigning issues, setting (and editing) milestones, creating new labels, etc. This is a case of "just because you can doesn't mean you should". In general, we expect folks to assign issues/MRs, set labels, and approve MRs that affect packages they maintain. It will take some time for us to find a good balance here, so this isn't to say that folks should never use the other permissions, just that it's worth checking if you aren't sure.
* @jenneron
* @minecrell (Minecrell)
* @minlexx (Alexey Min)
* @travmurav (Nikita Travkin)
* @funderscore (Ferass El Hafidi)
* @arnavion (Arnav Singh)
* @longnoserob (Robert Eckelmann)


=== Voting ===
This section will be updated to document our common practices as they evolve.
* Two people from the Trusted Contributors or Core Team need to endorse the potential new trusted contributor.
* Everybody from the Core Team needs to approve / gets a chance to veto the new contributor (exception: if somebody is on holiday, time limit 1 week).


== See also ==
== See also ==

Latest revision as of 22:13, 12 March 2025

Note Who the Core Contributors, Trusted Contributors, etc. are is now listed at https://postmarketos.org/team/. Here is some remaining information that we probably want to move other to the other page eventually.

Core Contributors

Responsibilities / Permissions

GitLab

Have approval and merge rights for all branches and repositories.

("Force push" is disabled for "master" and stable branches, even for the Core Team.)

Other

  • Steering of the project
  • Taking part in Core Team Meetings
  • Creating Releases and Service Packs
  • Making releases of pmOS projects (pmbootstrap, tinydm, ...)

Voting

  • An existing core team member needs to vouch for new core team members.
  • Voting in new team members requires unanimous votes from existing members.

Trusted Contributors

All this information is now available in https://gitlab.postmarketos.org/postmarketOS/apply-for-trusted-contributor

Active Contributors

The community plays a big role in the project. Device maintainers and active community members are able to get Reporter access on repositories relevant to their work. This is managed in a case-by-case basis, and requires having worked in postmarketOS for at least several months.

You can find the complete list in gitlab.

Expectations

Reporter access on GitLab includes a bunch of "project manager" type permissions, like assigning issues, setting (and editing) milestones, creating new labels, etc. This is a case of "just because you can doesn't mean you should". In general, we expect folks to assign issues/MRs, set labels, and approve MRs that affect packages they maintain. It will take some time for us to find a good balance here, so this isn't to say that folks should never use the other permissions, just that it's worth checking if you aren't sure.

This section will be updated to document our common practices as they evolve.

See also