Package Maintainers: Difference between revisions
Lahwaacz.bot (talk | contribs) (update old mailman URLs from (lists|mailman).archlinux.org/listinfo/ to lists.archlinux.org/mailman3/lists/) |
m (Update the Ja link.) |
||
(17 intermediate revisions by 9 users not shown) | |||
Line 3: | Line 3: | ||
[[es:Trusted Users]] | [[es:Trusted Users]] | ||
[[fr:Trusted Users]] | [[fr:Trusted Users]] | ||
[[ja: | [[ja:Package Maintainers]] | ||
[[pt: | [[pt:Package Maintainers]] | ||
[[zh-hans: | [[zh-hans:Package Maintainers]] | ||
[https://archlinux.org/people/package-maintainers/ Package Maintainers] (previously called [https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/6UPKMAL2A7FNAUNWMTHWI4EXV2KS5OSC/ Trusted Users]) are an official Arch Linux staff role. Package Maintainers fulfill the following tasks: | |||
* Maintain packages in the official repositories (aside from the ''core'' one). | |||
* Maintain, manage, and watch over the operation of the [[AUR]]. | |||
The generic term "package maintainer" is also used to describe any person maintaining a package, regardless of the repository, as described in [[Arch terminology#Package maintainer]]. | |||
The ''minimum'' requirements to becoming a | == How do I become a Package Maintainer? == | ||
The ''minimum'' requirements to becoming a Package Maintainer are as follows: | |||
* know basic shell scripting | * know basic shell scripting | ||
Line 19: | Line 21: | ||
* basic community involvement (mailing list, forums, IRC) | * basic community involvement (mailing list, forums, IRC) | ||
* know Google-Fu | * know Google-Fu | ||
* a general idea of the kind of packages you want to maintain (basically, why do you want to become | * a general idea of the kind of packages you want to maintain (basically, why do you want to become Package Maintainer?) | ||
Even though you could become a | Even though you could become a Package Maintainer by merely fulfilling those minimum requirements, the people judging you during the [https://package-maintainer-bylaws.aur.archlinux.org/#_standard_voting_procedure standard voting procedure] might expect more from you. Such as: | ||
* involvement in the bug tracker (reporting, research, info) | * involvement in the bug tracker (reporting, research, info) | ||
Line 27: | Line 29: | ||
* involvement in a few open-source projects (even if they are your own) | * involvement in a few open-source projects (even if they are your own) | ||
If you still feel up to becoming a | If you still feel up to becoming a Package Maintainer after reading these lines, the first step is to find two Package Maintainers who agree to sponsor you. Once sponsored, you should write a witty application signed with your GPG key to the [https://lists.archlinux.org/mailman3/lists/aur-general.lists.archlinux.org/ aur-general mailing list]. | ||
{{Note|Should a | {{Note|Should a Package Maintainer you contact decline to sponsor your application, you should make this fact known if you seek sponsorship from another Package Maintainer.}} | ||
For more information, see the [https://aur.archlinux.org/ | For more information, see the [https://package-maintainer-bylaws.aur.archlinux.org/ Package Maintainer Bylaws] and [[Package Maintainer guidelines]]. | ||
== Active | == Active Package Maintainers == | ||
See https://archlinux.org/people/ | See https://archlinux.org/people/package-maintainers/ | ||
== Past | == Past Package Maintainers == | ||
See https://archlinux.org/people/ | See https://archlinux.org/people/package-maintainer-fellows/ |
Latest revision as of 15:24, 4 February 2024
Package Maintainers (previously called Trusted Users) are an official Arch Linux staff role. Package Maintainers fulfill the following tasks:
- Maintain packages in the official repositories (aside from the core one).
- Maintain, manage, and watch over the operation of the AUR.
The generic term "package maintainer" is also used to describe any person maintaining a package, regardless of the repository, as described in Arch terminology#Package maintainer.
How do I become a Package Maintainer?
The minimum requirements to becoming a Package Maintainer are as follows:
- know basic shell scripting
- maintain a few packages in AUR with clean, high-quality PKGBUILDs
- basic community involvement (mailing list, forums, IRC)
- know Google-Fu
- a general idea of the kind of packages you want to maintain (basically, why do you want to become Package Maintainer?)
Even though you could become a Package Maintainer by merely fulfilling those minimum requirements, the people judging you during the standard voting procedure might expect more from you. Such as:
- involvement in the bug tracker (reporting, research, info)
- patches for Arch projects
- involvement in a few open-source projects (even if they are your own)
If you still feel up to becoming a Package Maintainer after reading these lines, the first step is to find two Package Maintainers who agree to sponsor you. Once sponsored, you should write a witty application signed with your GPG key to the aur-general mailing list.
For more information, see the Package Maintainer Bylaws and Package Maintainer guidelines.
Active Package Maintainers
See https://archlinux.org/people/package-maintainers/
Past Package Maintainers
See https://archlinux.org/people/package-maintainer-fellows/