8000 Add When's the Race to Calendar by tristanheilman · Pull Request #10 · subinium/awesome-f1 · GitHub
[go: up one dir, main page]

Skip to content

Add When's the Race to Calendar - #10

Open
tristanheilman wants to merge 1 commit into
subinium:mainfrom
tristanheilman:add-whens-the-race
Open

tristanheilman wants to merge 1 commit into
subinium:mainfrom
tristanheilman:add-whens-the-race

Conversation

@tristanheilman
Copy link
Copy Markdown

Adds When's the Race to the Calendar section, next to F1 Calendar.

It's a free site that shows every F1 session (practice, qualifying, sprint and race) in the visitor's local timezone, with live countdowns and an auto-updating calendar subscription (webcal/.ics). It also publishes a free, no-key JSON/RSS/iCal schedule feed with CORS enabled, documented at https://whenstherace.com/f1-schedule-json/. The data is refreshed daily from Jolpica. It's actively maintained, with current 2026 data and results updated through each race weekend.

@subinium
subinium commented Nov 7, 2026
Copy link
Copy Markdown
Owner

Thanks for the submission. The schedule JSON is populated and the timezone/calendar utility is relevant, but I found discrepancies to resolve before inclusion:

  1. Please make the calendar scope accurate. On 7 November, f1.ics contained 23 race events, not separate practice, qualifying or sprint sessions. The calendar page describes qualifying/sprint coverage. Either provide those events or explicitly label the subscription as race-only in both the site and README entry.

  2. Please correct the PR's provenance description: it says Jolpica, while the current feed documentation and privacy page identify F1DB and sportstimes/f1. The RSS/JSON Feed also include a karting article, despite being described as calendar-only feeds; please narrow the feeds or their description.

  3. Reconcile the cookie-free analytics description with the deployed Google Analytics initialization. The layout bundle initializes GA4, while the policy describes analytics without cookies. Please name the providers and explain actual collection/consent behavior. Static initialization alone does not prove cookies are set or a privacy violation.

No-key access and the JSON CORS header did check out. Please address the feed scope, attribution and privacy wording; screenshots alone would not resolve the feed mismatch.

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.

2 participants

0