Skip to content

Commit 5d08dd8

Browse files
committed
Add calendar emoji convention for Google Meet meetings
Adds a new Calendar Conventions section to the operations handbook documenting the use of 🎥 emoji for Google Meet calendar entries. This helps team members quickly identify meeting types in menubar apps and distinguishes Google Meet from Slack Huddles at a glance.
1 parent 2b763ec commit 5d08dd8

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

src/handbook/operations/index.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,19 @@ or go bankrupt a table is maintained with where to go in case of service disrupt
2828
| [Google Appointment Schedules](https://support.google.com/calendar/answer/10729749?hl=en) | Scheduling meetings with external parties | Calendly | - |
2929
| AWS | Hosting for FlowFuse Cloud | ? | - |
3030

31+
## Calendar Conventions
32+
33+
To help team members quickly identify meeting types in calendar apps and menubar tools, use these emoji conventions when creating calendar entries:
34+
35+
- 🎥 - Google Meet meetings (add this emoji to the event title for quick visual identification)
36+
37+
This convention is particularly helpful for:
38+
- Quick visual scanning in menubar calendar apps
39+
- Distinguishing Google Meet from Slack Huddles at a glance
40+
- Identifying external-facing meetings quickly
41+
42+
**Note:** For internal face-to-face discussions, prefer Slack Huddles in public channels over Google Meet when possible, as noted in the services table above.
43+
3144
## Email
3245

3346
While there are a number of email aliases and google groups used throughout the organization, there is some activities across operations, people operations, and finance management that requires that activities be done with external parties. As a redundancy, rather than use a person's individual email (e.g. zj@), we use a google group to avoid the risk of information getting lost. For example, for some government filings, we use ops@.

0 commit comments

Comments
 (0)