MirageOS bug cleaning day: Friday, 17th November 2017

mirageos

#1

In the MirageOS organization, we have many repositories that have lots of old and no-longer-relevant issues in them (some have even been fixed!) as well as issues that haven’t gotten a reply yet from a maintainer. In preparation for the upcoming hack retreat (starting on 29th November), when more eyes are on obscure corners of the Mirage ecosystem than usual, I think it would be nice to take a day and do some housecleaning.

On Friday, 17th November (a week from now), @hannes, @djs55, and I will be going through old issues and coordinating our efforts on the #mirage channel over on irc.freenode.net (the same venue as our biweekly catchups). I expect there to be the most activity during the afternoon UTC and maybe a bit later, but don’t feel limited to that timeslot – if you’re familiar with a repository and have a bit of time, we’d love your help any time at all. Please do join us if you’re free!

If you’re not sure where to start, here’s a link to a GitHub search for all issues in repositories owned by the Mirage organization which are open and not archived, sorted with the least recently updated first, for your editing and browsing pleasure:

https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Amirage+archived%3Afalse+sort%3Aupdated-asc


#2

I’m considering to start contributing soon, but it will take me a while to find out where I should start. Will probably pick a sub-project based on interest.


#3

I just completed some missed issues about ocaml-git :slight_smile: . Happy to see that mirage move on!


Week 46: What’s everyone hacking on this week?
#4

When introducing new people to mirage configure I often hear complaints that it is very confusing that -t, which could be said to be one of the most important options, is missing from mirage configure --help.

The fact that mirage configure --help does not work correctly when you are not located in the directory with your (valid) config.ml seems very confusing to the newcomers, and I think it would be good to either include the documentation regardless of cwd, or at the very least have a notice at the top of the help page saying “You should be in a directory with a valid config.ml if you want to get help with this tool.”

Not sure where to post this, so I’m posting it here in the hope someone will pick it up. :slight_smile:


#5

To close the loop on the bug reported here, I updated https://github.com/mirage/mirage/issues/717 although I didn’t make any progress on fixing it. :confused: I mean, uh, I left it for an interested contributor. Yes.

Bug cleaning day felt so good we decided to hold it on the first Friday of every month, starting around 14.00 UTC and going until late (UTC or later :wink: ) We’ll keep coordinating on IRC. You can see our logs from the inaugural bug cleaning day at https://irclog.whitequark.org/mirage/2017-11-17 , thanks to whitequark’s IRC logger, if you want to get a preview for next time!