From 1cad8721a6b79fb10c1325eba4b9c4abf3f44381 Mon Sep 17 00:00:00 2001 From: Mariano Montone Date: Fri, 11 May 2018 16:34:07 -0300 Subject: [PATCH] Page titles and templates cleanup --- content/about.html | 4 - content/contribute.html | 4 - content/downloads.html | 4 - content/faq.html | 69 +- .../gitlab-migration-repository-mapping.html | 579 ++++++------ content/gitlab-migration-status.html | 177 ++-- content/independent-lists.html | 71 +- content/index.html | 305 +++--- content/news.html | 861 ++++++++--------- content/orphaned-mailing-lists.html | 225 ++--- content/orphaned-projects.html | 197 ++-- content/phub.html | 891 +++++++++--------- content/project-intro.html | 385 ++++---- content/tools.html | 113 +-- content/tutorials.html | 32 +- globals.lisp | 34 +- output/placeholder | 0 process.lisp | 5 +- 18 files changed, 1871 insertions(+), 2085 deletions(-) delete mode 100644 output/placeholder diff --git a/content/about.html b/content/about.html index af6c102..10433b6 100644 --- a/content/about.html +++ b/content/about.html @@ -1,7 +1,3 @@ ---- -title: About ---- -

About Common-Lisp.net

Common-Lisp.net provides hosting for projects and user groups diff --git a/content/contribute.html b/content/contribute.html index 0c5c1f7..6e26026 100644 --- a/content/contribute.html +++ b/content/contribute.html @@ -1,7 +1,3 @@ ---- -title: Contribute ---- -

Donations

The easiest way to contribute is to donate. The costs of running diff --git a/content/downloads.html b/content/downloads.html index 1747c5a..5ad3cad 100644 --- a/content/downloads.html +++ b/content/downloads.html @@ -1,7 +1,3 @@ ---- -title: Downloads ---- -

Download/Install

Common Lisp comes in many different flavors, or implementations. Two popular ones are Steel Bank Common Lisp (SBCL) and Clozure Common Lisp (CCL).

diff --git a/content/faq.html b/content/faq.html index 687a0ab..a629be8 100644 --- a/content/faq.html +++ b/content/faq.html @@ -1,50 +1,19 @@ ---- -title: Frequently asked questions for common-lisp.net ---- - - - - -
-
-

Common-Lisp.net Frequently Asked Questions

- -
    -
  • GitLab: configure e-mail on push
  • -
- -
-

GitLab: configure e-mail on push

-

- GitLab supports sending an e-mail upon pushing - commits by project members. In order to use the functionality, - please follow the steps outlined in our configuration guide. -

-
-
- - -
- +
+
+

Common-Lisp.net Frequently Asked Questions

+ +
    +
  • GitLab: configure e-mail on push
  • +
+ +
+

GitLab: configure e-mail on push

+

+ GitLab supports sending an e-mail upon pushing + commits by project members. In order to use the functionality, + please follow the steps outlined in our configuration guide. +

+
+
+
diff --git a/content/gitlab-migration-repository-mapping.html b/content/gitlab-migration-repository-mapping.html index 4324f4c..e091fc7 100644 --- a/content/gitlab-migration-repository-mapping.html +++ b/content/gitlab-migration-repository-mapping.html @@ -1,310 +1,281 @@ ---- -title: Mapping of existing repositories to GitLab groups/projects ---- - +
+
+

Introduction

+

+ As part of the migration to GitLab, all existing public git + repositories will be brought under management of GitLab. + The tables below list the locations where the repositories + reside now and under which <group>/<repository-name> + they will be made available in gitlab. +

+ +
- + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -
-
-

Introduction

-

- As part of the migration to GitLab, all existing public git - repositories will be brought under management of GitLab. - The tables below list the locations where the repositories - reside now and under which <group>/<repository-name> - they will be made available in gitlab. -

- -
+
+
Mapping of public user repositories (54 items)
/home/abridgewater/public_html/git/clx.gitabridgewater/clx.git
/home/abridgewater/public_html/git/game-stuff.gitabridgewater/game-stuff.git
/home/abridgewater/public_html/git/nq-clim.gitabridgewater/nq-clim.git
/home/abridgewater/public_html/git/perry.gitabridgewater/perry.git
/home/crhodes/public_html/git/swankr.gitcrhodes/swankr.git
/home/crhodes/public_html/tmp/sbclcrhodes/sbcl.git
/home/dchang/dotfiles.gitdchang/dotfiles.git
/home/dcrampsie/dcrampsie/public_html/ftw.gitdcrampsie/ftw.git
/home/frideau/public_html/private/S7GHYB8AWY9UN34H/slime.gitfrideau/slime.git
/home/frideau/git/exscribe.gitfrideau/exscribe.git
/home/frideau/git/fare-csv.gitfrideau/fare-csv.git
/home/frideau/git/fare-matcher.gitfrideau/fare-matcher.git
/home/frideau/git/fare-memoization.gitfrideau/fare-memoization.git
/home/frideau/git/fare-mop.gitfrideau/fare-mop.git
/home/frideau/git/fare-quasiquote.gitfrideau/fare-quasiquote.git
/home/frideau/git/fare-unbaked.gitfrideau/fare-unbaked.git
/home/frideau/git/fare-utils.gitfrideau/fare-utils.git
/home/frideau/git/lambda-reader.gitfrideau/lambda-reader.git
/home/frideau/git/meta.gitfrideau/meta.git
/home/frideau/git/package-renaming.gitfrideau/package-renaming.git
/home/frideau/git/philip-jose.gitfrideau/philip-jose.git
/home/frideau/git/ptc.gitfrideau/ptc.git
/home/frideau/git/ql-test.gitfrideau/ql-test.git
/home/frideau/git/reader-interception.gitfrideau/reader-interception.git
/home/frideau/git/scribble.gitfrideau/scribble.git
/home/frideau/git/tthsum.gitfrideau/tthsum.git
/home/frideau/git/wordgames.gitfrideau/wordgames.git
/home/frideau/git/workout-timer.gitfrideau/workout-timer.git
/home/gpfeil/public_html/git/LOOMgpfeil/LOOM.git
/home/loliveira/public_html/git/dot-emacsloliveira/dot-emacs.git
/home/loliveira/public_html/git/texinfo-docstringsloliveira/texinfo-docstrings.git
/home/loliveira/public_html/tmp/freecapi.gitloliveira/freecapi.git
/home/loliveira/public_html/tmp/mirrors/cl-vectorsloliveira/cl-vectors.git
/home/mflambard/CLERICmflambard/CLERIC
/home/mjansson/public_html/sicl.gitmjansson/sicl.git
/home/sionescu/public_html/git/clbuild.gitsionescu/clbuild.git
/home/sionescu/public_html/git/texinfo-docstrings.gitsionescu/texinfo-docstrings.git
/home/vsedach/public_html/mirror/daemonize/cl-daemonizevsedach/cl-daemonize.git
/home/vsedach/public_html/mirror/object-stores/anardbvsedach/anardb.git
/home/vsedach/public_html/mirror/object-stores/planksvsedach/planks.git
/home/vsedach/public_html/mirror/object-stores/storagevsedach/storage.git
+

+ Should there be a mapping in the tables shown on this page, + please contact admin@common-lisp.net so we can sort out the correct + mapping (or deletion). +

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mapping of public user repositories (54 items)
/home/abridgewater/public_html/git/clx.gitabridgewater/clx.git
/home/abridgewater/public_html/git/game-stuff.gitabridgewater/game-stuff.git
/home/abridgewater/public_html/git/nq-clim.gitabridgewater/nq-clim.git
/home/abridgewater/public_html/git/perry.gitabridgewater/perry.git
/home/crhodes/public_html/git/swankr.gitcrhodes/swankr.git
/home/crhodes/public_html/tmp/sbclcrhodes/sbcl.git
/home/dchang/dotfiles.gitdchang/dotfiles.git
/home/dcrampsie/dcrampsie/public_html/ftw.gitdcrampsie/ftw.git
/home/frideau/public_html/private/S7GHYB8AWY9UN34H/slime.gitfrideau/slime.git
/home/frideau/git/exscribe.gitfrideau/exscribe.git
/home/frideau/git/fare-csv.gitfrideau/fare-csv.git
/home/frideau/git/fare-matcher.gitfrideau/fare-matcher.git
/home/frideau/git/fare-memoization.gitfrideau/fare-memoization.git
/home/frideau/git/fare-mop.gitfrideau/fare-mop.git
/home/frideau/git/fare-quasiquote.gitfrideau/fare-quasiquote.git
/home/frideau/git/fare-unbaked.gitfrideau/fare-unbaked.git
/home/frideau/git/fare-utils.gitfrideau/fare-utils.git
/home/frideau/git/lambda-reader.gitfrideau/lambda-reader.git
/home/frideau/git/meta.gitfrideau/meta.git
/home/frideau/git/package-renaming.gitfrideau/package-renaming.git
/home/frideau/git/philip-jose.gitfrideau/philip-jose.git
/home/frideau/git/ptc.gitfrideau/ptc.git
/home/frideau/git/ql-test.gitfrideau/ql-test.git
/home/frideau/git/reader-interception.gitfrideau/reader-interception.git
/home/frideau/git/scribble.gitfrideau/scribble.git
/home/frideau/git/tthsum.gitfrideau/tthsum.git
/home/frideau/git/wordgames.gitfrideau/wordgames.git
/home/frideau/git/workout-timer.gitfrideau/workout-timer.git
/home/gpfeil/public_html/git/LOOMgpfeil/LOOM.git
/home/loliveira/public_html/git/dot-emacsloliveira/dot-emacs.git
/home/loliveira/public_html/git/texinfo-docstringsloliveira/texinfo-docstrings.git
/home/loliveira/public_html/tmp/freecapi.gitloliveira/freecapi.git
/home/loliveira/public_html/tmp/mirrors/cl-vectorsloliveira/cl-vectors.git
/home/mflambard/CLERICmflambard/CLERIC
/home/mjansson/public_html/sicl.gitmjansson/sicl.git
/home/sionescu/public_html/git/clbuild.gitsionescu/clbuild.git
/home/sionescu/public_html/git/texinfo-docstrings.gitsionescu/texinfo-docstrings.git
/home/vsedach/public_html/mirror/daemonize/cl-daemonizevsedach/cl-daemonize.git
/home/vsedach/public_html/mirror/object-stores/anardbvsedach/anardb.git
/home/vsedach/public_html/mirror/object-stores/planksvsedach/planks.git
/home/vsedach/public_html/mirror/object-stores/storagevsedach/storage.git
- -

