Morganamilo
Place repo into organization, establish governance + other contributors
Affected Version
All
Description
We have several PRs and issues around the libalpm updates that are sitting in the queue. The repo owner (who also has commit rights on the libalpm rust bindings under the archlinux org) has only just become active in the last 8 hours after been inactive for most of the month.
While this is not Critical Infrastructure for Arch users, it is definitely a great FOSS project, used and beloved by the community, that deserves attention.
Some trusted contributors who can approve/merge PRs should be designated, and the project should probably be placed into an organization to protect against an Extended Vacation from the owner due to burnout or other causes. I am not qualified to make the determinations as to who should be designated and where the repo should go. This is an effort that should be lead by @Morganamilo
I am just a user of this application, and have no commits; I have very little skin in-the-game and no table stakes. But I think the above is reasonable and natural for a FOSS project that grows in popularity, but relies on a single critical person who may not always be available.
All of this is shared with the utmost respect and in the spirit of preventing future breaks (like the reality that paru has been broken for several days in mainline arch/endevouros installs because of the the libalpm update). yay is just not as good, let's face it.
I concur 100%. It's not the first time this happens after a core/pacman update breaking libalpm compatibility.
