Team members

From postmarketOS

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.

Core Team

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, ...)

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

  • 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

See also: How to become a Trusted Contributor, Part 2

Responsibilities / Permissions

GitLab

Have approval and merge rights for all branches and repositories, with the following exceptions:

  • stable branches of pmaports (v21.06 etc.)
  • master branch of pmbootstrap
  • homepage
    • apkbrowser.git
    • cast.postmarketos.org.git
    • postmarketos.org.git
  • bpo

Members

  • @jenneron
  • @minecrell (Minecrell)
  • @minlexx (Alexey Min)
  • @travmurav (Nikita Travkin)
  • @funderscore (Ferass El Hafidi)
  • @arnavion (Arnav Singh)
  • @longnoserob (Robert Eckelmann)
  • @Grimler (Henrik Grimler)
  • @wonderfulShrineMaidenOfParadise (Raymond Hackley)

Voting

  • 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