summaryrefslogtreecommitdiff
path: root/communication
diff options
context:
space:
mode:
authorparispittman <parispittman@google.com>2019-03-20 02:29:14 -0700
committerparispittman <parispittman@google.com>2019-03-20 02:36:36 -0700
commitd7ca367ed1ba14442e107eb82df1960064399c49 (patch)
treeaa822bd64e3f7eb979d8da099a16054e4c1327b6 /communication
parent32b54fb1b7d0dfd4eccd83dc9f7b2f2aecf9e20e (diff)
calendar clean up
Diffstat (limited to 'communication')
-rw-r--r--communication/calendar-guidelines.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/communication/calendar-guidelines.md b/communication/calendar-guidelines.md
index 67721396..45fa80db 100644
--- a/communication/calendar-guidelines.md
+++ b/communication/calendar-guidelines.md
@@ -35,7 +35,6 @@ Best advice here is to recreate one. It won't hurt to recreate a meeting invite
Make sure your work account doesn't have restrictions for public viewing of calendar invites you create. Test this with other contributors before sending it to mailing lists if you are unsure. This would be for both the calendar entry itself and the shared calendar if you are the chair creating it.
If this is the case, use a personal account (ex: gmail).
-
#### If you are viewing calendar events:
TODO