Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oops. Failure to maintain game state. #24

Closed
pimotte opened this issue May 21, 2016 · 2 comments
Closed

Oops. Failure to maintain game state. #24

pimotte opened this issue May 21, 2016 · 2 comments

Comments

@pimotte
Copy link
Owner

pimotte commented May 21, 2016

I just merged #22 , which did not include a point total update, which I found out when inspecting #21. In my opinion I have violated rule 309, by submitting (and merging) a pull request that did not accurately reflect the game state. Given how #311 has not passed yet, and as of now, the rules are unclear on how to resolve this. Hence I am invoking Judgement to request an answer to the following question:

How should the current situation be resolved?

By rule 305, @MrHug will be the judge.

@MrHug
Copy link
Collaborator

MrHug commented May 22, 2016

As @pimotte indicates, there are no rules that currently tell us how to resolve this situation, nor are there rules that allow us to sanction a player for breaking our rules. As a result I feel the only judgement I can (begrudgingly) give is as follows:

As the breaking of the rules did not lead to a disruption of gameplay, either positive or negative, I see no need to undo the merging of the Pull Request that led us to this violation. Thus I rule that @pimotte will rectify the score totals to again reflect the current game state and no further action is taken.

I would like to take this opportunity to again highlight the need for a rule such as outlined in #18 (although it is hard to be impartial about this, since it is my pull request). Such a rule would allow us to deal with violations like this in a more impartial, objective, and streamlined manner.

As per rule 305, this issue can be closed soon, assuming no objections to this judgement are raised.

@pimotte
Copy link
Owner Author

pimotte commented May 22, 2016

I won't object to this ruling, so unanimity to overturn this decision cannot be reached. I will rectify the game state and then close this issue.

pimotte added a commit that referenced this issue May 22, 2016
@pimotte pimotte closed this as completed May 22, 2016
This was referenced May 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants