expanded officer acronyms
This commit is contained in:
parent
dddf50bc09
commit
4a66d48dd4
BIN
src/.Ulysses-Group.plist
Normal file
BIN
src/.Ulysses-Group.plist
Normal file
Binary file not shown.
131
src/SUMMARY.md
131
src/SUMMARY.md
@ -1,61 +1,102 @@
|
|||||||
# TSYS Group Handbook
|
# TSYS Group Handbook
|
||||||
|
|
||||||
# Introduction and overview
|
# Introduction and overview
|
||||||
- [TSYS Group Introduction](./intro.md)
|
- [TSYS Group Introduction][1]
|
||||||
|
|
||||||
# Board Of Directors
|
# Board Of Directors
|
||||||
|
|
||||||
- [Board Of Directors Manual](./Board/BoardOfDirectorsManual.md)
|
- [Board Of Directors Manual][2]
|
||||||
- [Committe Charter - Audit](./Board/charters/Audit-Committee-Charter.md)
|
- [Committe Charter - Audit][3]
|
||||||
- [Committe Charter - Executive](./Board/charters/Executive-Committee-Charter.md)
|
- [Committe Charter - Executive][4]
|
||||||
- [Committe Charter - ForProfit](./Board/charters/ForProfitCommittee-Charter.md)
|
- [Committe Charter - ForProfit][5]
|
||||||
- [Committe Charter - NonProfit](./Board/charters/NonProfit-Committee-Charter.md)
|
- [Committe Charter - NonProfit][6]
|
||||||
- [Committe Charter - HFNOC](./Board/charters/HFNOC-Committee-Charter.md)
|
- [Committe Charter - HFNOC][7]
|
||||||
- [Committe Charter - Redwood](./Board/charters/Redwood-Committee-Charter.md)
|
- [Committe Charter - Redwood][8]
|
||||||
|
|
||||||
# CEO
|
# Chief Executive Officer
|
||||||
|
|
||||||
# CTO
|
# Chief Technology Officer
|
||||||
|
|
||||||
- [CTO Overview](./CTO/CTO.md)
|
- [CTO Overview][9]
|
||||||
- [TeamHwEng - Supply Chain](./CTO/team-hweng/HwEngSupplyChain.md)
|
- [TeamHwEng - Supply Chain][10]
|
||||||
- [TeamHwEng - Component Inventory](./CTO/team-hweng/labComponentInventory.md)
|
- [TeamHwEng - Component Inventory][11]
|
||||||
- [TeamHwEng - Tooling](./CTO/team-hweng/HwEngTooling.md)
|
- [TeamHwEng - Tooling][12]
|
||||||
- [TeamSwEng - Supply Chain](./CTO/team-sweng/SwEngSupplyChain.md)
|
- [TeamSwEng - Supply Chain][13]
|
||||||
- [TeamSwEng - Tooling](./CTO/team-sweng/SwEngTooling.md)
|
- [TeamSwEng - Tooling][14]
|
||||||
- [TeamMecheng - Supply Chain](./CTO/team-mecheng/MechEngSupplyChain.md)
|
- [TeamMecheng - Supply Chain][15]
|
||||||
- [TeamMecheng - Tooling](./CTO/team-mecheng/MechEngTooling.md)
|
- [TeamMecheng - Tooling][16]
|
||||||
|
|
||||||
|
|
||||||
# CIO
|
# Chief Information Technology Officer
|
||||||
|
|
||||||
- [CIO Overview](./CIO/CIO.md)
|
- [CIO Overview][17]
|
||||||
- [Policies - Business Continuity Plan](./CIO/Policies/BusinessContinuityPlan.md)
|
- [Policies - Business Continuity Plan][18]
|
||||||
- [Policies - Authentication](./CIO/Policies/Authentication.md)
|
- [Policies - Authentication][19]
|
||||||
- [Processes - Two Factor Authentication ](./CIO/Processes/2fa.md)
|
- [Processes - Two Factor Authentication ][20]
|
||||||
- [Processes - Move To Production](./CIO/Processes/MoveToProduction.md)
|
- [Processes - Move To Production][21]
|
||||||
- [Processes - New Team Member Onboarding](./CIO/Processes/NewTeamMemberOnboarding.md)
|
- [Processes - New Team Member Onboarding][22]
|
||||||
- [Processes - PFV Datacenter Runbook](./CIO/Processes/PFVRunbook.md)
|
- [Processes - PFV Datacenter Runbook][23]
|
||||||
- [Processes - VPN User Management](./CIO/Processes/VpnUser.md)
|
- [Processes - VPN User Management][24]
|
||||||
- [Processes - Vulnerability Management](./CIO/Processes/VulnerabilityManagmentNotes.md)
|
- [Processes - Vulnerability Management][25]
|
||||||
- [Systems - Applications And Web Services](./CIO/Systems/Admin-Application/AppsAndServices.md)
|
- [Systems - Applications And Web Services][26]
|
||||||
- [Systems - Runtime Environment for Hosted Services](./CIO/Systems/Admin-Application/RuntimeLayer.md)
|
- [Systems - Runtime Environment for Hosted Services][27]
|
||||||
- [Systems - Web Server Configuration](./CIO/Systems/Admin-Application/WebServerSetupNotes.md)
|
- [Systems - Web Server Configuration][28]
|
||||||
- [Systems - Overview](./CIO/Systems/TSYS-Systems.md)
|
- [Systems - Overview][29]
|
||||||
- [Systems - Cooling](./CIO/Systems/Admin-DataCenter/cooling/PFVCooling2021.md)
|
- [Systems - Cooling][30]
|
||||||
- [Systems - Power](./CIO/Systems/Admin-DataCenter/power/PFVPower2021Prod.md)
|
- [Systems - Power][31]
|
||||||
- [Systems - Security](./CIO/Systems/Admin-DataCenter/security/PhysicalSecurity.md)
|
- [Systems - Security][32]
|
||||||
- [Systems - Storage](./CIO/Systems/Admin-DataCenter/storage/PFVStorage2021.md)
|
- [Systems - Storage][33]
|
||||||
- [Systems - TSYS HQ LAN](./CIO/Systems/Admin-DataCenter/networking/PFV-LAN.md)
|
- [Systems - TSYS HQ LAN][34]
|
||||||
- [Systems - TSYS HQ WAN](./CIO/Systems/Admin-DataCenter/networking/PFV-WAN.md)
|
- [Systems - TSYS HQ WAN][35]
|
||||||
- [Systems - Virtual Guests Inventory](./CIO/Systems/Admin-Platform/TSYS-Systems.md)
|
- [Systems - Virtual Guests Inventory][36]
|
||||||
- [Systems - Workstation Build Guide](./CIO/Systems/Admin-RAndD/EngWorkstationBuildGuide.md)
|
- [Systems - Workstation Build Guide][37]
|
||||||
- [Systems - VsCode Configuration Guide](./CIO/Systems/Admin-RAndD/VsCodeConfigGuide.md)
|
- [Systems - VsCode Configuration Guide][38]
|
||||||
|
|
||||||
# CMO
|
# Chief Marketing Officer
|
||||||
|
|
||||||
# CRO
|
# Chief Sales Officer
|
||||||
|
|
||||||
# CFO
|
# Chief Finance Officer
|
||||||
|
|
||||||
# COO
|
# Chief Operations Officer
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
[1]: ./intro.md
|
||||||
|
[2]: ./Board/BoardOfDirectorsManual.md
|
||||||
|
[3]: ./Board/charters/Audit-Committee-Charter.md
|
||||||
|
[4]: ./Board/charters/Executive-Committee-Charter.md
|
||||||
|
[5]: ./Board/charters/ForProfitCommittee-Charter.md
|
||||||
|
[6]: ./Board/charters/NonProfit-Committee-Charter.md
|
||||||
|
[7]: ./Board/charters/HFNOC-Committee-Charter.md
|
||||||
|
[8]: ./Board/charters/Redwood-Committee-Charter.md
|
||||||
|
[9]: ./CTO/CTO.md
|
||||||
|
[10]: ./CTO/team-hweng/HwEngSupplyChain.md
|
||||||
|
[11]: ./CTO/team-hweng/labComponentInventory.md
|
||||||
|
[12]: ./CTO/team-hweng/HwEngTooling.md
|
||||||
|
[13]: ./CTO/team-sweng/SwEngSupplyChain.md
|
||||||
|
[14]: ./CTO/team-sweng/SwEngTooling.md
|
||||||
|
[15]: ./CTO/team-mecheng/MechEngSupplyChain.md
|
||||||
|
[16]: ./CTO/team-mecheng/MechEngTooling.md
|
||||||
|
[17]: ./CIO/CIO.md
|
||||||
|
[18]: ./CIO/Policies/BusinessContinuityPlan.md
|
||||||
|
[19]: ./CIO/Policies/Authentication.md
|
||||||
|
[20]: ./CIO/Processes/2fa.md
|
||||||
|
[21]: ./CIO/Processes/MoveToProduction.md
|
||||||
|
[22]: ./CIO/Processes/NewTeamMemberOnboarding.md
|
||||||
|
[23]: ./CIO/Processes/PFVRunbook.md
|
||||||
|
[24]: ./CIO/Processes/VpnUser.md
|
||||||
|
[25]: ./CIO/Processes/VulnerabilityManagmentNotes.md
|
||||||
|
[26]: ./CIO/Systems/Admin-Application/AppsAndServices.md
|
||||||
|
[27]: ./CIO/Systems/Admin-Application/RuntimeLayer.md
|
||||||
|
[28]: ./CIO/Systems/Admin-Application/WebServerSetupNotes.md
|
||||||
|
[29]: ./CIO/Systems/TSYS-Systems.md
|
||||||
|
[30]: ./CIO/Systems/Admin-DataCenter/cooling/PFVCooling2021.md
|
||||||
|
[31]: ./CIO/Systems/Admin-DataCenter/power/PFVPower2021Prod.md
|
||||||
|
[32]: ./CIO/Systems/Admin-DataCenter/security/PhysicalSecurity.md
|
||||||
|
[33]: ./CIO/Systems/Admin-DataCenter/storage/PFVStorage2021.md
|
||||||
|
[34]: ./CIO/Systems/Admin-DataCenter/networking/PFV-LAN.md
|
||||||
|
[35]: ./CIO/Systems/Admin-DataCenter/networking/PFV-WAN.md
|
||||||
|
[36]: ./CIO/Systems/Admin-Platform/TSYS-Systems.md
|
||||||
|
[37]: ./CIO/Systems/Admin-RAndD/EngWorkstationBuildGuide.md
|
||||||
|
[38]: ./CIO/Systems/Admin-RAndD/VsCodeConfigGuide.md
|
||||||
@ -1,83 +0,0 @@
|
|||||||
---
|
|
||||||
title: Breaking glass to debug production
|
|
||||||
sidebar: Handbook
|
|
||||||
showTitle: true
|
|
||||||
---
|
|
||||||
|
|
||||||
We've all been there. Something was just merged and now there is a bug that you are having a real hard time pinning down.
|
|
||||||
You hate to do it...but you need to get on a prod box to see what's going on. _SHAME_
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Step 1
|
|
||||||
|
|
||||||
Make sure that you have `awscli` installed locally on your computer.
|
|
||||||
|
|
||||||
For macOS you should [brew install](https://formulae.brew.sh/formula/awscli) it:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
brew install awscli
|
|
||||||
```
|
|
||||||
|
|
||||||
#### Configure AWS CLI
|
|
||||||
|
|
||||||
```bash
|
|
||||||
aws configure
|
|
||||||
```
|
|
||||||
|
|
||||||
From here follow the wizard and enter your AWS Key ID and Secret Key. You should default to `us-east-1` as your region.
|
|
||||||
|
|
||||||
### Step 2
|
|
||||||
|
|
||||||
You'll need to make sure that you have the [Session Manager plugin for AWS ClI](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html) installed.
|
|
||||||
Follow the steps below (for macOS) to install the [Session Manager plugin](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html) using the bundled installer.
|
|
||||||
|
|
||||||
#### Download the bundled installer.
|
|
||||||
|
|
||||||
```bash
|
|
||||||
curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/mac/sessionmanager-bundle.zip" -o "sessionmanager-bundle.zip"
|
|
||||||
```
|
|
||||||
|
|
||||||
#### Unzip the package.
|
|
||||||
|
|
||||||
```bash
|
|
||||||
unzip sessionmanager-bundle.zip
|
|
||||||
```
|
|
||||||
|
|
||||||
#### Run the install command.
|
|
||||||
|
|
||||||
```bash
|
|
||||||
sudo ./sessionmanager-bundle/install -i /usr/local/sessionmanagerplugin -b /usr/local/bin/session-manager-plugin
|
|
||||||
```
|
|
||||||
|
|
||||||
### Step 3
|
|
||||||
|
|
||||||
Go to the ECS console in AWS. Select the `posthog-production-cluster` and then select the service that you would like to exec into (most likely a `web` or `worker` task).
|
|
||||||
From that service select a currently running task. **IT MUST BE RUNNING AND STABLE**. If the service is flapping this will not help you.
|
|
||||||
|
|
||||||
Copy the _TASK ID_. We'll be using that later.
|
|
||||||
|
|
||||||
### Step 4
|
|
||||||
|
|
||||||
#### Exec into the container
|
|
||||||
|
|
||||||
Plug the Task ID (from the previous step) into the following command and get to work slacker!
|
|
||||||
(You may also need to change the container name depending on the service you are hoping into)
|
|
||||||
|
|
||||||
```bash
|
|
||||||
aws ecs execute-command \
|
|
||||||
--region us-east-1 \
|
|
||||||
--cluster posthog-production-cluster \
|
|
||||||
--task <TASK_ID from earlier> \
|
|
||||||
--container posthog-production \
|
|
||||||
--command "/bin/bash" \
|
|
||||||
--interactive
|
|
||||||
```
|
|
||||||
|
|
||||||
If you need a Django shell, just run the following after connecting
|
|
||||||
|
|
||||||
```bash
|
|
||||||
python manage.py shell_plus
|
|
||||||
```
|
|
||||||
|
|
||||||
If all of this fails reach out to the engineer on call.
|
|
||||||
@ -1,101 +0,0 @@
|
|||||||
---
|
|
||||||
title: YC Onboarding
|
|
||||||
sidebar: Handbook
|
|
||||||
showTitle: true
|
|
||||||
---
|
|
||||||
|
|
||||||
As a YCombinator company ourselves, we want to be supportive of other YC companies that want to use PostHog. As such, our onboarding process for YC companies is different and more extensive than our general process.
|
|
||||||
|
|
||||||
## The YC Deal
|
|
||||||
|
|
||||||
Our YC Deal provides the following:
|
|
||||||
|
|
||||||
One free year of PostHog Cloud with up to 10 million events per month *or* a one-year enterprise license if they want to self-host PostHog.
|
|
||||||
|
|
||||||
Companies also get a \$50 gift card to spend on our merch and enterprise support (i.e. a private Slack with our core team members).
|
|
||||||
|
|
||||||
For YC W21 companies, we also offer:
|
|
||||||
|
|
||||||
- A choice of Airpods or Allbirds shoes
|
|
||||||
- A referral scheme to get more of the above
|
|
||||||
- We will also give more merch (an extra $50 voucher for our store) to the company they refer to us
|
|
||||||
|
|
||||||
> **Note:** Batch-specific deals will be updated here as new batches come along.
|
|
||||||
|
|
||||||
## Onboarding Call
|
|
||||||
|
|
||||||
### Inbound Request Sources
|
|
||||||
|
|
||||||
YC companies can reach out to us in many ways. Ideally we will steer them towards the [dedicated YC Onboarding page](/yc-onboarding), but they may also reach out to us on _yc@posthog.com_ or _ycdeal@posthog.com_ (as well as individual emails and _hey@posthog.com_).
|
|
||||||
|
|
||||||
Having received a demo request through one of these sources, schedule an appropriate 1h slot and make sure at least one person is certainly able to attend it.
|
|
||||||
|
|
||||||
### Before the call
|
|
||||||
|
|
||||||
Ideally we want users to have gotten started with PostHog before the demo call. From our YC Onboarding page:
|
|
||||||
|
|
||||||
<div class="blog-quote">
|
|
||||||
Before the call, we recommend you sign up to our Cloud version and try your hand at installing our snippet on your website. Doing so would allow us to tailor the onboarding to your needs, leveraging data from your own website instead of demo data. However, if you prefer to get a demo first, we'll give you access to a demo playground during our call.
|
|
||||||
</div>
|
|
||||||
|
|
||||||
> **Note:** We recommend PostHog Cloud as a way to get started quick, but it's up to them if they want to set up a self-hosted instance before the call. You should also help with this.
|
|
||||||
|
|
||||||
If users come to the call with a ready instance, we can focus more on their needs and setting up relevant views for them than a basic overview of the platform that they could have gotten without us.
|
|
||||||
|
|
||||||
### The Demo
|
|
||||||
|
|
||||||
When doing a demo of PostHog, you should prioritize using the following environments:
|
|
||||||
|
|
||||||
1. The client's own instance or PostHog Cloud account (if they have one **and** are OK with this).
|
|
||||||
2. The [PostHog Demo Environment](https://playground.posthog.com)
|
|
||||||
3. A local environment
|
|
||||||
4. PostHog Cloud
|
|
||||||
|
|
||||||
Read more about running demos on our [dedicated page](/handbook/growth/yc-onboarding).
|
|
||||||
|
|
||||||
#### Bookmarklet
|
|
||||||
|
|
||||||
A super cool way of doing demos for websites and web apps is using the PostHog bookmarklet. This way you can set up funnels, charts, and other views for the user (or, ideally, have them set it up themselves) by leveraging their *own data*. If done on their own instance, some of these views might even be ready for them to start analyzing user data once "real events" start coming in.
|
|
||||||
|
|
||||||
To learn more about the bookmarklet, check out our [Snippet Installation](/docs/deployment/snippet-installation#get-started-with-no-code) page.
|
|
||||||
|
|
||||||
#### Let the user drive
|
|
||||||
|
|
||||||
Always tailor the demo to the user specifically! Skip things they don't need, and let them decide what they want to see. Be friendly and helpful, not salesy! Our goal is for these users to be able to use PostHog to improve *their* product.
|
|
||||||
|
|
||||||
### After the call
|
|
||||||
|
|
||||||
If you have time left in the 1h slot, **do this during the call** - it ensures the user is fully set up by the time the call is over.
|
|
||||||
|
|
||||||
You should:
|
|
||||||
|
|
||||||
- Set up a private Slack group with them on our core team Slack group.
|
|
||||||
- If they do not use Slack internally, set up a private chat on the PostHog Users Slack.
|
|
||||||
- You should add Yakko, James, Tim, Paolo, and a random engineer to each group.
|
|
||||||
- Send them a link to [the merch form](https://forms.gle/K61bhD6uLxaaTqoK6).
|
|
||||||
- Let them know that if they refer another company, they will get another set of merch. All the other company needs to do is say that "Company X" referred them. We'll double merch for both of them.
|
|
||||||
- If they will use PostHog Cloud, [update their plan to the Startup plan](http://localhost:8000/handbook/growth/sales/billing) using the Django Admin panel.
|
|
||||||
- Also set `should_setup_billing` to `True` - this will prompt them to add card details (but ensure them they won't get charged!)
|
|
||||||
- If they will self-host PostHog, set them up with a [one-year EE license](http://localhost:8000/handbook/growth/sales/billing) (Paolo can help with this).
|
|
||||||
- Ask them to confirm they've tagged themselves as using us, and send a direct link [to the deal](https://bookface.ycombinator.com/deals/687), so this is easy.
|
|
||||||
- If they refer another company, use Shopify to send them a $50 voucher at [our store](https://merch.posthog.com).
|
|
||||||
- After they've gotten set up, [create a deal on the appropriate Hubspot pipeline](/handbook/growth/sales/sales-operations)
|
|
||||||
- Add their email domain to the 'YC W21 Onboarded Users' cohort as a new match group that tags `email contains @theirdomain.com`
|
|
||||||
|
|
||||||
## Processing AirPods and Allbirds orders
|
|
||||||
|
|
||||||
We collect responses to the [the merch form](https://forms.gle/K61bhD6uLxaaTqoK6) and process these manually once a week by placing the orders on the user's behalf. You can just place the order on your Brex card.
|
|
||||||
|
|
||||||
We provide the standard [AirPods](https://www.apple.com/shop/product/MV7N2AM/A/airpods-with-charging-case) and case (ie. not AirPods Pro or the wireless charging case). For Allbirds, we provide any shoes that show as $95 or less on their [US site](https://www.allbirds.com/).
|
|
||||||
|
|
||||||
This is where we buy from, in descending order of preference:
|
|
||||||
|
|
||||||
1. Buy directly from that country's Apple or Allbirds site. This usually applies to the USA, UK and EU. For Apple, use your Brex card via [this referral link](https://apple.sjv.io/c/2279798/524650/7613?subId1=VXNlcjpjdXVzZXJfY2tlY28zN29zMDAyMTAxcmF5OWY4c201OA==&sharedId=RewardsMarketplace) as it gets us cashback.
|
|
||||||
2. Send an Amazon gift card for $100 equivalent from their local store.
|
|
||||||
3. If Amazon is not available in their country, ask the user to buy and send us a receipt, and we will reimburse to their bank account.
|
|
||||||
|
|
||||||
When ordering from Apple, put in your email address as the main one for the order, and then add the user's email address under 'Share delivery updates' so they can easily track their order. For Allbirds, you will need to put in your email address and then just forward the receipt to the user for them to track. You should not just put in their email address for the order, as you won't then get a copy of the receipt for expenses.
|
|
||||||
|
|
||||||
## Current Responsibilities
|
|
||||||
|
|
||||||
Yakko currently handles YC onboarding calls while Charles processes merch requests. Paolo is the point of contact for billing issues.
|
|
||||||
Loading…
Reference in New Issue
Block a user