fleet/handbook/people.md

# People

## Directly responsible individuals

At Fleet we use the concept of directly responsible individuals (**DRI**s), a person who is singularly responsible for a given aspect of the open source project, the product, or the company.

This person is responsible for accomplishing goals and making decisions about a particular aspect of Fleet.

DRIs help us collaborate efficiently by knowing exactly who is responsible, and can make decisions about the work they're doing.

|    Aspect              										| DRI     		|
| ------------------------------------------------------------- | ------------- |
| Wireframes (figma)	 										| Noah Talerman	|
| How the product works 										| Noah Talerman |
| fleetctl CLI interface (and other tools) 						| Tomás Touceda |
| REST API interface design 							| Luke Heath	|
| [REST API docs](https://fleetdm.com/docs/using-fleet/rest-api) | Luke Heath | 
| Postman 											| Luke Heath 	|
| Terraform 											| Ben Edwards 	|
| Customer PoV deployments like acme.fleetdm.com 				| Ben Edwards 	|
| dogfood.fleetdm.com 											| Ben Edwards  	|
| Quality of core product UI 									| Luke Heath 	|
| Quality of tickets after Noah's done with them   				| Luke Heath 	|
| ["Escaped work"](https://docs.google.com/document/d/1vXL_WSUqASJWuNnQhUVrkudIeG4zlaiOCqJEa7xB2do/edit) | Luke Heath |
| Customer Slack channels | Tony Gauda |
| Quality of core product backend 									| Tomás Touceda |
| Quality of fleetctl (and other tools)							| Tomás Touceda |
| Final cut of what goes into each release 						| Zach Wasserman|
| When we cut a release, version numbers, and whether to release| Zach Wasserman|
| Release notes 												| Noah Talerman |
| Publishing release blog post, and promoting releases 			| Mike Thomas  	|

>You can read more about directly responsible individuals in [Gitlab's handbook](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/)

## Spending company money
As we continue to expand our own company policies, we use [GitLab's open expense policy](https://about.gitlab.com/handbook/spending-company-money/) as a guide for company spending.

In brief, this means that as a Fleet team member, you may:

* Spend company money like it is your own money.
* Be responsible for what you need to purchase or expense in order to do your job effectively.
* Feel free to make purchases __in the interest of the company__ without asking for permission beforehand (when in doubt, do __inform__ your manager prior to purchase, or as soon as possible after the purchase).

For more developed thoughts about __spending guidelines and limits__, please read [GitLab's open expense policy](https://about.gitlab.com/handbook/spending-company-money/).

## Meetings

* At Fleet, meetings start whether you're there or not. Nevertheless, being even a few minutes late can make a big difference and slow your meeting counterparts down. When in doubt, show up a couple of minutes early.
* It's okay to spend the first minute or two of a meeting to be present and make small talk, if you want.  Being all-remote, it's easy to miss out on hallway chatter and human connections that happen in [meatspace](https://www.dictionary.com/browse/meatspace).  Why not use this time together during the first minute to say "hi"?  Then you can jump in to the topics being discussed.
* Turning on your camera allows for more complete and intuitive verbal and non-verbal communication.  When joining meetings with new participants who you might not be familiar with yet, feel free to leave your camera on or to turn it off.  When you lead or cohost a meeting, turn your camera on.
* In an all-remote company, “face time” matters. Remember: even if someone’s calendar is open, they have other work to do. Limiting (or batching up) internal meetings can enable longer, uninterrupted stretches of deep work.

### Internal meeting scheduling

Use the Google Calendar [find a meeting
time](https://support.google.com/calendar/answer/37161?hl=en&co=GENIE.Platform%3DDesktop#zippy=%2Cfind-a-meeting-time)
feature to coordinate meetings with Fleet team members. Enter the `@fleetdm.com` emails for each
participant into the "Meet with..." box in Google Calendar and the calendar availability for each
participant will appear in your view. Then, when you select a meeting time, those participants will
automatically be invited and a video conference will be attached to the invite.

Please prefer this strategy over negotiating meeting times via chat -- This can save a lot of
communication overhead, especially when scheduling with multiple participants.

It is important to [set your working
hours](https://support.google.com/calendar/answer/7638168?hl=en&co=GENIE.Platform%3DDesktop) in
Google Calendar, and block out any personal time/events/PTO so that team members do not inadvertently
schedule time when you are not available. Many team members use the free tier of
[reclaim.ai](https://reclaim.ai/) to synchronize personal event times (without event details) into
their work calendars. It is also common practice to block out time for focused work.

### External meeting scheduling

When scheduling external meetings, provide external participants with a
[Calendly](https://calendly.com) link to schedule with the relevant internal participants. If you
need a Calendly account, reach out to `@eashaw` via Slack.

## Slack

At Fleet, we do not send internal emails to each other. Instead, we prefer to use Slack to communicate with other folks who work at Fleet.

We use threads in Slack as much as possible. Threads help limit noise for other people following the channel and reduce notification overload.

We configure our working hours in Slack to ensure everyone knows when they can get in touch with others.

### Slack channels

We have specific channels for various topics, but we also have more general channels for the teams at Fleet.

We use these prefixes to organize the Fleet Slack:
 * ***g-***: for team/group channels. *(Note: "g-" is short for "grupo")*
 * ***oooh-***: used to discuss and share interesting information about a topic.
 * ***help-***: for asking for help on specific topics.
 * ***at*** or ***fleet-at***: for customer channels.

<meta name="maintainedBy" value="eashaw">