- Should there be a mapping in the tables shown on this page, - please contact admin@common-lisp.net so we can sort out the correct - mapping (or deletion). -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mapping of public project repositories (203 items)
/project/able/able.gitable/able.git
/project/adw-charting/public_html/git/adw-charting.gitadw-charting/adw-charting.git
/project/alexandria/alexandria.gitalexandria/alexandria.git
/project/antik/antikantik/antik.git
/project/asdf/git/asdf-bundle.gitasdf/asdf-bundle.git
/project/asdf/git/asdf-contrib.gitasdf/asdf-contrib.git
/project/asdf/git/asdf-encodings.gitasdf/asdf-encodings.git
/project/asdf/git/asdf-finalizers.gitasdf/asdf-finalizers.git
/project/asdf/git/asdf-package-system.gitasdf/asdf-package-system.git
/project/asdf/git/asdf-utils.gitasdf/asdf-utils.git
/project/asdf/git/asdf.gitasdf/asdf.git
/project/asdf/git/ilc2010.gitasdf/ilc2010.git
/project/bknr/public_html/static/lmmanbknr/lmman.git
/project/bordeaux-threads/public_html/git/bordeaux-threads.gitbordeaux-threads/bordeaux-threads.git
/project/bytemap/public_html/bytemap.gitbytemap/bytemap.git
/project/cffi/public_html/git/cffi.gitcffi/cffi.git
/project/cffi/public_html/git-webpagecffi/git-webpage.git
/project/cl-api/public_html/git/cl-api.gitcl-api/cl-api.git
/project/cl-irregsexp/public_html/cl-irregsexp.gitcl-irregsexp/cl-irregsexp.git
/project/cl-machine-learning/git/cl-machine-learningcl-machine-learning/cl-machine-learning.git
/project/cl-machine-learning/git/cl-svmcl-machine-learning/cl-svm.git
/project/cl-org-mode/public_html/cl-org-mode.gitcl-org-mode/cl-org-mode.git
/project/cl-plplot/cl-plplot.gitcl-plplot/cl-plplot.git
/project/cl-stomp/git/cl-stomp.gitcl-stomp/cl-stomp.git
/project/cl-trane/public_html/cl-trane.gitcl-trane/cl-trane.git
/project/cl-unification/git/cl-unification.gitcl-unification/cl-unification.git
/project/claw/public_html/git/claw.gitclaw/claw.git
/project/clazy/git/clazy.gitclazy/clazy.git
/project/clfswm/public_html/0801/clfswm.git.bakclfswm/clfswm.git.bak.git
/project/clfswm/public_html/git/clfswm.gitclfswm/clfswm.git
/project/clo/git/public_html.gitclo/public_html.git
/project/clonsigna/public_html/git/clonsigna.gitclonsigna/clonsigna.git
/project/cmucl/public_html/git/cmucl-www.gitcmucl/cmucl-www.git
/project/cmucl/public_html/git/cmucl.gitcmucl/cmucl.git
/project/css-sexp/git/css-sexpcss-sexp/css-sexp.git
/project/de-setf-amqp/public_html/gitde-setf-amqp/git.git
/project/ecl/public_html/git/eclecl/ecl.git
/project/ecl/public_html/git/ecl-doc.gitecl/ecl-doc.git
/project/ecl/public_html/git/ecl-test.gitecl/ecl-test.git
/project/ecl/public_html/git/ecl.gitecl/ecl.git
/project/editor-hints/public_html/git/named-readtables.giteditor-hints/named-readtables.git
/project/erlang-in-lisp/.git_olderlang-in-lisp/.git_old.git
/project/erlang-in-lisp/giterlang-in-lisp/git.git
/project/fiveam/public_html/git/fiveam.gitfiveam/fiveam.git
/project/gestalt/public_html/git/gestaltgestalt/gestalt.git
/project/ginseng/gitginseng/git.git
/project/gsharp/git/gsharp.gitgsharp/gsharp.git
/project/iolib/public_html/git/iolib.gitiolib/iolib.git
/project/iolib/public_html/git/libfixposix.gitiolib/libfixposix.git
/project/iolib/public_html/git/static-vectors.gitiolib/static-vectors.git
/project/lift/public_html/lift.gitlift/lift.git
/project/linedit/linedit.gitlinedit/linedit.git
/project/linedit/linedit.git-badlinedit/linedit.git-bad.git
/project/lisp-matrix/gitlisp-matrix/git.git
/project/lisp-on-lines/public_html/lisp-on-lines.gitlisp-on-lines/lisp-on-lines.git
/project/mel-base/public_html/mel-base.gitmel-base/mel-base.git
/project/mirror/public_html/git/ch-asdf.gitmirror/ch-asdf.git
/project/mirror/public_html/git/ch-image.gitmirror/ch-image.git
/project/mirror/public_html/git/ch-util.gitmirror/ch-util.git
/project/mirror/public_html/git/cl-base64.gitmirror/cl-base64.git
/project/mirror/public_html/git/cl-bio.gitmirror/cl-bio.git
/project/mirror/public_html/git/cl-modlisp.gitmirror/cl-modlisp.git
/project/mirror/public_html/git/cl-photo.gitmirror/cl-photo.git
/project/mirror/public_html/git/cl-readline.gitmirror/cl-readline.git
/project/mirror/public_html/git/cl-rss.gitmirror/cl-rss.git
/project/mirror/public_html/git/clem.gitmirror/clem.git
/project/mirror/public_html/git/clisp.gitmirror/clisp.git
/project/mirror/public_html/git/clsql.gitmirror/clsql.git
/project/mirror/public_html/git/clsr.gitmirror/clsr.git
/project/mirror/public_html/git/cluck.gitmirror/cluck.git
/project/mirror/public_html/git/cluster-ffi.gitmirror/cluster-ffi.git
/project/mirror/public_html/git/epigraph.gitmirror/epigraph.git
/project/mirror/public_html/git/gcc-xml-ffi.gitmirror/gcc-xml-ffi.git
/project/mirror/public_html/git/getopt.gitmirror/getopt.git
/project/mirror/public_html/git/hunchentoot-auth.gitmirror/hunchentoot-auth.git
/project/mirror/public_html/git/hunchentoot-cgi.gitmirror/hunchentoot-cgi.git
/project/mirror/public_html/git/hunchentoot-vhost.gitmirror/hunchentoot-vhost.git
/project/mirror/public_html/git/hyperobject.gitmirror/hyperobject.git
/project/mirror/public_html/git/irc-logger.gitmirror/irc-logger.git
/project/mirror/public_html/git/kmrcl.gitmirror/kmrcl.git
/project/mirror/public_html/git/lml.gitmirror/lml.git
/project/mirror/public_html/git/lml2.gitmirror/lml2.git
/project/mirror/public_html/git/md5.gitmirror/md5.git
/project/mirror/public_html/git/nuclblog.gitmirror/nuclblog.git
/project/mirror/public_html/git/pipes.gitmirror/pipes.git
/project/mirror/public_html/git/postoffice.gitmirror/postoffice.git
/project/mirror/public_html/git/ptester.gitmirror/ptester.git
/project/mirror/public_html/git/pubmed.gitmirror/pubmed.git
/project/mirror/public_html/git/puri.gitmirror/puri.git
/project/mirror/public_html/git/quicktime-ffi.gitmirror/quicktime-ffi.git
/project/mirror/public_html/git/retrospectiff.gitmirror/retrospectiff.git
/project/mirror/public_html/git/reversi.gitmirror/reversi.git
/project/mirror/public_html/git/rlc.gitmirror/rlc.git
/project/mirror/public_html/git/rt.gitmirror/rt.git
/project/mirror/public_html/git/salza2.gitmirror/salza2.git
/project/mirror/public_html/git/sbcl.gitmirror/sbcl.git
/project/mirror/public_html/git/skippy.gitmirror/skippy.git
/project/mirror/public_html/git/slime.gitmirror/slime.git
/project/mirror/public_html/git/smarkup.gitmirror/smarkup.git
/project/mirror/public_html/git/tiff-ffi.gitmirror/tiff-ffi.git
/project/mirror/public_html/git/time-interval.gitmirror/time-interval.git
/project/mirror/public_html/git/trivial-setuid.gitmirror/trivial-setuid.git
/project/mirror/public_html/git/uffi.gitmirror/uffi.git
/project/mirror/public_html/git/umlisp-orf.gitmirror/umlisp-orf.git
/project/mirror/public_html/git/umlisp.gitmirror/umlisp.git
/project/mirror/public_html/git/vcs-tree.gitmirror/vcs-tree.git
/project/mirror/public_html/git/vecto.gitmirror/vecto.git
/project/mirror/public_html/git/wol.gitmirror/wol.git
/project/mirror/public_html/git/xlunit.gitmirror/xlunit.git
/project/mirror/public_html/git/xmlutils.gitmirror/xmlutils.git
/project/mirror/public_html/git/xptest.gitmirror/xptest.git
/project/mirror/public_html/git/zpb-ttf.gitmirror/zpb-ttf.git
/project/mirror/public_html/git/zpng.gitmirror/zpng.git
/project/mirror/public_html/git/zs3.gitmirror/zs3.git
/project/mkcl/public_html/git/mkcl.gitmkcl/mkcl.git
/project/moptilities/public_html/gitmoptilities/git.git
/project/new-op/public_html/git/new-op.gitnew-op/new-op.git
/project/oct/public_html/git/oct.gitoct/oct.git
/project/osicat/git/osicat.gitosicat/osicat.git
/project/osicat/public_html/old/old-git/osicat.gitosicat/osicat.git
/project/parenscript/public_html/git/parenscriptparenscript/parenscript.git
/project/ply/public_html/src/plyply/ply.git
/project/qitab/git/cl-protobufs.gitqitab/cl-protobufs.git
/project/qitab/git/command-line-arguments.gitqitab/command-line-arguments.git
/project/qitab/git/inferior-shell.gitqitab/inferior-shell.git
/project/qitab/git/lisp-invocation.gitqitab/lisp-invocation.git
/project/qitab/git/poiu.gitqitab/poiu.git
/project/qitab/git/qmynd.gitqitab/qmynd.git
/project/qitab/git/quux-hunchentoot.gitqitab/quux-hunchentoot.git
/project/qitab/git/quux-time.gitqitab/quux-time.git
/project/qitab/git/rpm.gitqitab/rpm.git
/project/qitab/git/single-threaded-ccl.gitqitab/single-threaded-ccl.git
/project/rclg/public_html/git/rclg.gitrclg/rclg.git
/project/sheeple/public_html/git/sheeple.gitsheeple/sheeple.git
/project/sicl/public_html/git/SICL.gitsicl/SICL.git
/project/slime/public_html/slime.gitslime/slime.git
/project/suave/git/amazon-ecssuave/amazon-ecs.git
/project/suave/git/cl-sailssuave/cl-sails.git
/project/suave/git/cl-tidysuave/cl-tidy.git
/project/suave/git/js-parsersuave/js-parser.git
/project/suave/git/paren-eventssuave/paren-events.git
/project/suave/git/paren-filessuave/paren-files.git
/project/suave/git/paren-psossuave/paren-psos.git
/project/suave/git/paren-testsuave/paren-test.git
/project/suave/git/paren-utilsuave/paren-util.git
/project/suave/git/rjsonsuave/rjson.git
/project/suave/git/tmp/cl-svmsuave/cl-svm.git
/project/suave/git/webfunksuave/webfunk.git
/project/suave/git/xml-mopsuave/xml-mop.git
/project/sudoku/public_html/git/sudoku.gitsudoku/sudoku.git
/project/trivial-backtrace/public_html/tb.gittrivial-backtrace/tb.git
/project/trivial-backtrace/public_html/trivial-backtrace.gittrivial-backtrace/trivial-backtrace.git
/project/trivial-iconv/public_html/trivial-iconv.gittrivial-iconv/trivial-iconv.git
/project/xcvb/git/alexandria.gitxcvb/alexandria.git
/project/xcvb/git/asdf-dependency-grovel.gitxcvb/asdf-dependency-grovel.git
/project/xcvb/git/babel.gitxcvb/babel.git
/project/xcvb/git/binascii.gitxcvb/binascii.git
/project/xcvb/git/bordeaux-threads.gitxcvb/bordeaux-threads.git
/project/xcvb/git/cffi.gitxcvb/cffi.git
/project/xcvb/git/chunga.gitxcvb/chunga.git
/project/xcvb/git/cl+ssl.gitxcvb/cl-plus-ssl.git
/project/xcvb/git/cl-base64.gitxcvb/cl-base64.git
/project/xcvb/git/cl-fad.gitxcvb/cl-fad.git
/project/xcvb/git/cl-launch.gitxcvb/cl-launch.git
/project/xcvb/git/cl-ppcre.gitxcvb/cl-ppcre.git
/project/xcvb/git/cl-unicode.gitxcvb/cl-unicode.git
/project/xcvb/git/cl-who.gitxcvb/cl-who.git
/project/xcvb/git/closer-mop.gitxcvb/closer-mop.git
/project/xcvb/git/drakma.gitxcvb/drakma.git
/project/xcvb/git/flexi-streams.gitxcvb/flexi-streams.git
/project/xcvb/git/hu.dwim.stefil.gitxcvb/hu.dwim.stefil.git
/project/xcvb/git/hunchentoot.gitxcvb/hunchentoot.git
/project/xcvb/git/iolib.gitxcvb/iolib.git
/project/xcvb/git/ironclad.gitxcvb/ironclad.git
/project/xcvb/git/iterate.gitxcvb/iterate.git
/project/xcvb/git/lw-compat.gitxcvb/lw-compat.git
/project/xcvb/git/md5.gitxcvb/md5.git
/project/xcvb/git/metabang-bind.gitxcvb/metabang-bind.git
/project/xcvb/git/named-readtables.gitxcvb/named-readtables.git
/project/xcvb/git/nibbles.gitxcvb/nibbles.git
/project/xcvb/git/ptester.gitxcvb/ptester.git
/project/xcvb/git/puri.gitxcvb/puri.git
/project/xcvb/git/quux-iolib.gitxcvb/quux-iolib.git
/project/xcvb/git/rfc2388.gitxcvb/rfc2388.git
/project/xcvb/git/rucksack.gitxcvb/rucksack.git
/project/xcvb/git/split-sequence.gitxcvb/split-sequence.git
/project/xcvb/git/trivial-backtrace.gitxcvb/trivial-backtrace.git
/project/xcvb/git/trivial-features.gitxcvb/trivial-features.git
/project/xcvb/git/trivial-garbage.gitxcvb/trivial-garbage.git
/project/xcvb/git/trivial-gray-streams.gitxcvb/trivial-gray-streams.git
/project/xcvb/git/trivial-ldap.gitxcvb/trivial-ldap.git
/project/xcvb/git/usocket.gitxcvb/usocket.git
/project/xcvb/git/xcvb.gitxcvb/xcvb.git
/project/xhtmlambda/public_html/git/XHTMLambda.gitxhtmlambda/XHTMLambda.git
/project/yason/public_html/yasonyason/yason.git
- -
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Mapping of public project repositories (203 items)
/project/able/able.gitable/able.git
/project/adw-charting/public_html/git/adw-charting.gitadw-charting/adw-charting.git
/project/alexandria/alexandria.gitalexandria/alexandria.git
/project/antik/antikantik/antik.git
/project/asdf/git/asdf-bundle.gitasdf/asdf-bundle.git
/project/asdf/git/asdf-contrib.gitasdf/asdf-contrib.git
/project/asdf/git/asdf-encodings.gitasdf/asdf-encodings.git
/project/asdf/git/asdf-finalizers.gitasdf/asdf-finalizers.git
/project/asdf/git/asdf-package-system.gitasdf/asdf-package-system.git
/project/asdf/git/asdf-utils.gitasdf/asdf-utils.git
/project/asdf/git/asdf.gitasdf/asdf.git
/project/asdf/git/ilc2010.gitasdf/ilc2010.git
/project/bknr/public_html/static/lmmanbknr/lmman.git
/project/bordeaux-threads/public_html/git/bordeaux-threads.gitbordeaux-threads/bordeaux-threads.git
/project/bytemap/public_html/bytemap.gitbytemap/bytemap.git
/project/cffi/public_html/git/cffi.gitcffi/cffi.git
/project/cffi/public_html/git-webpagecffi/git-webpage.git
/project/cl-api/public_html/git/cl-api.gitcl-api/cl-api.git
/project/cl-irregsexp/public_html/cl-irregsexp.gitcl-irregsexp/cl-irregsexp.git
/project/cl-machine-learning/git/cl-machine-learningcl-machine-learning/cl-machine-learning.git
/project/cl-machine-learning/git/cl-svmcl-machine-learning/cl-svm.git
/project/cl-org-mode/public_html/cl-org-mode.gitcl-org-mode/cl-org-mode.git
/project/cl-plplot/cl-plplot.gitcl-plplot/cl-plplot.git
/project/cl-stomp/git/cl-stomp.gitcl-stomp/cl-stomp.git
/project/cl-trane/public_html/cl-trane.gitcl-trane/cl-trane.git
/project/cl-unification/git/cl-unification.gitcl-unification/cl-unification.git
/project/claw/public_html/git/claw.gitclaw/claw.git
/project/clazy/git/clazy.gitclazy/clazy.git
/project/clfswm/public_html/0801/clfswm.git.bakclfswm/clfswm.git.bak.git
/project/clfswm/public_html/git/clfswm.gitclfswm/clfswm.git
/project/clo/git/public_html.gitclo/public_html.git
/project/clonsigna/public_html/git/clonsigna.gitclonsigna/clonsigna.git
/project/cmucl/public_html/git/cmucl-www.gitcmucl/cmucl-www.git
/project/cmucl/public_html/git/cmucl.gitcmucl/cmucl.git
/project/css-sexp/git/css-sexpcss-sexp/css-sexp.git
/project/de-setf-amqp/public_html/gitde-setf-amqp/git.git
/project/ecl/public_html/git/eclecl/ecl.git
/project/ecl/public_html/git/ecl-doc.gitecl/ecl-doc.git
/project/ecl/public_html/git/ecl-test.gitecl/ecl-test.git
/project/ecl/public_html/git/ecl.gitecl/ecl.git
/project/editor-hints/public_html/git/named-readtables.giteditor-hints/named-readtables.git
/project/erlang-in-lisp/.git_olderlang-in-lisp/.git_old.git
/project/erlang-in-lisp/giterlang-in-lisp/git.git
/project/fiveam/public_html/git/fiveam.gitfiveam/fiveam.git
/project/gestalt/public_html/git/gestaltgestalt/gestalt.git
/project/ginseng/gitginseng/git.git
/project/gsharp/git/gsharp.gitgsharp/gsharp.git
/project/iolib/public_html/git/iolib.gitiolib/iolib.git
/project/iolib/public_html/git/libfixposix.gitiolib/libfixposix.git
/project/iolib/public_html/git/static-vectors.gitiolib/static-vectors.git
/project/lift/public_html/lift.gitlift/lift.git
/project/linedit/linedit.gitlinedit/linedit.git
/project/linedit/linedit.git-badlinedit/linedit.git-bad.git
/project/lisp-matrix/gitlisp-matrix/git.git
/project/lisp-on-lines/public_html/lisp-on-lines.gitlisp-on-lines/lisp-on-lines.git
/project/mel-base/public_html/mel-base.gitmel-base/mel-base.git
/project/mirror/public_html/git/ch-asdf.gitmirror/ch-asdf.git
/project/mirror/public_html/git/ch-image.gitmirror/ch-image.git
/project/mirror/public_html/git/ch-util.gitmirror/ch-util.git
/project/mirror/public_html/git/cl-base64.gitmirror/cl-base64.git
/project/mirror/public_html/git/cl-bio.gitmirror/cl-bio.git
/project/mirror/public_html/git/cl-modlisp.gitmirror/cl-modlisp.git
/project/mirror/public_html/git/cl-photo.gitmirror/cl-photo.git
/project/mirror/public_html/git/cl-readline.gitmirror/cl-readline.git
/project/mirror/public_html/git/cl-rss.gitmirror/cl-rss.git
/project/mirror/public_html/git/clem.gitmirror/clem.git
/project/mirror/public_html/git/clisp.gitmirror/clisp.git
/project/mirror/public_html/git/clsql.gitmirror/clsql.git
/project/mirror/public_html/git/clsr.gitmirror/clsr.git
/project/mirror/public_html/git/cluck.gitmirror/cluck.git
/project/mirror/public_html/git/cluster-ffi.gitmirror/cluster-ffi.git
/project/mirror/public_html/git/epigraph.gitmirror/epigraph.git
/project/mirror/public_html/git/gcc-xml-ffi.gitmirror/gcc-xml-ffi.git
/project/mirror/public_html/git/getopt.gitmirror/getopt.git
/project/mirror/public_html/git/hunchentoot-auth.gitmirror/hunchentoot-auth.git
/project/mirror/public_html/git/hunchentoot-cgi.gitmirror/hunchentoot-cgi.git
/project/mirror/public_html/git/hunchentoot-vhost.gitmirror/hunchentoot-vhost.git
/project/mirror/public_html/git/hyperobject.gitmirror/hyperobject.git
/project/mirror/public_html/git/irc-logger.gitmirror/irc-logger.git
/project/mirror/public_html/git/kmrcl.gitmirror/kmrcl.git
/project/mirror/public_html/git/lml.gitmirror/lml.git
/project/mirror/public_html/git/lml2.gitmirror/lml2.git
/project/mirror/public_html/git/md5.gitmirror/md5.git
/project/mirror/public_html/git/nuclblog.gitmirror/nuclblog.git
/project/mirror/public_html/git/pipes.gitmirror/pipes.git
/project/mirror/public_html/git/postoffice.gitmirror/postoffice.git
/project/mirror/public_html/git/ptester.gitmirror/ptester.git
/project/mirror/public_html/git/pubmed.gitmirror/pubmed.git
/project/mirror/public_html/git/puri.gitmirror/puri.git
/project/mirror/public_html/git/quicktime-ffi.gitmirror/quicktime-ffi.git
/project/mirror/public_html/git/retrospectiff.gitmirror/retrospectiff.git
/project/mirror/public_html/git/reversi.gitmirror/reversi.git
/project/mirror/public_html/git/rlc.gitmirror/rlc.git
/project/mirror/public_html/git/rt.gitmirror/rt.git
/project/mirror/public_html/git/salza2.gitmirror/salza2.git
/project/mirror/public_html/git/sbcl.gitmirror/sbcl.git
/project/mirror/public_html/git/skippy.gitmirror/skippy.git
/project/mirror/public_html/git/slime.gitmirror/slime.git
/project/mirror/public_html/git/smarkup.gitmirror/smarkup.git
/project/mirror/public_html/git/tiff-ffi.gitmirror/tiff-ffi.git
/project/mirror/public_html/git/time-interval.gitmirror/time-interval.git
/project/mirror/public_html/git/trivial-setuid.gitmirror/trivial-setuid.git
/project/mirror/public_html/git/uffi.gitmirror/uffi.git
/project/mirror/public_html/git/umlisp-orf.gitmirror/umlisp-orf.git
/project/mirror/public_html/git/umlisp.gitmirror/umlisp.git
/project/mirror/public_html/git/vcs-tree.gitmirror/vcs-tree.git
/project/mirror/public_html/git/vecto.gitmirror/vecto.git
/project/mirror/public_html/git/wol.gitmirror/wol.git
/project/mirror/public_html/git/xlunit.gitmirror/xlunit.git
/project/mirror/public_html/git/xmlutils.gitmirror/xmlutils.git
/project/mirror/public_html/git/xptest.gitmirror/xptest.git
/project/mirror/public_html/git/zpb-ttf.gitmirror/zpb-ttf.git
/project/mirror/public_html/git/zpng.gitmirror/zpng.git
/project/mirror/public_html/git/zs3.gitmirror/zs3.git
/project/mkcl/public_html/git/mkcl.gitmkcl/mkcl.git
/project/moptilities/public_html/gitmoptilities/git.git
/project/new-op/public_html/git/new-op.gitnew-op/new-op.git
/project/oct/public_html/git/oct.gitoct/oct.git
/project/osicat/git/osicat.gitosicat/osicat.git
/project/osicat/public_html/old/old-git/osicat.gitosicat/osicat.git
/project/parenscript/public_html/git/parenscriptparenscript/parenscript.git
/project/ply/public_html/src/plyply/ply.git
/project/qitab/git/cl-protobufs.gitqitab/cl-protobufs.git
/project/qitab/git/command-line-arguments.gitqitab/command-line-arguments.git
/project/qitab/git/inferior-shell.gitqitab/inferior-shell.git
/project/qitab/git/lisp-invocation.gitqitab/lisp-invocation.git
/project/qitab/git/poiu.gitqitab/poiu.git
/project/qitab/git/qmynd.gitqitab/qmynd.git
/project/qitab/git/quux-hunchentoot.gitqitab/quux-hunchentoot.git
/project/qitab/git/quux-time.gitqitab/quux-time.git
/project/qitab/git/rpm.gitqitab/rpm.git
/project/qitab/git/single-threaded-ccl.gitqitab/single-threaded-ccl.git
/project/rclg/public_html/git/rclg.gitrclg/rclg.git
/project/sheeple/public_html/git/sheeple.gitsheeple/sheeple.git
/project/sicl/public_html/git/SICL.gitsicl/SICL.git
/project/slime/public_html/slime.gitslime/slime.git
/project/suave/git/amazon-ecssuave/amazon-ecs.git
/project/suave/git/cl-sailssuave/cl-sails.git
/project/suave/git/cl-tidysuave/cl-tidy.git
/project/suave/git/js-parsersuave/js-parser.git
/project/suave/git/paren-eventssuave/paren-events.git
/project/suave/git/paren-filessuave/paren-files.git
/project/suave/git/paren-psossuave/paren-psos.git
/project/suave/git/paren-testsuave/paren-test.git
/project/suave/git/paren-utilsuave/paren-util.git
/project/suave/git/rjsonsuave/rjson.git
/project/suave/git/tmp/cl-svmsuave/cl-svm.git
/project/suave/git/webfunksuave/webfunk.git
/project/suave/git/xml-mopsuave/xml-mop.git
/project/sudoku/public_html/git/sudoku.gitsudoku/sudoku.git
/project/trivial-backtrace/public_html/tb.gittrivial-backtrace/tb.git
/project/trivial-backtrace/public_html/trivial-backtrace.gittrivial-backtrace/trivial-backtrace.git
/project/trivial-iconv/public_html/trivial-iconv.gittrivial-iconv/trivial-iconv.git
/project/xcvb/git/alexandria.gitxcvb/alexandria.git
/project/xcvb/git/asdf-dependency-grovel.gitxcvb/asdf-dependency-grovel.git
/project/xcvb/git/babel.gitxcvb/babel.git
/project/xcvb/git/binascii.gitxcvb/binascii.git
/project/xcvb/git/bordeaux-threads.gitxcvb/bordeaux-threads.git
/project/xcvb/git/cffi.gitxcvb/cffi.git
/project/xcvb/git/chunga.gitxcvb/chunga.git
/project/xcvb/git/cl+ssl.gitxcvb/cl-plus-ssl.git
/project/xcvb/git/cl-base64.gitxcvb/cl-base64.git
/project/xcvb/git/cl-fad.gitxcvb/cl-fad.git
/project/xcvb/git/cl-launch.gitxcvb/cl-launch.git
/project/xcvb/git/cl-ppcre.gitxcvb/cl-ppcre.git
/project/xcvb/git/cl-unicode.gitxcvb/cl-unicode.git
/project/xcvb/git/cl-who.gitxcvb/cl-who.git
/project/xcvb/git/closer-mop.gitxcvb/closer-mop.git
/project/xcvb/git/drakma.gitxcvb/drakma.git
/project/xcvb/git/flexi-streams.gitxcvb/flexi-streams.git
/project/xcvb/git/hu.dwim.stefil.gitxcvb/hu.dwim.stefil.git
/project/xcvb/git/hunchentoot.gitxcvb/hunchentoot.git
/project/xcvb/git/iolib.gitxcvb/iolib.git
/project/xcvb/git/ironclad.gitxcvb/ironclad.git
/project/xcvb/git/iterate.gitxcvb/iterate.git
/project/xcvb/git/lw-compat.gitxcvb/lw-compat.git
/project/xcvb/git/md5.gitxcvb/md5.git
/project/xcvb/git/metabang-bind.gitxcvb/metabang-bind.git
/project/xcvb/git/named-readtables.gitxcvb/named-readtables.git
/project/xcvb/git/nibbles.gitxcvb/nibbles.git
/project/xcvb/git/ptester.gitxcvb/ptester.git
/project/xcvb/git/puri.gitxcvb/puri.git
/project/xcvb/git/quux-iolib.gitxcvb/quux-iolib.git
/project/xcvb/git/rfc2388.gitxcvb/rfc2388.git
/project/xcvb/git/rucksack.gitxcvb/rucksack.git
/project/xcvb/git/split-sequence.gitxcvb/split-sequence.git
/project/xcvb/git/trivial-backtrace.gitxcvb/trivial-backtrace.git
/project/xcvb/git/trivial-features.gitxcvb/trivial-features.git
/project/xcvb/git/trivial-garbage.gitxcvb/trivial-garbage.git
/project/xcvb/git/trivial-gray-streams.gitxcvb/trivial-gray-streams.git
/project/xcvb/git/trivial-ldap.gitxcvb/trivial-ldap.git
/project/xcvb/git/usocket.gitxcvb/usocket.git
/project/xcvb/git/xcvb.gitxcvb/xcvb.git
/project/xhtmlambda/public_html/git/XHTMLambda.gitxhtmlambda/XHTMLambda.git
/project/yason/public_html/yasonyason/yason.git
+ diff --git a/content/gitlab-migration-status.html b/content/gitlab-migration-status.html index cda6d72..588fcfb 100644 --- a/content/gitlab-migration-status.html +++ b/content/gitlab-migration-status.html @@ -1,107 +1,78 @@ ---- -title: Migration to GitLab for Common-Lisp.net ---- - +
+
+

