From 5af8392615d70afcc31c013c4dca59206b7f2cc1 Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Tue, 14 May 2024 08:49:33 -0500 Subject: [PATCH] Update why-this-way.md (#18980) # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://fleetdm.com/docs/contributing/committing-changes#changes-files) for more information. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for new osquery data ingestion features. - [ ] Added/updated tests - [ ] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [ ] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [ ] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [ ] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)). --- handbook/company/why-this-way.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/handbook/company/why-this-way.md b/handbook/company/why-this-way.md index 5fe726ce66..dcc754269a 100644 --- a/handbook/company/why-this-way.md +++ b/handbook/company/why-this-way.md @@ -8,6 +8,9 @@ Any past decision is open to questioning in a future iteration, as long as you a Here are some of Fleet's decisions about the best way to work, and the reasoning for them. +image + + ## Why open source? Fleet's source code, website, documentation, company handbook, and internal tools are [public](https://github.com/fleetdm/fleet) and accessible to everyone, including engineers, executives, and end users. (Even [paid features](https://fleetdm.com/pricing) are source-available.)