Monitor source management practices of other working groups

On the front of "technical reproducibility", we want to ensure that the code we write is operable on other people's machines. For that, in the absence of a clear standard we are adopting a subset of these [ten simple rules for making research software more robust](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005412).

There is a handy summary of these in a checklist which I have added to the repo [here](../blob/master/docs/journal.pcbi.1005412.s001.pdf).

For the hackathon we need to select a subset of these rules and review the work of the other groups to ensure they are compliant. We can attain compliance either by nudging other participants, or by doing the work ourselves. TBD.

Start by reading docs/journal.pcbi.1005412.s001.pdf and the linked ten-rule summary. Define the subset of rules for the hackathon, then review the other working groups' work and record or address compliance gaps. Done means the selected rules and review outcome are agreed and documented.

Written by the indexing model from the issue text.