Common-Lisp.net migration to GitLab: status

+ +

+ As announced in this e-mail, + common-lisp.net services will be restructured - to the benefit + of (most) users as well as the admins. +

+

In this follow-up e-mail, + 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. +

+
- + + 0.Install a Code Commenting plugin on Trac to + make it match the GitLab code commenting capabilities + Pending  + 1.Finish my experiments regarding the GitLab + setup / installation
+ see feedback solicited + and mapping of repositoriesDoneMarch 20, 2015 + 2.Install GitLab on common-lisp.net (under the + gitlab.common-lisp.net domain? or should we prefer + git.common-lisp.net?)DoneMarch 20, 2015 + 3.Run the migration to create all users and + groups in GitLabDoneMarch 20, 2015 + 4.Import the CMUCL git repositories (using the + script to be used for all projects)skipped  + 5.Run a trial period of 2 months with Raymond Toy + and CMUCL to iron out any unnoticed issuesskipped  + 6.Import the user's git repositoriesDoneMarch 20, 2015 + 7.Import all projects with Git + repositoriesDoneMarch 20, 2015 + 8.Turn off gitweb --> introduce rewrite rules + to point to gitlabDoneMarch 20, 2015 + 9.Turn off git plugin for Trac --> introduce + rewrite rules to point to gitlabDoneMarch 20, 2015 + 10.Turn off git-daemon (fully depend on https + checkouts)DoneMarch 20, 2015 + 11.Convert all project darcs repositories to git + --> Notify all darcs project owners before we do about a + planning/timing   + 12.Import the converted darcs repositories   + 13.Convert users' darcs repositories
+ --> Notify all darcs users before we do about a + planning/timing   + 14.Import converted users' darcs + repositories   + 15.Turn off darcsweb webbrowsing --> introduce + rewrite rules to point to gitlab   + 16.Contact CVS repository owners to ask if they + want to migrate to Git (the default) or SubversionIn progressApril 19, 2015 + 17.Convert CVS repositories to Subversion (where + requested / defaulted)none requested  + 18.Convert CVS repositories to Git (where + requested / defaulted)In progressApril 19, 2015 + 19.Import git-converted CVS repositoriesIn progressApril 19, 2015 + 20.Turn off ViewVC (Subversion & CVS) web-browsing
+ --> introduce rewrite rules to point to gitlab/TracIn progressApril 19, 2015 + 21.Turn off cvsd and related cron jobs   + 22.Turn off svnserve (fully depend on https + checkouts)   + + +
-
-
-

