[ANN] Wednesday, 25th November 2020 is MirageOS Bug Cleaning Day!

Hi folks,

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
next release, I think it would be nice to take a day and do some
housecleaning.

Our last bug cleaning day was on 17th November 2017, and pretty successful.

On Wednesday, 25th November (in two days) most people of the mirage-core
team will be going through old issues and coordinating our efforts on
the #mirage channel over on irc.freenode.net. I expect there to be the
most activity during 10:00-18:00 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! We’ll as well be watching the OCaml discord
#mirage channel
https://discord.com/channels/436568060288172042/519199441769594911

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

If you’ve a specific issue at your heart that you want to be solved,
please show up and tell us about it.

See you on Wednesday,

Hannes

9 Likes

Out of curiosity, is there a list of things that got resolved?

Hi @ulrikstrid, we did not keep a list of “things that got resolved”. Some issues were closed, some packages got released to opam-repository (fat-filesystem, pecu, mrmime, charrua, arp, mirage-protocols, …) - other project got bugfixes (i.e. mirage-qubes), and some repositories got archived, and others were transferred to the Mirage organization. So there’s progress :slight_smile:

3 Likes