Use Google team calendar to track operator duty (#6008, PR #6020)

OPERATOR.rst

@@ -63,6 +63,22 @@ Getting started as operator
 Operator jobs
 -------------
 
+First order of business: add a calendar event for the next scheduled operator
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+As soon as your shift begins and before performing any other actions as an
+operator create the following Google Calendar event in the `Team Boardwalk
+calendar`_.
+
+Create an all-day calendar event for the two weeks after your current stint,
+using the title ``Azul Operator: <name>`` with the name of the operator who will
+be serving next.
+
+If you are aware of any schedule irregularities, such as one operator performing
+more than one consecutive stints, create events for those as well.
+
+.. _`Team Boardwalk calendar`: https://calendar.google.com/calendar/u/0/r?cid=dWNzYy5lZHVfMDRuZ3J1NXQzNDB0aWd0cW5qYWQ5Nm5jOWtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
+
 Check weekly for Amazon OpenSearch Service updates
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -249,7 +265,7 @@ For an example of how to document failures within a PR `click here`_.
 .. _click here: https://github.com/DataBiosphere/azul/pull/3050#issuecomment-840033931
 
 Reindexing a specific catalog in GitLab
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+"""""""""""""""""""""""""""""""""""""""
 
 From the GitLab web app, select the ``reindex`` or ``reindex_early`` job for
 the pipeline that needs reindexing of a specific catalog. From there, you