Common-Lisp.net migration to GitLab: status

- -

- As announced in this e-mail, - common-lisp.net services will be restructured - to the benefit - of (most) users as well as the admins. -

-

In this follow-up e-mail, - 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. -

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#StepStatusDate
0.Install a Code Commenting plugin on Trac to - make it match the GitLab code commenting capabilitiesPending 
1.Finish my experiments regarding the GitLab - setup / installation
- see feedback solicited - and mapping of repositories
DoneMarch 20, 2015
2.Install GitLab on common-lisp.net (under the - gitlab.common-lisp.net domain? or should we prefer - git.common-lisp.net?)DoneMarch 20, 2015
3.Run the migration to create all users and - groups in GitLabDoneMarch 20, 2015
4.Import the CMUCL git repositories (using the - script to be used for all projects)skipped 
5.Run a trial period of 2 months with Raymond Toy - and CMUCL to iron out any unnoticed issuesskipped 
6.Import the user's git repositoriesDoneMarch 20, 2015
7.Import all projects with Git - repositoriesDoneMarch 20, 2015
8.Turn off gitweb --> introduce rewrite rules - to point to gitlabDoneMarch 20, 2015
9.Turn off git plugin for Trac --> introduce - rewrite rules to point to gitlabDoneMarch 20, 2015
10.Turn off git-daemon (fully depend on https - checkouts)DoneMarch 20, 2015
11.Convert all project darcs repositories to git - --> Notify all darcs project owners before we do about a - planning/timing  
12.Import the converted darcs repositories  
13.Convert users' darcs repositories
- --> Notify all darcs users before we do about a - planning/timing
  
14.Import converted users' darcs - repositories  
15.Turn off darcsweb webbrowsing --> introduce - rewrite rules to point to gitlab  
16.Contact CVS repository owners to ask if they - want to migrate to Git (the default) or SubversionIn progressApril 19, 2015
17.Convert CVS repositories to Subversion (where - requested / defaulted)none requested 
18.Convert CVS repositories to Git (where - requested / defaulted)In progressApril 19, 2015
19.Import git-converted CVS repositoriesIn progressApril 19, 2015
20.Turn off ViewVC (Subversion & CVS) web-browsing
- --> introduce rewrite rules to point to gitlab/Trac
In progressApril 19, 2015
21.Turn off cvsd and related cron jobs  
22.Turn off svnserve (fully depend on https - checkouts)  
-
- - -
+
diff --git a/content/independent-lists.html b/content/independent-lists.html index a002c1a..ad5635e 100644 --- a/content/independent-lists.html +++ b/content/independent-lists.html @@ -1,39 +1,36 @@ ---- -title: Independent Mailing Lists ---- -
-

How to apply

-

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.

+
+

How to apply

+

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.

-
-
-

Lists

- - - - - - - - - - - - - - - - - - - - - - - -
BLIS by Pascal Constanza
boston-lisp by Dan Stranger
cl-debian by Peter Van Eynde
cl-user by Arthur Lemmens
chicago-lisp by Paul F. Dietz
eurolisp by Tayssir John Gabbour and Arthur Lemmens
fm-lisp by Edi Weitz
hungarian-lispers by Attila Lendvai
l4-lisp by Julian Stecklina
lisp-game-dev by Brandon Edens
lisp-hh by Edi Weitz
lisppaste-requests by Brian Mastenbrook
ltk-user by Peter Herth
mac-lisp-ide by Brian Mastenbrook
mop-standard-discuss by Daniel Barlow
munich-lisp by Jim Newton
regex-coach by Edi Weitz
seattle by Daniel Pezely
streams-standard-discuss by Daniel Barlow
small-cl-src by Ingvar Mattsson and Mario Mommer
small-cl-src-discuss by Ingvar Mattsson and Mario Mommer
threads-standard-discuss by Daniel Barlow
+
+
+

Lists

+ + + + + + + + + + + + + + + + + + + + + + + +
BLIS by Pascal Constanza
boston-lisp by Dan Stranger
cl-debian by Peter Van Eynde
cl-user by Arthur Lemmens
chicago-lisp by Paul F. Dietz
eurolisp by Tayssir John Gabbour and Arthur Lemmens
fm-lisp by Edi Weitz
hungarian-lispers by Attila Lendvai
l4-lisp by Julian Stecklina
lisp-game-dev by Brandon Edens
lisp-hh by Edi Weitz
lisppaste-requests by Brian Mastenbrook
ltk-user by Peter Herth
mac-lisp-ide by Brian Mastenbrook
mop-standard-discuss by Daniel Barlow
munich-lisp by Jim Newton
regex-coach by Edi Weitz
seattle by Daniel Pezely
streams-standard-discuss by Daniel Barlow
small-cl-src by Ingvar Mattsson and Mario Mommer
small-cl-src-discuss by Ingvar Mattsson and Mario Mommer
threads-standard-discuss by Daniel Barlow
-
+
diff --git a/content/index.html b/content/index.html index 09e9bef..5fed72e 100644 --- a/content/index.html +++ b/content/index.html @@ -1,167 +1,138 @@ ---- -title: Welcome to Common-Lisp.net! ---- - - - - -
-
-

Introduction

-

Welcome to the amazing world of Common Lisp, the - programmable programming language.

- -

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.

-
- -
-

Latest news

- - -
- 2015-05-25 -

Today the system has been declared "CVS clean"! All - remnants of CVS have been removed.

-
- -
- 2015-05-23 -

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.

-
- - - -
- 2015-05-22 -

GitLab upgraded to GitLab 7.11.1.

-
- - -
- 2015-05-15 -

Proposed approach for Darcs repository migration sent out.

-

Read more...

-
- - -
- 2015-05-12 -

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.

-

Now that the projects have been migrated, we'll start - preparations to migrate the Darcs repositories on the system.

-

Read more...

-
- -
- 2015-05-03 -

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.

-

Read more...

-
- -
- 2015-04-27 -

GitLab fixes issue reported by common-lisp.net admin: loading of commit data -

-
- -

Read older news...

-
- -
-

What is Common Lisp?

- -

Common Lisp is the modern, multi-paradigm, high-performance, - compiled, ANSI-standardized, most prominent (along with Scheme) descendant of the - long-running family of Lisp programming languages. Curious? Click - here to get started! -

- -

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).

- -

Common Lisp is a multi-paradigm programming language that - allows you to to choose the approach and paradigm according to - your application domain.

- -

You may find more of the Common Lisp community at these resources:

- -
- -
-

Services

- - -
- -
-

Support

- -

If you need technical support, please contact our - admins.

-
- -
-

About this site

- -

Check out our about page.

-
-
- +
+
+

Introduction

+

Welcome to the amazing world of Common Lisp, the + programmable programming language.

+ +

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.

+
+ +
+

Latest news

+ + +
+ 2015-05-25 +

Today the system has been declared "CVS clean"! All + remnants of CVS have been removed.

+
+ +
+ 2015-05-23 +

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.

+
+ + + +
+ 2015-05-22 +

GitLab upgraded to GitLab 7.11.1.

+
+ + +
+ 2015-05-15 +

Proposed approach for Darcs repository migration sent out.

+

Read more...

+
+ + +
+ 2015-05-12 +

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.

+

Now that the projects have been migrated, we'll start + preparations to migrate the Darcs repositories on the system.

+

Read more...

+
+ +
+ 2015-05-03 +

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.

+

Read more...

+
+ +
+ 2015-04-27 +

GitLab fixes issue reported by common-lisp.net admin: loading of commit data +

