Most websites contain pretty basic information. Using the DOAP files, we should be able to create a basic website.

It should create:
projects.gnome.org/$modulename

where $modulename refers to the Git module name.

Each module could have one or more tarballs. By default (if the DOAP doesn't have any specific info), it is assumed the module and tarball name are the same. Using this information, latest releases can be shown on projects.gnome.org/$modulename (perhaps some subpage).

The DOAP generated projects.gnome.org should be linked to:
 * git.gnome.org (DOAP files)
   --> when a DOAP file is changed, projects.gnome.org should be updated asap
 * master.gnome.org (basically ftp.gnome.org)
   --> when a new release is made, projects.gnome.org should mention it asap

The basic projects.gnome.org site should:
 * description, license info, bugzilla, wiki
 * link to git.gnome.org with basic instructions on how to use that
   --> as module name is known, exact instructions can be given
 * link to ftp.gnome.org
 * link to mail.gnome.org
 * names of the *maintainers*

For git.gnome.org it should rely on something generic like the
http://git.gnome.org/repositories.doap. Already some hook checks the doap files, can easily be extended to make it update projects.gnome.org.

For master.gnome.org, perhaps just NFS mount the /ftp directory? Also, extend install-module (maintained in the releng module). Finding the right tarball names means the DOAP files should be parsed first.

Further, the automatically found information should again be made available using e.g. http://projects.gnome.org/$modulename.doap. That is basically the repositories.doap split out per module, with the addition of the releases on ftp.gnome.org.

To parse a doap file, see e.g. sysadmin-bin module and gitadmin-bin module.