Services Outside Savannah

GNU Savannah is operated by volunteer admins. Many servers and services which are closely related to Savannah's operation are not handled by Savannah admins.

When a problem arises with these servers or services, it is best to contact the relevant party directly: FSF sysadmins for server-related issues and GNU teams for GNU-related issues. See below for details.

GNU Project and Official GNU Packages

Savannah administrators cannot help with official GNU-related matters, such as: approving a new GNU package, changing the stasus of a Savannah group from gnu to nongnu or vice versa, approving new co-maintainers, dealing with FSF copyright assignments, and plenty more.

• GNU package maintenance issues (e.g., if you are a GNU package maintainer and have a question regarding GNU issues): See the "Getting Help" section in the GNU Maintainers Guide at https://www.gnu.org/prep/maintain/maintain.html#Getting-Help.

• General GNU-related issues: See https://www.gnu.org/contact/.

Server Issues - Contacting FSF sysadmin:

Many servers and services which are closely related to Savannah operation are maintained by FSF sysadmins, and Savannah volunteers do not have access to them.

When a problem arises with these servers, it is best to contact FSF admins directly (although notifying Savannah admins by CC'ing savannah-hackers-public@gnu.org is ok and can help us keep track of problems).

• FSF out-of-band outage notifications: https://hostux.social/@fsfstatus

• IRC: #fsfsys channel on Libera.chat (https://web.libera.chat/). FSF sysadmins are currently quidam, sudoman, and iank. John Sullivan (FSF Executive Director) is johnsu01 (http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00037.html). See also GNU,FSF IRC Channels.

• Email: sysadmin@gnu.org, equivalently sysadmin@fsf.org. Emailing will create a new support ticket in their queue. Please try not to burden them unnecessarily; prefer IRC for faster communication.

• FSF personnel: see FSF Staff and Board.

Servers and services

• fencepost.gnu.org - maintained by FSF sysadmins (including login issues, sending/receiving email there, installed packages, etc.). Before contacting FSF sysadmins, try writing to fencepost-users@gnu.org (https://lists.gnu.org/mailman/listinfo/fencepost-users).

• Mailing lists (lists.gnu.org) - the host, mail setup, and Mailman installation are managed by FSF sysadmins. Savannah hackers have limited (non-root) access to mailing lists and archives. All requests for deletion of archived email must go to FSF sysadmin.

• Web pages at http://www.gnu.org: the served files are maintained by webmasters@gnu.org and GNU package maintainers, Apache configuration by FSF sysadmins. A copy of the live configuration is in fencepost:/srv/data/www-config/ and a copy of the live server is in fencepost:/srv/data/www-mirror/. Individual package web pages are hosted in Savannah CVS "webpages" repositories (always CVS), but are sync'd to www.gnu.org for the actual serving (HomePage).

• ftp.gnu.org - the main distribution server for GNU, managed entirely by FSF sysadmin. Compare with downloads for nongnu.org, which does happen on Savannah DownloadArea.

• GNU Bug Tracker (http://debbugs.gnu.org) - managed by other non-Savannah volunteers; write to help-debbugs@gnu.org (https://lists.gnu.org/mailman/listinfo/help-debbugs) for help.

• The Savannah hosts themselves are virtual machines on FSF-managed hardware; Savannah volunteers have root access to the virtual hosts, but no access to the hardware.

More information

• Savannah/FSF servers: SavannahServices, SavannahArchitecture, GnuArchitecture

• Email: MailSystem. See also detailed description of mail system by Bob Proulx: http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00029.html, http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00036.html, http://lists.gnu.org/archive/html/savannah-hackers-public/2016-04/msg00040.html.

• Lists: ListServer.