Web pages for Savannah groups

Each group at Savannah may have a "web pages" CVS repository, completely separate from any "sources" repositories. These are the standard URLs provided:

  • For non-GNU groups: www.nongnu.org/group/ and group.nongnu.org/
  • For GNU packages: www.gnu.org/software/group/ (shortcut: www.gnu.org/s/group/)
  • For GNU translation teams: www.gnu.org/server/standards/translations/language-code
  • For portions of www.gnu.org: specific for each group.

Initial upload of web pages: HomepageUpload.

Basic CVS usage: CvsGettingStarted.


No symbolic links (sysadmin@fsf.org says: "security reasons" and "there's also the fact that CVS doesn't handle symlinks") - use .symlinks instead. Add a file named .symlinks in each directory where you want to make symbolic links. Each line of the file lists a real file name followed by the name of the symbolic link. The symbolic links are built every hour.


An Apache .htaccess file can be used, with some limitations. The enclosing server configuration says:

AllowOverride Indexes FileInfo Limit AuthConfig

General CGI scripts are not enabled. Basic Apache SSI commands do work.

Using a different VCS

Many people have requested using something other than CVS for their web page repositories. This requires substantial frontend work, backend work, and coordination with the FSF sysadmins. CVS is more than sufficient as the version control system for webpages. Using Git would increase both the general traffic and Git system load, and as of 2022, Git operation is far from faultless.

Source repositories can use any supported VC.