Marc

We can break the API, but it's best to make the breaking changes as a batch, and with a new major release version. I think we won't really know the...

#1288 is going to have a lot of merge conflicts anyway, and it's waiting on another PR, so feel free to work on whatever regardless.

Sure.

@Adam-Flammino We're happy to e.g. help write tests, just open a PR or ask us here (or on gitter).

@Adam-Flammino Either way, really. We don't have a scheme for which strategies go in which files, we just group them as we go wherever they seem to fit.

I don't believe so, what reference are they from?

These are not yet implemented, go for it!

If you are willing to look through some Fortran, this strategy appears to be in the second Axelrod tournament as well. See the [source code](http://www-personal.umich.edu/~axe/CC/CC2/TourExec1.1.f.html) and look for a line...

If (...) < 0 go to 1, == 0 Goto 2, < 0 Goto 3. See 11.4 [here](https://www.fortran.com/F77_std/rjcnf-11.html).

Ideally these are the same -- hopefully the Fortran can help explain anything missing.