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

Consistent FMC Requirements #217

Closed
lgarron opened this issue Nov 5, 2014 · 1 comment
Closed

Consistent FMC Requirements #217

lgarron opened this issue Nov 5, 2014 · 1 comment

Comments

@lgarron
Copy link
Member

lgarron commented Nov 5, 2014

Some things that are enforced inconsistently:

  • No one may join the attempt after it has started
  • No cellphones
  • Availability of clocks/timers
    • ... which sometimes leads to cellphone use

There have been a few Delegate reports with instances of suspected/potential cheating.
It gets harder to trust everyone when a lot more competitors and organizers are holding the event, but organizers should only hold the event if they can make sure no one is cheating.

@lgarron lgarron added the clarity label Nov 5, 2014
@lgarron lgarron added this to the 2015 milestone Dec 21, 2014
This was referenced May 18, 2015
KitClement added a commit that referenced this issue May 21, 2015
KitClement added a commit that referenced this issue Jun 5, 2015
@lgarron lgarron removed this from the 2015 milestone Jul 29, 2015
@Laura-O
Copy link
Member

Laura-O commented Oct 4, 2017

This has been solved by adding Guideline E3d.
Competitors being late for the start of the attempt are sometimes allowed to compete, but I think delegates are aware of potential issues, so I am closing this.

@Laura-O Laura-O closed this as completed Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants