mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Misc typo fixes (#8694)
* Misc. typo fixes in handbook * add change file Co-authored-by: Jacob Shandling <jacob@fleetdm.com>
This commit is contained in:
parent
6219de0723
commit
3c8fd12ebf
5 changed files with 5 additions and 4 deletions
1
changes/misc-handbook-typos
Normal file
1
changes/misc-handbook-typos
Normal file
|
|
@ -0,0 +1 @@
|
|||
* Fixed some small typos in the company handbook
|
||||
|
|
@ -336,7 +336,7 @@ There are some defaults that we use for these agreements:
|
|||
- Services rendered: [use this doc](https://docs.google.com/document/d/1b5SGgYEHqDmq5QF8p29WWN3it3XJh3xRT3zG0RdXARo/edit)
|
||||
- Work will commence and complete by dates: Start date and end of term date
|
||||
- Fee: Get from the contractor
|
||||
- Hours: Default to 10 hr/week = 40hr/week
|
||||
- Hours: Default to 10 hr/week - 40 hr/week
|
||||
Then hit send! After all of the signatures are there, the completed document will automatically be uploaded to the appropriate Google Drive folder, and a Slack message will appear in the `#g-people` channel.
|
||||
|
||||
#### Updating a consultant's fee
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ Empathy leads to better understanding, better communication, and better decision
|
|||
|
||||
- Think and make customer-first choices.
|
||||
- Consider your counterpart.
|
||||
- For example: keep in mind customers, contributors, colleagues, the other person in your Zoom meeting, the other folks in a Slack channel, and the people who use software and APIs you build, the people following the processes you design.
|
||||
- For example: keep in mind customers, contributors, colleagues, the other person in your Zoom meeting, the other folks in a Slack channel, the people who use software and APIs you build, and the people following the processes you design.
|
||||
- Ask questions in a way you would want to be asked.
|
||||
- Assume others have positive intent.
|
||||
- Be kind.
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ At Fleet, we keep everything in one repo. The only exception is when we're worki
|
|||
- One repo is easier to manage. It has less surface area for keeping content up to date and reduces the risk of things getting lost and forgotten.
|
||||
- Our work is more visible and accessible to the community when all project pieces are available in one repo.
|
||||
- One repo pools GitHub stars and more accurately reflects Fleet’s presence.
|
||||
- One repo means one set of automations and labels to manage. Resulting in a consistent GitHub experience that is easier to keep organized.
|
||||
- One repo means one set of automations and labels to manage, resulting in a consistent GitHub experience that is easier to keep organized.
|
||||
|
||||
## Why organize work in team-based kanban boards?
|
||||
It's helpful to have a consistent framework for how every team works, plans, and requests things from each other. Fleet's kanban boards are that framework, and they cover three goals:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
This Information Security Policy is intended to protect Fleet Device Management Inc's employees, contractors, partners, customers, and the company from illegal or damaging actions by individuals, either knowingly or unknowingly.
|
||||
|
||||
Internet/Intranet/Extranet-related systems are the property of Fleet Device Management Inc. This includes but not limited to
|
||||
Internet/Intranet/Extranet-related systems are the property of Fleet Device Management Inc. This includes, but is not limited to
|
||||
|
||||
- computer equipment.
|
||||
- software.
|
||||
|
|
|
|||
Loading…
Reference in a new issue