empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 17:05:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Include "Why should you join us?" (#9955)

Browse Source 
. .
This commit is contained in:
Mike McNeil 2023-02-20 14:43:24 -06:00 committed by GitHub
parent b8811f04e5
commit f197d8dbe1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 44 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
handbook/company/README.md
View File

@ -2,7 +2,7 @@
## Purpose
Fleet Device Management Inc is an [open-core company](https://www.heavybit.com/library/video/commercial-open-source-business-strategies/) that sells subscriptions that offer [more features and support](https://fleetdm.com/pricing) for Fleet and [osquery](https://osquery.io), the leading open source endpoint agent.
Fleet Device Management Inc is an [open-core company](https://fleetdm.com/handbook/company/why-this-way#why-this-way) that sells subscriptions that offer [more features and support](https://fleetdm.com/pricing) for Fleet and osquery, the leading open-source security agent. Today, Fleet enrolls millions of laptops and servers, and it is especially popular with [enterprise IT and security teams](https://www.linuxfoundation.org/press/press-release/the-linux-foundation-announces-intent-to-form-new-foundation-to-support-osquery-community).
We are dedicated to:
@ -14,17 +14,13 @@ We are dedicated to:
## Culture
### All remote
Fleet Device Management Inc. is an all-remote company with team members spread across four continents and eight time zones. The broader team of contributors [worldwide](https://github.com/fleetdm/fleet/graphs/contributors) submits patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open-source code base, documentation, website, and [company handbook](https://fleetdm.com/handbook/company/why-this-way#why-handbook-first-strategy).
Fleet Device Management Inc. is an all-remote company with 30+ team members spread across four continents and eight time zones. The broader team of contributors [worldwide](https://github.com/fleetdm/fleet/graphs/contributors) submits patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open-source code base, documentation, website, and [company handbook](https://fleetdm.com/handbook/company/why-this-way#why-handbook-first-strategy).
### Open source
The majority of the code, documentation, and content we create at Fleet is public and source-available. The Fleet handbook is the central guide for how we run the company, and even it is open to the world. We [strive to be open](https://fleetdm.com/handbook/company/why-this-way#why-open-source) 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.
The majority of the code, documentation, and content we create at Fleet is public and source-available. The Fleet handbook is the central guide for how we run the company, and even it is open to the world. We [strive to be open](https://fleetdm.com/handbook/company/why-this-way#why-open-source) 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](https://fleetdm.com/handbook/company/why-this-way#why-open-source) with us.
### Why this way?
At Fleet, we rarely label ideas as drafts or theories. Everything is [always in draft](https://about.gitlab.com/handbook/values/#everything-is-in-draft) and subject to change in future iterations. But to get [results](https://fleetdm.com/handbook/company#results), we need to balance being smart with moving quickly. That means embracing decisiveness in the face of uncertainty.
To increase clarity and encourage teams to make decisions quickly, leaders and [DRIs (directly responsible individuals)](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) should explicitly mention when they are voicing an opinion or a decision. When an [opinion](https://blog.codinghorror.com/strong-opinions-weakly-held/) is voiced, there's space for near-term debate. When a [decision](https://about.gitlab.com/handbook/values/#disagree-commit-and-disagree) is voiced, team commitment is required.
The ["Why this way?"](https://fleetdm.com/handbook/company/why-this-way) page discusses some of Fleet's decisions about the best way to work. For example: ["Why open source?"](https://fleetdm.com/handbook/company/why-this-way#why-open-source) and ["Why do we use a wireframe-first approach?"](https://fleetdm.com/handbook/company/why-this-way#why-do-we-use-a-wireframe-first-approach) and ["Why handbook-first strategy?"](https://fleetdm.com/handbook/company/why-this-way#why-handbook-first-strategy).
At Fleet, we write things down. Even when we might be wrong. This helps us move quickly, provides clarity, and enables asynchronous work. The "Why this way?" page in the handbook discusses some of our most important decisions about the best way to work and the reasoning for them. For example: _"Why open source?"_, _"Why do we use a wireframe-first approach?"_, _"Why direct responsibility?_, and _"Why handbook-first strategy?"_ You can read more about these principles and suggest improvements in ["Why this way?"](https://fleetdm.com/handbook/company/why-this-way)
## Open positions
@ -36,29 +32,26 @@ Fleet is currently hiring for the following positions:
- 🫧 [Revenue Operations Manager](https://fleet-device-management.breezy.hr/p/c28cce9abf5e-revenue-ops)
- 🫧 [Field Marketer](https://fleet-device-management.breezy.hr/p/3bd97ce5f54a-field-marketing-manager-enterprise)
> Interested in joining the team at Fleet, or know someone who might be? Click one of the positions to read the job description and apply, or you can share a [direct link to this page](https://fleetdm.com/handbook/company) for a short read about the company, including our vision, values, history, and all currently open positions. Thank you for the help!
> Interested in joining the team at Fleet, or know someone who might be? Click one of the positions to read the job description and apply, or you can share a [direct link to this page](https://fleetdm.com/handbook/company#open-positions) for a short read about the company, including our vision, values, history, and all currently open positions. Thank you for the help!
### Is it any good?
Why should you join us? 🛸
- Work from anywhere with good internet. (We're 100% remote. No office. No commute.) Everyone works remote, but you don't feel remote. There is no 'headquarters'. You are free to travel and move.
- Fleet can offer you a competitive salary, significant equity, and an independent, outsider-friendly culture. Work with helpful, kind, and motivated people who know what they're doing.
- At Fleet, we value focus, iteration, and meaningful results – not 60 hour work weeks. We are non-judgmental and laser-focused on growing the company.
- Work closely with experienced, well-funded founders and a great team, including the people who created osquery and Sails. We care about openness and transparency.
- Work computers can be private and safe. Help make endpoint monitoring less intrusive and more transparent.
- Protect the production servers and employee laptops of Earth's largest companies. Work on a product used by lots of people who care about what you do.
- Fleet is growing quickly, with significant revenue from Fortune 1000 customers. You will have lots of opportunities to make decisions, learn, and try new things.
## Org chart
## Values
Fleet's organizational chart is accessible as a sub-tab in ["🧑‍🚀 Fleeties" (private google doc)](https://docs.google.com/spreadsheets/d/1OSLn-ZCbGSjPusHPiR5dwQhheH1K8-xqyZdsOe9y7qc/edit#gid=0). On the other sub-tabs, you can also check out a world map of where everyone is located, hiring stats, and fun facts about each team member.
Fleet's values are a set of five ideals adopted by everyone on the team. They describe the culture we are working together to deliver, inside and outside the company: 🔴 Empathy, 🟠 Ownership, 🟢 Results, 🔵 Objectivity, and 🟣 Openness.
## Product groups
Fleet organizes cross-functional groups focused on particular business goals. These include the product quality lead, a designer, developers, a product manager, and an engineering manager. For more information, check out the ["Product groups"](./development-groups.md) page.
## 🌈 Values
Fleet's values are a set of five ideals adopted by everyone on the team. They describe the culture we are working together to deliver, inside and outside the company:
1. 🔴 Empathy
2. 🟠 Ownership
3. 🟢 Results
4. 🔵 Objectivity
5. 🟣 Openness
When a new team member joins Fleet, they adopt the values, from day one. This way, even as the company grows, everybody knows what to expect from the people with whom they work. Having a shared mindset keeps us quick and determined.
Values play an important role in hiring, performance management, and compensation decisions. When a new team member joins Fleet, they adopt the values, from day one. This way, even as the company grows, everybody knows what to expect from the people they work with. Having a shared mindset keeps us quick and determined.
### 🔴 Empathy
Empathy leads to better understanding, better communication, and better decisions. Try to understand what people may be going through, so you can help make it better.
@ -115,6 +108,8 @@ When Kolide's attention shifted away from Fleet, and towards their separate, use
### 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.
### 2022: Millions of hosts
Fleet raised its Series A funding round. The world now has at least 1.65 million computers and virtual hosts enrolled in Fleet, including enterprises, governments, startups, families, and hobbyist racks all over the world.
## Slack channels

28
handbook/company/why-this-way.md
View File

@ -1,10 +1,12 @@
# Why this way?
Here are some of Fleet's decisions about the best way to work, and the reasoning for them.
At Fleet, we rarely label ideas as drafts or theories. Everything is [always in draft](https://about.gitlab.com/handbook/values/#everything-is-in-draft) and subject to change in future iterations.
To increase clarity and encourage teams to make decisions quickly, leaders and [DRIs](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) sometimes need to explicitly mention when they are voicing an [opinion](https://blog.codinghorror.com/strong-opinions-weakly-held/) or a [decision](https://about.gitlab.com/handbook/values/#disagree-commit-and-disagree). When an _opinion_ is voiced, there's space for near-term debate. When a _decision_ is voiced, team commitment is required.
Any past decision is open to questioning in a future iteration, as long as you act in accordance with it until it is changed. When you want to reopen a conversation about a past decision, communicate with the [DRI (directly responsible individual)](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) who can change the decision instead of someone who can't. Show your argument is informed by previous conversations, and assume the original decision was made [with the best intent](https://about.gitlab.com/handbook/values/#assume-positive-intent).
Fleet's CEO is the directly-responsible individual for the decisions on this handbook page.
Here are some of Fleet's decisions about the best way to work, and the reasoning for them.
## Why open source?
@ -50,12 +52,21 @@ Like Apple and GitLab, Fleet uses the concept of [directly responsible individua
A DRI is a person who is singularly responsble for a given aspect of the open-source project, the product, or the company. A DRI is responsible for making decisions, accomplishing goals, and getting any resources necessary to make a given area of Fleet successful.
For example, every department maintains its own dedicated [handbook page](https://fleetdm.com/handbook), with a single DRI, and which is kept up to date with accurate, current information, including the group's [kanban board](https://github.com/orgs/fleetdm/projects?type=beta), Slack channels, and recurring tasks ("rituals").
For example, every department maintains its own dedicated [handbook page](https://fleetdm.com/handbook), with a single DRI, and which is kept up to date with accurate, current information, including the group's kanban board, Slack channels, and recurring tasks ("rituals").
DRIs help us collaborate efficiently by knowing exactly who is responsible and can make decisions about the work they're doing. This saves time by eliminating a requirement for consensus decisions or political presenteeism, enables faster decision-making, and ensures a single individual is aware of what to do next.
You can view DRIs in:
1. The [CODEOWNERS files](https://github.com/fleetdm/fleet/blob/main/CODEOWNERS) of the fleetdm/fleet and fleetdm/confidential repositories.
### Org chart
To provide clarity about decision-making, responsibility, and resources, everyone at Fleet has a manager, and every manager has direct reports. Fleet's organizational chart is accessible company-wide as a sub-tab in ["🧑‍🚀 Fleeties" (private google doc)](https://docs.google.com/spreadsheets/d/1OSLn-ZCbGSjPusHPiR5dwQhheH1K8-xqyZdsOe9y7qc/edit#gid=0). On the other sub-tabs, you can also check out a world map of where everyone is located, hiring stats, and fun facts about each team member.
### Product groups
Fleet organizes additional, cross-functional groups focused on particular business goals. These include the product quality lead, a designer, developers, a product manager, and an engineering manager. For more information, check out the ["Product groups"](./development-groups.md) page.
### Reviewers
Fleet aims to make picking the right reviewer for your change as easy and automatic as possible. In many cases, you won't need to select a particular reviewer for your pull request. (It will just happen automatically.)
To check out the right person to review a given piece of content or source code path, consider:
1. The [CODEOWNERS](https://github.com/fleetdm/fleet/blob/main/CODEOWNERS) files of the fleetdm/fleet and fleetdm/confidential repositories.
2. The `name="maintainedBy"` tags at the very bottom of the raw markdown source for [every handbook page](https://github.com/fleetdm/fleet/tree/main/handbook) and [individual article](https://github.com/fleetdm/fleet/tree/main/articles).
3. The job titles and reporting structure indicated by the [company's organizational chart](https://fleetdm.com/handbook/company#org-chart) and the roles in our [cross-functional product groups](https://fleetdm.com/handbook/company#product-groups).
@ -79,14 +90,19 @@ Here's why we use a wireframe-first approach at Fleet.
- Wireframing is important for both maintaining the quality of our work and outlining what work needs to be done.
- With Figma, thanks to its powerful component and auto-layout features, we can create high-fidelity wireframes - fast. We can iterate quickly without costing more work and less [sunk-cost fallacy](https://dictionary.cambridge.org/dictionary/english/sunk-cost-fallacy).
## Why do we use one repo?
At Fleet, we keep everything in one repo. The only exception is when we're working on something confidential since GitHub does not allow confidential issues inside public repos. Here's why:
At Fleet, we keep everything in one repo ([`fleetdm/fleet`](https://github.com/fleetdm/fleet)). Here's why:
- 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.
The only exception ([`fleetdm/confidential`](https://github.com/fleetdm/confidential)) is when we're working on something confidential since GitHub does not allow confidential issues inside public repos.
> Tip: Did you know that you can [search through issues from both repos](https://github.com/issues?q=archived%3Afalse+org%3Afleetdm+is%3Aissue+is%3Aopen+) at the same time? In addition to the built-in search in the handbook on fleetdm.com, you can also search for any content from the handbook, documentation, or issue templates from either repo [using GitHub search](https://github.com/search?q=org%3Afleetdm+path%3A.github%2FISSUE_TEMPLATE+path%3Ahandbook%2F+path%3Adocs%2F+foo&type=code).
## Why not continuously generate REST API reference docs from javadoc-style code comments?
Here are a few of the drawbacks that we have experienced when generating docs via tools like Swagger or OpenAPI, and some of the advantages of doing it by hand with Markdown.