common-lisp.net
Services
What common-lisp.net runs for the community today, and what it could run for you.
New: custom images
Describe the Lisp image you want, in a form or to an agent, and take away a kit for it: the base image of your choice pinned by digest, Quicklisp pinned by dist, your systems loaded, a core saved if you like, all generated from one image.sexp. The kit is free; a build here, for amd64 and arm64, takes mites from the community pot.
New: deploy an app
Your Common Lisp web application at its own name under common-lisp.app, built and run by the house from a public project on gitlab.common-lisp.net, behind the house's tollbooths if you want to charge for it. It takes five rules the application meets, and a press of Deploy; the lab's agent can bring an application into shape for them.
Free, for the community
- Project hosting: Git on GitLab, CI, a project web site and mailing lists, for open source Common Lisp projects.
- Container images: Current images of SBCL, Clozure CL, ECL, ABCL, Clasp, CLISP, CMUCL and Allegro CL Express on Docker Hub.
- Mailing lists: Lists for Lisp topics that do not need a whole project: user groups, working groups, regional meetings.
Paid services, built on the same machinery
A proposal, under discussion.
The pipelines that build the images, and the runners they build on, are now dependable enough to do work for others. common-lisp.net is considering offering that work as paid services, with the income going to the running costs of the rest.
None of what follows can be ordered yet. It is an outline: what each service would be, and for whom. If one of them would be worth paying for where you work, say so below; that is what decides which are built first, and at what price.
Supported images
For teams that ship Lisp in containers
The same images, with a commitment behind them: a rebuild within days of a security fix in the base system, tags that stay put for as long as you subscribe, advance notice of changes, and someone who answers when a build breaks.
- Security rebuilds on a stated schedule
- Long-lived tags for the versions you depend on
- amd64 and arm64
- A private channel for notices and questions
CI on every implementation
For libraries and products that must run everywhere
Your test suite, run on each release of each implementation and on both architectures, on common-lisp.net's runners. You get a report of what passed where and a notice the day a new SBCL or CCL breaks you, before your users find out.
- A scheduled matrix: implementations × versions × architectures
- Native arm64 runners
- Works for projects hosted here, on GitHub or on GitLab.com
Custom images, kept current
For a fixed environment, built once and reproducible
Kits, and builds from the community pot, are above. This is the work after a build: the image rebuilt when its base gets a security fix or its inputs change, delivered to your registry, on a subscription.
- Rebuilt on a security fix in the base
- Long-lived tags
- Delivered to your registry or to common-lisp.net's
Private hosting
For companies that work in Common Lisp
Private groups and repositories on gitlab.common-lisp.net, with CI on the Lisp images, for teams that would rather pay the community's infrastructure than a general-purpose forge.
- Private groups with CI
- Mirrors to and from other forges
- The same admins that run the public service
Sponsorship
For organisations that depend on Common Lisp
A yearly contribution to the running costs of the services on this page, acknowledged here. Not a purchase of anything: the way to keep the shared infrastructure of the language in good health.
- Named on this site
- An invitation to the board's meetings
- A say in what gets built next
Interested?
Say which service, and what you would need from it. The people who run the site read these; nothing is promised on either side. You can also write to clf@cl-foundation.org.
Something wrong or missing here? Edit this page on GitLab.