@@ -4,9 +4,9 @@ Here are rough guidelines about the responsibilities of people added as [https:/
First of all: team members don't have any authority, only responsibilities. They don't get special mentions because they are in the team. We highlight contributors in the blog post, no matter if they are part of the team or not because everybody's contributions and opinions are important. Everybody should be able to challenge the opinions of everyone in this project, so we have to find the best technical arguments to make decisions.
Team members have the responsibility of moderating issues and merge requests (closing obsolete ones, assigning labels, updating outdated messages, ...). Team members can directly write to all non-protected branches of relevant repositories (<code>master</code> in pmbootstrap is protected as a security measurement, only MartijnBraam and ollieparanoid can write to it).
Team members have the responsibility of moderating issues and merge requests (closing obsolete ones, assigning labels, updating outdated messages, ...). Team members can directly write to all non-protected branches of relevant repositories (<code>master</code> in pmbootstrap is protected as a security measure; only MartijnBraam and ollieparanoid can write to it).
Finally, everybody can select team members to review their merge requests. To keep the quality of code in postmarketOS on a good level, we let all code changes and most aport changes get reviewed by another person before merging them. The exception are tiny obvious changes and critical fixes without which some functionallity is completely broken (e.g. a missing comma made it impossible to install plasma mobile, or updating the cross compilers to the gcc version from Alpine which we do very often).
Finally, everybody can select team members to review their merge requests. To keep the quality of code in postmarketOS on a good level, we let all code changes and most aport changes get reviewed by another person before merging them. The exception are tiny obvious changes and critical fixes without which some functionality is completely broken (e.g. a missing comma made it impossible to install plasma mobile, or updating the cross compilers to the gcc version from Alpine which we do very often).
Because of that workflow, we have a lot of merge requests, and it is highly important that people properly test and review them, so we can keep up with our fast development speed without sacrificing quality.
