We are dedicated to
- 🧑🚀 automating IT and security.
- 🪟 privacy, transparency, and trust through open source software.
- 💻 a better way to manage computers.
While GitLab's handbook inspires this handbook, it is nowhere near as complete (yet!) We will continue adding and updating this handbook and gradually migrating information from Fleet's shared Google Drive folder as time allows.
You can review more information about contributing to Fleet's handbook on this page Contributing to the handbook
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 submits patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open source code base, documentation, website, and company handbook.
The majority of the code, documentation, and content we create at Fleet is public and source-available. We strive to be 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. Learn more about why we use open source.
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
- 🟣 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.
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.
- Be considerate. Keep the needs of customers, contributors, and colleagues in mind. Treat others the way you’d like to be treated.
- Be curious. Ask questions. Try seeing situations from different perspectives. Use your imagination to find understanding.
- Remember the user. Prioritize product quality. Create patches with care. Fix bugs quickly. Take time writing error messages.
- Invest in hospitality. Apply customer service principles to all users. Be generous with your time. Think and say positive things.
Achieving ambitious goals requires reliability and initiative. That’s why we encourage every Fleetie to think like an owner. Your impact goes beyond the responsibilities of your role.
- Be accountable. Follow through on commitments. Own up to mistakes. Understand how your work furthers Fleet’s goals.
- Be responsive. Respond quickly whether or not you can take immediate action. Offer feedback freely (even if you disagree).
- Think bigger. Remember the big picture beyond your team's goals. Consider how Fleet creates value for customers.
- Take initiative. You don't need permission to be thoughtful. Think for yourself (from first principles). Great ideas come from everyone.
We work to get results. How we work determines the results we deliver. Between overthinking and rushing, there's a golden mean. We balance speed and sustainability to build high-quality products.
- Iterate your work. Look for ways to make frequent, small changes. Get perspective on complex problems. There may be a simpler solution.
- Move quickly. Aim to deliver results daily. "Everything is in draft." Resist gold-plating and avoid bike-shedding.
- Be efficient. Focus on fewer tasks at one time. Use fewer words when possible. Go with "boring solutions." Keep things simple.
- Practice self-care. Remember to take breaks. Schedule time off to recharge. Organize your workday to fit your lifestyle.
Our objective as a company is to make money. This is how we measure success. Customers pay for products that make a difference. Approach every project with this in mind.
- Be humble. Seek feedback and understanding. Remember, it’s rare to get things right the first time. Question yourself.
- Underpromise and overdeliver. Be practical about what's possible. But don’t settle for the “happy path” right away.
- Prioritize the truth. Feel free to change your mind in the face of new evidence. Avoid the sunk cost fallacy. Give credit where credit is due.
- Be rigorous. A lucky fix without understanding does more harm than good. When something isn't working, use the scientific method.
Openness leads to better products and stronger partnerships. Being open about your work isn’t always easy. But practicing this skill will help you throughout your career.
- Welcome contributions. Be friendly, inclusive, and approachable. Get comfortable letting others contribute to your domain.
- Embrace candor. Be positive and assume positive intent. Don’t be afraid to speak up. Give pointed and respectful feedback.
- Write everything down. Let people learn about your work. Use simple language. Avoid acronyms and idioms that might not translate.
- Be transparent. We build in the open. Everything we do is public by default. Declassify confidential information with care.
When Kolide's attention shifted away from Fleet, and towards their separate, user-focused SaaS offering, the Fleet community took over maintenance of the open source project. After his time at Kolide, Zach continued as lead maintainer of Fleet. He spent 2019 consulting and working with the growing open source community to support and extend the capabilities of the Fleet platform.
Zach partnered with our CEO, Mike McNeil, to found a new, independent company: Fleet Device Management Inc. In November 2020, we announced the transition and kicked off the logistics of moving the GitHub repository.
Fleet has a unique way of organizing work. For more information, check out this page Why this way.
Fleet organizes cross-functional groups focused on particular business goals. These include members from Design, Engineering, Quality, and Product. For more information, check out this page Development groups.
- Public (share with anyone, anywhere in the world)
- Confidential (share only with team members who've signed an NDA, consulting agreement, or employment agreement)
- Classified (share only with founders of Fleet, peepops, and/or the people involved. e.g., US social security numbers during hiring)
There are several special email addresses that automatically relay messages to the appropriate people at Fleet. Each email address meets a minimum response time ("Min RT"), expressed in business hours/days, and has a dedicated, directly responsible individual (DRI) who is responsible for reading and replying to emails sent to that address. You can see a list of those email addresses in "Contacting Fleet" (private Google doc).
There are a number of tools that are used throughout Fleet. Some of these tools are used company-wide, while others are department-specific. You can see a list of those tools in "Tools we use" (private Google doc).
We use special characters to define different types of GitHub labels. By combining labels, we
organize and categorize GitHub issues. This reduces the total number of labels required while
maintaining an expressive labeling system. For example, instead of a label called
platform-dev-backend, we use
#platform :dev ~backend.
|Special character||Label type||Examples|
|Weekly update reminder||Weekly||On Thursday, Charlie starts a thread in the
|Weekly update||Weekly||On Friday, Charlie updates the KPIs in the "🌈 Weekly updates" spreadsheet, combines the updates from managers into a single message and adds any hiring announcements. Charlie posts the company update in the
The following Slack channels are maintained by Fleet's founders and executive collaborators:
||N/A (announce something company-wide)|
||N/A (say thank you)|
||N/A (be random)|