mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Define okrs, change labels (#9964)
# Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/` or `orbit/changes/`. See [Changes files](https://fleetdm.com/docs/contributing/committing-changes#changes-files) for more information. - [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or docs/Contributing/API-for-contributors.md) - [ ] Documented any permissions changes - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for new osquery data ingestion features. - [ ] Added/updated tests - [ ] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [ ] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [ ] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)).
This commit is contained in:
parent
7b1e63189e
commit
f94ec3e535
1 changed files with 1 additions and 2 deletions
|
|
@ -35,7 +35,7 @@ We use the Zoom add-on for Google Calendar to schedule Zoom meetings when we cre
|
|||
We configure our Zoom meetings to let participants join before the host starts the meeting. We do this to make sure meetings start on time, even if the host isn't there.
|
||||
|
||||
### Key reviews
|
||||
Every release cycle, each department leader prepares a [key review deck](https://about.gitlab.com/handbook/key-review/#purpose) and presents it to the CEO. In this deck, the department will highlight KPI metrics and progress of OKRs. The information for creating this deck is located in the ["🌈 Fleet" Google drive](https://drive.google.com/drive/folders/1lizTSi7YotG_zA7zJeHuOXTg_KF1Ji8k) using ["How to create key review"](https://docs.google.com/document/d/1PDwJL0HiCz-KbEGZMfldAYX_aLk5OVAU1MMSgMYYF2A/edit?usp=sharing)(internal doc).
|
||||
Every release cycle, each department leader prepares a [key review deck](https://about.gitlab.com/handbook/key-review/#purpose) and presents it to the CEO. In this deck, the department will highlight KPI metrics (numbers measuring everyday excellence) and progress of timebound goals for a particular quarter (OKRs). The information for creating this deck is located in the ["🌈 Fleet" Google drive](https://drive.google.com/drive/folders/1lizTSi7YotG_zA7zJeHuOXTg_KF1Ji8k) using ["How to create key review"](https://docs.google.com/document/d/1PDwJL0HiCz-KbEGZMfldAYX_aLk5OVAU1MMSgMYYF2A/edit?usp=sharing)(internal doc).
|
||||
|
||||
|
||||
## Spending company money
|
||||
|
|
@ -193,7 +193,6 @@ maintaining an expressive labeling system. For example, instead of a label calle
|
|||
| `#` | Noun | `#platform`, `#interface`, `#agent`
|
||||
| `:` | Verb | `:dev`, `:research`, `:design`
|
||||
| `~` | Adjective | `~blocked`, `~frontend`, `~backend`
|
||||
| `!` | OKR | `!vuln`, `!desktop`, `!upgrade`
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue