Rust Berlin Calendars

This repository defines the calendars for the Rust Berlin group. Calendars per event are defined in their respective TOML files 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.

Events will be generally also announced on https://berline.rs/.

How do I subscribe to these calendars?

Each of the toml files in this repository generates an ics file of the same name at https://berlinrs.github.io/calendar/$name.ics. Below are links to the ics files for all the current calendars in this repository:

• All
  • Rust Hack and Learn
  • Rust Berlin Talks
  • Rust Berlin on Location

You can copy these links and import them into your calendar application of choice.

How do I add a calendar?

Add a new file in the repository with an appropriate name. Add the path to the meta.includes list in all.toml.

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?.

How do I remove a calendar?

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.

How do I add an event?

First, select a TOML file that is relevant for your event - we can always add new events!

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 = { date = "2024-01-11T15:00:00.00", timezone = "Europe/Berlin" }
end = { date = "2024-01-11T16:00:00.00", timezone = "Europe/Berlin" }
status = "confirmed"
organizer = { name = "Who is running the event", email = "What is their email" } # optional

All dates must be in RFC 3339 format (the same as in the examples above), and should list the timezone.

Each event have a globally UID (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, see How to generate a UID for an event?.

See What is the schema for the calendars? for a list of options you can set in an event.

How do I update an event?

Modify whatever details you like - except uid, which should never be changed

• and make sure to update last_modified_on. Some clients use last_modified_on to decide whether to publish an update to an event or recurrence or not. To ensure the client will publish the event, set last_modified_on to a value in the future (a few days past the current date should be enough).

How do I generate a UID for a new event?

To generate a UID, run:

date +%s%N | cut -b1-13

Use the printed value as the uid for the event.

How do I remove an event?

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" } ]

What is the schema for the calendars?

You can see the example.toml from the calendar-generation repository for a complete list of all supported configuration options.

Testing and validating calendar files

To test that your calendar changes work, you can install the calendar generation tool and generate the all.ics calendar (which should include every other calendar, but you can run it on a specific file too).

$ cargo install --git https://github.com/rust-lang/calendar-generation.git
$ toml-to-ical -i all.toml -o /dev/null

Sources

Based on rust-lang/calendar. Licensed under MIT.