Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Add first draft of values to Fleet handbook (#2498)

Browse source 
* Update company.md

* updated h5 styles, add values section
This commit is contained in:
eashaw 2021-10-12 23:54:48 -05:00 committed by GitHub
parent b3e492d10b
commit 01d38150c8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 37 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/README.md
View file

@ -8,6 +8,8 @@ The Fleet handbook is the central guide for how we run the company. As part of o
[History](./company.md#history)
[Values](./company.md#values)
[Culture](./company.md#culture)
### People

32
handbook/company.md
View file

@ -18,6 +18,38 @@ When Kolide's attention shifted away from Fleet and towards their separate, user
### 2020: Fleet was incorporated
Zach partnered with our CEO, Mike McNeil, to found a new, independent company: Fleet Device Management Inc. In November 2020, we [announced](https://medium.com/fleetdm/a-new-fleet-d4096c7de978) the transition and kicked off the logistics of moving the GitHub repository.
## Values
### Quickly with craft
##### Iterate by taking baby steps.
We try to always make the minimum viable change. Small changes provide faster feedback, and help us to stay focused on quality.
##### Help each other get all the way done.
We collaborate and help our teammates to see tasks through to completion.
##### Focus on fewer tasks at one time.
By focusing on fewer tasks at once, we are able to get more done, and to a higher standard, while feeling more positive about our work in the process.
##### Role play as a user.
When making changes, we put ourselves in the mindset of the end user. We keep in mind how someone might use the product for the first time, or how an existing user might react to a new change.
##### Reread anything you write for users.
We check everything that a user might read for clarity, spelling errors, and to make sure that it provides value.
##### Review and merge PRs daily.
We value constant iteration and feedback. Reviewing and merging PRs daily keeps our open source community thriving.
### Patch with care
Patches improve security, usability, and performance. We may cut a patch release if there is a security concern, previously stable features are unusable, or if a new feature advertised in the current release is unusable.
## Culture

6
website/assets/styles/pages/handbook/basic-handbook.less vendored
View file

@ -187,9 +187,9 @@
margin-bottom: 0px;
}
h5 {
font-weight: normal;
font-size: 14px;
margin-top: 16px;
font-weight: 700;
font-size: 16px;
padding-top: 16px;
margin-bottom: 16px;
}
a {