<yomimono>
We're a bit shorthanded both because of the late announcement, and because many people are traveling today or have just arrived at the hack retreat, so I expect it to be a short catchup :)
<yomimono>
first on the agenda -- this is our first catchup since MirageOS 3 was released on Thursday of last week :D
<amirmc>
Yay!
<yomimono>
as perhaps you have seen from the shiny new /topic !
<yomimono>
thanks a ton, amirmc, for doing the coordination and press work :)
<amirmc>
I'm glad it landed in time. :)
avsm has joined #mirage
<yomimono>
we have a few folks going through the new tutorial & building their first Mirage 3 unikernels at the hack retreat :D I expect lots of issues and PRs
<avsm>
hello! Sounds like network connectivity is great at the retreat :-)
gemmag has joined #mirage
<yomimono>
errrrrrrr
<yomimono>
wellllllll
<yomimono>
not exactly ;)
<yomimono>
but good enough, maybe!
<yomimono>
I put an agenda item for hack retreat discussion on the end of the agenda, but the only other item is Irmin 1.0 (yay!)
<yomimono>
I don't see samoht here, so I can't congratulate/thank him :(
<amirmc>
I added an item, which we can cover before or after the hack retreat
thomasga has joined #mirage
mort___ has joined #mirage
<thomasga>
Bonjour!
<avsm>
Speak of the unicolonel, and he arrives!
<mort___>
.
<yomimono>
bonjour, monsieur!
<yomimono>
thomasga: I put an agenda item up for Irmin 1.0 - congratulations & thank you :)
<thomasga>
Thanks :-)
<avsm>
Yes! A huge milestone :-) Also interesting to see KC's ezirmin layer
<thomasga>
I am writing a blog post, I have an early draft available somewhere
<avsm>
he told me he's going to port it to Irmin 1.0 soon, and he has a bunch of notes on the API that he will mail to the miragos-devel list soon
<thomasga>
I am looking for a better running example than "distributed metric collection"
<thomasga>
avsm: great!
<thomasga>
hopefully he likes it better than the pre-1.0 API
<thomasga>
anyone using the new API is welcome to send some feedback. I am pretty ok (and happy) to make a quick 1.1 release with the feedback if needed.
<avsm>
yeah, but he ran into a few issues when setting up a large distributed cluster
<avsm>
so I guess post-1.0 Irmin will be the multi-host modes :-)
<thomasga>
yup, the "distributed" part is not as well tested than the rest
<thomasga>
I am really looking forward having a Git server implementation
<thomasga>
so we can sort all of this out more easily
<thomasga>
Fortunately dinosaure is making a lot of progress :-)
djwillia` has joined #mirage
<yomimono>
:D
<yomimono>
he is hacking hard RIGHT NOW.
<avsm>
glad to hear it :-)
<yomimono>
everyone OK to move on?
* yomimono
waits for latency bar to drop to 0
<avsm>
+1
ricarkol has joined #mirage
<yomimono>
must be fine! next item is the hack retreat - a bunch of us are here. afaik there's not a dedicated canopy instance like we had last time, but we can try to get one with the mirage 3 patches
<yomimono>
a bunch of rad T-shirts just arrived - thanks gemma! :D
<yomimono>
thanks again to hannes for organizing. :)
<yomimono>
I am done talking now!
<avsm>
Would the existing Canopy not work?
<avsm>
Or do you need a local one due to latency?
<amirmc>
More t-shirts arriving on Friday
<yomimono>
Is the existing one running Mirage3 + Irmin1?
<avsm>
It would be great if you could capture the early user experiences -- feel free to dump them into emails to me if there's nowhere else to put them :-)
<amirmc>
Existing canopy probably isn't on Mirage3 yet
<avsm>
Also: if anyone wants to test `opam2 build` that would be awesome
<avsm>
yomimono: amirmc: its still on mirage too, but its the live one
<avsm>
you should be able to git clone the repo and merge all your stuff in there, and push to live mirage/canopy-data whenever you have net
<amirmc>
Support was added though (by thomasga)
<yomimono>
Sounds good :D
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<amirmc>
Last item on the agenda is blog posts.
<amirmc>
i.e. who can write some and by when :)
<amirmc>
So far we've had content by Hannes, Mindy, and Thomas. Is there anyone else who can write up something related to Mirage 3?
<avsm>
I'm working on documenting the CI at the moment so I can hand it off to more people :)
<avsm>
so could be a spinoff post about how that works on mirage.io, but am focussing on actual docs content
<amirmc>
avsm: docs first makes sense but can we commit to a date for a post? Otherwise this might get forgotten. I tried to make a schedule but it's pretty thin (https://github.com/mirage/mirage-www/issues/513)
<avsm>
I can't commit at the moment sadly -- but I'll update the issue when I make progress. I've got a stack of infrastructure work (like fixing up docs.mirage.io) that takes priority at the moment
<avsm>
Would be great to see more articles from the newcomers though -- anyone at the retreat who'd be willing to narrate their projects?
<amirmc>
If there's anyone else who has things they can write up, please do post on that issue.
<amirmc>
Happy to help copy/edit with enough notice (i.e. couple of days).
<avsm>
thanks! I'm on a campaign to document the project infrastructure :-)
<avsm>
yomimono: the more i think about it, the more a clone of mirage/canopy-data makes sense
<avsm>
you dont need an actual live copy of canopy running there
<yomimono>
no, what I'm proposing is port canopy to mirage3 + irmin1, host that somewhere else
<amirmc>
You should only need to push git logs, right? Unless I misunderstood how canopy works.
<yomimono>
the net is fine for stuff like git push/git pull
<yomimono>
it's just not great for realtime stuff
<avsm>
ah i see -- do you have a machine you can host a git server on?
<avsm>
sorry, a canopy/mirage server
<yomimono>
can repurpose an aws instance
<avsm>
(since you can use the live github.com/mirage/canopy-data for the content)