# 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>
As we're going to be hiring for an SDR, here is a job spec with no
fluff. Please criticise....
---------
Co-authored-by: Sampfluger88 <108141731+Sampfluger88@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)).
- Added manage g-ceo intake to CEO page
- Added ritual manage g-ceo intake
- Add Manage intake to communications
- Update "👑Crown jewels" to "🎐Why Fleet?"
- Deleted extra space in why this way
...
1. Adding a 'to be scheduled' column to the bug board so that the group
product manager knows which churned bugs need to be prioritized back
into the sprint after the de-prioritization meeting. We'd previously
been sending them back to the bug board inbox, but this was causing some
confusion.
2. Changing terminology from 'continue' to 'schedule' as discussed at
de-prioritization meeting.
# 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)).
@zhumo this is much leaner than I originally drafted for your review,
but I think we can achieve the same thing using links. WDYT?
I haven't included the product ops quality check as it will be covered
under product rituals.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
The product group capacities is # of engineers * 13. #g-website seemed
way too high given it's just Eric, so I dropped that to 13. Note that
he's also being counted for 13 on the CX capacity, so we're
double-counting Eric.
His vuln dashboard work is tracked on the CX board, which is why we're
counting him there.
It's consistently a todo I send back for HM's prior to an offer going
out, realized we don't actually ask them to fill in that specific cell
in fleeties. Updating to fix.
