~~Nathan Holiday~~ => Business Operations
# 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)).
Vulnerability management positioning notes from Mike added as a linked
confidential document.
# 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: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
Added instructions on how to do it and an entry to the rituals table.
---------
Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
Add clarification about what "packs" are and why they aren't considered
deprecated in spite of removing the "Packs" section of the UI.
This is a modified version of [an
answer](https://osquery.slack.com/archives/C01DXJL16D8/p1685473347649069?thread_ts=1685447394.383489&cid=C01DXJL16D8)
@mikermcneil posted in the osquery slack. I trimmed a little bit of the
content in hopes of making this clearer (namely the specific list of
improvements that led to removing the "Packs" UI) but if you think that
context is too important to leave out I'll include it here.
.
---------
Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
Closes: https://github.com/fleetdm/fleet/issues/12385
Changes:
- Added a starting anchor to the regex route for Markdown article pages.
Currently, the regex route matches a sub-page in the engineering
handbook.
- Changed the `meta` title of the "Scaling Fleet" handbook page
It seems like we’ve been incorporating “emergency drafting” more
frequently into sprint cycles. This totally makes sense given that we
want to be an agile, design-driven company. It might be an easy cultural
win to instead call it something like “expedited drafting” to soften the
dissonance that comes from the sense of being in a constant state of
emergency.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [x] 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.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
asgdagsda
- [x] 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.
....
....
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Closes: #12361
Changes:
- Added an error to the `build-static-content` script that is thrown if
a a handbook page is missing a `maintainedBy` meta tag.
- Added a `maintainedBy` meta tag to
`handbook/company/head-of-public-sector.md`
I got [nerd sniped](https://en.wikipedia.org/wiki/Nerd_sniping) while
adding the QA process for the website and did some long overdue
housekeeping of the brand section of the handbook. There's still more to
do, but this is a good start.
## Changes
- Updated the `maintainedby` meta tag on `commonly-used-terms.md`
- Added a line break that I spotted on `content-style-guide.md`
- Moved the docs handbook content to its own page and linked to it from
the marketing page of the handbook to reduce the excessive scroll.
- Consolidated the Markdown instructions from the docs handbook section
into `markdown-guide.md` and linked to it from the relevant section of
the docs handbook page.
- Moved the website handbook content to its own handbook page and linked
to it from the marketing page of the handbook to reduce the excessive
scroll.
- Added quality assurance process to the website handbook page.
- Re-ordered the brand section of the handbook to show brand resources
and content style guide first.
## QA
- [x] Manual QA for all new/changed functionality
Proposed changes:
- I spotted a typo
- I updated references to previous staff members while reading.
- I spelled out "Executive Assistant" in the first couple of instances
and included "(EA)." It may seem an obvious acronym, but I'm a dumbo,
and the first time I heard EA mentioned, I thought we were talking about
Electronic Arts, the software developer. That is not entirely true, but
you get my point 😉
There are also two more references to @mentioning Charlie in Slack on
lines 148 and 150 that I don't know who to update to, so I have left
them untouched for the time being.
Closes#11965
Changes:
- Updated the pricing table on the pricing page to be rendered by the
server.
- Updated the pricing page's view action to create another version of
the pricing table that does not have the "Device management" category
and that has security features sorted to the top of the table.
- Moved two features from the "Device management" category to "Security
and compliance" in `pricing-features-table.yml`.
