Project hosting

What you get

A Git repository on gitlab.common-lisp.net, with issues, merge requests and pipelines that can test on every major implementation; a web site at <project>.common-lisp.dev; and a <project>-devel mailing list on request, with more if the project needs them. Projects from before the move to Git may still use Subversion with Trac.

A project on GitLab can use GitLab Pages to publish its site. The Boston Lisp site repository is an example; its .gitlab-ci.yml shows how, and the FAQ has step-by-step instructions. To test on several implementations, see Using GitLab CI to test CL projects.

Joining an existing project

Anyone can read and clone a public repository over https; no account is needed for that.

To contribute, get an account and ask for access on the project's GitLab page; the project's owners are notified and can add you themselves. You can also reach them on the project's mailing list, usually <project>-devel@common-lisp.net. If the project is orphaned or has no list, send the admins a request or write to admin@common-lisp.net.

Starting a project

1. Get an account and tell the admins that you want to create projects. Because of spam this permission is given by hand.
2. Create the project on GitLab. You can create up to ten in your own namespace, but a group for the project is strongly encouraged: it gives the project's site a nicer address and gives you better control over who can do what when several people work on related repositories. Ask for a group with the same request.
3. Set up a simple web page for the project with GitLab Pages, as described above.
4. If you want commits announced on a mailing list, turn on e-mail on push.

House rules

There are no hard limits on what a project may use. You are sharing the system with others, so please:

• run no CPU- or memory-intensive tasks, and no long-running ones (no chat clients, no screen sessions);
• use shell access, if you have it, only to administer your projects;
• store only data that is meant to be public;
• ask the admins before hosting video or other large files, before setting up cron jobs, and if you would like your project mirrored.

Mailing lists

When a project is set up, one list, <project>-devel@common-lisp.net, can be created for it, with the requester subscribed. Later members subscribe themselves through the list server. More lists are available on request.

Backups

All data is backed up regularly, on site and off, against both accident and disaster. There is no self-service restore, though, so please be careful before deleting anything in your project.

Subversion and Trac

Projects that still use Subversion keep their repository at /project/<project>/svn; anonymous read-only access is at https://svn.common-lisp.net/<project>, and commits are mailed to <project>-cvs@common-lisp.net. A Subversion account is separate from a GitLab account and is requested from the admins with an SSH public key. Such a project's web site is /project/<project>/public_html, published as https://<project>.common-lisp.dev/. Trac is available to these projects on request; see Tools.

Asking the admins

For adding or removing project members, new groups, more mailing lists and anything else that needs an admin, send the admins a request or write to admin@common-lisp.net, with the name of the project and the details.