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

WCRP 5.3 Update #435

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

WCRP 5.3 Update #435

wants to merge 21 commits into from

Conversation

zekemackay06
Copy link
Contributor

As requested by Board, this update contains several new baseline quality standards for WCA competitions.

Changes made:

  • Strengthen proximity policy to 30km, only allow two competitions within proximity distance regardless of events
  • Disallow competitions in vehicles
  • Heavily restrict private residences as venues
  • Require a complete schedule at announcement
  • Disallow competition days of more than 16 hours

Minor changes

  • Fix wording of exceptions
  • Require competitors to only compete at one location of an FMC simultaneous competition

@zekemackay06 zekemackay06 requested a review from a team as a code owner October 16, 2024 16:38
@EdHollingdale
Copy link
Contributor

These seem like sensible changes.

Honestly I think if we want to take ourselves seriously as WCA comps being serious "competitions" 16 hours is still ridiculous, but having a limit at all is a start.

Its a shame that some proximity restrictions have come back in - I'd have hoped that basically removing all restrictions would lead to people being sensible. But I agree that there have been some ridiculous examples and we can't actually trust Delegates to apply common sense.

@dmint789
Copy link
Member

It would be good to link the explainer document in the description. Also, someone mentioned that one of the changes still says minimum 8 hours between comp days, so that should be changed to 10 too.

@jgouly
Copy link

jgouly commented Oct 17, 2024

Would be good to clarify if:

5. The schedule must include a distinct timeframe for all rounds of official events at the time of announcement.

Means you can't add an extra round during a competition (if running early etc)

@Bitzerr
Copy link

Bitzerr commented Oct 18, 2024

I don't really see how any of these changes are necessary. I don't think formality in competitions is something the WCA should be trying to achieve. The primary reason for going to competitions is to have fun.

@Justiniscoding
Copy link

While I think most of these changes are positive, the last major change doesn't sit right with me. While it is good to prevent people from competing for too long consecutively, why not make this limit reset at midnight? This new rule change would prevent 24 hour competitions from existing, which may not be common but are very popular and a once in a lifetime opportunity for cubers.

To keep 24 hour comps allowed, why not change
iv. Official events at a competition must not run for more than a 16-hour period without a break of 10 hours or more
to
iv. Official events at a competition must not run for more than a 16-hour period without a break of 10 hours or more (limit resets at midnight)

@sushantshah-dev
Copy link

I don't see any reason for restricting competition duration. Is it causing any issues to the WCA as an organisation? Is it causing trouble to competitors?

Add exception to proximity policy for competitions in different countries.
Clarify complete schedule at announcement
Change time limit from 10 to 9 hours
Weaken vehicle and private residence policy
Change private residence and vehicle policies
@dmint789
Copy link
Member

I love the updates! @zekemackay06

Copy link
Contributor

@KerrieJarman KerrieJarman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by a formal Board vote

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

Successfully merging this pull request may close these issues.

10 participants