+
+ +

Read older news...

+
+ +
+

What is Common Lisp?

+ +

Common Lisp is the modern, multi-paradigm, high-performance, + compiled, ANSI-standardized, most prominent (along with Scheme) descendant of the + long-running family of Lisp programming languages. Curious? Click + here to get started! +

+ +

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).

+ +

Common Lisp is a multi-paradigm programming language that + allows you to to choose the approach and paradigm according to + your application domain.

+ +

You may find more of the Common Lisp community at these resources:

+ +
+ +
+

Services

+ + +
+ +
+

Support

+ +

If you need technical support, please contact our + admins.

+
+ +
+

About this site

+ +

Check out our about page.

+
+
diff --git a/content/news.html b/content/news.html index af69f72..68f9386 100644 --- a/content/news.html +++ b/content/news.html @@ -1,446 +1,417 @@ ---- -title: News from Common-Lisp.net ---- - - - - -
-

Latest news

- - -

2015-05-25

-

Today the system has been declared "CVS clean"! All - remnants of CVS have been removed.

- -

2015-05-23

-

On Friday, the system had performance problems due to slow I/O. - Checking the S.M.A.R.T. parameters of the disks didn't show anything - unusual. Today, the disk system reports running in degraded mode, - so we ordered the failing disk to be replaced, causing only minor - downtime. The disk array has been rebuilt and it's smooth sailing - from here again!

- - -

2015-05-22

-

GitLab upgraded to GitLab 7.11.1.

- - -

2015-05-15

-

Proposed approach for Darcs repository migration sent out.

- - -

2015-05-12

-

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:

- - -

Now that the CVS repositories have been migrated, we'll - move to clean up the cvs services from the underlying box and - preparations will start to migrate the Darcs repositories on the - system. For progress on the Darcs repository migration, watch - the clo-devel mailing list.

- -

2015-05-03

-

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:

- - -

2015-04-27

-

GitLab project fixes issues reported by common-lisp.net admin: - loading - of commit data. -

- -

2015-04-26

-

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:

- - - -

2015-04-22

-

GitLab has been upgraded to 7.10.0; one - of the tickets we filed with the GitLab project, has been - resolved now.

- -

2015-04-19

-

Migration of CVS repositories to Git+GitLab has started. The - first batch (10 projects) was converted: -

- - - -

In total there are 120 CVS repositories to convert. Project members - receive an announcement mail in advance. CVS repositories which are - left behind after conversion to another VC will be skipped and - projects which are in such a situation are kindly requested - to notify the admins of such situation - or even better: clean it - up before the admins run into it. Now is your chance! :-) -

- -

2015-04-17

-

GitLab upgraded to - 7.9.4 -

- -

2015-04-11

-

The first projects with CVS repositories have received e-mails - about the planned migration according to the proposed procedure. We're going in batches, using aphabetical - order, so you may not have received e-mail for your projects yet. - Don't dispair, it'll come! -

-

The announcement e-mail requires action if you want to migrate - to Subversion instead of to Git. If you want to migrate to - Git+GitLab, there's no - need to respond. It's the default. -

-

If you want to declare that your project wants to migrate to - Subversion without awaiting your announcement e-mail, please file - a ticket in the site's Trac instance. -

- - -

2015-04-08

-

Due to a variety of reasons, the history of the mailing lists - of common-lisp.net had spread over a number of sources:

- -

With only the archives from the last bullet hosted in viewable form, - valuable Common Lisp history and coding advice collected over the years - has been unavailable for at least 9 months. -

-

Now, this long-overdue task has finally been completed. The - mailing list history can be browsed and indexed again from - the online - archive

- -

2015-03-27

-

Today we enabled project imports from GitHub. Should you want - to import your project (which should import both the repository - and the issues) into gitlab, please check out gitlab - documentation for the github import workflow.

-

As part of the effort to enable GitHub imports, we had to do a minor - GitLab upgrade. The current hosted GitLab version is now 7.9.1.

-

Another part of enabling GitHub imports was to allow users to - log in on our site using their GitHub credentials. Please note - that this will only work for those who already have a valid - (i.e. pre-existing and confirmed) GitLab account. If you want to - use this option (which is also available for Google accounts), - please check the GitLab omniauth for existing - users documentation. -

- - -

2015-03-24

-

GitLab upgraded to 7.9.0. GitLab released its newest version - (7.9.0) on the Sunday after the Friday we went live with our - self-hosted GitLab (7.8.4 -- then latest). The release - contains a large number of fixes and enhancements. -

- - -

2015-03-20

-

Our self-hosted git repository management environment - gitlab.common-lisp.net - is now live! During the deployment, the system was seeded with 390 - users, 434 groups and 210 repositories.

- -

The deployment itself took little over an hour, while we were able - to resolve the issues we identified after completion well within - the migration timeframe of 4 hours. During this time, most services - were fully available. Only SSH has been impacted shortly.

- -

If you experience any issues, please report to the site admins.

-

We hope you enjoy the new user experience!

- -

2015-03-16

-

Today the date has been announced for the final - migration of all git repositories to GitLab: Friday March 20th! -

- - -

2015-03-08

-

- While testing the seeding scripts for the new GitLab site, - a number of e-mails to live users have unintentionally been - sent instead of held. -

-

The content of the messages suggests one may be able to log in - on the system. When trying so, the system denies access. - This is a side effect of the testing setup. In the final migration - run, you will receive an account confirmation mail. A mail not - distributed in the test-run. Once the account is confirmed, the - system will allow changing passwords and logging in. -

-

- We're sorry for any inconvenience caused. -

- -

2015-02-19

-

- The site admins have announced a change in policies for the - mailing lists to be in effect as of March 15th, 2015. Please read the original announcement e-mail for details. -

- -

In summary, there are two changes being implemented:

-
    -
  1. Subject prefix '[<mailing-list>]' won't be added anymore.
  2. -
  3. Moderation requests won't be held indefinitely anymore, defaulting - to a hold period of 90 days (expiring the unmoderated e-mail - when unhandled).
  4. -
-

The former addresses problems with delivery of DKIM signed mail - being sent through mailing lists. Changing the message headers and - body may invalidate any prior DKIM signatures, leading to mailing list - e-mail looking suspect to large mail receiving providers like Google - and Yahoo!.

-

The later addresses the fact that the moderation queue is growing - indefinitely, with most lists set to never expire moderation requests. -

- - -

2015-02-10

-

- The site admins identified a - list of mailing lists for which contact with the list owner has - been lost list for your favorite list or your name. -

- -

2015-02-08

-

- Due to a failed system upgrade, the system experienced extended - downtime on Sunday. Our apologies for any inconvenience. -

-

- The maintenance was completed successfully around 18.00 UTC and - is a step towards easier maintainance for the system and support - the development of new and simplified configuration. -

- -

2015-02-06

-

- Erik Huelsmann -one of the common-lisp.net maintainers- has submitted - a proposal for the nearby future of the site. Read the details in his mail to the - clo-devel mailing list in the archive. Feedback is very much - appreciated. -

- -

2015-02-01

-

- The (www.)common-lisp.net domain has started using the https - protocol for all its URLs. In the weeks to come, the various - sub-domains will be switched too. This change has been made - in response to user requests. Should you have a request too, - please let us know on the mailing +

+

Latest news

+ + +

2015-05-25

+

Today the system has been declared "CVS clean"! All + remnants of CVS have been removed.

+ +

2015-05-23

+

On Friday, the system had performance problems due to slow I/O. + Checking the S.M.A.R.T. parameters of the disks didn't show anything + unusual. Today, the disk system reports running in degraded mode, + so we ordered the failing disk to be replaced, causing only minor + downtime. The disk array has been rebuilt and it's smooth sailing + from here again!

+ + +

2015-05-22

+

GitLab upgraded to GitLab 7.11.1.

+ + +

2015-05-15

+

Proposed approach for Darcs repository migration sent out.

+ + +

2015-05-12

+

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:

+
    +
  • gamelib
  • +
  • ganelon
  • +
  • geometry
  • +
  • ginseng
  • +
  • glouton
  • +
  • gsharp
  • +
  • gtk-cffi
  • +
  • html-template
  • +
  • hyperdoc
  • +
  • hyperspec-lookup
  • +
  • ieeefp-tests
  • +
  • imago
  • +
  • iso8601-date
  • +
  • jnil
  • +
  • lambda-gtk
  • +
  • lgtk
  • +
  • lispfaq
  • +
  • lispy
  • +
  • lmud
  • +
  • log4cl
  • +
  • mcclim
  • +
  • meta-cvs
  • +
  • misc-extensions
  • +
  • morphologie
  • +
  • movitz
  • +
  • nio
  • +
  • noctool
  • +
  • pal
  • +
  • pg
  • +
  • phemlock
  • +
  • plain-odbc
  • +
  • rfc2388
  • +
  • rfc2822
  • +
  • rjain-utils
  • +
  • rucksack
  • +
  • sapaclisp
  • +
  • sb-simd
  • +
  • snmp1
  • +
  • spray
  • +
  • stamp
  • +
  • s-xml
  • +
  • s-xml-rpc
  • +
  • trivial-freeimage
  • +
  • unetwork
  • +
  • zip
  • +
  • zlib
  • +
+ +

Now that the CVS repositories have been migrated, we'll + move to clean up the cvs services from the underlying box and + preparations will start to migrate the Darcs repositories on the + system. For progress on the Darcs repository migration, watch + the clo-devel mailing list.

+ +

2015-05-03

+

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:

+
    +
  • cl-magick
  • +
  • cl-menusystem
  • +
  • cl-mp3-parse
  • +
  • closure
  • +
  • clouchdb
  • +
  • cl-plus-ssl
  • +
  • cl-ppcre
  • +
  • cl-prevalence
  • +
  • cl-rope
  • +
  • cl-sbml
  • +
  • cl-screen
  • +
  • cl-selenium
  • +
  • cl-semantic
  • +
  • cl-smogames
  • +
  • cl-smtp
  • +
  • cl-snmp
  • +
  • cl-soap
  • +
  • cl-store
  • +
  • cl-syslog
  • +
  • cl-telnetd
  • +
  • cl-utilities
  • +
  • cl-wav-synth
  • +
  • cl-who
  • +
  • cl-x86-asm
  • +
  • cl-xmms
  • +
  • cl-xmpp
  • +
  • corman-sdl
  • +
  • cparse
  • +
  • crypticl
  • +
  • cxml
  • +
  • defdoc
  • +
  • defeditor
  • +
  • definer
  • +
  • defplayer
  • +
  • defwm
  • +
  • eclipse
  • +
  • elephant
  • +
  • fetter
  • +
  • flexichain
  • +
  • fomus
  • +
+ +

2015-04-27

+

GitLab project fixes issues reported by common-lisp.net admin: + loading + of commit data. +

+ +

2015-04-26

+

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:

+
    +
  • cinline
  • +
  • cl-blog
  • +
  • cl-carbon
  • +
  • cl-cli-parser
  • +
  • cl-cracklib
  • +
  • cl-dbf
  • +
  • cldoc
  • +
  • cl-enumeration
  • +
  • cl-fltk
  • +
  • cl-godb
  • +
  • cl-gsl
  • +
  • climacs
  • +
  • clim-desktop
  • +
  • cl-interpol
  • +
  • cl-ipc
  • +
  • cl-jpeg
  • +
  • cl-libtai
  • +
+ + +

2015-04-22

+

GitLab has been upgraded to 7.10.0; one + of the tickets we filed with the GitLab project, has been + resolved now.

+ +

2015-04-19

+

Migration of CVS repositories to Git+GitLab has started. The + first batch (10 projects) was converted: +

+ +
    +
  • anaphora
  • +
  • aspiwork-pdm
  • +
  • bayescl
  • +
  • beep
  • +
  • beirc
  • +
  • bese
  • +
  • cello
  • +
  • cells
  • +
  • cells-gtk
  • +
  • cells-ode
  • +
+ +

In total there are 120 CVS repositories to convert. Project members + receive an announcement mail in advance. CVS repositories which are + left behind after conversion to another VC will be skipped and + projects which are in such a situation are kindly requested + to notify the admins of such situation - or even better: clean it + up before the admins run into it. Now is your chance! :-) +

+ +

2015-04-17

+

GitLab upgraded to + 7.9.4 +

+ +

2015-04-11

+

The first projects with CVS repositories have received e-mails + about the planned migration according to the proposed procedure. We're going in batches, using aphabetical + order, so you may not have received e-mail for your projects yet. + Don't dispair, it'll come! +

+

The announcement e-mail requires action if you want to migrate + to Subversion instead of to Git. If you want to migrate to + Git+GitLab, there's no + need to respond. It's the default. +

+

