Firstly, that was an incredible hackathon in Morocco -- the Canopy posts on http://canopy.mirage.io <http://canopy.mirage.io/> with the daily hacklist were great, and I greatly enjoyed merging all the new libraries into OPAM repository :-)
It looks like tomorrow's video call is going to be tricky since many people are double booked due to the California <-> UK timezone shift that leaves us a mere 7 hours adrift. So for tomorrow, we're going to try an experimental meeting format: - Everyone push any updates you have to Canopy as a brief paragraph or two. Mine is up at http://canopy.mirage.io/Posts/Bulk-build <http://canopy.mirage.io/Posts/Bulk-build> for example - You can do this push by: - Fork https://github.com/hannesm/canopy-data <https://github.com/hannesm/canopy-data> to your own Github - Write a brief paragraph in Posts/, e.g. like https://github.com/hannesm/canopy-data/pull/3/files <https://github.com/hannesm/canopy-data/pull/3/files> for mine - Send a PR to canopy-data and merge it yourself if you have access - We gather in #mirage in Freenode IRC at 4pm GMT tomorrow (Wednesday) and have a quick sync up chat online, and the results are also written into Canopy. - If there are things that require a video call, we can schedule a smaller group to go through it later. This is still an experiment, but the Canopy model is really encouraging -- we can push ongoing progress to a git repository and have it appear on the website nice and fast. It's also self-hosted using Mirage, which is a big deal to push us forward into using our own infrastructure. We'll need to keep refining Canopy to make it work for us. I was wondering about a few things Enguerrand/Thomas: - how do we date posts? Is it just the commit date at the moment? - should we add tags, or is that just the subdirectory in canopy-data? - whats remaining to get it working as a Xen unikernel instead of Unix? Just git push? If people are interested, I also have a few OPAM reporting scripts that could output in Canopy format, if you'd like a "OPAM libraries this week roundup" there too. That unifies our changelog scripts too... Also, I'd like to thank Amir very very much for his manual labours in maintaining the Mirage meeting notes so studiously for so long. I'm hoping that as our community grows, the Canopy approach will reduce the workload on him and spread it out among all of us. If the IRC format meeting doesn't work out, we can just go back to the normal Jitsi meetings, or work out some rotation so that we get the best of both worlds. Thoughts welcome, and see you on IRC tomorrow at 4pm UK time! -a > On 15 Mar 2016, at 22:37, Amir Chaudhry <[email protected]> wrote: > > Hi folks, > > Since a number of people are still at the Hackathon in Marrakech [1] it seems > better to shift the call by one week. Therefore, the next MirageOS call will > take place *next week* on Wednesday afternoon at 4pm GMT (23rd March). > > The call is open to all and I’ll send a reminder closer to the time. > > The notes from last few calls are finally in a PR [2] (phew). If anyone is > able/willing to take notes going forward, please do get in touch with me. > We’re also exploring other approaches too — for example, we’ve mentioned the > idea of an IRC based catchup. Your thoughts are welcome! > > Agenda items for next week are being gathered so please add any points to: > https://github.com/mirage/mirage-www/wiki/Call-Agenda > > Best wishes, > Amir > > [1] If you haven’t already seen it, you should definitely check out the > Hackthon webpage — itself a project built during the week! See the site at > http://canopy.mirage.io > > [2] https://github.com/mirage/mirage-www/pull/441 > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
