Vince Knight

> We can break the API, but it's best to make the breaking changes as a batch, and with a new major release version. Yeah, our previously discussed plan was...

I'm in favour. We can add a check to the CI to check all files are in the required format (for example: https://github.com/drvinceknight/Nashpy/blob/master/.github/workflows/config.yml#L34). We'd need to add something to the...

I can have a go at moving it to the expected location?

This is a brilliant issue: :+1:

This strategy was mentioned on reddit (Random TitForTat and/or Grudger: defects with random probability): https://www.reddit.com/r/GAMETHEORY/comments/480xb3/how_to_beat_this_strategy_of_prisoners_dilemma/

Absolutely @Adam-Flammino: please do! I suggest that when you decide on a strategy you run it past us just to make sure it hasn't been implemented yet (it's possible that...

If you're going to go with nasty tit for that as the strategy I'd suggest that you just add that to the bottom of the existing tit for tat file:)

Welcome @souravsingh! Drop in to our gitter channel: gitter.im/Axelrod-Python/Axelrod Otherwise, take a look at the contribution guidelines and don't hesitate to ask any questions :) http://axelrod.readthedocs.io/en/latest/tutorials/contributing/strategy/index.html

@mturzanska I'm afraid that that's in already to under `TitFor2Tats`: http://axelrod.readthedocs.io/en/latest/_modules/axelrod/strategies/titfortat.html#TitFor2Tats (Please correct me if you think I'm not quite right reading the two logics).

> Would you mind if I start working on those? That would be awesome! Let us know if we can assist in any way :) 👍