Commit 821b70e4 authored by Dave Cooper's avatar Dave Cooper
Browse files

trying to merge the reduction in globals merge from Erik

parents 432f0639 8ce18015
......@@ -9,4 +9,5 @@ auto-save-list
\ No newline at end of file
title: Frequently asked questions
<h1><i class="far fa-question-circle"></i>&nbsp;FAQ - Frequently Asked Questions</h1>
title: GitLab migration
<main id="bodyText">
<header id="summary">
title: Migration to GitLab
<h2> migration to GitLab: status</h2>
title: Independent Mailing Lists
<div id="bodyText">
<h1>Independent Mailing Lists</h1>
<h2 id="apply">How to apply</h2>
title: Welcome to!
<main id="bodyText">
<a class="btn btn-primary float-right" href="/downloads"><i class="fa fa-arrow-right"></i>&nbsp;&nbsp;Get started</a>
<h1>Welcome to</h1>
placeholder until we support detecting *.md files as page sources.
\ No newline at end of file
<div id="bodyText"><a class="btn btn-secondary float-right" href=""><i class="far fa-edit"></i>&nbsp;Edit this page</a><h1>Latest news</h1><h3>2018-10-12 <em>Intent to remove unused projects</em></h3><p>As per <a href="">the announcement</a>, the site admins plan to remove the following list of projects which have been determined to neither have a project page nor a code repository. Please contact the site admins before October 26, 2018 to cancel project cleanup in case your project is wrongfully listed. </p><ul><li>arxana</li><li>asdf-install</li><li>asdf-packaging</li><li>boston-lisp</li><li>chemboy</li><li>cl-amqp</li><li>cl-buchberger</li><li>cl-cactus-kev</li><li>cl-captcha</li><li>cl-clickatell</li><li>cl-gdbm</li><li>cl-gtk2</li><li>clint</li><li>cl-lazy-list</li><li>cl-lexer</li><li>cl-match</li><li>cl-ode</li><li>clotnet</li><li>cl-peg</li><li>cl-player</li><li>cl-rundown</li><li>cltl3</li><li>cl-yacc-ebnf</li><li>decl</li><li>defmud</li><li>docutrack</li><li>innen</li><li>israel-lisp</li><li>jess-parse</li><li>lisp-interface-library</li><li>mk-defsystem</li><li>movies</li><li>objective-cl</li><li>phorplay</li><li>same</li><li>sqlisp</li><li>tioga</li><li>trivial-features</li><li>trivial-shell</li><li>ucs-sort</li><li>umpa-lumpa</li><li>xml-psychiatrist</li></ul><h3>2018-10-12</h3><p>Today I found some time to enable GitLab's 'reply by e-mail' functionality. </p><p>When you receive a notification e-mail from our GitLab instance, you can now send a reply to that notification. If the notification was from an issue being updated, then your reply will update the issue with a follow-up commont. </p><h3>2018-10-10</h3><p>A new version of has been launched! </p><p>Among other things, the new site features: </p><ul><li>A site generator implemented in Common Lisp.</li><li>A gitlab pipeline for automatic deployment.</li><li>A new responsive design based on Bootstrap and new content.</li></ul><h3>2018-10-06</h3><p>As per <a href="">the announcement in August</a>, the list of users with O/S level access has been cleaned up: those accounts which haven't been accessed since 2013 (and for which the owner didn't object to removal), have been removed. Home directories will be destructed to comply with GDPR regulations. </p><p>If you once had an account and you need your access restored, please contact our admins. </p><h3>2018-02-17</h3><p>The Darcs (a distributed version control system before Git) repositories listed in our darcsweb instance have been converted to <a href="">our GitLab instance</a>. All use of Darcs on our site has been marked deprecated for a long time and we're happy to have found a way forward, keeping the repository content available to more modern VCSes. </p><h3>2017-07-15</h3><p>Our server was upgraded to Stretch as part of the regular life cycle management. See <a href="">our announcement</a>. </p><h3>2015-05-25</h3><p>Today the system has been declared "CVS clean"! All remnants of CVS have been removed. </p><h3>2015-05-23</h3><p>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! </p><h3>2015-05-22</h3><p>GitLab upgraded to <a href="">GitLab 7.11.1.</a> </p><h3>2015-05-15</h3><p>Proposed approach for <a href="">Darcs repository migration</a> sent out. </p><h3>2015-05-12</h3><p>The final batch of CVS projects has been migrated. None of the projects opted to move to Subversion, so all of them were migrated to Git+GitLab: </p><ul><li>gamelib</li><li>ganelon</li><li>geometry</li><li>ginseng</li><li>glouton</li><li>gsharp</li><li>gtk-cffi</li><li>html-template</li><li>hyperdoc</li><li>hyperspec-lookup</li><li>ieeefp-tests</li><li>imago</li><li>iso8601-date</li><li>jnil</li><li>lambda-gtk</li><li>lgtk</li><li>lispfaq</li><li>lispy</li><li>lmud</li><li>log4cl</li><li>mcclim</li><li>meta-cvs</li><li>misc-extensions</li><li>morphologie</li><li>movitz</li><li>nio</li><li>noctool</li><li>pal</li><li>pg</li><li>phemlock</li><li>plain-odbc</li><li>rfc2388</li><li>rfc2822</li><li>rjain-utils</li><li>rucksack</li><li>sapaclisp</li><li>sb-simd</li><li>snmp1</li><li>spray</li><li>stamp</li><li>s-xml</li><li>s-xml-rpc</li><li>trivial-freeimage</li><li>unetwork</li><li>zip</li><li>zlib</li></ul><p>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 <a href="">clo-devel mailing list</a>. </p><h3>2015-05-03</h3><p>The next batch of CVS projects has been migrated. None of the projects opted to move to Subversion, so all of them were migrated to Git+GitLab: </p><ul><li>cl-magick</li><li>cl-menusystem</li><li>cl-mp3-parse</li><li>closure</li><li>clouchdb</li><li>cl-plus-ssl</li><li>cl-ppcre</li><li>cl-prevalence</li><li>cl-rope</li><li>cl-sbml</li><li>cl-screen</li><li>cl-selenium</li><li>cl-semantic</li><li>cl-smogames</li><li>cl-smtp</li><li>cl-snmp</li><li>cl-soap</li><li>cl-store</li><li>cl-syslog</li><li>cl-telnetd</li><li>cl-utilities</li><li>cl-wav-synth</li><li>cl-who</li><li>cl-x86-asm</li><li>cl-xmms</li><li>cl-xmpp</li><li>corman-sdl</li><li>cparse</li><li>crypticl</li><li>cxml</li><li>defdoc</li><li>defeditor</li><li>definer</li><li>defplayer</li><li>defwm</li><li>eclipse</li><li>elephant</li><li>fetter</li><li>flexichain</li><li>fomus</li></ul><h3>2015-04-27</h3><p>GitLab project fixes issues reported by admin: <a href="">loading of commit data</a>. </p><h3>2015-04-26</h3><p>The next batch of CVS projects has been migrated. None of the projects opted to move to Subversion, so all of them were migrated to Git+GitLab: </p><ul><li>cinline</li><li>cl-blog</li><li>cl-carbon</li><li>cl-cli-parser</li><li>cl-cracklib</li><li>cl-dbf</li><li>cldoc</li><li>cl-enumeration</li><li>cl-fltk</li><li>cl-godb</li><li>cl-gsl</li><li>climacs</li><li>clim-desktop</li><li>cl-interpol</li><li>cl-ipc</li><li>cl-jpeg</li><li>cl-libtai</li></ul><h3>2015-04-22</h3><p>GitLab has been upgraded to 7.10.0; <a href="">one of the tickets we filed with the GitLab project</a>, has been resolved now. </p><h3>2015-04-19</h3><p>Migration of CVS repositories to Git+GitLab has started. The first batch (10 projects) was converted: </p><ul><li>anaphora</li><li>aspiwork-pdm</li><li>bayescl</li><li>beep</li><li>beirc</li><li>bese</li><li>cello</li><li>cells</li><li>cells-gtk</li><li>cells-ode</li></ul><p>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! :-) </p><h3>2015-04-17</h3><p><a href="">GitLab</a> upgraded to <a href="">7.9.4</a> </p><h3>2015-04-11</h3><p>The first projects with CVS repositories have received e-mails about the planned migration according to the <a href="">proposed procedure</a>. 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! </p><p>The announcement e-mail requires action <em>if you want to migrate to Subversion instead of to Git</em>. If you want to migrate to Git+<a href="">GitLab</a>, there's no need to respond. It's the default. </p><p>If you want to declare that your project wants to migrate to Subversion without awaiting your announcement e-mail, please <a href="">file a ticket in the site's Trac instance</a>. </p><h3>2015-04-08</h3><p>Due to a variety of reasons, the history of the mailing lists of had spread over a number of sources: </p><ul><li>the older system's mailman list manager's history (mbox format)</li><li>the intermediately used mlmmj list manager's history (spool directory, individual mails)</li><li>the new system's mailman list manager's history (mbox format)</li></ul><p>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. </p><p>Now, this long-overdue task has finally been completed. The mailing list history can be browsed and indexed again from <a href="">the online archive</a> </p><h3>2015-03-27</h3><p>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 <a href="">gitlab documentation for the github import workflow</a>. </p><p>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. </p><p>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 <em>only</em> 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 <a href="">GitLab omniauth for existing users documentation</a>. </p><h3>2015-03-24</h3><p>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 <a href="">large number of fixes and enhancements</a>. </p><h3>2015-03-20</h3><p>Our self-hosted git repository management environment <a href=""></a> is now live! During the deployment, the system was seeded with 390 users, 434 groups and 210 repositories. </p><p>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. </p><p>If you experience any issues, please report to the site admins. </p><p>We hope you enjoy the new user experience! </p><h3>2015-03-16</h3><p>Today the date has been <a href="">announced</a> for the final migration of all git repositories to GitLab: Friday March 20th! </p><h3>2015-03-08</h3><p>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. </p><p>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. </p><p>We're sorry for any inconvenience caused. </p><h3>2015-02-19</h3><p>The site admins have announced a change in policies for the mailing lists to be in effect as of March 15th, 2015. Please read <a href="">the original announcement e-mail for details</a>. </p><p>In summary, there are two changes being implemented: </p><ol><li>Subject prefix '[<mailing-list> ]' won't be added anymore. </li><li>Moderation requests won't be held indefinitely anymore, defaulting to a hold period of 90 days (expiring the unmoderated e-mail when unhandled). </li></ol><p>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!. </p><p>The later addresses the fact that the moderation queue is growing indefinitely, with most lists set to never expire moderation requests. </p><h3>2015-02-10</h3><p>The site admins identified <a href="/orphaned-mailing-lists/">a list of mailing lists for which contact with the list owner has been lost</a> list for your favorite list or your name. </p><h3>2015-02-08</h3><p>Due to a failed system upgrade, the system experienced extended downtime on Sunday. Our apologies for any inconvenience. </p><p>The maintenance was completed successfully around 18.00 UTC and is a step towards easier maintainance for the system and support the development of <a href="#2015_02_06">new and simplified configuration</a>. </p><h3>2015-02-06</h3><p>Erik Huelsmann -one of the maintainers- has submitted a proposal for the nearby future of the site. Read <a href="">the details in his mail</a> to the <a href="">clo-devel mailing list</a> in the archive. Feedback is very much appreciated. </p><h3>2015-02-01</h3><p>The (www.) domain has started using the <em>https</em> 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]( /clo-devel)! </p><h3>2015-01-30</h3><p>The mail system's criteria for accepting mail have been tightened and mail forwarding now uses <abbr title="Sender rewriting scheme"><a href="">SRS</a></abbr> when the sender domain specifies an <a href=""><abbr title="Sender Policy Framework">SPF</abbr> policy</a>. The changes address these issues: </p><ul><li>too many spam mails entering the moderation queues</li><li>improved reputation of the domain at Google</li></ul><p>Google considers a Bulk Sender, which means we must abide by <a href="">a number of requirements to make sure mail gets accepted</a>. </p><p>Some of the stricter criteria to accept mail on are: </p><p>Mail failing SPF validation is no longer accepted. </p><p>Due to the SRS rewriting, these mails would leave as legitimate mail. By rejecting these mails, we honor the policy stated by the sender domain.<br />
<em>Note: We're currently not rejecting soft-failing mails.</em> </p><p>Mail failing DKIM validation is no longer accepted </p><p>Forwarding mail which fails DKIM validation reflects poorly on's reputation as a mail host. By rejecting mail failing DKIM validation, we honor the policy stated by the sender domain. </p><p>A series of requirements on the host submitting mail </p><p>By enforcing a number of requirements on the DNS configuration and protocol conformity of the hosts submitting mail to, we enforce the same requirements that Google and other mail hosters enforce on us, can't be used as a hub by spammers to increase legitemacy of the mail flow. Nor can accidental forwarding of spam mail hurt's reputation with the large mail hosters. </p><h3>2014-09-22</h3><p>Hello everybody. The site moved to a shiny new server a few moments ago. Everything should work, and if it doesn't, please <a href="">let us know.</a> </p><p>You can also help us by <a href="/contribute/">donating</a>. </p></div>
\ No newline at end of file
title: Orphaned mailing lists
<div id="bodyText">
<h2 id="intro">Introduction</h2>
title: Orphaned projects
<h1>Orphaned Projects</h1>
<div id="bodyText">
<h2 id="intro">Introduction</h2>
title: Projects
<a style="clear:both;" class="btn btn-primary float-right" href="/project-intro"><i class="fa fa-arrow-right"></i>&nbsp;&nbsp;Projects Hosting</a>
<div id="bodyText">
<h1 style="padding-bottom: 30px;"><i class="fa fa-project-diagram"></i>&nbsp; projects</h1>
title: Project Hosting
<a style="clear:both;" class="btn btn-primary float-right" href="/phub"><i class="fa fa-arrow-right"></i>&nbsp;&nbsp; projects</a>
<div style="clear:both;margin-top: 20px;" class="tocbox">
......@@ -23,37 +23,11 @@
"Pathname for location of page content.")
(defparameter *PRIVATE-KEYS* '(:slug :content))
;; Extra context for pages
(defparameter *PAGE-CONTEXT*
`(("about.html" ((:title . " | About")))
("index.html" ((:title . "Welcome to!")))
("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 " | ~a"
(pathname-name (pathname filename))))))
(defparameter *PAGES*
(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)))
(list (cons :content (file-namestring p))
(cons :title (file-namestring p))))
(directory (make-pathname :defaults *PAGES-DIR*
:name :wild
:type "html")))
;;;; -*- Mode: Lisp; Syntax: ANSI-Common-Lisp; Base: 10 -*-
(in-package :cl-site)
(defun split-content-from-header (path)
"Returns two values; the header and the content"
(with-open-file (f path :direction :input)
(let ((header-lines
(loop for line = (read-line f nil)
unless line do (return-from split-content-from-header
(values nil lines))
when (string= line "---") return lines
collect line into lines)))
(loop for line = (read-line f nil)
collect line into lines
unless line
return (values header-lines lines)))))
;; Copies/renders static assets (imgs, etc)
(defun process-static ()
(let ((destination-root (merge-pathnames #P"static/" *output-dir*))
......@@ -20,22 +35,24 @@
(defun render-page (page template-path)
((page-path (make-path *PAGES-DIR* page t))
(output-path (make-path *OUTPUT-DIR* page t))
(page-content (let ((mustache:*load-path* (cons *PAGES-DIR* mustache:*load-path*))
(mustache:*default-pathname-type* "html"))
(mustache:render* page-path)))
(page-context (remove-if (lambda (p) (find p *PRIVATE-KEYS*))
(push (cons :page-content page-content) page) :key 'car)))
(with-open-file (output-stream output-path
:direction :output
:if-exists :supersede)
(let ((mustache:*load-path* (cons *PAGES-DIR* mustache:*load-path*))
(mustache:*default-pathname-type* "html"))
(mustache:render template-path (append page-context *GLOBAL-CONTEXT*)
(let ((page-path (make-path *PAGES-DIR* page t))
(output-path (make-path *OUTPUT-DIR* page t)))
(header content)
(split-content-from-header page-path)
(let* ((header-text (format nil "~{~A~%~}" header))
(content-text (format nil "~{~A~%~}" content))
(parsed-header (yaml:parse header-text))
(when parsed-header
(loop for k being each hash-key of parsed-header
using (hash-value v)
collect (cons k v)))))
(with-open-file (output-stream output-path
:direction :output
:if-exists :supersede)
(mustache:render template-path (append (acons :page-content content-text page-context) *GLOBAL-CONTEXT*)
(defun process-pages (pages)
(format t "Processing pages...~%")
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment