Verified Commit 4774cb15 authored by Konstantin Gizdov's avatar Konstantin Gizdov
Browse files

address Jakub's comments

parent d8c115d5
Pipeline #11833 passed with stage
in 11 seconds
......@@ -2,7 +2,7 @@
Rename the Trusted User role
============================
- Date proposed: 2021-07-27
- Date proposed: 2021-10-07
- RFC MR: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/7
Summary
......@@ -20,7 +20,7 @@ Motivation
There have been several discussions among Arch Linux members both on IRC
and more recently (27th Jul 2021) on the staff@lists.archlinux.org mailing
list about the "Trusted User" naming (later referred to simply by
list [1]_ about the "Trusted User" naming (later referred to simply by
"the naming" or "the name") and its associated controversies.
Some relevant points of the discussion:
......@@ -59,11 +59,19 @@ Drawbacks
The simple name change should have minimal impact internally and externally
for Arch Linux. In terms of their responsibilities and descriptions,
the roles remain unchanged making this the minimal incremental change
given the ideas discussed (Sections #Motivation and #Alternatives-Considered).
given the ideas discussed (Sections `Motivation`_ and `Alternatives Considered`_).
Possible difficulties exist in amending the legal documentation and making
sure all relevant Wiki and other public and private information is updated
timely to mitigate any confusion.
However, there is a the partial naming overlap with the role of ArchWiki Maintainer [2]_
where this proposal will have Trusted User be fully read as Arch Linux Maintainer
or simply Maintainer. While this could lead to partial ambiguity it will address
many more and more serious issues discussed in section `Motivation`_.
Additionally, the current TUs have overlapping privileges over the ArchWiki
and could act as an ArchWiki Maintainer, similarly to the dynamic where a
Developer is performing TU tasks.
It should also be noted that this change should be allowed to propagate
internally and externally for enough time so that members and the public
become accustomed to the naming before allowing any further re-structuring
......@@ -85,8 +93,8 @@ raised to re-think this point.
Alternatives Considered
-----------------------
There have been multiple other suggestions that have been considered before
the above selection in the #Specification section, e.g.:
There have been multiple other suggestions that have been considered before [1]_
the above selection in the `Specification`_ section, e.g.:
- Member
- Package Maintainer
- Proponent
......@@ -95,14 +103,14 @@ the above selection in the #Specification section, e.g.:
Furthermore, there have been ideas towards renaming the role of "Developer"
to "Core Maintainer", the role of "Trusted User" to simply "Maintainer" and
creating a new role called "Developer" solely reserved for members of Arch
Linux who do code development work directly relevant to Arch Linux.
Linux who do code development work directly relevant to Arch Linux [3]_.
Another similar idea was to keep the role structure as is but rename the
current "Developer" role into "Core Developer" and re-labelling the
"Trusted User" role to "Developer".
"Trusted User" role to "Developer" [4]_ [5]_.
Finally, this proposal has been seen by some as the first step towards
a larger, more meaningful re-design as so ("->" is to be read as "becomes"):
a larger, more meaningful re-design as so ("->" is to be read as "becomes") [6]_:
- package maintenance, in [core]/[extra] (Developer only)
and [community] (everyone, especially TU) -> (Core) Maintainer
......@@ -111,3 +119,10 @@ a larger, more meaningful re-design as so ("->" is to be read as "becomes"):
- tooling development, be it pacman, archweb, devtools -> Developers
- Wiki, forum, IRC/Matrix, bug wrangler, (...) -> Support Staff
- AUR handling, especially PRQ -> Trusted Users
.. [1] https://lists.archlinux.org/private/staff/2021-July/000673.html
.. [2] https://wiki.archlinux.org/title/ArchWiki:Maintenance_Team
.. [3] https://lists.archlinux.org/private/staff/2021-July/000702.html
.. [4] https://lists.archlinux.org/private/staff/2021-July/000678.html
.. [5] https://lists.archlinux.org/private/staff/2021-July/000705.html
.. [6] https://lists.archlinux.org/private/staff/2021-July/000687.html
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment