Skip to content

Add latest draft of v3 rules#2

Merged
AhmadAmine998 merged 1 commit intodev-2026from
v3-2026-draft
Feb 9, 2026
Merged

Add latest draft of v3 rules#2
AhmadAmine998 merged 1 commit intodev-2026from
v3-2026-draft

Conversation

@jara001
Copy link
Collaborator

@jara001 jara001 commented Nov 18, 2025

Here is the latest draft of the new ruleset. It did not go through corrections, but I managed to do another two iterations since our last call (e.g., I added the stuff we discussed). Some notes are still present.

Main points:

  • Create a base ruleset "general rules" that are fixed for some time, e.g., 1 year.
    • These rules should be shorter, but on the other hand they should give more options for competition organizers.
  • General rules are accompanied by additional rules "competition rules". They add competition-specific rules, e.g.:
    • Competition location.
    • Track parameters.
    • Which parts of general rules apply.
  • Definitions. A lot of phrases and labels were not described before.
  • Duplicit rules are removed (e.g., parts about the box on the car).
  • Rules that are not used anymore (or not used at all) are also removed.
  • (Ongoing) Changed will/must into may in parts where the rules might not be applied because of the competition setting (e.g., small competitions have different need than big competitions).

Feel free to discuss and comment even on small parts of the draft.

I think it starts to get a certain shape, but some parts are still missing (and, therefore, might be eventually removed) and some parts are not detailed enough.

Just to note, I am still thinking about making a version (or maybe just add comments invisible to the teams) suited more for the organizers.

Note 2: I plan to add a diff with the current rules as well.

Note 3: I force-pushed the branch so it does not mess up in GitHub. Diff with current rules will be in README.md.

Copy link
Contributor

@AhmadAmine998 AhmadAmine998 left a comment

Choose a reason for hiding this comment

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

This is a great starting point

@jara001
Copy link
Collaborator Author

jara001 commented Nov 26, 2025

Thanks a lot! I'll try to look into it as soon as possible :-)

Note: Added some notes, next version during tomorrow/Friday.

@jara001 jara001 requested a review from AhmadAmine998 January 5, 2026 16:24
@jara001
Copy link
Collaborator Author

jara001 commented Jan 5, 2026

Hello! Sorry for being delayed so much, but I had to work on other, unexpected, assignments. I tried to push the whole draft close to the final version, therefore, the amount of TODOs is very limited. I also tried to be much more strict with words Felix suggested (MUST, MUST NOT, etc.) but it is still not used everywhere.

@jara001
Copy link
Collaborator Author

jara001 commented Jan 7, 2026

Nice, I'll look into it (hopefully) tomorrow. Note that for some reason you were commenting on an older version. Newest one is currently d24d04b

@AhmadAmine998
Copy link
Contributor

@jara001 can you please resolve threads that have been addressed in the latest commit?

@AhmadAmine998
Copy link
Contributor

Minor suggestion: We should change the pr to be into #1 dev-2026, then merge dev-2026 into main. This would just help keep a standard dev-20xx for branches (and helps us check history in the future).

@jara001
Copy link
Collaborator Author

jara001 commented Jan 20, 2026

Minor suggestion: We should change the pr to be into #1 dev-2026, then merge dev-2026 into main. This would just help keep a standard dev-20xx for branches (and helps us check history in the future).

Nice suggestion! Should I overwrite your changes there or merge it?

I've added offenses/violations, and included some other minor feedback. Lately it seems that most of the requested/suggested changes are just minor ones... does it mean that we are FINALLY getting close to the final version? :)

Copy link
Contributor

@AhmadAmine998 AhmadAmine998 left a comment

Choose a reason for hiding this comment

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

All seems good now. I did one final pass of wording adjustments for consistency and clarity, but all content is great. Will merge into dev-2026 to finalize the merge into main there.

Copy link
Contributor

@AhmadAmine998 AhmadAmine998 left a comment

Choose a reason for hiding this comment

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

All seems good now. I did one final pass of wording adjustments for consistency and clarity, but all content is great. Will merge into dev-2026 to finalize the merge into main there.

@AhmadAmine998 AhmadAmine998 changed the base branch from main to dev-2026 February 9, 2026 08:36
@AhmadAmine998
Copy link
Contributor

Merging this into dev-2026 to move towards final commit and release. Only two issues left to address imo:

  1. We should add a specification to where the car may be configured in head-to-head races (i.e not in the middle of the track)
  2. We should specify that the competition rules MUST specify the heat/brackets for the competition.

@AhmadAmine998 AhmadAmine998 merged commit 5ea4ba0 into dev-2026 Feb 9, 2026
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.

4 participants