Package Maintainer application - Giovanni Harting
Hey everyone. 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. ## 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. 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. 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. Giovanni
On 2024-05-20 11:46:16 (+0200), Giovanni Harting wrote:
I confirm my sponsorship. I have first met Giovanni in person at last year's All Systems Go! in Berlin and was left with the impression of a friendly person with diverse technical interests, working on pragmatic solutions to some of our distribution's longstanding problems. I believe him to be a great addition to the team. :) Best, David -- https://sleepmap.de
On 20-05-2024 11:46, Giovanni Harting wrote:
I confirm my sponsorship! Greetings, Jelle van der Waa
On 2024-05-20 13:46:38 (+0200), Jelle van der Waa wrote:
As reminder: The discussion period for Giovanni's application has started with the acknowledgement of the 2nd sponsor. There is still one week to go, after which the voting period will start :) Best, David -- https://sleepmap.de
On 5/20/24 11:46 AM, Giovanni Harting wrote:
Hey everyone.
Hey!
Thanks for your application!
Impressive work, congrats!
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).
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
On 24/05/20 11:46AM, Giovanni Harting wrote:
Hey everyone.
Hey Giovanni 👋
Thanks for applying and good luck in the process! 😋 Sorry for replying last minute, but I didn't find the time / got sidetracked with other things in the last week!
That sounds cool and like a very useful addition to the team! In which way did these endeavours make you contribute back to the Arch Linux ecosystem so far? Because your name only rings a bell for me regarding the ALHP project but not i.e. via bug reports, merge requests or similar 🤔 Then again I'm not part of the team for too long 😄
Sounds good, especially since this is already ratified from the RFC side (RFC002) and can (in theory) just be started with!
Is this an AUR package already? If yes I think I couldn't find it.
With regard to votes & popularity some of these seem a bit low (with prismlauncher being the obvious outlier), so even though the related rules[0] are not enforced strictly some of these might need some extra consideration 🤔
I had a quick look at your AUR packages and didn't find many extra comments to those of Antiz. Some things are weirdly indented, but well thats just nitpicking 😆
Again, thanks for applying and I already got some ideas/questions looking at the repositories so I'm looking forward to having you on the team and discussing/implementing these things! 🚀 Cheers, chris [0]: https://wiki.archlinux.org/title/Package_Maintainer_guidelines#Rules_for_pac...
On 02/06/2024 01:11, Christian Heusel wrote:
Hey Christian.
There are a few here and there, but that's mostly packaging stuff (most recent one was a (more or less) missing mesa dep. I found because the ALHP build failed). There are also some related to outdated packages (like firefox currently not building because llvm introduced a bug in 18.1 preventing the build with lto: https://somegit.dev/ALHP/ALHP.GO/issues/222), for which I do not want to file bugs. I think most would creep up if Arch would introduce x86_64-v3, since there are quite a few special snowflake packages that I collected over the years :) pkgctl has a few odd behaviours (like if/when one moves a package between any and x86_64) I want to have a look at that if I find time. Until now I mostly "fixed" things like this on ALHPs end, but I think now is certainly the time to change that. The git migration also helped immensely in that area :)
https://aur.archlinux.org/packages/batsignal
Sure, if you have anything in mind regards to what should be considered, please let me know.
Happy to be here and looking forward to getting things rolling :)
Hi all, On 2024-05-20 11:46:16 (+0200), Giovanni Harting wrote:
The discussion period is now over and I have created a vote which will end on 2024-06-12 00:13 (CEST). https://aur.archlinux.org/package-maintainer/154 Thanks to everyone who participated in the discussion period! Best, David -- https://sleepmap.de
On 2024-06-05 00:15:53 (+0200), David Runge wrote:
The discussion period is now over and I have created a vote which will end on 2024-06-12 00:13 (CEST).
The vote is over and the results are in: Yes No Abstain Total Participation 49 2 5 56 86.15% I am pleased to welcome Giovanni as new Arch Linux packager! Best, David -- https://sleepmap.de
participants (6)
-
Christian Heusel
-
David Runge
-
Giovanni Harting
-
Jelle van der Waa
-
Robin Candau
-
Santiago Torres-Arias