Group: Software/FSDG distributions/infrastructure

Introduction

For some people, the infrastructure of FSDG compliant distributions is something important for choosing a distribution.

It's also useful to know about it to see how fragile the distribution is.

Hosting	Hosting details	Service	Software
GNU		Git repositories
GNU		Mailing lists	Mailman
GNU?	Probably a small VM at the FSF^[1]	Builder and packages hosting: ci.guix.gnu.org
MDC at INRIA (French academic research institution)?	* Machine with a nonfree boot software^[2]	Builder and packages hosting: bordeaux.guix.gnu.org

Service	Software	Hosting
Bug tracker	Redmine	Self hosted in a VM, probably in some machine with a nonfree boot software not controlled by Parabola.
git	?
Mailing lists	Mailman

Hosting	Hosting details	Service	Software
FSF VM	Self hosted in a VM in the FSF infrastructure. The FSF handles only the backups. Source code available in the git.replicant.us front website and in various git repositories. Uses letsencrypt Runs Trisquel with automatic security updates	Contact mail address	Apache 2.0 for letsencrypt renwal Configuration settings Dovecot OpenSMTPD
		git	Apache 2.0 Apache 2.0 public configuration cgit gitolite gitolite secret configuration^[3]
		IRC Bridge	Guix for the matterbridge package guix configuration for easy install / removal of Guix to not have guix installed all the time and reduce the space and attack surface. Parabola systemd unit for sandboxing matterbridge Matterbridge Matterbridge configuration
OSUOSL	managed by OSUOSL	Bug tracker	Redmine
		FTP	A web server (Apache? Nginx?) OpenSSH with sftp enabled A script inside the server to make new changes public
		Mailing list	Mailman Probably some SMTP server software

↑ If it's the same machine than the previous hydra.gnu.org, the Ten years of failures talk at Ten Years of Guix says that hydra.gnu.org is a "Virtual machine hosted at the FSF" and that it is "Too weak for our growing needs".
↑ See the Ten years of failures talk at Ten Years of Guix for more details.
↑ This allows to create secret repositories if necessary, for instance to work on criteria for choosing a community manager, to work on mails for reviewing applications for that, etc.