Jump to content

Team members: Difference between revisions

From postmarketOS Wiki
Move Minecrell from Core Team to Trusted Contributor as he requested
Line 20: Line 20:
* @MartijnBraam (Martijn Braam)
* @MartijnBraam (Martijn Braam)
* @minlexx (Alexey Min)
* @minlexx (Alexey Min)
* @Newbyte
* @Newbyte (Stefan Hansson)
* @PureTryOut (Bart Ribbers)
* @PureTryOut (Bart Ribbers)
* @ollieparanoid (Oliver Smith)
* @ollieparanoid (Oliver Smith)

Revision as of 06:35, 5 September 2022

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)
  • @MartijnBraam (Martijn Braam)
  • @minlexx (Alexey Min)
  • @Newbyte (Stefan Hansson)
  • @PureTryOut (Bart Ribbers)
  • @ollieparanoid (Oliver Smith)
  • @z3ntu (Luca Weiss)

Voting

Voting in new team members requires unanimous votes from existing members.

Trusted Contributors

Responsibilities / Permissions

GitLab

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

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

Members

  • @minecrell (Minecrell)

GitLab configuration

Group mapping

postmarketOS GitLab Group
Core Team Maintainer (or Owner)
Trusted Contributor Developer

Settings per repository

# Settings / General
## Merge Requests
Merge Method:
[x] Fast-forward merge

Merge options:
[ ] Automatically resolve merge request diff discussions when they become outdated
[x] Enable "Delete source branch" option by default

Squash commits when merging:
[x] Do not allow

Merge checks:
[ ] Pipelines must succeed
[x] All discussions must be resolved

## Merge request approvals
[ ] Remove all approvals when commits are added to the source branch.

# Settings / Repository
## Protected Branches
master:
	Allowed to merge:	Developers + Maintainers
	Allowed to push:	Developers + Maintainers
	Allowed to force push:	False
	Code owner approval:	False (we only use it for notification)

(stable branches):
	Allowed to merge:	Maintainers
	Allowed to push:	Maintainers
	Allowed to force push:	False
	Code owner approval:	False

## Protected tags
*:
	Allowed to create:	Maintainers