If you want to declare that your project wants to migrate to + Subversion without awaiting your announcement e-mail, please file + a ticket in the site's Trac instance. +

+ + +

2015-04-08

+

Due to a variety of reasons, the history of the mailing lists + of common-lisp.net had spread over a number of sources:

+
    +
  • the older system's mailman list manager's history (mbox format)
  • +
  • the intermediately used mlmmj list manager's history (spool directory, individual mails)
  • +
  • the new system's mailman list manager's history (mbox format)
  • +
+

With only the archives from the last bullet hosted in viewable form, + valuable Common Lisp history and coding advice collected over the years + has been unavailable for at least 9 months. +

+

Now, this long-overdue task has finally been completed. The + mailing list history can be browsed and indexed again from + the online + archive

+ +

2015-03-27

+

Today we enabled project imports from GitHub. Should you want + to import your project (which should import both the repository + and the issues) into gitlab, please check out gitlab + documentation for the github import workflow.

+

As part of the effort to enable GitHub imports, we had to do a minor + GitLab upgrade. The current hosted GitLab version is now 7.9.1.

+

Another part of enabling GitHub imports was to allow users to + log in on our site using their GitHub credentials. Please note + that this will only work for those who already have a valid + (i.e. pre-existing and confirmed) GitLab account. If you want to + use this option (which is also available for Google accounts), + please check the GitLab omniauth for existing + users documentation. +

+ + +

2015-03-24

+

GitLab upgraded to 7.9.0. GitLab released its newest version + (7.9.0) on the Sunday after the Friday we went live with our + self-hosted GitLab (7.8.4 -- then latest). The release + contains a large number of fixes and enhancements. +

+ + +

2015-03-20

+

Our self-hosted git repository management environment + gitlab.common-lisp.net + is now live! During the deployment, the system was seeded with 390 + users, 434 groups and 210 repositories.

+ +

The deployment itself took little over an hour, while we were able + to resolve the issues we identified after completion well within + the migration timeframe of 4 hours. During this time, most services + were fully available. Only SSH has been impacted shortly.

+ +

If you experience any issues, please report to the site admins.

+

We hope you enjoy the new user experience!

+ +

2015-03-16

+

Today the date has been announced for the final + migration of all git repositories to GitLab: Friday March 20th! +

+ + +

2015-03-08

+

+ While testing the seeding scripts for the new GitLab site, + a number of e-mails to live users have unintentionally been + sent instead of held. +

+

The content of the messages suggests one may be able to log in + on the system. When trying so, the system denies access. + This is a side effect of the testing setup. In the final migration + run, you will receive an account confirmation mail. A mail not + distributed in the test-run. Once the account is confirmed, the + system will allow changing passwords and logging in. +

+

+ We're sorry for any inconvenience caused. +

+ +

2015-02-19

+

+ The site admins have announced a change in policies for the + mailing lists to be in effect as of March 15th, 2015. Please read the original announcement e-mail for details. +

+ +

In summary, there are two changes being implemented:

+
    +
  1. Subject prefix '[<mailing-list>]' won't be added anymore.
  2. +
  3. Moderation requests won't be held indefinitely anymore, defaulting + to a hold period of 90 days (expiring the unmoderated e-mail + when unhandled).
  4. +
+

The former addresses problems with delivery of DKIM signed mail + being sent through mailing lists. Changing the message headers and + body may invalidate any prior DKIM signatures, leading to mailing list + e-mail looking suspect to large mail receiving providers like Google + and Yahoo!.

+

The later addresses the fact that the moderation queue is growing + indefinitely, with most lists set to never expire moderation requests. +

+ + +

2015-02-10

+

+ The site admins identified a + list of mailing lists for which contact with the list owner has + been lost list for your favorite list or your name. +

+ +

2015-02-08

+

+ Due to a failed system upgrade, the system experienced extended + downtime on Sunday. Our apologies for any inconvenience. +

+

+ The maintenance was completed successfully around 18.00 UTC and + is a step towards easier maintainance for the system and support + the development of new and simplified configuration. +

+ +

2015-02-06

+

+ Erik Huelsmann -one of the common-lisp.net maintainers- has submitted + a proposal for the nearby future of the site. Read the details in his mail to the + clo-devel mailing list in the archive. Feedback is very much + appreciated. +

+ +

2015-02-01

+

+ The (www.)common-lisp.net domain has started using the https + protocol for all its URLs. In the weeks to come, the various + sub-domains will be switched too. This change has been made + in response to user requests. Should you have a request too, + please let us know on the mailing list! -

- -

2015-01-30

-

- The mail system's criteria for accepting mail have been tightened - and mail forwarding now uses SRS when the sender domain specifies an - SPF policy. - The changes address these issues: -

-
    -
  • too many spam mails entering the moderation queues
  • -
  • improved reputation of the common-lisp.net domain at Google
  • -
-

Google considers common-lisp.net a Bulk Sender, which means - we must abide by a number of requirements to make sure mail gets accepted. -

-

Some of the stricter criteria to accept mail on common-lisp.net are: -

-
-
Mail failing SPF validation is no longer accepted
-
Due to the SRS rewriting, these mails would leave - common-lisp.net as legitimate mail. By rejecting these - mails, we honor the policy stated by the sender domain.
- Note: We're currently not rejecting soft-failing mails.
-
Mail failing DKIM validation is no longer accepted
-
Forwarding mail which fails DKIM validation reflects - poorly on common-lisp.net's reputation as a mail host. - By rejecting mail failing DKIM validation, we honor the - policy stated by the sender domain.
-
A series of requirements on the host submitting mail
-
By enforcing a number of requirements on the DNS configuration - and protocol conformity of the hosts submitting mail to - common-lisp.net, we enforce the same requirements that Google - and other mail hosters enforce on us, common-lisp.net can't - be used as a hub by spammers to increase legitemacy of the mail - flow. Nor can accidental forwarding of spam mail hurt - common-lisp.net's reputation with the large mail hosters.
-
- -

2014-09-22

- -

Hello everybody. The site moved to a shiny new server a few - moments ago. Everything should work, and if it doesn't, please - let - us know.

- -

You can also help us by donating.

- -
- +

+ +

2015-01-30

+

+ The mail system's criteria for accepting mail have been tightened + and mail forwarding now uses SRS when the sender domain specifies an + SPF policy. + The changes address these issues: +

+ +

Google considers common-lisp.net a Bulk Sender, which means + we must abide by a number of requirements to make sure mail gets accepted. +

+

Some of the stricter criteria to accept mail on common-lisp.net are: +

+
+
Mail failing SPF validation is no longer accepted
+
Due to the SRS rewriting, these mails would leave + common-lisp.net as legitimate mail. By rejecting these + mails, we honor the policy stated by the sender domain.
+ Note: We're currently not rejecting soft-failing mails.
+
Mail failing DKIM validation is no longer accepted
+
Forwarding mail which fails DKIM validation reflects + poorly on common-lisp.net's reputation as a mail host. + By rejecting mail failing DKIM validation, we honor the + policy stated by the sender domain.
+
A series of requirements on the host submitting mail
+
By enforcing a number of requirements on the DNS configuration + and protocol conformity of the hosts submitting mail to + common-lisp.net, we enforce the same requirements that Google + and other mail hosters enforce on us, common-lisp.net can't + be used as a hub by spammers to increase legitemacy of the mail + flow. Nor can accidental forwarding of spam mail hurt + common-lisp.net's reputation with the large mail hosters.
+
+ +

2014-09-22

+ +

Hello everybody. The site moved to a shiny new server a few + moments ago. Everything should work, and if it doesn't, please + let + us know.

+ +

You can also help us by donating.

+ +
diff --git a/content/orphaned-mailing-lists.html b/content/orphaned-mailing-lists.html index 32f34aa..89d8e2e 100644 --- a/content/orphaned-mailing-lists.html +++ b/content/orphaned-mailing-lists.html @@ -1,136 +1,107 @@ ---- -title: Orphaned mailing lists on common-lisp.net! ---- - +
+

Introduction

- +

+ Most of the mailing list have been configured to hold mails + from non-mailing list members for moderation. Every now and + then (once every few months, usually) a mail like that is to + be expected. The list owner can delegate handling of these + mails to mailing list moderators, if the volume of mails to + be handled grows too big. +

-
-

Introduction

+

+ The position of mailing list owner can be shared to assure + continuity of the position. +

-

- Each mailing list needs an owner. Owners take care of the day - to day management of the mailing list. For most mailing lists, - this doesn't mean much, since (un)subscriptions are processed - automatically. -

+

+ Concluding: Being a mailing list owner is mostly a formality + and will consume extremely little time. +

-

- Most of the mailing list have been configured to hold mails - from non-mailing list members for moderation. Every now and - then (once every few months, usually) a mail like that is to - be expected. The list owner can delegate handling of these - mails to mailing list moderators, if the volume of mails to - be handled grows too big. -

+

+ Sometimes the e-mail address of the mailing list owner + stops receiving mail from the mailing list management software. + That's when the site admins add the mailing list to the table + below. Volunteers are free to request transfer of ownership + by mailing the site developers mailing list. +

-

- The position of mailing list owner can be shared to assure - continuity of the position. -

+

Lost contacts

-

- Concluding: Being a mailing list owner is mostly a formality - and will consume extremely little time. -

+

+ The table below lists (in random order) the mailing lists + for which the site admins lost contact with the current owner. +

+

+ Please contact the mailing list mentioned above if you have + contact info of the people listed, or if you want to claim + list ownership yourself. +

-

- Sometimes the e-mail address of the mailing list owner - stops receiving mail from the mailing list management software. - That's when the site admins add the mailing list to the table - below. Volunteers are free to request transfer of ownership - by mailing the site developers mailing list. -

- -

Lost contacts

- -

- The table below lists (in random order) the mailing lists - for which the site admins lost contact with the current owner. -

-

- Please contact the mailing list mentioned above if you have - contact info of the people listed, or if you want to claim - list ownership yourself. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mailing list Last contactDate
closure-develGilbert Baumann
cl-plus-ssl-develDavid Lichteblau
cxml-develDavid Lichteblau
cldoc-develIban Hatchondo
cl-store-develSean Ross
movitz-develFrode Vatvedt Fjeld
zlib-develDavid Lichteblau
commonqt-develDavid Lichteblau
gecol-develKillian Sprotte
xuriella-develDavid Lichteblau
cl-l10n-develSean Ross
zip-develDavid Lichteblau2015-02-12
lisppaste-requestsBrian Mastenbrook2015-02-22
cl-irc-develBrian Mastenbrook2015-02-22
iterate-develAndreas Fuchs2015-02-24
-
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Mailing list Last contactDate
closure-develGilbert Baumann
cl-plus-ssl-develDavid Lichteblau
cxml-develDavid Lichteblau
cldoc-develIban Hatchondo
cl-store-develSean Ross
movitz-develFrode Vatvedt Fjeld
zlib-develDavid Lichteblau
commonqt-develDavid Lichteblau
gecol-develKillian Sprotte
xuriella-develDavid Lichteblau
cl-l10n-develSean Ross
zip-develDavid Lichteblau2015-02-12
lisppaste-requestsBrian Mastenbrook2015-02-22
cl-irc-develBrian Mastenbrook2015-02-22
iterate-develAndreas Fuchs2015-02-24
+
diff --git a/content/orphaned-projects.html b/content/orphaned-projects.html index 113beac..a1cf224 100644 --- a/content/orphaned-projects.html +++ b/content/orphaned-projects.html @@ -1,118 +1,89 @@ ---- -title: Orphaned projects on common-lisp.net! ---- - +
+

Introduction

- +

+ If you feel compelled to pick up development or maintenance + of an orphaned project, please send mail to the common-lisp.net's mailing list. +

-
-

Introduction

+

Dormant projects

-

- Each project on common-lisp.net has at least one member. - Sometimes, project members actively indicate to want to - be removed from a project. If there are no project members - left, projects are listed on this page. -

- -

- If you feel compelled to pick up development or maintenance - of an orphaned project, please send mail to the common-lisp.net's mailing list. -

- -

Dormant projects

- -

- The table below lists (in random order) all dormant projects. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Since
lw-vim-modeFebruary 19, 2015
lmudMarch 18, 2015
cl-telnetdMarch 18, 2015
cl-curlMarch 28, 2015
c2ffiMarch 28, 2015
cl-applescriptMarch 28, 2015
bayesclApril 11, 2015
cl-blogApril 18, 2015
clhpApril 18, 2015
cl-date-calcApril 18, 2015
defeditorApril 26, 2015
defdocApril 26, 2015
defwmApril 26, 2015
defplayerApril 26, 2015
plain-odbcMay 5, 2015
jnilMay 5, 2015
rjain-utilsMay 5, 2015
snmp1May 5, 2015
gamelibMay 15, 2015
-
+

