Commit 46d1d033 authored by Erik Huelsmann's avatar Erik Huelsmann

Remove unused news.html page

parent d69cef4f
Pipeline #468 passed with stage
in 3 seconds
<div id="bodyText">
<h1>Latest news</h1>
<h3 id="2015_05_25">2015-05-25</h3>
<p>Today the system has been declared &quot;CVS clean&quot;! All
remnants of CVS have been removed.</p>
<h3 id="2015_05_23">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 id="2015_05_22">2015-05-22</h3>
<p>GitLab upgraded to <a href="">GitLab 7.11.1.</a></p>
<h3 id="2015_05_15">2015-05-15</h3>
<p>Proposed approach for <a
>Darcs repository migration</a> sent out.</p>
<h3 id="2015_05_12">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>
<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 id="2015_05_03">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>
<h3 id="2015_04_27">2015-04-27</h3>
<p>GitLab project fixes issues reported by admin:
<a href="">loading
of commit data</a>.
<h3 id="2015_04_26">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>
<h3 id="2015_04_22">2015-04-22</h3>
<p>GitLab has been upgraded to 7.10.0; <a
of the tickets we filed with the GitLab project</a>, has been
resolved now.</p>
<h3 id="2015_04_19">2015-04-19</h3>
<p>Migration of CVS repositories to Git+GitLab has started. The
first batch (10 projects) was converted:
<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! :-)
<h3 id="2015_04_17">2015-04-17</h3>
<p><a href="">GitLab</a> upgraded to
<a href="">7.9.4</a>
<h3 id="2015_04_11">2015-04-11</h3>
<p>The first projects with CVS repositories have received e-mails
about the planned migration according to the <a
>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>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>If you want to declare that your project wants to migrate to
Subversion without awaiting your announcement e-mail, please <a
a ticket in the site's Trac instance</a>.
<h3 id="2015_04_08">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>
<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>
<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>Now, this long-overdue task has finally been completed. The
mailing list history can be browsed and indexed again from
<a href="">the online
<h3 id="2015_03_27">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>.
<h3 id="2015_03_24">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>.
<h3 id="2015_03_20">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 id="2015_03_24">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!
<h3 id="2015_03_08">2015-03-08</h3>
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>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.
<h3 id="2015_02_19">2015-02-19</h3>
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
>the original announcement e-mail for details</a>.
<p>In summary, there are two changes being implemented:</p>
<li>Subject prefix '[&lt;mailing-list&gt;]' 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>
<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.
<h3 id="2015_02_10">2015-02-10</h3>
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.
<h3 id="2015_02_08">2015-02-08</h3>
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 <a href="#2015_02_06"
>new and simplified configuration</a>.
<h3 id="2015_02_06">2015-02-06</h3>
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
<h3 id="2015_02_01">2015-02-01</h3>
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 <a
<h3 id="2015_01_30">2015-01-30</h3>
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:
<li>too many spam mails entering the moderation queues</li>
<li>improved reputation of the domain at Google</li>
<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>Some of the stricter criteria to accept mail on are:
<dl style="margin-left: 3em">
<dt>Mail failing SPF validation is no longer accepted</dt>
<dd>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></dd>
<dt>Mail failing DKIM validation is no longer accepted</dt>
<dd>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.</dd>
<dt>A series of requirements on the host submitting mail</dt>
<dd>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.</dd>
<h3 id="2014_09_22">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
us know.</a></p>
<p>You can also help us by <a href="/contribute/">donating</a>.</p>
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