mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 01:18:42 +00:00
Update README.md (#10776)
# 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 - [ ] 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: Mike McNeil <mikermcneil@users.noreply.github.com>
This commit is contained in:
parent
8c10b54388
commit
9f12f7040d
1 changed files with 2 additions and 2 deletions
|
|
@ -85,7 +85,7 @@ For team members working in jurisdictions that require certain mandatory sick le
|
|||
When you take any time off, you should follow this process:
|
||||
- Let your manager and team know as soon as possible (i.e., post a message in your team's Slack channel with when and how long).
|
||||
- Find someone to cover anything that needs covering while you're out and communicate what they need to take over the responsibilities as well as who to refer to for help (e.g., meetings, planned tasks, unfinished business, important Slack/email threads, anything where someone might be depending on you).
|
||||
- Mark an all-day "Out of office" event in Google Calendar for the day(s) you're taking off.
|
||||
- Mark an all-day "Out of office" event in Google Calendar for the day(s) you're taking off or for the hours that you will be off if less than a day. Google Calendar recognizes the event title "OOO" and will give you the option to decline existing and new meetings or just new meetings. You are expected to attend any meetings that you have accepted, so be sure to decline meetings you are not going to attend.
|
||||
If you can’t complete the above because you need to take the day off quickly due to an emergency, let your manager know and they will help you complete the handoff.
|
||||
If you ever want to take a day off, and the only thing stopping you is internal (Fleetie-only) meetings, don’t stress. Consider, “Is this a meeting that I can reschedule to another day, or is this a meeting that can go on without me and not interfere with the company’s plans?” Talk to your manager if you’re unsure, but it is perfectly OK to reschedule internal meetings that can wait so that you can take a day off.
|
||||
This process is the same for any days you take off, whether it's a holiday or you just need a break.
|
||||
|
|
@ -153,7 +153,7 @@ Certain new team members, especially in go-to-market (GTM) roles, will need paid
|
|||
| 🫧 Other role | ❌ | ❌ | ❌ | ❌ | ❌
|
||||
| Other department | ❌ | ❌ | ❌ | ❌ | ❌
|
||||
|
||||
> _**Warning:** Do NOT buy LinkedIn Recruiter. Use the cheapest possible LinkedIn tier. The goal is access to profile views and data, not InMail. Fleet does not send InMail._
|
||||
> _**Warning:** Do NOT buy LinkedIn Recruiter. Use the cheapest possible LinkedIn tier. Fleet has a Sales Navigator account. AEs and SDRs should [ask the operations team for a license.](https://fleetdm.com/handbook/business-operations#intake) The goal is access to profile views and data, not InMail. Fleet does not send InMail._
|
||||
|
||||
### Training
|
||||
It's [important](https://fleetdm.com/handbook/company/why-this-way#why-the-emphasis-on-training) that every team member at Fleet takes the time to get fully trained and onboarded.
|
||||
|
|
|
|||
Loading…
Reference in a new issue