# 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>
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.
1. Churned bug rituals moved to mid-sprint
2. Isabell as DRI for CX KPI numbers
3. Maintenance ritual added.
4. Add "Settled" quality check
5. Add notifying CS as part of churned bug round-up
Added colons for readability (aka so the sentences in this section would
still make sense if the labels were unbolded). Found it a bit harder to
parse than lists on other pages that use ":" as a separator. Also, added
a missing bullet point.
Screenshot with change made in the inspector for comparison:
# 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>
# 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>
Updating sprint demos verbiage in the handbook. This change reflects an
ongoing effort not to mention customer names so that we can share Sprint
Demos with the community..
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Closes: #13536
Changes:
- Deleted all handbook pages for current open positions.
- Created `/handbook/company/open-positions.yml`, and created entries
for the deleted handbook pages.
- Updated the build script to generate handbook pages for every entry in
`open-positions.yml`, and add information about each open position to
`sails.config.builtStaticContent.openPositions`
- Created a new component: `<open-positions>` - A component that takes a
single prop (named `openPositions`) that renders links to open position
handbook pages.
- Updated the "Creating a new position" section of the handbook to have
updated instructions for adding a new position to `open-positions.yml`
.
Updated the "Product groups" page to emphasize **🟢 iteration** when
considering whether to bring a user story back for expedited drafting.
---------
Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
Still need to get the actual numbers, but in the interest of **🟢
iteration**, I figured I'd open this as-is to get the structure in place
(since we're usually OK with the occasional TODO on a handbook page).
After chatting with @zhumo about it today, it sounds like sprint points
don't necessarily correspond to an amount of time (reflect effort
instead) and should be much the same across the organization now, so I
didn't leave stubs for that information in the different product group
sections.
Happy to convert this to a draft and revisit any of this if it feels too
far off what @mikermcneil had envisioned, lmk!
---------
Co-authored-by: Sharon Katz <121527325+sharon-fdm@users.noreply.github.com>
Co-authored-by: Luke Heath <luke@fleetdm.com>
While archiving #help-docs, I saw an opportunity to add more detail to
the website group's description by including more specific references to
managing documentation and the group's purpose.
The goal of this PR:
1. As Mike, I don't want to be surprised as I'm about to send the offer
email that the equity or cash compensation has been changed in that
offer, even though the candidate and I just discussed different numbers
and I had updated the equity plan accordingly, only to see it changed to
something. Often the hiring manager and candidate had also already
discussed numbers, I'd asked the candidate what they were.
2. As Sam, I want the best practices for scheduling with the CEO to be
observed.
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Handbook update to add opening to focus on windows MDM.
---------
Co-authored-by: George Karr <gkarr@xerithas-mac-16.local>
Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
resolves issue #13327
Adds a section laying out the reasoning behind short/simple issue
templates
---------
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