+ The table below lists (in random order) all dormant projects. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Project Since
lw-vim-modeFebruary 19, 2015
lmudMarch 18, 2015
cl-telnetdMarch 18, 2015
cl-curlMarch 28, 2015
c2ffiMarch 28, 2015
cl-applescriptMarch 28, 2015
bayesclApril 11, 2015
cl-blogApril 18, 2015
clhpApril 18, 2015
cl-date-calcApril 18, 2015
defeditorApril 26, 2015
defdocApril 26, 2015
defwmApril 26, 2015
defplayerApril 26, 2015
plain-odbcMay 5, 2015
jnilMay 5, 2015
rjain-utilsMay 5, 2015
snmp1May 5, 2015
gamelibMay 15, 2015
+
diff --git a/content/phub.html b/content/phub.html index 86932d5..0153371 100644 --- a/content/phub.html +++ b/content/phub.html @@ -1,450 +1,445 @@ ---- -title: Projects ---- -
-

Alphabetical index

-

+

+

Alphabetical index

+

+ able
+ advanced-readtable
+ adw-charting
+ ait
+ alexandria
+ anaphora
+ ansi-test
+ antik
+ araneida
+ armedbear
+ armish
+ arxana
+ asdf
+ asdf-addons
+ asdf-binary-locations
+ asdf-install
+ asdf-packaging
+ asdf-system-connections
+ asia
+ aspectl
+ aspiwork-pdm
+ babel
+ bayescl
+ bdb
+ beep
+ beirc
+ berkeley-db
+ bese
+ bknr
+ bordeaux-threads
+ boston-lisp
+ bpm
+ buclet
+ bytemap
+ c2ffi
+ caleb
+ cdr
+ cello
+ cells
+ cells-gtk
+ cells-ode
+ cffi
+ cffi-objects
+ chemboy
+ chtml-matcher
+ cinline
+ cl+j
+ cl-amqp
+ cl-api
+ cl-applescript
+ cl-bench
+ cl-berkeley-db
+ cl-bio
+ cl-blog
+ cl-buchberger
+ cl-bzip2
+ cl-cactus-kev
+ cl-cairo2
+ cl-captcha
+ cl-carbon
+ cl-cli-parser
+ cl-clickatell
+ cl-colors
+ cl-component
+ cl-cont
+ cl-containers
+ cl-couch
+ cl-cracklib
+ cl-curl
+ cl-darcs
+ cl-date-calc
+ cl-dbf
+ cl-def
+ cl-dises
+ cl-dwim
+ cl-ec2
+ cl-emb
+ cl-enumeration
+ cl-facebook
+ cl-fltk
+ cl-fuse
+ cl-gd
+ cl-gdbm
+ cl-glpk
+ cl-godb
+ cl-graph
+ cl-graphviz
+ cl-gsl
+ cl-gtk2
+ cl-heap
+ cl-hooks
+ cl-interpol
+ cl-ipc
+ cl-irc
+ cl-irregsexp
+ cl-jpeg
+ cl-json
+ cl-kanren-trs
+ cl-l10n
+ cl-launchpad
+ cl-lazy-list
+ cl-lexer
+ cl-librarian
+ cl-libtai
+ cl-machine-learning
+ cl-magick
+ cl-markdown
+ cl-match
+ cl-mathstats
+ cl-memcached
+ cl-menusystem
+ cl-migrations
+ cl-monad-macros
+ cl-mp3-parse
+ cl-mpd
+ cl-mpi
+ cl-muproc
+ cl-ncurses
+ cl-neo4j
+ cl-net-snmp
+ cl-objc
+ cl-octave
+ cl-ode
+ cl-opengl
+ cl-openid
+ cl-org-mode
+ cl-pdf
+ cl-peg
+ cl-perec
+ cl-plplot
+ cl-plus-j
+ cl-plus-ssl
+ cl-pop
+ cl-ppcre
+ cl-prevalence
+ cl-proc
+ cl-quasi-quote
+ cl-rdbms
+ cl-rope
+ cl-rundown
+ cl-sbml
+ cl-screen
+ cl-selenium
+ cl-semantic
+ cl-serializer
+ cl-smogames
+ cl-smtp
+ cl-snmp
+ cl-soap
+ cl-sockets
+ cl-sqlite
+ cl-stm
+ cl-stomp
+ cl-store
+ cl-syntax-sugar
+ cl-syslog
+ cl-table
+ cl-taint
+ cl-telnetd
+ cl-test-grid
+ cl-trane
+ cl-twitter
+ cl-typesetting
+ cl-unification
+ cl-uri
+ cl-utilities
+ cl-variates
+ cl-walker
+ cl-wav-synth
+ cl-wdim
+ cl-weblocks
+ cl-who
+ cl-wiki
+ cl-x86-asm
+ cl-xml
+ cl-xmlspam
+ cl-xmms
+ cl-xmpp
+ cl-yacc-ebnf
+ clTcl
+ clappa
+ clarity
+ claw
+ clazy
+ clbuild
+ cldoc
+ cleric
+ clfswm
+ clget
+ clhp
+ cliki
+ clim-desktop
+ climacs
+ climplayer
+ clkd
+ clnuplot
+ clo
+ clois-lane
+ clonsigna
+ closer
+ closure
+ clotnet
+ clouchdb
+ cloud
+ clpython
+ clsql-fluid
+ clsql-mysql-introspect
+ cltl3
+ cmucl
+ common-lisp-beginner
+ common-math
+ commonqt
+ computed-class
+ core-services
+ corman-sdl
+ cparse
+ crypticl
+ css-sexp
+ cxml
+ de-setf-amqp
+ de-setf-graphics
+ de.setf.amqp
+ decl
+ defclass-star
+ defdoc
+ defeditor
+ definer
+ defmud
+ defplayer
+ defwm
+ docudown
+ docutrack
+ drakma
+ dynamic-classes
+ dyslexia
+ eager-future
+ ecl
+ ecl-readline
+ eclipse
+ editor-hints
+ elephant
+ encline
+ erlang-in-lisp
+ erlisp
+ external-program
+ f2cl
+ fetter
+ fiveam
+ flexi-streams
+ flexichain
+ fomus
+ fret
+ fset
+ ftd
+ fucc
+ funds
+ gamelib
+ ganelon
+ geco
+ gecol
+ geohash
+ geometry
+ gestalt
+ ginseng
+ glouton
+ gnucard
+ grand-prix
+ graphic-forms
+ gsharp
+ gsll
+ gtk-cffi
+ gzip-stream
+ ht-ajax
+ html-template
+ hyperdoc
+ hyperspec-lookup
+ iaxphone
+ ieee-floats
+ ieeefp-tests
+ imago
+ innen
+ iolib
+ ip-interfaces
+ isidorus
+ iso8601-date
+ israel-lisp
+ iterate
+ iterate-clsql
+ jess-parse
+ jnil
+ kpax
+ l-math
+ lambda-gtk
+ langutils
+ lgtk
+ liards
+ lifp
+ lift
+ limp
+ lineal
+ linedit
+ lisp-interface-library
+ lisp-matrix
+ lisp-on-lines
+ lisp-res-kit
+ lispbox
+ lispfaq
+ lisplab
+ lisppaste
+ lispvirt
+ lispy
+ lmud
+ local-time
+ log4cl
+ log5
+ lost+found
+ lw-vim-mode
+ macho
+ macondoolap
+ magicffi
+ mcclim
+ mel-base
+ meta-cvs
+ metabang-bind
+ metacopy
+ metatilities
+ metatilities-base
+ mirror
+ misc-extensions
+ misrouted
+ mit-cadr
+ mk-defsystem
+ mkcl
+ mod-lisp
+ modisc
+ moptilities
+ morphologie
+ movies
+ movitz
+ named-readtables
+ names-and-paths
+ new-op
+ nio
+ nixies
+ noctool
+ nrw-xmcl
+ nxtlisp
+ objective-cl
+ oct
+ okra
+ openair
+ osicat
+ pal
+ parenscript
+ parse-declarations
+ patty
+ pg
+ pg-introspect
+ phemlock
+ phorplay
+ plain-odbc
+ plexippus-xpath
+ ply
+ portage-overlay
+ postmodern
+ pretty-function
+ protobuf
+ py-configparser
+ python-on-lisp
+ qitab
+ quiz
+ rcl
+ rclg
+ rdnzl
+ rfc2109
+ rfc2388
+ rfc2822
+ rjain-utils
+ rucksack
+ s-xml
+ s-xml-rpc
+ same
+ sapaclisp
+ sb-simd
+ sequence-iterators
+ sexpc
+ sfip
+ sheeple
+ sicl
+ simple-http
+ slime
+ snmp1
+ snow
+ sparklines
+ spray
+ sqlisp
+ ssc
+ stamp
+ stdutil
+ steeldump
+ stefil
+ suave
+ submarine
+ sudoku
+ tbnl
+ teepeedee2
+ the-feebs-war
+ tinaa
+ tioga
+ trivial-backtrace
+ trivial-features
+ trivial-freeimage
+ trivial-garbage
+ trivial-gray-streams
+ trivial-http
+ trivial-iconv
+ trivial-shell
+ trivial-timeout
+ trivial-utf-8
+ ubf
+ ucs-sort
+ ucw
+ ucw-extras
+ umpa-lumpa
+ unetwork
+ uri-template
+ usocket
+ vial
+ vivace-graph
+ wispylisp
+ xcvb
+ xhtmlambda
+ xml-psychiatrist
+ xmls
+ xuriella
+ yason
+ zip
+ zlib
-able
-advanced-readtable
-adw-charting
-ait
-alexandria
-anaphora
-ansi-test
-antik
-araneida
-armedbear
-armish
-arxana
-asdf
-asdf-addons
-asdf-binary-locations
-asdf-install
-asdf-packaging
-asdf-system-connections
-asia
-aspectl
-aspiwork-pdm
-babel
-bayescl
-bdb
-beep
-beirc
-berkeley-db
-bese
-bknr
-bordeaux-threads
-boston-lisp
-bpm
-buclet
-bytemap
-c2ffi
-caleb
-cdr
-cello
-cells
-cells-gtk
-cells-ode
-cffi
-cffi-objects
-chemboy
-chtml-matcher
-cinline
-cl+j
-cl-amqp
-cl-api
-cl-applescript
-cl-bench
-cl-berkeley-db
-cl-bio
-cl-blog
-cl-buchberger
-cl-bzip2
-cl-cactus-kev
-cl-cairo2
-cl-captcha
-cl-carbon
-cl-cli-parser
-cl-clickatell
-cl-colors
-cl-component
-cl-cont
-cl-containers
-cl-couch
-cl-cracklib
-cl-curl
-cl-darcs
-cl-date-calc
-cl-dbf
-cl-def
-cl-dises
-cl-dwim
-cl-ec2
-cl-emb
-cl-enumeration
-cl-facebook
-cl-fltk
-cl-fuse
-cl-gd
-cl-gdbm
-cl-glpk
-cl-godb
-cl-graph
-cl-graphviz
-cl-gsl
-cl-gtk2
-cl-heap
-cl-hooks
-cl-interpol
-cl-ipc
-cl-irc
-cl-irregsexp
-cl-jpeg
-cl-json
-cl-kanren-trs
-cl-l10n
-cl-launchpad
-cl-lazy-list
-cl-lexer
-cl-librarian
-cl-libtai
-cl-machine-learning
-cl-magick
-cl-markdown
-cl-match
-cl-mathstats
-cl-memcached
-cl-menusystem
-cl-migrations
-cl-monad-macros
-cl-mp3-parse
-cl-mpd
-cl-mpi
-cl-muproc
-cl-ncurses
-cl-neo4j
-cl-net-snmp
-cl-objc
-cl-octave
-cl-ode
-cl-opengl
-cl-openid
-cl-org-mode
-cl-pdf
-cl-peg
-cl-perec
-cl-plplot
-cl-plus-j
-cl-plus-ssl
-cl-pop
-cl-ppcre
-cl-prevalence
-cl-proc
-cl-quasi-quote
-cl-rdbms
-cl-rope
-cl-rundown
-cl-sbml
-cl-screen
-cl-selenium
-cl-semantic
-cl-serializer
-cl-smogames
-cl-smtp
-cl-snmp
-cl-soap
-cl-sockets
-cl-sqlite
-cl-stm
-cl-stomp
-cl-store
-cl-syntax-sugar
-cl-syslog
-cl-table
-cl-taint
-cl-telnetd
-cl-test-grid
-cl-trane
-cl-twitter
-cl-typesetting
-cl-unification
-cl-uri
-cl-utilities
-cl-variates
-cl-walker
-cl-wav-synth
-cl-wdim
-cl-weblocks
-cl-who
-cl-wiki
-cl-x86-asm
-cl-xml
-cl-xmlspam
-cl-xmms
-cl-xmpp
-cl-yacc-ebnf
-clTcl
-clappa
-clarity
-claw
-clazy
-clbuild
-cldoc
-cleric
-clfswm
-clget
-clhp
-cliki
-clim-desktop
-climacs
-climplayer
-clkd
-clnuplot
-clo
-clois-lane
-clonsigna
-closer
-closure
-clotnet
-clouchdb
-cloud
-clpython
-clsql-fluid
-clsql-mysql-introspect
-cltl3
-cmucl
-common-lisp-beginner
-common-math
-commonqt
-computed-class
-core-services
-corman-sdl
-cparse
-crypticl
-css-sexp
-cxml
-de-setf-amqp
-de-setf-graphics
-de.setf.amqp
-decl
-defclass-star
-defdoc
-defeditor
-definer
-defmud
-defplayer
-defwm
-docudown
-docutrack
-drakma
-dynamic-classes
-dyslexia
-eager-future
-ecl
-ecl-readline
-eclipse
-editor-hints
-elephant
-encline
-erlang-in-lisp
-erlisp
-external-program
-f2cl
-fetter
-fiveam
-flexi-streams
-flexichain
-fomus
-fret
-fset
-ftd
-fucc
-funds
-gamelib
-ganelon
-geco
-gecol
-geohash
-geometry
-gestalt
-ginseng
-glouton
-gnucard
-grand-prix
-graphic-forms
-gsharp
-gsll
-gtk-cffi
-gzip-stream
-ht-ajax
-html-template
-hyperdoc
-hyperspec-lookup
-iaxphone
-ieee-floats
-ieeefp-tests
-imago
-innen
-iolib
-ip-interfaces
-isidorus
-iso8601-date
-israel-lisp
-iterate
-iterate-clsql
-jess-parse
-jnil
-kpax
-l-math
-lambda-gtk
-langutils
-lgtk
-liards
-lifp
-lift
-limp
-lineal
-linedit
-lisp-interface-library
-lisp-matrix
-lisp-on-lines
-lisp-res-kit
-lispbox
-lispfaq
-lisplab
-lisppaste
-lispvirt
-lispy
-lmud
-local-time
-log4cl
-log5
-lost+found
-lw-vim-mode
-macho
-macondoolap
-magicffi
-mcclim
-mel-base
-meta-cvs
-metabang-bind
-metacopy
-metatilities
-metatilities-base
-mirror
-misc-extensions
-misrouted
-mit-cadr
-mk-defsystem
-mkcl
-mod-lisp
-modisc
-moptilities
-morphologie
-movies
-movitz
-named-readtables
-names-and-paths
-new-op
-nio
-nixies
-noctool
-nrw-xmcl
-nxtlisp
-objective-cl
-oct
-okra
-openair
-osicat
-pal
-parenscript
-parse-declarations
-patty
-pg
-pg-introspect
-phemlock
-phorplay
-plain-odbc
-plexippus-xpath
-ply
-portage-overlay
-postmodern
-pretty-function
-protobuf
-py-configparser
-python-on-lisp
-qitab
-quiz
-rcl
-rclg
-rdnzl
-rfc2109
-rfc2388
-rfc2822
-rjain-utils
-rucksack
-s-xml
-s-xml-rpc
-same
-sapaclisp
-sb-simd
-sequence-iterators
-sexpc
-sfip
-sheeple
-sicl
-simple-http
-slime
-snmp1
-snow
-sparklines
-spray
-sqlisp
-ssc
-stamp
-stdutil
-steeldump
-stefil
-suave
-submarine
-sudoku
-tbnl
-teepeedee2
-the-feebs-war
-tinaa
-tioga
-trivial-backtrace
-trivial-features
-trivial-freeimage
-trivial-garbage
-trivial-gray-streams
-trivial-http
-trivial-iconv
-trivial-shell
-trivial-timeout
-trivial-utf-8
-ubf
-ucs-sort
-ucw
-ucw-extras
-umpa-lumpa
-unetwork
-uri-template
-usocket
-vial
-vivace-graph
-wispylisp
-xcvb
-xhtmlambda
-xml-psychiatrist
-xmls
-xuriella
-yason
-zip
-zlib
- -

