From ee7625c3da974f6b58208a4d2e6222d84325c1ee Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Wed, 22 Dec 2021 11:39:34 +0900 Subject: [PATCH] moving DRIs table to People (#3454) --- handbook/people.md | 24 +++++++++++++++++++++++- handbook/product.md | 27 +-------------------------- 2 files changed, 24 insertions(+), 27 deletions(-) diff --git a/handbook/people.md b/handbook/people.md index 2e86c96dc4..160cf62375 100644 --- a/handbook/people.md +++ b/handbook/people.md @@ -1,11 +1,33 @@ ## 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. To see who is DRI of what, see the [list of DRIs at Fleet](https://fleetdm.com/handbook/product#product-dr-is). +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 diff --git a/handbook/product.md b/handbook/product.md index 0a61a9f5e0..674232b273 100644 --- a/handbook/product.md +++ b/handbook/product.md @@ -1,30 +1,5 @@ -## Product DRIs - -Below is a table of [directly responsible individuals (DRIs)](./people.md#directly-resonsible-individuals) for aspects of the Fleet product: - -| 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 | - ## Feature flags + In Fleet, features are placed behind feature flags if the changes could affect Fleet's availability of existing functionalities. The following highlights should be considered when deciding if feature flags should be leveraged: