Table of contents
Common-Lisp.net project hosting
What you get
Hosted projects get web space, mailing lists, and disk space for a version control system. We offer git through GitLab and Subversion, augmented with Trac. Older projects may be using different version control systems, but those services have been deprecated -- new projects should use Git or Subversion and old projects will be migrated in the course of 2015.
Requesting access to an existing project
If you want to join an existing project, please contact the project owners through the project mailing list (usually <project>-firstname.lastname@example.org). One of the project members will contact the site admins to ask a user to be added to their project.
If the project is orphaned, or has no mailing list, please contact email@example.com directly.
Your common-lisp.net account
In order to access project resources, you'll be assigned an account on the common-lisp.net system.
An e-mail alias will be set up for you as >user-name<@common-lisp.net. The account will forward mail to an account of your choice. If you want to change the address to which the alias forwards, please change the mail address in the .forward file in your home directory.
The machine doesn't allow password-based logins. To access the machine, you need an SSH public key, which will be stored in the file .ssh/authorized_keys in your home directory.
There are no limits placed on how much space you can use but please exercise care; you will be sharing this system with others. No CPU/RAM intensive tasks are to be performed on the server. You have shell access but don't use it unless you need to perform administrative tasks on your project(s).
Please note that the above also means 'no long running processes' - e.g. no running irc or xmpp clients.
If you want to run a mirror of some resource on common-lisp.net, please contact the administrators to set up the mirroring as a system service and monitoring thereof. Please do not use your a cron job with your own user without consulting the admins.
Creating a project
Send an email to admin (at) common-lisp (dot) net with details about your project (your full name, your gpg public key, description of project, any members (and their full names), name of project and what license the code is released under). Hosting decisions are made on case-by-case basis.
As a first step, please take some time to add a simple web-page for your project. The quickest alternative edit the HTML for our sample project. After editing it to fit your project, you can upload it to our server (via scp). See also our section titled "Website".
Git repository access
Git repositories are managed using GitLab. When your account gets created, a GitLab account will be created as well. Your GitLab account will be assigned to the GitLab groups you're a member of.
Using your GitLab account, you can create Git repositories for your project. Anonymous git access is available for public repositories through https.
Your commit mails are not automatically replicated to your commit mailing list (<project-name>-firstname.lastname@example.org). It's easy to set up though. Simply go through the following steps:
- Go to the project's landing page (not the group's), e.g. SLIME's: https://gitlab.common-lisp.net/slime/slime
- Click on "Settings" at the bottom of the left menu bar
- Click on "Services" in the next page
- From the list of services in the resulting page, select "E-mail on push"
- Enter the recipients for push mails, including the mailing list name of your project (i.e. <project-name>-email@example.com)
Subversion repository access
Your Subversion repository is in /project/<project-name>/svn. By default, any commits to it will be sent to <project-name>-firstname.lastname@example.org.
Anonymous read-only Subversion access is enabled by default.
Repositories over the web
CVS and Subversion repositories are viewable over the web by default as long as you don't change the default configuration. For darcs you have to create your repositories in /project/<project>/public_html/darcs/ and a nightly cronjob will pick them up and add them to the darcsweb config file.
/project/<project-name>/public_html is symlinked to from our webserver hierarchy and any files you put there will be available by pointing your webbrowser to http://common-lisp.net/project/<project-name>
We would like to ask you to put up a minimal webpage as soon as possible (an empty directory does not say much about your project). The quickest way is to edit the HTML of our sample project page.
Apache Server-Side Includes are enabled.
Automatic and manual mailinglists
When your project is set up, three mailinglists are created (if you'd rather use NNTP you can subscribe Gmane to your list):
You, the owner, are subscribed to all of these mailinglists by default. Any members added later will have to subscribe to the ones they want on their own, via the Mailman interface at:
Additional mailing lists available on request.
To stay up-to-date with all releases that are announced on the various mailinglists you simply need to be subscribed to the announcements mailinglist as this mailinglist is in turn subscribed to all <project-name>-announce lists.
For adding/removing project members, additional mailing lists, etc, send an email to admin (at) common-lisp (dot) net with all the relevant details (project name, etc).
List of project members
Every night a cronjob runs which generates a list of users who
have write access to your repositories and files. This list is
You may use Apache SSI to include this list on your project's
web page, ie
<!--#include virtual="../../pprinted-project-members/<project>" -->
Restoring from backup
All the data is backed up regularly both on- and off-site, to cover for scenarios of user-accident as well as disaster recovery. There is, however, no provision for user-driven recovery. Please be careful before deleting anything on your server.
We have cronjobs which look for broken links, to see if you have
changed from the default webpage, etc. If they detect any problems
they will nag you about it every week until you fix the problem. To
which email address are these nags sent? By default,
however you can change this by creating a file named
/project/<project-name>/owner-email-address and putting whatever email address you want in there. Only put your email address there or someone who
has given you permission to do so; if you misuse this your project's approval is rescinded.
We offer a Trac instance for projects who would like one. Please specify
if want one when you set up your project or email
admin (at) common-lisp (dot) net
to request it for an existing project.
To learn more about how Trac works at common-lisp.net, please read our Trac @ clnet introduction .