Re: [MirageOS-devel] Canopy and Liveblogging

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 19 Oct 2016, at 11:46, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
> 
> On 19/10/2016 10:13, Anil Madhavapeddy wrote:
>>> On Wed, Oct 19, 2016, 5:32 PM Gemma Gordon <gg417@xxxxxxxxxxxx> wrote:
>> I've also got a slightly rushed PR of the various changes that went into the 
>> ICFP 2016 Canopy deployment here, including Mirage3 API support:
>> https://github.com/Engil/Canopy/pull/62
> 
> Since there are several instances running Canopy with MirageOS2 (and no
> releases of Canopy), I'd take the same approach as e.g.
> ocaml-git/mirage-skeleton: master works with opam repo released
> software, a mirage-dev branch works with MirageOS3.  Your PR includes
> cosmetic changes (which should be a separate PR, to be merged into
> master), some workarounds (git / "temporary" CSS fix -- which should be
> properly fixed), and Mirage3 support (which should target mirage-dev).
> If you cleanup that PR, I'm happy to have the individual bits merged.

Yeah, agreed. I've actually got a separate library that does very simple
processing of Jekyll-style files (which Canopy also uses). I'll publish that
separately in OPAM and then send a PR to make Canopy use it. I'm using
that other library in the rewrite of my personal blog.

>>> I also made a few small changes to the mirage-canopy site to cover the 
>>> Docker summit: http://canopy.mirage.io/Liveblogand wrote summaries of each 
>>> talk plus Q&As. The focus of the summit was distributed systems, and much 
>>> of the work featured was open-source, OCaml-related, or relevant to Mirage 
>>> e.g. the TUF Framework: http://canopy.mirage.io/Liveblog/TUFDDS2016
> 
> I am slightly confused what the intended layout is - the Liveblog now
> contains a chunk of not-really-Mirage/OCaml related posts without any
> indication why they are there (such as an event name).  It seems like it
> needs another iteration on the intended structure, maybe even with more
> code support (such as nested directories, having those in
> /liveblog/dockersummit/<entry> would be much more intuitive, at least
> for me).

The current structure is the result of bugs in nested directory handling
discovered at the nth minute at ICFP and DDS :-) I'd probably just annotate
the URLs with an explanation of the event in the index page rather than
move them around, since they've been linked to now in external posts
and communication.

-anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel