[jka]

This looks very neat!

Just a thought - one that could involve implementation challenges and/or require too much effort to be worthwhile:

It might be possible to generate iCalendar-format schedules, which could widen compatibility and ease up the access permissions concerns you mention in the readme.

Python has a decent icalendar[1] library - and updates to existing entries be handled by ensuring that the ID for each schedule object is stable when updates are distributed[2].

[1] - https://icalendar.readthedocs.io/en/latest/usage.html#exampl...

[2] - https://en.wikipedia.org/wiki/ICalendar#Distributing_updates

[X-Cubed]

iCalendar is a pretty nice format to use and well supported, but the trouble that you then need a website to host the iCalendar file. It adds more yak-shaving to the process.

[jka]

Yep, true; how you get the iCalendar file to the user could affect the requirements and experience a lot.

Web could work well for pull-based retrieval, and email's probably a good push option when you have a defined set of recipients.