[Clo-devel] Follow up to "proposed direction for common-lisp.net in 2015" -- the steps

Chun Tian (binghe) binghe.lisp at gmail.com
Fri Feb 13 20:07:51 UTC 2015

Hey guys,

I know I “disappeared" for a long time and I’m not an important one, but I have one suggestion here. If I’m wrong or you don’t like it, please don’t blame me:

We should move all responsibilities to Github (or sourceForge if SVN or CVS is still required by some projects), and then ONLY use common-lisp.net for project web site hosting (project web pages, and file downloads for users who don’t use quicklisp) , because the hostname (common-lisp.net) is still the best choice for Common Lisp related projects.


Chun Tian (binghe)

Il giorno 13/feb/2015, alle ore 17:23, Raymond Toy <toy.raymond at gmail.com> ha scritto:

>>>>>> "Erik" == Erik Huelsmann <ehuels at gmail.com> writes:
>    Erik> Hi everybody,
> Hmm. Is this some kind of Friday the 13th joke? :-)
> These plans seem awfully ambitious, but I look forward to them.
>    Erik> 0. Install a Code Commenting plugin on Trac to make it match
>    Erik>    the GitLab code commenting capabilities
> Is this step necessary?  We haven't had one thus far, and it seems
> that gitlab is the way to go, so adding functionality to Trac is just
> more work.
> Depending on the difficulty, I think I would rather just migrate all
> of my Trac stuff to gitlab instead of trying to make Trac work with
> gitlab in some fashion.  (Unless gitlab and Trac already have some
> kind of integration.)
> In any case, I'm excited about these changes.
> --
> Ray
> _______________________________________________
> Clo-devel mailing list
> Clo-devel at common-lisp.net
> https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel

More information about the clo-devel mailing list