mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +00:00
Updating documentation DRIs (#18877)
Per our chat, we realized we need to have DRIs listed for specific documentation sections, as right now it is unclear who is responsible for some pages in docs. This PR aims to set an explicit DRI for every section and page in the docs. ... --------- Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
This commit is contained in:
Luke Heath
GitHub
parent
397f56ab1c
commit
5876681c78
1 changed files with 45 additions and 28 deletions
|
|
@ -18,35 +18,38 @@ We track competitors' capabilities and adjacent (or commonly integrated) product
|
|||
|
||||
| Area of responsibility | [DRI](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) |
|
||||
| -------------- | --- |
|
||||
| Revenue | <sup><sub>_See [🐋 Chief Revenue Officer](https://fleetdm.com/handbook/sales#team)_</sup></sub>
|
||||
| Pricing | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Illustrations | <sup><sub>_See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_</sup></sub>
|
||||
| Website | <sup><sub>_See [🌐 Digital Experience team](https://fleetdm.com/handbook/digital-experience#team)_
|
||||
| Product marketing (PMM) | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Brand marketing | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Public relations | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Revenue pipeline | <sup><sub>_See [🫧 Head of Demand Generation](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Ads | <sup><sub>_See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Video | <sup><sub>_See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Social media | <sup><sub>_See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Blog | <sup><sub>_See [🚀 Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_</sup></sub>
|
||||
| Information technology (IT) | <sup><sub>_See [🚀 Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_</sup></sub>
|
||||
| Payroll, bookkeeping, AR/AP | <sup><sub>_See [🔦 Head of Business Operations](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Legal contracts | <sup><sub>_See [🔦 Business Operations team](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Customer renewals | <sup><sub>_See [🌦️ VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Customer deployments | <sup><sub>_See [🌦️ Infrastructure Engineer](https://fleetdm.com/handbook/customer-success#team)_ </sup></sub>
|
||||
| Customer support | <sup><sub>_See [🌦️ Customer Success team](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Quality assurance (QA) | <sup><sub>_See [🚀 Engineering team](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Features & product adoption | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Feature prioritization | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Revenue | <sup><sub>_See [🐋 Chief Revenue Officer](https://fleetdm.com/handbook/sales#team)_</sup></sub>
|
||||
| Pricing | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Illustrations | <sup><sub>_See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_</sup></sub>
|
||||
| Website | <sup><sub>_See [🌐 Digital Experience team](https://fleetdm.com/handbook/digital-experience#team)_
|
||||
| Product marketing (PMM) | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Brand marketing | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Public relations | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Revenue pipeline | <sup><sub>_See [🫧 Head of Demand Generation](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Ads | <sup><sub>_See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Video | <sup><sub>_See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Social media | <sup><sub>_See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_</sup></sub>
|
||||
| Blog | <sup><sub>_See [🚀 Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_</sup></sub>
|
||||
| Information technology (IT) | <sup><sub>_See [🚀 Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_</sup></sub>
|
||||
| Payroll, bookkeeping, AR/AP | <sup><sub>_See [🔦 Head of Business Operations](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Legal contracts | <sup><sub>_See [🔦 Business Operations team](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Customer renewals | <sup><sub>_See [🌦️ VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Customer deployments | <sup><sub>_See [🌦️ Infrastructure Engineer](https://fleetdm.com/handbook/customer-success#team)_ </sup></sub>
|
||||
| Customer support | <sup><sub>_See [🌦️ Customer Success team](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
|
||||
| Quality assurance (QA) | <sup><sub>_See [🚀 Engineering team](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Features & product adoption | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Feature prioritization | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Intentionality of Fleet's interfaces | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Best practices for using Fleet | <sup><sub>_See [🦢 Product Design team](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Best practices for using Fleet | <sup><sub>_See [🦢 Product Design team](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| [API design](https://fleetdm.com/docs/rest-api/rest-api) | <sup><sub>_See [🦢 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Structure of the [docs](https://fleetdm.com/docs/get-started/why-fleet) | <sup><sub>_See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_</sup></sub>
|
||||
| Product reference documentation | <sup><sub>_See [🦢 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| What goes in a release | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Engineering output and architecture | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Product development | <sup><sub>_See [🛩️ Product groups](https://fleetdm.com/handbook/company/product-groups#current-product-groups)_ </sup></sub>
|
||||
| Product introduction docs | <sup><sub>_See [🛠️ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_</sup></sub>
|
||||
| Product deployment docs | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_</sup></sub>
|
||||
| Product usage docs | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| Product reference docs | <sup><sub>_See [🦢 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
|
||||
| What goes in a release | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Engineering output and architecture | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
|
||||
| Product development | <sup><sub>_See [🛩️ Product groups](https://fleetdm.com/handbook/company/product-groups#current-product-groups)_ </sup></sub>
|
||||
|
||||
### Docs
|
||||
This page details processes related to maintaining and updating the [Fleet documentation](https://fleetdm.com/docs).
|
||||
|
|
@ -59,6 +62,20 @@ Fleet's goal is to answer every question with a link to the docs and/or result i
|
|||
|
||||
> Fleet's philosophy on how to write useful documentation is public and open-source: ["Why read documentation?"](https://fleetdm.com/handbook/company/why-this-way#why-read-documentation)
|
||||
|
||||
The docs are separated into four categories:
|
||||
|
||||
1. [Get started](https://fleetdm.com/docs/get-started/why-fleet)
|
||||
|
||||
2. [Deploy](https://fleetdm.com/docs/deploy/introduction)
|
||||
|
||||
3. [Using Fleet](https://fleetdm.com/docs/using-fleet/fleet-ui)
|
||||
|
||||
4. Reference
|
||||
- [Configuration](https://fleetdm.com/docs/configuration/fleet-server-configuration)
|
||||
- [REST API](https://fleetdm.com/docs/rest-api/rest-api)
|
||||
- [Data tables](https://fleetdm.com/tables/account_policy_data)
|
||||
- [Built-in queries](https://fleetdm.com/queries)
|
||||
|
||||
## Fleetdm.com
|
||||
Any change to fleetdm.com follows the same process as [making changes](https://fleetdm.com/handbook/company/product-groups#making-changes) to the core product. To propose a change to Fleet's website [create a website request](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%23g-digital-experience&projects=&template=website-request.md&title=Request%3A+__________________________) on the #g-digital-experience kanban board.
|
||||
|
||||
|
|
@ -227,8 +244,8 @@ Fleet uses these levels to standardize a commitment to minimal esotericism acros
|
|||
- **"Public":** _(Available to public)_
|
||||
- _(Confidential - for Fleet eyes only)_
|
||||
- **"¶":** _(E-group - Direct reports the the CEO)_
|
||||
- **"¶¶":** _(Classified - Founders and BizOps)_
|
||||
- **"¶¶¶":** _(Founders and board members)_
|
||||
- **"¶¶":** _(Classified - CEO, Apprentice, and BizOps)_
|
||||
- **"¶¶¶":** _(CEO, Apprentice to the CEO, and board members)_
|
||||
|
||||
## Email relays
|
||||
There are [several special email addresses](https://docs.google.com/document/d/1tE-NpNfw1icmU2MjYuBRib0VWBPVAdmq4NiCrpuI0F0/edit#) that automatically relay messages to the appropriate people in Fleet. Each email address meets a minimum response time ("Min RT"), expressed in business hours/days, and has a dedicated, directly responsible individual (DRI) who is responsible for reading and replying to emails sent to that address.
|
||||
|
|
|
|||
Loading…
Reference in a new issue