Add or correct a competition

An entry also needs: entrants build or program a system that acts in the physical world, or in a simulation that stands in for one; there is a ranked or judged result; and at least one edition was held or is confirmed, with a source. One-off and ended competitions are welcome as history. Not in scope: challenges without a physical body, such as prediction contests, language or vision benchmarks, and games.

How it works

1. Copy an existing file in the GitHub repository, such as unibots.yml, and fill in yours. You can do this in your browser with the GitHub editor.
2. Name the city and country of each venue. Do not look up coordinates; they are added after your change is merged.
3. List where your facts come from, and set last_verified to today if you checked them against the organiser's site.
4. Open a pull request. Automatic checks tell you about anything to fix. A maintainer merges it, usually within a few days.

Prefer not to edit files? Suggest a competition in an issue and a maintainer will add it.

Before you submit

• The competition is open beyond one institution or company.
• The summary is in your own words, not copied from another site.
• The organiser contact is a website or a role mailbox such as info@, never a person's address.
• Upcoming editions carry a start date and an application deadline where known, so people can find them.
• who_can_enter records restrictions: levels lists the kinds of team admitted (school, university, research) and only_from lists country codes when entry is limited to teams from those countries. No block means open to everyone; levels: [everyone] says so explicitly and cannot be combined with other levels.

Organisers who want a record corrected or removed: see the removal policy.