hannes changed the topic of #mirage to: bug cleaning day on friday, 17th November, UTC afternoon until late -- good news everyone, MirageOS 3.0 was released in February 2017! hack on
mort___ has joined #mirage
mort___ has left #mirage [#mirage]
AltGr has joined #mirage
argent_smith has joined #mirage
wendar has quit [Remote host closed the connection]
wendar has joined #mirage
argent_smith has quit [Ping timeout: 240 seconds]
mort___ has joined #mirage
argent_smith has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
olle has joined #mirage
mort___ has joined #mirage
dtornabene has joined #mirage
olle has quit [Quit: olle]
olle has joined #mirage
olle has quit [Client Quit]
olle has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
talex5 has joined #mirage
<yomimono> oh no, I'm late!
<yomimono> hi everyone! I think it's supposed to be catchup meeting time
<hannes> o/
mort___ has quit [Quit: Leaving.]
<yomimono> we meet every other week in here at 4pm UK time (16.00 UTC currently), agenda is at https://github.com/mirage/mirage-www/wiki/Call-Agenda#22-november-2017 if you'd like to check it out or add stuff :)
<kensan> \o
<mato> hey ho... i'll have to leave around half-past-ish, but otherwise here :)
<yomimono> not much on the docket for today so maybe we'll be done by then :)
<raboof> o/
<yomimono> first up we had an item about the upcoming hack retreat (29th nov - 6th dec)
<yomimono> I put this on here as "hack retreat prep", thinking we should probably do some (like try to make sure tests are passing, etc)
<mato> i'm in the process of releasing a new ocaml-freestanding with 4.06.0 support to have it in time for the hack retreat :)
<hannes> \o/
<yomimono> yay! \o/ thanks to talex5 we'll also have a new mirage-xen-ocaml for 4.05.0
<hannes> ocaml-freestanding.0.2.3 fixes an annoying floating point issue which we should use as a regression test
<hannes> i made no progress on printing out code, but still have plans to do so (though time is getting tough)
<yomimono> +1. mato filed an issue on the same issue on the xen side, which we should fix too
<yomimono> hannes: I have some access to printing if you want to split things up, although I admit I'm not super pumped about carrying a lot of paper across 3 continents
<kensan> Is there some stuff missing or that would be handy that one could bring along (e.g. long cable etc)?
<yomimono> kensan: I've seen some coordination about that on the marrakesh mailing list
<hannes> yomimono: I still have to evaluate the pandoc || a2ps pipelines I got pointed to... the actual printing should be easily done in the computer lab :)
mort___ has joined #mirage
<yomimono> hannes: gotcha
<hannes> kensan: there is no need to bring power cords, since i usually buy enough on-site and leave them there
<mato> printing-in-the-medina is also possible, as i found out last time :-)
<hannes> mato: but expensive... let's see whether i'll manage to do something useful
<mato> yes, for a fee, but you get the find-the-internet-cafe adventure included for free
avsm has joined #mirage
<kensan> kensan: I was thinking ethernet cable ;) but that was just an example. I could also bring a small switch that I could leave there (100mbit though).
<hannes> host is happy to have us there, it may be a bit crowded, but i saw that even avsm booked a flight!!!!
<yomimono> O_O
<hannes> kensan: ethernet cable: highly appreciated! mato will bring a switch... there's no need for more than 100MB/s
<hannes> if you have a 4G to wireless/ethernet adapter (as in self-running system which only needs a 4G card, that will be handy)
<yomimono> I have one of those, I'll confirm that it's unlocked before I depart and bring it if so
<mato> i will bring a 4G USB dongle which works when plugged into anything with a USB port, however it enforces an extra layer of NAT (not really an issue here)
<kensan> hannes: I have to check if I can fit the 30m cable...
<avsm> i'm going to be there for a couple of days over the sun/monday, can bring supplemental kit if you let me know when you arrive
<mato> i did some research and in theory those of us who have inwi SIM cards from march they should still be valid
<yomimono> oh nice!
<hannes> and, bring some liquor from duty free if you like to drink and share liquor (availability on-site is non-existing)
<kensan> As avsm I will be arriving late (Fr) so if something is missing you can hit me up.
<hannes> kensan: sure, we'll write a wishlist via email! :)
<kensan> hannes: Currently I plan to travel with only carry-on but I guess that plan will change *heh*
<yomimono> if anyone has ideas for small gifts for our hosts I'd appreciate hearing them - they've taken good care of us and I would like to bring them something small and nice
<hannes> I travel with carry-on only..
<hannes> (i guess we should move on)
<yomimono> anything else? probably a good idea to take the physical-thing stuff to the marrakesh list
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Client Quit]
<yomimono> next up we had an item that came up during bug cleaning day
<yomimono> there are a lot of repositories in the mirage org that seem not used anymore
<yomimono> since the best tools we have for dealing with the mirage universe in github use membership in the mirage organization as a filtering tool, this is annoying
<yomimono> we made an issue in mirage/mirage with a list of proposed repositories to move to ocaml-attic: https://github.com/mirage/mirage/issues/866
<yomimono> I don't know who has the necessary access to do this - I think the person needs to be an admin in both mirage and ocaml-attic?
<mato> we could also create a mirage-attic org if those are mirage-specific...
<hannes> (NB: there's as well a mirage-attic organisation, but i'm not sure who's in charge)
<yomimono> mirage-attic was made by mistake last time a bunch of stuff was moved to an attic; all the stuff actually ended up in ocaml-attic that time
<avsm> me i think
<yomimono> amirmc controls mirage-attic iirc?
<yomimono> oh nm
<avsm> ocaml-attic is fine though
<avsm> we might as well just use that?
<avsm> it is, after all, an attic
<hannes> since github tracks repo ownership changes, there's no real cost in moving repos (old links keep working)
<yomimono> I don't care particularly, I just want them out of mirage :)
avsm has quit [Quit: Page closed]
<yomimono> tfw you think you may have accidentally trolled someone into ragequitting ;)
<hannes> yomimono: I strongly agree! less repositories means less unsolved issues and easier to find out about the neglected issues
<raboof> github also recently introduced a feature to 'archive' a repo (https://help.github.com/articles/archiving-a-github-repository/), I bet that shows up in the API and can be used to filter as well
<hannes> (but it needs someone with access to both mirage and ocaml-attic...)
<yomimono> oh, that would be a bit less awkward than transfering the ownership - I'll look into that, thanks raboof
<yomimono> we can try that, and if archived repositories still show up in search, move them to ocaml-attic anyway
<hannes> the question is: should there be a deadline for complaining about the list of repositories?
<hannes> maybe "this friday" with an announcement on mirageos-devel?
<yomimono> very good point; we should both state that one exists and take more steps to notify people who've committed into those repositories (I didn't do that at all beyond this agenda item)
<yomimono> hannes: sgtm
<hannes> I'd appreciate to get this out of the way before marrakesh tbh, but that may be a bit too tight!?
thomasga has joined #mirage
<yomimono> same :/ perhaps monday deadline?
<yomimono> that gives almost a full week, which seems a bit fairer
<hannes> yomimono: yes, will you write the mail to mirageos-devel?
<yomimono> will do, and I'll make a list of maintainers and contact them either via github mention or email
<yomimono> about their specific repos
<yomimono> anything else on that?
<yomimono> cool, I had one last thing (somewhat related):
<yomimono> we had a bug cleaning day last week on Friday :) I thought it was great and I think we should continue the tradition with some reasonable frequency, maybe every month-ish
<yomimono> thanks a ton to everyone who participated!
<hannes> I agree. while I didn't close any issues, I opened lots of PRs (to run travis with 4.04 and 4.06, and fixed some metadata in various repositories (hint: now I have ~30 PRs outstanding))
<yomimono> cripes, that's a lot.
<hannes> every first friday of a month would sound good to me tbh
<yomimono> maybe *that's* the hack retreat prep we need to do, just review all of hannes's PRs
<hannes> (in 14:00-late UTC time)
<hannes> most of them are simple... mirage-profile could do a release, mirage-flow and mirage-fs-unix need a release for safe-string..
<yomimono> first fridays sound great to me, we can do the first (regular) one in Marrakesh ;)
<hannes> (now off... see (many of) you in marrakesh!
<yomimono> that's all on the agenda :)
<yomimono> anything else folks want to add?
<mato> yomimono: thanks for running the meetings!
<yomimono> yes, I have a request for everyone related to that
<olle> \o/ it's seriously great
<yomimono> for the last three meetings I have submitted 100% of the agenda items and I also do way too much of the talking
<yomimono> if the meetings are useful for others, I would appreciate either more agenda item submissions or perhaps volunteers to run the meeting itself :)
<thomasga> I'm late but I've added a comment to the attic issue :-)
<yomimono> if the meetings are not useful for others, that's OK -- perhaps we can reduce their frequency or rethink the format :)
<yomimono> thanks thomasga!
<thomasga> for the meetings: I always have difficulty to join for random reasons (changing the time will not help) but I always read the transcripts
<thomasga> so they are very useful for me, even if I am not active at all
<thomasga> (just to have an idea on what is going on :p)
<yomimono> thomasga: would it be useful for that purpose to have a format where someone asks people to provide updates on what they're working on? we tried that for a few meetings a couple months ago, when avsm was working on hesternus I think
<yomimono> it puts people on the spot which isn't my favorite, but it's nicer for forming a big picture of what's actually happening
<thomasga> it's also harder to commit to do this regularly
<reynir> I was ready 20 minutes before, but then somehow forgot about it until now
* reynir spots a squirrel
<thomasga> :-)
<thomasga> but yea I don't know. It's nice to be able to comment on the agenda items all together as well.
<thomasga> anwyay, I quite like the current format but would be curious to hear what other think (and I am of course happy to change if another format is more appropriate)
<yomimono> we do have the results of the survey gemma prepared some time ago about the catchups, which suggest a number of concrete things (human-constructed summaries, more advance on agenda items) that require human time and so I haven't done
<yomimono> but might cause the catchups to be more useful or engaging
<yomimono> (those results are at https://github.com/mirage/mirage-www/issues/512 )
<mato> fwiw i'm happy with the current format.
<mato> ...and find the meetings useful
<mato> gotta run, ttyl
<reynir> I wanted to write a reminder-bot, but never got around to it-maybe something to do in Marrakech heh
<yomimono> yeah! it might be possible to resurrect the imaginary friend also
<yomimono> (the irc bot which would archive discussions and submit them automatically to canopy)
<yomimono> last time in marrakesh I got all pumped about porting a random irc unikernel to mirage 3, and then discovered that this "irc library" actually only implemented PING? PONG!
<reynir> heh
<olle> aaagh
<yomimono> having gone mad with power I declare this meeting over
talex5 has quit [Quit: Leaving]
<yomimono> our next meeting will be on 6 december: add agenda items at https://github.com/mirage/mirage-www/wiki/Call-Agenda#6-december-2017 :)
<olle> yomimono: Thank you for adding the structure. This is hard work.
<yomimono> olle: thank you :)
<olle> this was a cool PR - https://github.com/mirage/mirage/pull/864
pagurus has joined #mirage
pagurus` has quit [Ping timeout: 240 seconds]
<yomimono> oh, thanks for the reminder on that olle - I thought "I should wait for travis" and then forgot about it
miragebot has joined #mirage
<miragebot> mirage/master d38a085 David Scott: travis: use the mirage-dev branch of mirage-skeleton...
<miragebot> mirage/master dd37705 David Scott: Prepare to release 3.0.6...
<miragebot> [mirage] yomimono pushed 4 new commits to master: https://git.io/vFN4P
<miragebot> mirage/master 2747017 David Scott: travis: minimum version is 4.04.0...
miragebot has left #mirage [#mirage]
<olle> yomimono: There were 2 Docker Cloud something build notifications, too, but they were behind some login wall, if I parsed that correctly.
<yomimono> yeah, I can't see those either, lost my superpowers when I quit :P
<hannes> \o/ so we should have mirage 3.0.6 ready nowish!?
<hannes> which.. ehm... works with cohttp 1.0
<yomimono> needs to be tagged, watermarked, uploaded, and sent to opam-repository yet
<hannes> and yes, yomimono, thank you very much for running the meetings and agenda!
<yomimono> (djs55 will take care of the rest of that release, he says out of band :D)
miragebot has joined #mirage
<miragebot> [mirage] djs55 tagged 3.0.6 at master: https://git.io/vFNBj
miragebot has left #mirage [#mirage]
hannes changed the topic of #mirage to: bug cleaning day first friday each month from 14:00 UTC till late, meet here. MirageOS 3 is released, happy hacking!
<yomimono> :D thanks hannes!
yomimono has quit [Quit: Leaving]
olle has quit [Quit: olle]
thomasga has quit [Quit: Leaving.]
argent_smith has quit [Quit: Leaving.]
dtornabene has quit [Remote host closed the connection]
argent_smith has joined #mirage
thomasga has joined #mirage
thomasga has quit [Ping timeout: 248 seconds]
argent_smith has quit [Quit: Leaving.]
AltGr has left #mirage [#mirage]