Thanks for helping keep this event feed accurate! A few ways to help, from easiest to most technical.
Fill in the form — no git, no JSON, no write access needed:
It generates the event data for you and opens a prefilled issue in this repository. A workflow validates it and turns it into a pull request; a maintainer reviews and merges it. Minutes later, it's published.
Wrong date, broken link, venue changed, event cancelled? Open an issue describing what's wrong. Small fixes are welcome — don't sit on one because it seems minor.
Events are one JSON file per event in events/ — see events/README.md for the format and a minimal example.
Every pull request is validated automatically against the OTE spec, so you can't break the published feed: if validation fails, the PR tells you exactly what's wrong, and nothing publishes until it passes and someone merges it.
A real contribution, and it needs no GitHub account at all: share the events, add the feed to your own community's calendar, or republish the data on your site. See Reuse the data in the README for the license and the feed URLs.
Event data in this repository is published under the license declared in ote.config.json. By contributing an event, you agree it's published under that license: reusable, republishable and buildable-upon by anyone, without asking permission.
So only submit event information you can publish on those terms — public facts (title, date, venue, public links), not material someone shared with you privately, and not text copied from a page under a more restrictive license.