The readme does not say or lead to everything that people need to know

[rptb1]

The MPS readme is oriented towards the MPS as a product supported by Ravenbrook. But now we want to foster its use as a community open source project, so it should cover things like contribution, planning, forking, and other management topics. Or at least point to further information. If someone comes across the repository somehow (wherever it is) we want them to be able to do things with it.

[thejayps]

I think a good way to slice this information for a potential new contributor (especially if they discover the MPS at some future time when it may not be being actively worked on by anyone else) would be according to the resource they have at their disposal. Some of our procedures require 2 or more people to complete. We could estimate the effect on quality of trying to complete those procedures without the intended resource to help potential contributors manage their expectations

[thejayps]

This is related to migration, because we need to absorb anything on the front page of the project into the readme: #98