On 24/05/20 11:46AM, Giovanni Harting wrote: > Hey everyone. Hey Giovanni 👋
> 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 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! > ## 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. 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 😄 > ## 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. Sounds good, especially since this is already ratified from the RFC side (RFC002) and can (in theory) just be started with! > 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 Is this an AUR package already? If yes I think I couldn't find it. > - wljoywake > - jellyfin-mpv-shim (+ deps) > - prismlauncher > - victoriametrics > - asus-numpad > - mmdbinspect 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'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 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 😆 > 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 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_packages_entering_the_extra_repository
signature.asc
Description: PGP signature
