Talk:Package Maintainers
Adding expected information to the list
After submitting my application to become a TU, it was brought to my attention that it would be desireable if I included links to my AUR, bug tracker, github, etc involvement. I thought it was enough to just mention that I have been active there - but perhaps clarifying the expected information a bit more would help.
Suggestion:
- Add a few links to some good applications in the mailing list
- Add a template of expected information (based on the most common information sources such as AUR packages and github)
Torxed (talk) 11:59, 14 March 2023 (UTC)
Minimum requirements for becoming a package maintainer
There was a recent discussion on IRC about the minimum requirements for becoming a Package Maintainer, which concluded that we want to put more emphasis on:
- Soft skills such as communication skills, positivity and helpfulness
- Hard skills such as packaging guideline compliance and amount of packages
This is already expected from the applicants for the role, so it's only fair to communicate in the article aswell. Are there suggestions for the exact wording in the article? See below for a possible modification of the existing bullet points:
- maintain a few packages in AUR with clean, high-quality PKGBUILDs (see Arch package guidelines)
- friendly, helpful interaction with the broader Arch Linux community (mailing lists, forums, IRC, Gitlab, AUR)
- a general idea of the kind of packages you want to maintain (basically, why do you want to become Package Maintainer? Also note that people are usually not onboarded to maintain a really narrow set of packages)