From 49ebafa8599082013f5951fd96e785f530c2836c Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Tue, 23 Mar 2021 23:02:23 +0900 Subject: [PATCH] Add expense policy to Fleet handbook (#524) * Add expense policy to Fleet handbook * Removed stray "." * capitalization, + added a couple of other culture points that stand out Co-authored-by: Mike McNeil --- handbook/README.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/handbook/README.md b/handbook/README.md index df036acd73..151df57a81 100644 --- a/handbook/README.md +++ b/handbook/README.md @@ -15,7 +15,6 @@ We are dedicated to making Fleet the best management platform for [osquery](http ##### 2014: Origins of osquery In 2014, our CTO Zach Wasserman, together with [Mike Arpaia](https://twitter.com/mikearpaia/status/1357455391588839424) and the rest of their team at Facebook, created an open source project called [osquery](https://osquery.io). - ##### 2016: Origins of Fleet v1.0 A few years later, Zach, Mike Arpaia, and [Jason Meller](https://honest.security) founded [Kolide](https://kolide.com) and created Fleet: an open source platform that made it easier and more productive to use osquery in an enterprise setting. @@ -25,6 +24,27 @@ 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. + +### Culture + +### All remote +Fleet is an all-remote conpany, with teammates spread across 3 continents and 5 time zones. + +### Openness +The majority of the code, documentation, and content we create at Fleet is public and source-available, and we strive to be broadly open and transparent in the way we run the business; as much as confidentiality agreements (and time) allow. We perform better with an audience, and our audience performs better with us. + +### Spending company money +As we continue to expand our own company policies, we use [GitLab's expense policy](https://about.gitlab.com/handbook/spending-company-money/) as a guide for company spending. + +In brief, this means that as a Fleet team member, you may: + +* Spend company money like is is your own money. +* Be responsible for what you need to purchase or expense in order to do your job effectively. +* Feel free to make purchases __in the interest of the company__ without asking for permission beforehand (when in doubt, do __inform__ your manager prior to purchase, or as soon as possible after the purchase). + +For more detailed information about __spending guidelines and limits__, please read [GitLab's expense policy](https://about.gitlab.com/handbook/spending-company-money/) + + ### About the handbook #### Why bother? The Fleet handbook is inspired by (and heavily influenced by) the [GitLab team handbook](https://about.gitlab.com/handbook/about/). It shares the same [advantages](https://about.gitlab.com/handbook/about/#advantages) and will probably undergo a similar [evolution](https://about.gitlab.com/handbook/ceo/#evolution-of-the-handbook).