The following infrastructure is needed to maintain this project successfully. ## Master build server This will hold the list of packages that needs to be packaged, and checks for new packages frequently. It must be always online, but not essentially build packages itself. [build master](archlinux32.org) ## Build machines These machines will build each packages in a clean chroot. This requires the most computing capacity, and requires to run Arch Linux, but not needed to be always online. ## Release engineering machine These machines will build the ISO. It requires to run Arch Linux, but not needed to be always online. ## Package repository server and mirrors This is the place where the built packages and the ISO will be hosted. [mirror master](mirror.archlinux32.org) ## Git server Currently we use GitHub for this, later it can be changed. ## Web server Ideally, it runs an [archweb](https://git.archlinux.org/archweb.git/) instance. It describes the project, and provide an overview about the packages. [web server](archlinux32.org) ## Bug tracker Currently we use GitHub for this, later it can be changed. ## Mailing list We use the official [arch-ports](https://lists.archlinux.org/listinfo/arch-ports) mailing list. ## IRC channel We use the official #archlinux-ports IRC channel on [Freenode](https://freenode.net/).