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...
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>
- 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
...
# 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)).
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.
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:
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`
.
