On 5/20/24 11:46 AM, Giovanni Harting wrote:
Hey everyone.
Hey!
I'm hereby applying as a package maintainer, which is kindly sponsored by David (dvzrv) and Jelle (jelly) and formally by Levente (anthraxx), for whom Jelle has taken over the sponsorship.
Thanks for your application!
## Who
I'm Giovanni, also known as anonfunc or idlegandalf. I've been using Arch Linux as my day-to-day driver since 2013 and Linux in general since probably 2008 (mostly server-side until 2011-12, last Windows I actually used was 7). As for notable contributions, you might have heard of ALHP, which I started in 2020.
ALHP developed from the idea of utilising modern CPU extensions all the way back in Q4 2019 (after I had a quick Gentoo detour on one of my laptops). At the time, no x86_64 levels were defined, so the first rough outlines still considered building for specific gcc CPU-baselines, like Haswell for example (which seems crazy in hindsight). When the x86_64 levels were announced in 2020, I started developing a buildbot capable of doing the heavy lifting, at the time in Python. After ditching Python in 2021 (after I got annoyed of multi-process) and rewriting the buildbot in Go, the project launched in July 2021. At the time, ALHP only provided x86_64-v3, shortly after launch x86_64-v2 followed. In December 2023 the x86_64-v4 repo launched, after I got my hands on a machine capable of building v4. Not sure how many users it actually has, since I do not do any tracking, but as far as requests on the tier 0 mirror go (ALHP has 7 mirrors in total, one operated by myself), it seems to see some usage. The buildbot is completely FOSS, you can have a look down in the links section.
Impressive work, congrats!
Outside of my Arch Linux involvement I work as a DevOps engineer. I can also support Arch Linux there if needed.
## Goals & Packages
I want to help with package maintenance and advance infrastructure topics with the overall goal of bringing x86_64-v3 and build automation to life, as well as helping with potential problems that may come with v3, since ALHP had plenty of those already.
Upstreaming those parts would be a really great achievement! \o/ I'd be glad seeing that becoming a thing in Arch (and help where I can).
As for packages, I have a few that I think would benefit the general Arch Linux audience by being promoted to official packages, mostly QoL stuff:
- batsignal - wljoywake - jellyfin-mpv-shim (+ deps) - prismlauncher - victoriametrics - asus-numpad - mmdbinspect
I'm also open to co-maintainer roles if there are any packages in need. Candidates could include DevOps related packages like Grafana or packages from the Go ecosystem in general, since I use that language extensively.
Besides the mentioned categories, I'm also interested to co-maintain:
- home-assistant - jellyfin
## Links
AUR packages: https://aur.archlinux.org/packages?SeB=m&K=anonfunc AUR source repo: https://somegit.dev/anonfunc/aur-packages
ALHP: https://somegit.dev/ALHP/ALHP.GO ALHP Status: https://status.alhp.dev/
Feel free to criticise PKGBUILDs to your heart's content :) Improvement is a continuous thing, so keep them coming.
Well... There's not much to criticize actually! Your PKGBUILDs generally looks really good. A few minor details, just for the sake of it: - Since python-pystray is not a split package anymore, the `package_python-pysystray()` function can be renamed to `package()` [1]. - Makepkg is now capable to generate checksums for git sources [2], so you could drop `_commit` custom variable in nginxbeautifier's PKGBUILD in favor of a `git+${url}.git#tag=${pkgver}` source to avoid eventual mistakes and ease maintenance [3]. - motion-git should provide motion (in additional of conflicting it) [4]. - The source renaming in unvpk-git's PKGBUILD (`source=("unvpk::git+$url.git")`) is redundant/useless as the source is already named that way [5]. - The source renamig in rvpk's PKGBUILD (`source=("$pkgname-$pkgver::$url/archive/refs/tags/v$pkgver.tar.gz")`) is missing the `.tar.gz` extension [6]. Once again, those are all minor details and the PKGBUILDs are generally all looking good!
Giovanni
Giovanni's great packaging knowledge and his high-quality Arch contributions are undeniable; and his goal to upstream them on Arch side is greatly appreciated. I have no doubt Giovanni's would be a great addition to the team! [1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-pystray#n22 [2] https://gitlab.archlinux.org/pacman/pacman/-/releases/v6.1.0 [3] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nginxbeautifier#n14 [4] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=motion-git#n14 [5] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=unvpk-git#n14 [6] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rvpk#n13 -- Regards, Robin Candau / Antiz