Hosted projects get web space, mailing lists, and disk space for a version control system. We offer git, Subversion, darcs and CVS.
topSend an email to admin (at) common-lisp (dot) net with details about your project (your full name, your SSH 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.
If your application is accepted a project directory owned by you, with project-name as its group will be created at /project/<project-name>. Any project members are simply made members of group project-name.
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".
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.
Email to your account @common-lisp.net will be forwarded to the email address that you have supplied in your account application. Edit the file .forwad in your home directory to change the forwarding address.
topYour CVS repository is in /project/<project-name>/cvsroot. By default, any commits to it will be sent to <project-name>-cvs@common-lisp.net.
Anonymous read-only CVS access is enabled by default (see FAQ), though it lags behind the writable repository by 15 minutes.
Your CVS repository will also be available through the web at http://common-lisp.net/cgi-bin/viewcvs.cgi/?cvsroot=<project-name>.
topYour Subversion repository is in /project/<project-name>/svn. By default, any commits to it will be sent to <project-name>-cvs@common-lisp.net.
Anonymous read-only Subversion access is enabled by default (see FAQ).
topYour 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.
top
/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.
topWhen 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.
topFor 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).
topEvery night a cronjob runs which generates a list of users who
have write access to your repositories and files. This list is
placed in /var/www/pprinted-project-members/<project>.
You may use Apache SSI to include this list on your project's
web page, ie <!--#include virtual="../../pprinted-project-members/<project> -->
We do not keep offsite backups so for all intents and purposes you must assume that there are no backups of any data. Please govern yourself accordingly.
topWe 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, <project-name>-devel@common-lisp.net
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 .
top