ArchZFS provides ZFS packages and repository tooling for Arch Linux. It is an independent community project and is not endorsed by Arch Linux or OpenZFS.

• Read the ArchZFS Wiki for current installation and package guidance.
• Download the current signed Pacman repository from the experimental release.
• Consult the ArchWiki ZFS article for general Arch Linux and ZFS guidance.
• Report reproducible ArchZFS problems in the main issue tracker and use Discussions for broader project questions and proposals.

The fixed-name experimental release is the current public Pacman repository. It uses the released OpenZFS version selected by ArchZFS, although individual kernel packages may lag or be unavailable when compatibility builds fail. Its artifacts are signed, but production keyring integration remains incomplete; follow the release page for the current repository configuration and trust options.

• archzfs is the production control repository for package generation, builds, signing, and GitHub Releases publication.

• archzfs-testing is the disposable staging fork for release-infrastructure changes. Its releases are not end-user repositories.
• archzfs-keyring contains the intended ArchZFS web-of-trust key material. Packaging and production integration are not complete.
• archzfs-mirror is intended to provide reusable mirror synchronization tooling. Its implementation remains proposed and is not deployed from the default branch.

Repositories such as zfs-utils, zfs-dkms, zfs-linux, zfs-linux-lts, zfs-linux-hardened, and zfs-linux-zen contain generated PKGBUILDs. Their source templates and build policy live in archzfs; they are not independent control repositories. Git and release-candidate variants remain in the organization but are not part of the current public package release.

• archzfs-ci contains the former Buildbot-based testing and deployment system. Current production uses GitHub Actions from archzfs.

Read the organization-wide contribution guide before choosing a repository. Release, signing, keyring, and generated-package changes have repository-specific safety and review requirements.