Changes:
- Combined the experimentation and landing page section on the
communications handbook page.
- Removed the note about the /imagine process on the "Why this way?"
handbook page.
# 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 (docs/Using
Fleet/manage-access.md)
- [ ] 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
- [x] 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)).
1. Process to formalize how we prioritize bugs across teams, recognize a
bug's origin, and indicate the team who is currently working on it.
2. Formalize that this coordination will happen at a joint sprint
kick-off review (there are currently separate sprint kick-off reviews
for each team).
---------
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Once bugs have been settled, they should be removed from the drafting
board and moved into the 'to be scheduled' column of the bugs board so
that the PM knows they need to be prioritized into the sprint backlog.
---------
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.
- [ ] 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 (docs/Using
Fleet/manage-access.md)
- [ ] 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)).
1. **Transition to Feature Fest board** to better manage requests and
streamline communication with requestors.
2. **Introduce KPI for customer requests** to monitor customer-driven
development.
3. **Feature Fest cleanup** adjusted to include Product Ops and new
board process.
@zhumo I haven't broken down the new KPIs (for the sake of using less
words) but WDYT?
---------
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.
- [ ] 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 (docs/Using
Fleet/manage-access.md)
- [ ] 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>
Changes:
- removed a closing tag that had no opening tag on `basic-article.ejs`.
- fixed lint errors in the `basic-article.less`
- Fixed the title of a ritual in `ceo.rituals.yml`
- Remove "coming soon" asterisk from scripts
- Update "remote scripts" to "custom scripts." I think it's obvious that
the scripts are remote. Communicate the value: these scripts are custom
(anything you want)
- Handbook/company/communications#meetiungs: clearly document that the
expectation is that someone takes notes during meetings based on what is
said (gitlab’s handbook has some language here)
- Handbook/company/ceo#Flaws-and-feedback
idea: add to CEO tips in handbook “riffing 🎸” about an adjacent topic in
meetings. I sometimes...
# 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 (docs/Using
Fleet/manage-access.md)
- [ ] 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 to rituals table and added processes for processing swag through
Printful and Postal.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
As a contributor to Fleet I want to make it easy and simple for new team
members current contributors to follow the process to gain new
equipment.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
