Project Maintainers¶
postmarketOS hosts various repositories at https://gitlab.postmarketos.org/postmarketOS.
This page describes by whom these different projects are maintained and how maintainership is handled for these repositories.
maintainers.txt files¶
Repositories in the postmarketOS namespaces may have a maintainers.txt text
file in the root directory. This file is the list of who maintains this
repository. It includes each maintainer’s GitLab username per line. Please keep
this file sorted and include the header comment to this page.
Example:
# https://postmarketos.org/maintainers.txt
Aelin
PureTryOut
fossdd
The exception for this file are collectively maintained projects like pmaports.
A file without maintainers declares the project as unmaintained. A missing
file doesn’t necessarily mean that the project is unmaintained, but that it
might not have yet been migrated to the maintainers.txt-format.
Maintainer powers¶
As a project maintainer you get the following powers:
Approve and merge all MRs on your project, see Code Review / Merge
Tag new releases
Accept new maintainers
Maintainer expectations¶
“With great power comes great responsibility” and we expect you to follow the following aspects:
Review (and merge) MRs assigned to your project in a reasonable time
Keep track of the issue tracker (e.g. make sure issues have enough info by the reporter).
Ideally subscribe to all activity in your project via GitLab
Becoming a maintainer¶
To become a maintainer we expect you to get in contact with the existing
maintainers first and discuss your maintainership. If the current maintainers
agree, open an MR adding yourself to the maintainers.txt file of the project.
If the project is unmaintained (i.e. the maintainers.txt file is empty), or
maintainers are unresponsive you can directly send an MR adding yourself as
maintainer, and ask TCs/CCs to merge the MR. If you’re a TC/CC, you can
directly merge the MR.
Now that you’re a maintainer of a project, you can ask the infra team to receive the Maintainer role on GitLab for the repository.
To remove your maintainership, delete the line and push it to the main branch.
List of projects¶
Open list of projects
Project |
Description |
Maintainers |
|---|---|---|
Python implementation of aports-turbo, runs on https://pkgs.postmarketos.org/ |
||
Apply aports/pmaports merge requests to a testing system |
||
See https://postmarketos.org/blog/2023/12/03/how-to-become-tc/ |
||
Logos, wallpapers, T-Shirt designs etc. |
||
Configures the MAC addresses of WLAN and Bluetooth interfaces at boot |
||
A suite of graphical applications for the terminal |
||
Status frontend and manager for the postmarketOS build queue |
||
postmarketOS podcast website & episode files |
||
SDL2 charging application for the initramfs |
||
Common scripts for continuous integration |
||
“brew” style package manager that offers the full power of the Alpine Linux aports repository, without root. |
||
postmarketOS deviceinfo validator, linter, and documentation generator |
||
Docker image for postmarketOS |
||
https://docs.postmarketos.org |
||
Immutable postmarketOS image building using mkosi |
||
A place to coordinate and log postmarketOS participation at conferences and other events |
||
Framebuffer debugging tool |
||
UAPI.6 compliant kernel commandline generator |
||
README that shows up at https://gitlab.postmarketos.org/postmarketOS |
||
Proof of concept for a GTK frontend. Pay attention to README.md, you probably want to use pmbootstrap instead. |
||
A lighter-weight hotkey daemon |
||
Simple script to install makedepends for Alpine and postmarketOS packages |
||
Matrix bot |
||
Alpine Package Keeper (apk) package manipulation library C++/Qt bindings |
||
(clone of https://gitlab.com/marge-org/marge-bot) |
||
People who own postmarketOS-related IRC/Matrix channels can request them to be bridged by us in this issue tracker |
||
Mobile and privacy friendly configuration for Firefox (distro-independent) |
||
Mobile and privacy friendly configuration for Thunderbird (distro-independent) |
||
postmarketOS tools for interacting with gitlab MRs |
||
Automatically load firmware from device partitions |
||
Common support for Qualcomm MSM modems |
||
Builds Alpine/postmarketOS packages from upstream development sources every night https://nightly.postmarketos.org |
||
Generate OBEX capabilities XML files on the fly |
||
Experimental new version of the on-device installer |
||
Website to be used for DRM_PANIC_SCREEN_QR_CODE_URL https://panic.postmarketos.org/ |
||
PCB design for HW-testing setup discussed in https://gitlab.postmarketos.org/postmarketOS/postmarketos/-/issues/63 (and possible more in the future) |
||
postmarketOS package build recipes |
||
postmarketOS package build recipes |
||
Sophisticated chroot/build/flash tool to develop and install postmarketOS |
||
postmarketOS Change Requests are a process to propose, approve, and endorse big changes to the project. They are an RFCs process |
||
Organizational issues |
||
TWRP compatible postmarketOS installer script |
||
Simple touch menu for a few demo programs |
||
Script to quickly install pmb_recommends for a package |
||
Release upgrade tool, to get from one pmOS release to the next one. See https://postmarketos.org/upgrade |
||
Upgrade notification app that get’s installed and launched automatically on End-Of-Life postmarketOS releases |
||
postmarketOS welcome app, based on GTK |
||
Source files of the postmarketOS website |
||
Graphical power_supply status tool for Linux mobile platforms |
||
Reboot a mobile device to a specific mode |
||
Shim that uses run0 to shim sudo invocations in shell scripts. |
||
Source files of postmarketOS status page |
||
tiny display manager - wayland / x11 session starter for single user machines |
||
CLI tool to query the Testing Team page from the postmarketOS wiki |
||
A collection of tools for allowing mobile users to switch to a TTY |
||
Issues about https://wiki.postmarketos.org |
||
Configuration making xfce4 suitable to use on phone |
||
A graphical installer for Linux phone distro images |