We want to provide a warm, friendly, and harassment-free environment, so that anyone can contribute to the best of their abilities. To this end our project uses a “Contributor Covenant”, which was adapted from https://contributor-covenant.org/. You can find the full pledge in the CODE-OF-CONDUCT file.
Participation to the project communication channels listed below is subject to this code of conduct.
#guix channel on the Libera Chat IRC network to
chat with the community about GNU Guix or to get help in real-time.
Subscribe to the
info-guix low-traffic mailing
list to receive important announcements sent by the project maintainers (in
If you found a bug in Guix, check whether the bug is already in the bug database. If it is not, please report it.
Discussion about the development of GNU Guix. Until July 2013, the bug-Guix mailing list filled that role.
Submission of patches. Every message sent to this mailing list leads to a new entry in our patch tracking tool. See this page for more information on how to use it; see the manual for more information on how to submit a patch. Until February 2017, the guix-devel mailing list filled that role.
Discussions about using GNU Guix for scientific purposes: reproducible research, high-performance computing (HPC), and more.
Notifications of commits made to the Git repositories.
This is a private mailing list that anyone can post to to report security issues in Guix itself or in the packages it provides. Posting here allows Guix developers to address the problem before it is widely publicized.
Private mailing list for the build farm system administration.
Private alias to reach the maintainer collective. This should generally not be used to discuss technical issues.
Discussion about the development of the broader GNU system.
Workgroup for fully free GNU/Linux distributions.
GNU software announcements.