Adding marketing experimentation guidelines to handbook
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] 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
- [ ] 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)).
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Moved sales paragraph onto 'Why this way' page in the same heading
format including the 'cold-outbound-strategy' URL (I can't figure out
how to edit URL text so it says 'Our sales strategy')
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] 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
- [ ] 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)).
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] 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
- [ ] 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)).
* Update why-this-way.md
These edits address items 6 and 9 from the handbook notes doc: https://docs.google.com/document/d/17BhgTqCI5255RY71m5ri3nDx71DqmfYwyJmRe_nJ4Ns/edit?usp=sharing.
The content for Why open source? identifies benefits and addresses security concerns. I ended this section with a sort of call to action. This differs from other content in Why this way, but it seemed like a good opportunity. If this feels too aggressive, I can cut the Results section.
I've consolidated the bullets for every company values, as well as wrote summaries for the values that didn't have them. The goal is to make each value more distinct and easier to understand.
* Update README.md
* Update README.md
* Handbook: Openness value
adding the Q&A session to the "why this way" page
* Update handbook/company/why-this-way.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update why-this-way.md
I revised the copy Charlie provided for two main reasons.
First, to keep formatting on the page consistent by removing the Q&A framework.
Second, to apply Mike's rationale from the Slack conversation to speak about Openness more broadly. People who find this section won't have the Slack conversation for context. Stepping back a bit will make this more approachable. However, I'm happy to add more detail if necessary.
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Create why-this-way.md
Moved "Why this way" to it's own page within Company handbook.
* Create development-groups.md
Added new page development-groups.md to Company handbook.
* Update README.md
Added space for Charlie to write summary for our new sections and add links to the nested pages.
* Update development-groups.md
Added meta tags to the page.
* Update why-this-way.md
* Update why-this-way.md
Changed head hierarchy to populate sub nav.
* preamble and links to sub pages
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
