* Handbook: Bizops rituals in people section
Not quite ready yet but want to get the changes going. Will require some further discussion to sort out missing details and settle format difference.
* Update handbook/people.md
* Update handbook/people.md
* Update handbook/people.md
* Update people.md
* Update people.md
* Update handbook/people.md
* Update handbook/people.md
* Update handbook/people.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Growing the team
Creating a new position
TODO: Creating a new position in Breezy
* Updated location of CEO confirmation info
Co-authored-by: Eric <eashaw@sailsjs.com>
* Registering in a new state w/ Gusto
Registering in a new state w/ Gusto
* Update people.md
* update indentation, remove whitespace change
Co-authored-by: eashaw <caglc@live.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
* Handbook editor pass - People
Corrected for content and copy.
* Update handbook/people.md
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
* Added 1:1 documentation to Rituals sections
Added 1:1 documentation to Rituals sections
* Team name edit
Changed Operations team to Digital Experience team.
* Update to wording of new ritual
Committing Eric's edit suggestions.
Co-authored-by: Eric <eashaw@sailsjs.com>
* Update people.md
Added new step for updating the All Hands link
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
* Update people.md
Added Sightseeing tour from https://github.com/fleetdm/fleet/issues/4372
Calendly link in progress.
* Update people.md
All edits are recorded by line:
266 added “, after “call”; replaced “which” with “that”
268 replaced “Github” with “GitHub”
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* Handbook Ritual Workversaries
Moved Slack channels heading down and added a ritual heading for "Workversaries."
Added a description line.
Added two lines summarizing the ritual.
* Update people.md
* Revised edits
Line 270 Changed Workversaries to Workiversaries
Line 274 traded out the list for a sentence summary of the Ritual.
Should reference to Mike be they/them or he/him in this context?
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
* update onboarding section
* Update people.md
* Update people.md
* Update people.md
All edits are recorded by line:
187 added “a” before “copy”; deleted “,” after “scenarios”
213 replaced “into” with “to”
215 replaced “for” with “For”; replaced “members” with “member’s”
216 replaced “an agreement is signed and stored” with “signing and storing an”; replaced “If” with “Eric will reach out to them if”; deleted “, Eric will reach out to them” after “employee”
218 added “usually” after “can”; deleted “Usually.” after “gusto”
220 replaced “the information about the new hire is confirmed by Eric,” with “Eric confirms the information about the new hire”; deleted “,” after “information”
223 added “to” after “out”; replace “prefered” with “preferred”; deleted “,” after “card”
225 replaced “purcahsed” with “purchased’
229 replaced “members” with “member’s”; deleted “,” after “Slack”; added “,” after “member”
231 replaced “Github” with “GitHub”; replaced “out” with “on”
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* add section about onboarding and
* Update people.md
All edits are recorded by line:
227 replace “out” with “on”; replaced “that” with “they”
229 replaced “important” with “essential”; deleted “a” before “good”; deleted “that” before “they”; replaced “like they take seriously” with “is necessary”; added “a” before “review”
223 added “,” after “screen”
235 replaced “Make” with “make”, added “.” after “quickly”
236 replaced “Make” with “make”, added “.” after “quickly
237 replaced “Make” with “make”, added “.” after “mean”
238 replaced “Make” with “make”, added “.” after “markdown”
239 replaced “Talk” with “talk”; added “.” after “calendar”
240 replaced “Give” with “give”; added “.” after “folder”
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* Update people.md
Things new and old employees should know
Why do we wireframe first?
- Wireframing is called “drafting” at Fleet and is done in Figma.
- Anyone can make a wireframe suggestion, and wireframes are easy to contribute without being code literate.
- Drafting is completed for each change.
- It can be thrown away after changes. Coding first leaves verbiage that is difficult to update, if it ever gets done at all.
- It allows you to simplify the creation and testing of error messages.
- Iterating in wireframes first lets us do all this for:
- Error messages
- Layouts
- Flows
- Interactions
- Help text
- Button text
- Forms
- URLs
- API parameters
- API response data…and more
Why mono repo?
- One repo keeps all of the relevant work in one place. The only exception is when working on something confidential.
- One repo means that there is less to get lost.
- One repo pools GitHub stars to reflect Fleet’s actual presence better.
Why organize work in team-based kanban boards?
- Kanban boards provide a uniform layout across all teams where anyone in the company can look to see what other teams are working on and have coming up.
- The different columns on the boards allow us to create a game plan for our to-do list for each 3 week iteration.
- These boards allow anyone in the world to contribute.
Why 3 week cadence?
- Fleet product is released every 3 weeks so everyone in the company is synced up to this same schedule.
- Other companies use a 4 week release cycle but at Fleet, we like to move a little faster so we can get more done.
- Everyone always knows when the new release is so they also know when their work is due.
Why agile?
- See: https://agilemanifesto.org/
- Collaborating and pushing for the next release creates the best product and culture.
Our values and mission.
- See: https://fleetdm.com/handbook/company
Why the emphasis on training?
- Investing in people makes them better and faster contributors.
- Creating a culture of helping others results in people feeling more comfortable and confident even if they aren’t familiar with osquery.
- A sharp focus on training means things are written down.
Why handbook-first strategy?
- Watch: https://www.youtube.com/watch?v=aZrK8AQM8Ro
- For more details see: https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/
- Documenting in the handbook allows Fleet to scale up and retain knowledge for consistency.
Why not continuously generate REST API docs from javadoc-style code comments?
- It looks cheap. Those using open API still are embarrassed by their docs.
- Generated documentation via tools like Swagger/OpenAPI have a tendency to get out of date and becomes harder to fix to make it up to date.
- There is less control over how to add annotations to the doc.
- It has less visibility/ accessibility/ modifiability for people without Golang coding experience.
- Fully integrating with swagger's format sufficiently to document everything involves more people on the team learning about the intricacies of swagger (instead of editing markdown that looks like any other markdown in the docs/website)).
- Autogenerating docs is not the only way to make sure docs accurately reflect the API.
- Generated docs become just as out of date as handmade docs, except since they are generated makes them more difficult to edit and therefore gated/siloed. Adaptability is efficient.
- Using markdown allows anyone to edit our docs.
- Replacing markdown files with code comments makes API reference docs harder to locate and edit.
I also removed "." from "### Purchasing a company-issued device" on line 120.
* Update people.md
39 replaced “employees with “team members”
79, 84, 94, 95 updated to a Markdown link
* Update company.md
All edits are recorded by line:
Lines 30- 97 added "Things new and old team members should know" section.
* Update people.md
Removed all edits
* Ritual Heading with OKR planning subheading
Proposing to add the ritual heading to handbook/people in line with [https://github.com/fleetdm/confidential/issues/1013] and [https://github.com/fleetdm/fleet/issues/4671].
cc: @hollidayn
* Ritual update
Added OKR planning context and ritual steps to "Ritual" section of handbook.
* Move ritual section above Slack channels
Co-authored-by: Eric <eashaw@sailsjs.com>
- Add "Ticket movement..." and "Lead engineering standup..." DRIs
- The new "Ticket movement..." DRI absorbs the "Escaped work" and "Ticket quality" responsibilities.
* Create operations.md
* link to operations page, draft of operations page
* Update operations.md
* Update operations.md
* Update operations.md
* Update operations.md
* Apply suggestions from code review
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* move new section to people page, delete operations page
* Update people.md
* update gusto link to fix test
* Update people.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* uncomment handbook route, disable redirect, add link to top nav
* Handbook page, note: most of this is directly copied from the docs, build handbook
* added maintainer <meta> tags
* handbook styles
* handbook broken up into different files
* update handbook layout
* updating markdown files
* handbook layout, adjusted header margins to make room for handbook
* handling links to specific sections in markdown compilation
* lint fixes
* commented out search bar for now
* cleaned up page script
* update handbook and clean up styles
* Delete handbook.md
* updated product content from latest version
* clean up styles, remove hardcoded image widths
* markdown updates
* title and description for /handbook, removed commented out route
* fix styles on firefox, remove commented logs
* lint fix
* update class name
* fix broken link
* updated how hashes are handled in links, adjusted links in handbook
* lint fix
* updated function names, removed comments, small markdown syntax fix
* move handbook link into footer
