This repository defines the calendars for the teams of the Rust project. Each team or working group can define a TOML file listing their events and a iCalendar file will be generated and hosted on GitHub Pages for contributors and interested parties to add to their calendar application of choice.
Some teams had previously used Google Calendar for their team calendar, but this wasn't ideal as permissions to update and add to the calendar had to be managed manually by team leads using a platform that the project otherwise didn't use. In contrast, everyone in the project already has a GitHub account and we already have processes and tooling in place to manage access to GitHub repositories.
Each of the toml files in this repository generates an ics file of the same name at
https://rust-lang.github.io/calendar/$name.ics. Below are links to the ics files for all the
current calendars in this repository:
- All teams and working groups
You can copy these links and import them into your calendar application of choice.
Add a new file in the repository with an appropriate name. Add the path to the meta.includes list
of any other calendars where that makes sense. For example, top-level team calendars are included
by all.toml, and working group calendars are included by their team's calendar.
In the new file, copy the following snippet to get started:
name = "Name your calendar"
description = "Describe your calendar"
[meta]
includes = [ ]Add any new calendars to the list above in How do I subscribe to these calendars?.
We shouldn't remove calendars, we can just stop using them - we can rename the files in this
repository to have an archived- prefix if we want.
First, select a TOML file that is relevant for your event - normally a team or working group's calendar will be appropriate.
Next, add a events table with the correct details for your event. You can copy the following
snippet to get started:
[[events]]
uid = "UID - see below!"
title = "Name your event"
description = "Describe your event"
location = "Where does the event take place - Zoom, Zulip?"
last_modified_on = "2024-01-05T15:46:00.00Z"
start = "2024-01-11T15:00:00.00Z"
end = "2024-01-11T16:00:00.00Z"
status = "confirmed"
organizer = { name = "Who is running the event", email = "What is their email (or team's email)" }All dates must be in RFC 3339 format (the same as in the examples above), and must be in UTC (ending
in Z).
Each event have a globally unique identifier (because calendars can be included in other calendars, they must be globally unique for this whole repository). It should never be changed after the calendar has been published. Just use the current UNIX time to basically guarantee that you don't overlap with anything or anyone else.
On Linux, you can get the current UNIX time with date +%s%N | cut -b1-13, and on Windows, with
PowerShell, ([DateTimeOffset]::UtcNow).ToUnixTimeMilliseconds(). Alternatively, you can copy the
current UNIX time from a website like currentmillis.com.
See What is the schema for the calendars? for a list of options you can set in an event.
Modify whatever details you like - except uid, which should never be changed - and make sure
to update last_modified_on.
On Linux, you can get the current time in the right format in UTC with the command
TZ=UTC date -u +"%Y-%m-%dT%H:%M:%S.%2NZ".
If the event isn't recurring, then you don't need to remove it, it'll just stay in the calendar in the past. If the event is incorrect, you can always update it, see How do I update an event?.
If the event is recurring, add until to the recurrence rules to stop the event atthe current date,
preventing future recurrences. For example, this rule..
recurrence_rules = [ { frequency = "weekly" } ]..would become..
# replace `until` with today's date
recurrence_rules = [ { frequency = "weekly", until = "2024-01-08T13:50:00.00Z" } ]You can see the example.toml from the calendar-generation
repository for a complete list of all supported configuration options.