Create new AUR moderator role

Create a dedicated role for the moderation of the AUR that supports and eventually replaces the Package Maintainers as the current moderators.

rfcs/0019-aur-moderator-role.rst

+---
+title: "Moderator role for AUR"
+---
+
+Moderator role for the AUR
+==========================
+
+- Date proposed: 2023-06-27
+- RFC MR: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/19
+
+Summary
+-------
+
+Create a dedicated role for the moderation of the AUR that supports and eventually replaces the Package Maintainers as the current moderators.
+
+Motivation
+----------
+
+Currently, Arch Linux has 63 Package Maintainers. Historically known as Trusted Users (TU), they had two main responsibilities: Moderation of the AUR and moving popular AUR packages to the official Arch Linux repositories. The combination of those two responsibilities has not worked out since quite some time, as most package maintainers simply do not really intend to moderate the platform. On the other hand potential moderators have a hard time applying as package maintainers just for the sake of moderating the AUR. This RFC proposes to split the old TU role into `Package Maintainers` and `AUR Moderators` to have a clear separation of concern and allow for an easier way to recruit `AUR Moderators`.
+
+Specification
+-------------
+
+Similar to forum moderators, the newly created role of AUR Moderators is to review requests on the AUR and accept or close them. Furthermore, they are allowed to suspend accounts that violate the AUR contribution guidelines. At the moment AUR web defines the following user types
+* `Normal user`
+* `Trusted User`
+* `Developer`
+* `Trusted User & Developer`
+
+After the implemention of this RFC the user types will be changed to
+* `Normal User`
+* `AUR Moderator`
+* `Package Maintainer`
+
+The moderation rights of `Package Maintainers` in the AUR are not changed, so that every `Package Maintainer` is an `AUR Moderator`, too. In contrast to `Package Maintainers`, `AUR Moderators` won't be able to participate in votings and will only be allowed to edit user accounts with role `Normal User`.
+`AUR Moderators` are recruited from the regular contributors of the AUR. To be promoted, users must secure the support of two `AUR Moderators`, `Package Maintainers` or `Developers`. They can seek for sponsorship support by contacting staff members directly or can be suggested by the group of `AUR Moderators`.
+Once two sponsors are found, the nominee writes an application email signed with their SSH key for their AUR profile to aur-general. After the two staff members confirmed their sponsorship, a discussion period of seven days starts. If not more than one staff member opposes the application, they are promoted to an `AUR Moderator`.
+The responsibility of the two sponsors is to guide their rookie through the duties of an `AUR Moderator` while frequently checking in on their work during their first month. On the other hand, the responsibility of an applicant and `AUR Moderator` is to be up to date on the latest AUR submission guidelines [1] and Arch package guidelines [2].
+
+Drawbacks
+---------
+
+Packages in the AUR are not officially supported by Arch Linux. Adding a special role to handle AUR requests may lead to the impression that the AUR is an official package source. However, AUR Moderators will only watch over the AUR submission guidelines [1] and Arch packaging guidelines [2].
+
+Unresolved Questions
+--------------------
+
+None
+
+Alternatives Considered
+-----------------------
+
+Package Maintainers should take care of the AUR more regularly. One possiblity is to name a group of up to five Package Maintainers who will focus on AUR requests for one week. A list with names is published as a markdown file every month.
+
+[1] https://wiki.archlinux.org/title/AUR_submission_guidelines
+[2] https://wiki.archlinux.org/title/Arch_package_guidelines