Commit 1cad8721 authored by Mariano Montone's avatar Mariano Montone

Page titles and templates cleanup

parent db86342e
---
title: About
---
<h2>About Common-Lisp.net</h2>
<p> Common-Lisp.net provides hosting for projects and user groups
......
---
title: Contribute
---
<h2>Donations</h2>
<p>The easiest way to contribute is to donate. The costs of running
......
---
title: Downloads
---
<h2>Download/Install</h2>
<p>Common Lisp comes in many different flavors, or implementations. Two popular ones are Steel Bank Common Lisp (SBCL) and Clozure Common Lisp (CCL).</p>
......
---
title: Frequently asked questions for common-lisp.net
---
<!-- <div class="sideBox LHS">
<div>This Page</div>
<a href="#introduction">Introduction</a>
<a href="#news">News</a>
<a href="#description">What is it</a>
<a href="#services">Services</a>
<a href="#about">About this site</a>
</div> -->
<!--
<div class="sideBox RHS">
<div>Recent projects
</div>
<table><tbody>
<tr><td colspan="2">
<a href="projects.shtml">More projects...</a>
</td></tr>
<tr><td colspan="2">
<a href="recent-projects.xml" class='rss-icon'>RSS</a>
</td></tr>
</tbody></table>
</div>
-->
<main>
<article>
<h2>Common-Lisp.net Frequently Asked Questions</h2>
<ul>
<li>GitLab: configure e-mail on push</li>
</ul>
<section id="faq-email-on-push">
<h3>GitLab: configure e-mail on push</h3>
<p>
GitLab supports sending an e-mail upon pushing
commits by project members. In order to use the functionality,
please follow the steps outlined in <a href="/faq/emailonpush/"
>our configuration guide</a>.
</p>
</section>
</article>
</main>
<main>
<article>
<h2>Common-Lisp.net Frequently Asked Questions</h2>
<ul>
<li>GitLab: configure e-mail on push</li>
</ul>
<section id="faq-email-on-push">
<h3>GitLab: configure e-mail on push</h3>
<p>
GitLab supports sending an e-mail upon pushing
commits by project members. In order to use the functionality,
please follow the steps outlined in <a href="/faq/emailonpush/"
>our configuration guide</a>.
</p>
</section>
</article>
</main>
---
title: Migration to GitLab for Common-Lisp.net
---
<!-- <div class="sideBox LHS">
<div>This Page</div>
<a href="#introduction">Introduction</a>
<a href="#news">News</a>
<a href="#description">What is it</a>
<a href="#services">Services</a>
<a href="#about">About this site</a>
</div> -->
<main>
<article>
<h2>Common-Lisp.net migration to GitLab: status</h2>
<summary>
<p>
As announced in <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000161.html">this e-mail</a>,
common-lisp.net services will be restructured - to the benefit
of (most) users as well as the admins.
</p>
<p>In this <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000168.html">follow-up e-mail</a>,
a roadmap was proposed on how to get services restructured.
Said roadmap is the basis for the table below showing the
status of each step and if completed - when the step was completed.
</p>
</summary>
<!--
<div class="sideBox RHS">
<div>Recent projects
</div>
<table><tbody>
<table class="cltable">
<thead>
<tr>
<th>#</th><th>Step</th><th>Status</th><th>Date</th>
</tr>
</thead>
<tr><td colspan="2">
<a href="projects.shtml">More projects...</a>
</td></tr>
<tr><td colspan="2">
<a href="recent-projects.xml" class='rss-icon'>RSS</a>
</td></tr>
</tbody></table>
</div>
-->
<tbody>
<tr><td>0.</td><td>Install a Code Commenting plugin on Trac to
make it match the GitLab code commenting capabilities</td>
<td>Pending</td><td>&nbsp;</td></tr>
<tr><td>1.</td><td>Finish my experiments regarding the GitLab
setup / installation <br />
see <a href="https://mailman.common-lisp.net/pipermail/announcements/2015-March/000003.html">feedback solicited</a>
and <a href="gitlab-migration-repository-mapping/">mapping of repositories</a></td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>2.</td><td>Install GitLab on common-lisp.net (under the
gitlab.common-lisp.net domain? or should we prefer
git.common-lisp.net?)</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>3.</td><td>Run the migration to create all users and
groups in GitLab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>4.</td><td>Import the CMUCL git repositories (using the
script to be used for all projects)</td><td>skipped</td><td>&nbsp;</td></tr>
<tr><td>5.</td><td>Run a trial period of 2 months with Raymond Toy
and CMUCL to iron out any unnoticed issues</td><td>skipped</td><td>&nbsp;</td></tr>
<tr><td>6.</td><td>Import the user's git repositories</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>7.</td><td>Import all projects with Git
repositories</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>8.</td><td>Turn off gitweb --&gt; introduce rewrite rules
to point to gitlab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>9.</td><td>Turn off git plugin for Trac --&gt; introduce
rewrite rules to point to gitlab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>10.</td><td>Turn off git-daemon (fully depend on https
checkouts)</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>11.</td><td>Convert all project darcs repositories to git
--&gt; Notify all darcs project owners before we do about a
planning/timing</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>12.</td><td>Import the converted darcs repositories</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>13.</td><td>Convert users' darcs repositories<br />
--&gt; Notify all darcs users before we do about a
planning/timing</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>14.</td><td>Import converted users' darcs
repositories</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>15.</td><td>Turn off darcsweb webbrowsing --&gt; introduce
rewrite rules to point to gitlab</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>16.</td><td>Contact CVS repository owners to ask if they
want to migrate to Git (the default) or Subversion</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>17.</td><td>Convert CVS repositories to Subversion (where
requested / defaulted)</td><td>none requested</td><td>&nbsp;</td></tr>
<tr><td>18.</td><td>Convert CVS repositories to Git (where
requested / defaulted)</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>19.</td><td>Import git-converted CVS repositories</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>20.</td><td>Turn off ViewVC (Subversion & CVS) web-browsing<br />
--&gt; introduce rewrite rules to point to gitlab/Trac</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>21.</td><td>Turn off cvsd and related cron jobs</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>22.</td><td>Turn off svnserve (fully depend on https
checkouts)</td><td>&nbsp;</td><td>&nbsp;</td></tr>
</tbody>
</table>
</article>
<main>
<article>
<h2>Common-Lisp.net migration to GitLab: status</h2>
<summary>
<p>
As announced in <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000161.html">this e-mail</a>,
common-lisp.net services will be restructured - to the benefit
of (most) users as well as the admins.
</p>
<p>In this <a href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000168.html">follow-up e-mail</a>,
a roadmap was proposed on how to get services restructured.
Said roadmap is the basis for the table below showing the
status of each step and if completed - when the step was completed.
</p>
</summary>
<table class="cltable">
<thead>
<tr>
<th>#</th><th>Step</th><th>Status</th><th>Date</th>
</tr>
</thead>
<tbody>
<tr><td>0.</td><td>Install a Code Commenting plugin on Trac to
make it match the GitLab code commenting capabilities</td>
<td>Pending</td><td>&nbsp;</td></tr>
<tr><td>1.</td><td>Finish my experiments regarding the GitLab
setup / installation <br />
see <a href="https://mailman.common-lisp.net/pipermail/announcements/2015-March/000003.html">feedback solicited</a>
and <a href="gitlab-migration-repository-mapping/">mapping of repositories</a></td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>2.</td><td>Install GitLab on common-lisp.net (under the
gitlab.common-lisp.net domain? or should we prefer
git.common-lisp.net?)</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>3.</td><td>Run the migration to create all users and
groups in GitLab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>4.</td><td>Import the CMUCL git repositories (using the
script to be used for all projects)</td><td>skipped</td><td>&nbsp;</td></tr>
<tr><td>5.</td><td>Run a trial period of 2 months with Raymond Toy
and CMUCL to iron out any unnoticed issues</td><td>skipped</td><td>&nbsp;</td></tr>
<tr><td>6.</td><td>Import the user's git repositories</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>7.</td><td>Import all projects with Git
repositories</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>8.</td><td>Turn off gitweb --&gt; introduce rewrite rules
to point to gitlab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>9.</td><td>Turn off git plugin for Trac --&gt; introduce
rewrite rules to point to gitlab</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>10.</td><td>Turn off git-daemon (fully depend on https
checkouts)</td><td>Done</td><td>March 20, 2015</td></tr>
<tr><td>11.</td><td>Convert all project darcs repositories to git
--&gt; Notify all darcs project owners before we do about a
planning/timing</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>12.</td><td>Import the converted darcs repositories</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>13.</td><td>Convert users' darcs repositories<br />
--&gt; Notify all darcs users before we do about a
planning/timing</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>14.</td><td>Import converted users' darcs
repositories</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>15.</td><td>Turn off darcsweb webbrowsing --&gt; introduce
rewrite rules to point to gitlab</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>16.</td><td>Contact CVS repository owners to ask if they
want to migrate to Git (the default) or Subversion</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>17.</td><td>Convert CVS repositories to Subversion (where
requested / defaulted)</td><td>none requested</td><td>&nbsp;</td></tr>
<tr><td>18.</td><td>Convert CVS repositories to Git (where
requested / defaulted)</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>19.</td><td>Import git-converted CVS repositories</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>20.</td><td>Turn off ViewVC (Subversion & CVS) web-browsing<br />
--&gt; introduce rewrite rules to point to gitlab/Trac</td><td>In progress</td><td>April 19, 2015</td></tr>
<tr><td>21.</td><td>Turn off cvsd and related cron jobs</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>22.</td><td>Turn off svnserve (fully depend on https
checkouts)</td><td>&nbsp;</td><td>&nbsp;</td></tr>
</tbody>
</table>
</article>
</main>
</main>
---
title: Independent Mailing Lists
---
<div id="bodyText">
<h2 id="apply">How to apply</h2>
<p>You may apply for a mailinglist if it's Common Lisp-related
but doesn't really need an entire project. Please email admin
(at) common-lisp (dot) net. with the ideal name for your
mailinglist and a brief description.</p>
<div id="bodyText">
<h2 id="apply">How to apply</h2>
<p>You may apply for a mailinglist if it's Common Lisp-related
but doesn't really need an entire project. Please email admin
(at) common-lisp (dot) net. with the ideal name for your
mailinglist and a brief description.</p>
</div>
<div id="bodyText">
<h2 id="lists">Lists</h2>
<table><tbody>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/blis">BLIS</a> by Pascal Constanza</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/boston-lisp">boston-lisp</a> by Dan Stranger</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/cl-debian">cl-debian</a> by Peter Van Eynde</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/cl-user">cl-user</a> by Arthur Lemmens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/chicago-lisp">chicago-lisp</a> by Paul F. Dietz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/eurolisp">eurolisp</a> by Tayssir John Gabbour and Arthur Lemmens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/fm-lisp">fm-lisp</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/hungarian-lispers">hungarian-lispers</a> by Attila Lendvai</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/l4-lisp">l4-lisp</a> by Julian Stecklina</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisp-game-dev">lisp-game-dev</a> by Brandon Edens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisp-hh">lisp-hh</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisppaste-requests">lisppaste-requests</a> by Brian Mastenbrook</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/ltk-user">ltk-user</a> by Peter Herth</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/mac-lisp-ide">mac-lisp-ide</a> by Brian Mastenbrook</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/mop-standard-discuss">mop-standard-discuss</a> by Daniel Barlow</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/munich-lisp">munich-lisp</a> by Jim Newton</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/regex-coach">regex-coach</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/seattle">seattle</a> by Daniel Pezely</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/streams-standard-discuss">streams-standard-discuss</a> by Daniel Barlow</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/small-cl-src">small-cl-src</a> by Ingvar Mattsson and Mario Mommer</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/small-cl-src-discuss">small-cl-src-discuss</a> by Ingvar Mattsson and Mario Mommer</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/threads-standard-discuss">threads-standard-discuss</a> by Daniel Barlow</td></tr>
</tbody></table>
</div>
<div id="bodyText">
<h2 id="lists">Lists</h2>
<table><tbody>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/blis">BLIS</a> by Pascal Constanza</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/boston-lisp">boston-lisp</a> by Dan Stranger</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/cl-debian">cl-debian</a> by Peter Van Eynde</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/cl-user">cl-user</a> by Arthur Lemmens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/chicago-lisp">chicago-lisp</a> by Paul F. Dietz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/eurolisp">eurolisp</a> by Tayssir John Gabbour and Arthur Lemmens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/fm-lisp">fm-lisp</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/hungarian-lispers">hungarian-lispers</a> by Attila Lendvai</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/l4-lisp">l4-lisp</a> by Julian Stecklina</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisp-game-dev">lisp-game-dev</a> by Brandon Edens</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisp-hh">lisp-hh</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/lisppaste-requests">lisppaste-requests</a> by Brian Mastenbrook</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/ltk-user">ltk-user</a> by Peter Herth</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/mac-lisp-ide">mac-lisp-ide</a> by Brian Mastenbrook</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/mop-standard-discuss">mop-standard-discuss</a> by Daniel Barlow</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/munich-lisp">munich-lisp</a> by Jim Newton</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/regex-coach">regex-coach</a> by Edi Weitz</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/seattle">seattle</a> by Daniel Pezely</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/streams-standard-discuss">streams-standard-discuss</a> by Daniel Barlow</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/small-cl-src">small-cl-src</a> by Ingvar Mattsson and Mario Mommer</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/small-cl-src-discuss">small-cl-src-discuss</a> by Ingvar Mattsson and Mario Mommer</td></tr>
<tr><td><a href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/threads-standard-discuss">threads-standard-discuss</a> by Daniel Barlow</td></tr>
</tbody></table>
</div>
</div>
---
title: Welcome to Common-Lisp.net!
---
<!-- <div class="sideBox LHS">
<div>This Page</div>
<a href="#introduction">Introduction</a>
<a href="#news">News</a>
<a href="#description">What is it</a>
<a href="#services">Services</a>
<a href="#about">About this site</a>
</div> -->
<!--
<div class="sideBox RHS">
<div>Recent projects
</div>
<table><tbody>
<tr><td colspan="2">
<a href="projects.shtml">More projects...</a>
</td></tr>
<tr><td colspan="2">
<a href="recent-projects.xml" class='rss-icon'>RSS</a>
</td></tr>
</tbody></table>
</div>
-->
<main id="bodyText">
<section id="introduction">
<h2>Introduction</h2>
<p>Welcome to the amazing world of Common Lisp, the
programmable programming language.</p>
<p>This site is one among many gateways to Common Lisp. Its
goal is to provide the Common Lisp community with development
resources and to work as a starting point for new
programmers.</p>
</section>
<article id="news">
<h2>Latest news</h2>
<section id="2015_05_25">
<h7>2015-05-25</h7>
<p>Today the system has been declared &quot;CVS clean&quot;! All
remnants of CVS have been removed.</p>
</section>
<section id="2015_05_23">
<h7>2015-05-23</h7>
<p>On Friday, the system had performance problems due to slow I/O.
Today, the disk system reports running in degraded mode,
so we ordered the failing disk to be replaced. The disk array
has been rebuilt.</p>
</section>
<section id="2015_05_22">
<h7 id="2015_05_22">2015-05-22</h7>
<p>GitLab upgraded to <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/v7.11.1/CHANGELOG">GitLab 7.11.1.</a></p>
</section>
<section id="2015_05_15">
<h7>2015-05-15</h7>
<p>Proposed approach for <a
href="https://mailman-test.common-lisp.net/pipermail/clo-devel/2015-May/001051.html"
>Darcs repository migration</a> sent out.</p>
<p><a href="/news/#2015_05_15" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_05_12">
<h7>2015-05-12</h7>
<p>The final batch of CVS projects has been migrated. None of the
projects opted to move to Subversion, so all of them were
migrated to Git+GitLab.</p>
<p>Now that the projects have been migrated, we'll start
preparations to migrate the Darcs repositories on the system.</p>
<p><a href="/news/#2015_05_12" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_05_03">
<h7>2015-05-03</h7>
<p>The next batch of CVS projects has been migrated. None of the
projects opted to move to Subversion, so all of them were
migrated to Git+GitLab.</p>
<p><a href="/news/#2015_05_03" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_04_27">
<h7>2015-04-27</h7>
<p>GitLab fixes issue reported by common-lisp.net admin: <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/1478">loading of commit data</a>
</p>
</section>
<p><a href="/news/" style="font-size: 80%"
>Read older news...</a></p>
</article>
<article id="description">
<h2>What is Common Lisp?</h2>
<p>Common Lisp is the modern, multi-paradigm, high-performance,
compiled, ANSI-standardized, most prominent (along with <a
href="http://www.schemers.org/">Scheme</a>) descendant of the
long-running family of Lisp programming languages. Curious? <a
href="http://cliki.net/Getting%20Started" class="emphasize">Click
here to get started!</a>
</p>
<p>Common Lisp is known for being extremely flexible, having
excellent support for object oriented programming, and fast
prototyping capabilities. It also sports an extremely powerful
macro system that allows you to tailor the language to your
application, and a flexible run-time environment that allows
modification and debugging of running applications (excellent
for server-side development and long-running critical
software).</p>
<p>Common Lisp is a multi-paradigm programming language that
allows you to to choose the approach and paradigm according to
your application domain.</p>
<p>You may find more of the Common Lisp community at these resources:</p>
<ul>
<li><a href="http://planet.lisp.org">Planet Lisp</a></li>
<li><a href="http://cliki.net">CLiki</a></li>
<li><a href="http://www.cliki.net/IRC">Various lisp irc
channels</a></li>
<li><a href="http://groups.google.com/group/comp.lang.lisp">The comp.lang.lisp newsgroup</a></li>
<li><a href="http://www.alu.org">The Association of Lisp Users</a></li>
</ul>
</article>
<section id="services">
<h2>Services</h2>
<ul>
<li><a href="/project-intro/">Project hosting</a> for open
source / free software Common Lisp projects.</li>
<li><a href="/independent-lists/">Mailing lists</a> for
Common Lisp related topics.</li>
</ul>
</section>
<section id="support">
<h2>Support</h2>
<p>If you need technical support, please contact <a
href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel">our
admins</a>.</p>
</section>
<section id="about">
<h2>About this site</h2>
<p>Check out our <a href="/about/">about page</a>.</p>
</section>
</main>
<main id="bodyText">
<section id="introduction">
<h2>Introduction</h2>
<p>Welcome to the amazing world of Common Lisp, the
programmable programming language.</p>
<p>This site is one among many gateways to Common Lisp. Its
goal is to provide the Common Lisp community with development
resources and to work as a starting point for new
programmers.</p>
</section>
<article id="news">
<h2>Latest news</h2>
<section id="2015_05_25">
<h7>2015-05-25</h7>
<p>Today the system has been declared &quot;CVS clean&quot;! All
remnants of CVS have been removed.</p>
</section>
<section id="2015_05_23">
<h7>2015-05-23</h7>
<p>On Friday, the system had performance problems due to slow I/O.
Today, the disk system reports running in degraded mode,
so we ordered the failing disk to be replaced. The disk array
has been rebuilt.</p>
</section>
<section id="2015_05_22">
<h7 id="2015_05_22">2015-05-22</h7>
<p>GitLab upgraded to <a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/v7.11.1/CHANGELOG">GitLab 7.11.1.</a></p>
</section>
<section id="2015_05_15">
<h7>2015-05-15</h7>
<p>Proposed approach for <a
href="https://mailman-test.common-lisp.net/pipermail/clo-devel/2015-May/001051.html"
>Darcs repository migration</a> sent out.</p>
<p><a href="/news/#2015_05_15" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_05_12">
<h7>2015-05-12</h7>
<p>The final batch of CVS projects has been migrated. None of the
projects opted to move to Subversion, so all of them were
migrated to Git+GitLab.</p>
<p>Now that the projects have been migrated, we'll start
preparations to migrate the Darcs repositories on the system.</p>
<p><a href="/news/#2015_05_12" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_05_03">
<h7>2015-05-03</h7>
<p>The next batch of CVS projects has been migrated. None of the
projects opted to move to Subversion, so all of them were
migrated to Git+GitLab.</p>
<p><a href="/news/#2015_05_03" style="font-size: 80%"
>Read more...</a></p>
</section>
<section id="2015_04_27">
<h7>2015-04-27</h7>
<p>GitLab fixes issue reported by common-lisp.net admin: <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/1478">loading of commit data</a>
</p>
</section>
<p><a href="/news/" style="font-size: 80%"
>Read older news...</a></p>
</article>
<article id="description">
<h2>What is Common Lisp?</h2>
<p>Common Lisp is the modern, multi-paradigm, high-performance,
compiled, ANSI-standardized, most prominent (along with <a
href="http://www.schemers.org/">Scheme</a>) descendant of the
long-running family of Lisp programming languages. Curious? <a
href="http://cliki.net/Getting%20Started" class="emphasize">Click
here to get started!</a>
</p>
<p>Common Lisp is known for being extremely flexible, having
excellent support for object oriented programming, and fast
prototyping capabilities. It also sports an extremely powerful
macro system that allows you to tailor the language to your
application, and a flexible run-time environment that allows
modification and debugging of running applications (excellent
for server-side development and long-running critical
software).</p>
<p>Common Lisp is a multi-paradigm programming language that
allows you to to choose the approach and paradigm according to
your application domain.</p>
<p>You may find more of the Common Lisp community at these resources:</p>
<ul>
<li><a href="http://planet.lisp.org">Planet Lisp</a></li>
<li><a href="http://cliki.net">CLiki</a></li>
<li><a href="http://www.cliki.net/IRC">Various lisp irc
channels</a></li>
<li><a href="http://groups.google.com/group/comp.lang.lisp">The comp.lang.lisp newsgroup</a></li>
<li><a href="http://www.alu.org">The Association of Lisp Users</a></li>
</ul>
</article>
<section id="services">
<h2>Services</h2>
<ul>
<li><a href="/project-intro/">Project hosting</a> for open
source / free software Common Lisp projects.</li>
<li><a href="/independent-lists/">Mailing lists</a> for
Common Lisp related topics.</li>
</ul>
</section>
<section id="support">