news.html 17.3 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363
<div id="bodyText">
    <h2>Latest news</h2>


    <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="https://gitlab.com/gitlab-org/gitlab-ce/blob/v7.11.1/CHANGELOG">GitLab 7.11.1.</a></p>


    <h3 id="2015_05_15">2015-05-15</h3>
    <p>Proposed approach for <a
                                 href="https://mailman-test.common-lisp.net/pipermail/clo-devel/2015-May/001051.html"
                             >Darcs repository migration</a> sent out.</p>


    <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>
    <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="https://mailman.common-lisp.net/listinfo/clo-devel"
            >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>
    <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 id="2015_04_27">2015-04-27</h3>
    <p>GitLab project fixes issues reported by common-lisp.net admin:
        <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/1478">loading
            of commit data</a>.
    </p>

    <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>
    <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 id="2015_04_22">2015-04-22</h3>
    <p>GitLab has been upgraded to 7.10.0; <a
                                               href="https://gitlab.com/gitlab-org/gitlab-ce/issues/1408">one
        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>

    <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 id="2015_04_17">2015-04-17</h3>
    <p><a href="https://gitlab.common-lisp.net/">GitLab</a> upgraded to
        <a href="https://about.gitlab.com/2015/04/15/gitlab-7-dot-9-4-released/">7.9.4</a>
    </p>

    <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
                                                         href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-April/001035.html"
                                                     >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="https://gitlab.common-lisp.net/">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="https://trac.common-lisp.net/clo/newticket">file
        a ticket in the site's Trac instance</a>.
    </p>


    <h3 id="2015_04_08">2015-04-08</h3>
    <p>Due to a variety of reasons, the history of the mailing lists
        of common-lisp.net 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="https://mailman.common-lisp.net/pipermail">the online
            archive</a></p>

    <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="http://doc.gitlab.com/ce/workflow/import_projects_from_github.html">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="http://doc.gitlab.com/ce/integration/omniauth.html#enable-omniauth-for-an-existing-user">GitLab omniauth for existing
        users documentation</a>.
    </p>


    <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="https://github.com/gitlabhq/gitlabhq/blob/v7.9.0/CHANGELOG">large number of fixes and enhancements</a>.
    </p>


    <h3 id="2015_03_20">2015-03-20</h3>
    <p>Our self-hosted git repository management environment
        <a href="https://gitlab.common-lisp.net/">gitlab.common-lisp.net</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="https://mailman.common-lisp.net/pipermail/clo-devel/2015-March/000972.html">announced</a> for the final
        migration of all git repositories to GitLab: Friday March 20th!
    </p>


    <h3 id="2015_03_08">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 id="2015_02_19">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="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000941.html"
                                                                          >the original announcement e-mail for details</a>.
    </p>

    <p>In summary, there are two changes being implemented:</p>
    <ol>
        <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>
    </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 id="2015_02_10">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 id="2015_02_08">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 id="2015_02_06">2015-02-06</h3>
    <p>
        Erik Huelsmann -one of the common-lisp.net maintainers- has submitted
        a proposal for the nearby future of the site.  Read <a
                                                                href="https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.html">the details in his mail</a> to the
        <a href="https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel">clo-devel mailing list</a> in the archive.  Feedback is very much
        appreciated.
    </p>

    <h3 id="2015_02_01">2015-02-01</h3>
    <p>
        The (www.)common-lisp.net 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
                                      href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo
                                            /clo-devel">mailing
364
        list</a>!
365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417
    </p>

    <h3 id="2015_01_30">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="http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme"
                                      >SRS</a></abbr> when the sender domain specifies an
        <a href="http://en.wikipedia.org/wiki/Sender_Policy_Framework"><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 common-lisp.net domain at Google</li>
    </ul>
    <p>Google considers common-lisp.net a Bulk Sender, which means
        we must abide by <a href="https://support.google.com/mail/answer/81126?hl=en">a number of requirements to make sure mail gets accepted</a>.
    </p>
    <p>Some of the stricter criteria to accept mail on common-lisp.net are:
    </p>
    <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
            common-lisp.net 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 common-lisp.net'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
            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.</dd>
    </dl>

    <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
        <a
            href="http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel">let
            us know.</a></p>

    <p>You can also help us by <a href="/contribute/">donating</a>.</p>

</div>