As previously mentioned, there is the ports RFC [1]. I'd argue that the only thing missing to get the ball really rolling is a bit of organization (and maybe breaking things down so users of all experience levels can help). I often find myself (like many others) going back to the ALARM repos mainly because they sort-of work; but contributing to those has been a pain and more often than not things break and everyone's on its own (mainly because there's no "central place" where to share things). I know there's been lots of efforts around this [2] but even then it feels like we are all waiting on the infra/tooling to magically appear and work for ports and the reality is that "talk is cheap, send patches". Some "talk" will be necessary as there's a lot of things that should be integrated into arch's tooling, but there's the need to get some momentum going. I think that the rest will come by itself; we're at a point where even building everything on an emulated VM would be kind-of feasible because there is the computing power. I'm going on a tangent here, of course there are better solutions, but what I'm trying to say is: what we need is involvement, interest, and people willing to organize and put in the work to move the project forward :) I'll open an issue there [2] mentioning this thread to see what the people actually working on the project think, and to ask how we can help! Fermín Olaiz. --- [1] https://rfc.archlinux.page/0032-arch-linux-ports/ [2] https://gitlab.archlinux.org/archlinux/ports/aarch64/project-management/