- -
+

+
diff --git a/content/project-intro.html b/content/project-intro.html index dfcbe38..afab543 100644 --- a/content/project-intro.html +++ b/content/project-intro.html @@ -1,231 +1,228 @@ ---- -title: Project Hosting ---- -
-

Contents:

- -
- -
-

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>-devel@common-lisp.net). 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 admin@common-lisp.net 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>-cvs@common-lisp.net). - It's easy to set up though. Simply go through the following steps:

-
    -
  1. Go to the project's landing page (not the group's), e.g. - SLIME's: https://gitlab.common-lisp.net/slime/slime
  2. -
  3. Click on "Settings" at the bottom of the left - menu bar
  4. -
  5. Click on "Services" in the next page
  6. -
  7. From the list of services in the resulting page, select - "E-mail on push"
  8. -
  9. Enter the recipients for push mails, including the - mailing list name of your project (i.e. <project-name>-cvs@common-lisp.net)
  10. -
- -

Subversion repository access

- -

Your 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.

- - -

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. - - -

Website

- -

/project/<project-name>/public_html is symlinked to +

+ +
+

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>-devel@common-lisp.net). 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 admin@common-lisp.net 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>-cvs@common-lisp.net). + It's easy to set up though. Simply go through the following steps:

+
    +
  1. Go to the project's landing page (not the group's), e.g. + SLIME's: https://gitlab.common-lisp.net/slime/slime
  2. +
  3. Click on "Settings" at the bottom of the left + menu bar
  4. +
  5. Click on "Services" in the next page
  6. +
  7. From the list of services in the resulting page, select + "E-mail on push"
  8. +
  9. Enter the recipients for push mails, including the + mailing list name of your project (i.e. <project-name>-cvs@common-lisp.net)
  10. +
+ +

Subversion repository access

+ +

Your 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.

+ + +

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. + + +

Website

+ +

/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 + 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.

-

+

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 + href="http://httpd.apache.org/docs/howto/ssi.html">Server-Side Includes are enabled. -

+

-

Automatic and manual mailinglists

+

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):

+

When your project is set up, three mailinglists are created (if you'd + rather use NNTP you can subscribe Gmane to your list):

-
    -
  • <project-name>-devel
  • -
  • <project-name>-announce
  • -
  • <project-name>-cvs
  • -
+
    +
  • <project-name>-devel
  • +
  • <project-name>-announce
  • +
  • <project-name>-cvs
  • +
-

You, the owner, are subscribed to all of these mailinglists +

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:

-
    -
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-devel
  • -
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-announce
  • -
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-cvs
  • -
+
    +
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-devel
  • +
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-announce
  • +
  • http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/<project-name>-cvs
  • +
+ +

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.

-

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.

+

Administrative requests

-

Administrative requests

- -

For adding/removing project members, additional mailing +

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 - 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>" -->

+

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 + 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>" -->

+ - -

Restoring from backup

+

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, +

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.

-

Auto-nagging

+

Auto-nagging

-

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, <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 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.

-

Trac

+

Trac

-

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. +

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 . -

+
diff --git a/content/tools.html b/content/tools.html index 457a63f..dff57f9 100644 --- a/content/tools.html +++ b/content/tools.html @@ -1,73 +1,58 @@ ---- -title: Tools ---- +

Trac

- -

Trac

- -

Click here to access Trac. - -

We are running Trac for projects who request it. It's a - fairly vanilla installation which resides in - /project/<project>/trac (on the filesystem) - and is writeable by the project administrator only. He/she may - choose to use trac-admin as per the documentation - to add milestones, components, etc. It's accessible through the web - as http://trac.common-lisp.net/<project> - -

The first thing you'll want to do after having logged in to your Trac - instance is to go to Settings and add your email address and - name. This will make your username show up in the Assign-To dropdown - list for tickets. +

The first thing you'll want to do after having logged in to your Trac + instance is to go to Settings and add your email address and + name. This will make your username show up in the Assign-To dropdown + list for tickets.

Permissions

Everyone with a common-lisp.net account has a Trac user and password, - it is stored in $HOME/trac-info.txt. Please see it for your username - and password. + it is stored in $HOME/trac-info.txt. Please see it for your username + and password.

Trac is configured such that anonymous users may not create or modify - the wiki (but may submit tickets) and authenticated users (ie. all - common-lisp.net users) can create or modify the wiki and submit tickets. - If you need to restrict this you can argue your case at - the clo-devel mailinglist or use trac-admin to change - it for your project. - -

Notifications

- -

Notifications are automatically sent to the <project>-ticket@common-lisp.net - mailinglist and Reply-To is set to the <project>-devel@common-lisp.net list. - If you want to change this you may change /project/<project>/trac/conf/trac.ini - to suit your needs. - - - - + the wiki (but may submit tickets) and authenticated users (ie. all + common-lisp.net users) can create or modify the wiki and submit tickets. + If you need to restrict this you can argue your case at + the clo-devel mailinglist or use trac-admin to change + it for your project. + +

Notifications

+ +

Notifications are automatically sent to the <project>-ticket@common-lisp.net + mailinglist and Reply-To is set to the <project>-devel@common-lisp.net list. + If you want to change this you may change /project/<project>/trac/conf/trac.ini + to suit your needs. + + + + diff --git a/content/tutorials.html b/content/tutorials.html index 96e1cbe..a6eaedf 100644 --- a/content/tutorials.html +++ b/content/tutorials.html @@ -1,27 +1,23 @@ ---- -title: Tutorials ---- -

Tutorials

Interested in learning Lisp? Here's some resources to help you get started.

diff --git a/globals.lisp b/globals.lisp index fd8a8a5..46fa4b8 100644 --- a/globals.lisp +++ b/globals.lisp @@ -37,8 +37,38 @@ (defparameter *PAGES-DIR* (asdf:system-relative-pathname :cl-site "content/") "Pathname for location of page content.") (defparameter *PRIVATE-KEYS* '(:slug :content)) + +;; Extra context for pages +(defparameter *PAGE-CONTEXT* + `(("about.html" ((:title . "Common-Lisp.net | About"))) + ("index.html" ((:title . "Welcome to Common-Lisp.net!"))) + ("faq.html" ((:title . "Frequently asked questions"))) + ("gitlab-migration-repository-mapping.html" ((:title . "GitLab migration"))) + ("gitlab-migration-status.html" ((:title . "Migration to GitLab"))) + ("independent-lists.html" ((:title . "Independent Mailing Lists"))) + ("orphaned-mailing-lists.html" ((:title . "Orphaned mailing lists"))) + ("orphaned-projects.html" ((:title . "Orphaned projects"))) + ("phub.html" ((:title . "Projects"))) + ("project-intro.html" ((:title . "Project Hosting"))))) + +(defun page-context (filename) + (cadr (assoc filename *page-context* :test 'equalp))) + +(defun page-title (filename) + (or (cdr (assoc :title (page-context filename))) + (format nil "Common-Lisp.net | ~a" + (string-capitalize + (pathname-name (pathname filename)))))) + (defparameter *PAGES* - (mapcar (lambda (p) (list (cons :content (file-namestring p)))) + (mapcar (lambda (p) + (let ((context + (append (list (cons :content (file-namestring p))) + (page-context (file-namestring p))))) + (when (not (assoc :title context)) + (push (cons :title (page-title (file-namestring p))) + context)) + context)) (directory (make-pathname :defaults *PAGES-DIR* :name :wild :type "html"))) @@ -46,4 +76,4 @@ ;; Initialize global context (will be appended to all individual page contexts) ;; Used to store things like stylesheets, etc... -(defparameter *GLOBAL-CONTEXT* ()) \ No newline at end of file +(defparameter *GLOBAL-CONTEXT* ()) diff --git a/output/placeholder b/output/placeholder deleted file mode 100644 index e69de29..0000000 diff --git a/process.lisp b/process.lisp index 6cbac8f..fb85863 100644 --- a/process.lisp +++ b/process.lisp @@ -35,6 +35,8 @@ (push (cons :static static-list) *GLOBAL-CONTEXT*))) ;; process-pages : Copies/renders pages - called last + + (defun render-page (page template-path) (let* ((page-path (make-path *PAGES-DIR* page t)) @@ -54,4 +56,5 @@ ((template-path (pathname (merge-pathnames *LAYOUT-DIR* *DEFAULT-PAGE-TEMPLATE*)))) (progn (ensure-directories-exist *OUTPUT-DIR*) (loop for page in *PAGES* - do (render-page page template-path))))) + do + (render-page page template-path))))) -- 2.22.0