hannes changed the topic of #mirage to: bug cleaning day every first friday in month (14:00 UTC - late, next: 2nd Feb); MirageOS 3 is released, happy hacking!
mk270 has quit [Ping timeout: 240 seconds]
mk270 has joined #mirage
contrapumpkin has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
contrapumpkin has joined #mirage
mort___ has joined #mirage
mort___ has quit [Client Quit]
bramford has joined #mirage
andersoncruz has quit [Quit: Leaving]
AltGr has joined #mirage
mort___ has joined #mirage
argent_smith has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has left #mirage [#mirage]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Ping timeout: 268 seconds]
mort___ has joined #mirage
mort___ has left #mirage [#mirage]
mort___ has joined #mirage
mort___ has quit [Ping timeout: 260 seconds]
mort___ has joined #mirage
demonimin has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Client Quit]
Timada has joined #mirage
yomimono has joined #mirage
<yomimono>
hi :)
<reynir>
Hi!
<Timada>
Hi!
<demonimin>
hi?
<yomimono>
normally this is fortnightly meeting time, but we have nothing on the agenda at the moment!
<mato>
yomimono: thanks for the reminder on slack, i like, totally forgot :)
<djs55>
I'd like to mention (sorry it's not on the agenda): https://github.com/mirage/mirage-protocols/pull/8 — I think it's approximately ready to go, I was going to do the remaining polishing, testing and releasing unless someone thinks it's a bad idea :)
<mato>
having also totally forgotten about the agenda, i can do an impromptu update on solo5 developments of which there are a few, some discussions may be interesting for people to be aware of...
<yomimono>
no objections here, djs55
<djs55>
yomimono: thanks!
<yomimono>
mato: sure, go for it :)
<mato>
so, several things. as i wrote on the mailing list, i have resurrected the Solo5/opam-solo5 remote, switched over CIs and done the upper-bounds juggling in the opam.ocaml.org repository.
<mato>
this means we can start breaking stuff, which is fun :-)
<mato>
people wanting to follow along with solo5 master henceforth should use the Solo5/opam-solo5 remote until further notice :-)
<mato>
the actual renaming i want to do after i've worked through the various Mirage/Solo5 PRs that are in-flight
<mato>
a question: For upcoming changes (renaming, muen) that relate to the 'mirage' front-end tool, should PRs be made primarily against 'master', and I will add a suitable `mirage` package to Solo5/opam-solo5?
<mato>
OR should we consolidate such PRs on a separate branch (e.g. `#solo5-dev`) and then try and merge it in one go "when it's ready" ?
<yomimono>
It's probably better to do in a feature branch. I believe you can point a package definition there directly from opam-solo5
<mato>
yes, that would work. PRs can be raised/merged against a feature branch, right?
<yomimono>
Yep. There's a box in the GitHub UI that specifies the branch the PR is against; by default it's whatever the primary branch of the repo is (usually master) but it can be changed to anything that already exists
<yomimono>
So someone with write access to mirage/mirage needs to start the branch, then PRs can be made against it normally.
<mato>
Great, that looks like the best way to approach this then.
<mato>
Apart from that I'm knee-deep in the refactoring. As part of considering the implications of the malloc() move from Solo5 to ocaml-freestanding I went over the current state of the Xen code in mirage-platform.
<mato>
... and can confirm that upstream Mini-OS has PVH support.
<hannes>
mato: \o/
<mato>
One thing I wanted to ask, djs55 may know... there appear to be way more historic C stubs in mirage-xen than what we're actually using.
DonRichie has quit [Ping timeout: 248 seconds]
<mato>
AFAICT, we're only using the low-level C interfaces to grant tables and event channels these days, right?
<djs55>
I've not looked at that code in a while, but there is probably lots of dead code lying around
DonRichie has joined #mirage
<mato>
That matches what I saw.
thomasga has joined #mirage
<hannes>
djs55: mirage-protocols/8 -- keepalive: sounds good to me, samoht observed that we can get rid of the `callback` type there... and this is a breaking change, but the only consumer atm is the tcp stack :)
<mato>
In any case, porting to ocaml-freestanding and upstream Mini-OS will not be trivial. so unclear who has time to do (and fund!) that work.
<djs55>
hannes: ok, sounds good to remove
<hannes>
marrakesh: a bit short on participants, could use more signups this week :)
<mato>
hannes: how many are we at?
<hannes>
21
<thomasga>
hey! I might be trying to sneak in for a few days at the retreat
<mato>
(That's all from me on Solo5 and the Xen digression)
<yomimono>
:D
<hannes>
thomasga: yes, please! :)
<thomasga>
but my agenda is pretty chaotic at the moment…
<thomasga>
but I'm very motivated to go to Marrakesh again :-)
<mato>
bring some crypto coins printed out on paper :-P
<thomasga>
haha
<thomasga>
I have papers but I just don't have crypto coins :-)
<thomasga>
you should ask Hannes ;-) Anyway I didn't want to interrupt the meeting
<yomimono>
happy to let you in on my ICO, rates very reasonable
<mato>
are there cats involved?
<jpdeplaix>
thomasga: \o/
<hannes>
thomasga: I never had any coins, sorry. and you don't interrupt the meeting, but contributing to it
<thomasga>
right right :-)
<yomimono>
thomasga: the whole meeting is the AOB part today :P
<thomasga>
can someone put the IRC archives address in the room motd?
<mato>
oh, following up on the TROVE discussion from last meeting, I also started writing some OCaml code using Andreas' ppx_graphql to get me a list of 'mirageos' tagged repos from Github, but then got stuck out of my depth on some type mismatch, so on the back burner for now.
hannes changed the topic of #mirage to: bug cleaning day every first friday in month (14:00 UTC - late, next: 2nd Feb) - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3 is released - happy hacking!
<hannes>
thomasga: done :D
<hannes>
mato: put your code somewhere, and we'll crowdsource the solution
<yomimono>
hannes: ah, can you update the "next bug cleaning day" too? it'll be 2nd March
<mato>
anyhow, the general ideal is to have a cronjob that runs every X hours, gets the list of repos from github, adds a static (for non-github) list to that and commits the result somewhere
hannes changed the topic of #mirage to: bug cleaning day every first friday in month (14:00 UTC - late, next: 2nd Mar) - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3 is released - happy hacking!
<yomimono>
thanks! :)
<hannes>
AoB: anyone has a pic on the interwebs with the mirage hackathon tshirt (not the design, the actual shirt)?
<yomimono>
hannes: I can easily generate one; do you want a human wearing the shirt also?
<yomimono>
or just shirt sitting flat on something?
<hannes>
yomimono: fine either way
<yomimono>
cool, I'll post such a photo on mastodon and tag you
<yomimono>
re: shirts, gemma who designed the batch we got two retreats ago is super busy this week, maybe best to ask her stuff about it next week
<hannes>
re: shirts, someone from zurich/barcelona who'll join us this time just wrote me a mail that he can do something; also halfdan had some drawings in december and wanted to make a tshirt design iirc
<hannes>
oh, hack retreat: i usually don't expose participants, but marek "lead developer at @qubesos" will join for 5 days \o/
<thomasga>
also, as said a few months ago, I've started a re-design/re-engineering of mirage-www. A random style is availabe here: http://gazagnaire.org/mirage/ feedback is welcome by private email (I don't want to start a flameware yet)
<reynir>
Yes, he showed me some sketches a week ago
<reynir>
And I think he still wanted to, but I don't want to make any promises on his behalf :)
<hannes>
thomasga: put it life, it's nice! :)
<yomimono>
thomasga: this looks great! :D
<thomasga>
need to add a few patches to ramen first, so need a few more days of hacking … once almost stable I'll make a new branch in mirage-www
<mato>
i'd still like to see a canopy-based solution for mirage-www
<yomimono>
hannes: please feel free to expose to people that I will be attending, and in particular if there are any non-men who have questions about what attending is like I am happy to answer them
<thomasga>
mato: yes it will be
<thomasga>
(based on something like canopy)
<mato>
thomasga: ah, then good. for the design, it's fine. i happen to like the old design myself :)
<mato>
yeah, mainly the user experience of canopy is what i want, i.e. push <something> to git, unikernel picks it up w/o redeployment
<mato>
and actual redeployment is only done if the code changes, not the data
<thomasga>
yup
<lars_kurth>
hannes: cool re marek - also, I still need to arrange a time when to meet in BLN (got here Sat, getting settled)
<thomasga>
mato: btw, if you are able to auto-generate the repos.yml file, that would be super-useful for the new website too
<mato>
can do all of that i think, just don't have bandwidth to focus on the ocaml required :)
<mato>
maybe face to face in marrakesh with someone who can walk me through "why doesn't this work"
<mato>
(which would be of the most benefit from a learning PoV for me)
<mato>
ok, i have to run. see you all later.
<yomimono>
later mato!
<hannes>
thomasga: how was cuba?
mort___ has joined #mirage
mort___ has quit [Client Quit]
<thomasga>
hannes: really really great :-) and as usual too short
<hannes>
thomasga: did you travel around the island a bit?
suhdood has joined #mirage
<yomimono>
thomasga takes amazing holidays and amazing holiday photos
mort___ has joined #mirage
yomimono has quit [Quit: Leaving]
Timada has quit [Ping timeout: 260 seconds]
AltGr has left #mirage [#mirage]
mort___ has quit [Quit: Leaving.]
jnavila has joined #mirage
thomasga has quit [Quit: Leaving.]
suhdood_ has joined #mirage
suhdood has quit [Ping timeout: 255 seconds]
suhdood_ has quit [Read error: Connection reset by peer]