Add files via upload

* Update and rename contributing-to-the-handbook.md to contributing-to-this-page.md

* Rename src/welcome-to-status/index.md to src/welcome-to-status.md

* Update SUMMARY.md

book.toml

@@ -3,7 +3,7 @@ authors = ["Jakub Sokołowski"]
 language = "en"
 multilingual = false
 src = "src"
-title = "Status Employee Handbook"
+title = "Status Contributors Guide"
 
 [output.html]
 cname = "handbook.status.im"

src/SUMMARY.md

@@ -1,12 +1,34 @@
 # Summary
 
 - [Introduction](./index.md)
-- [Catalog](./catalog.md)
-- [Get Started!](./get-started/index.md)
-- [Perks](./perks/index.md)
-- [Working Here](./working-here/index.md)
-- [Health](./health/index.md)
-- [Travel](./travel/index.md)
-- [Hirign](./hiring/index.md)
-- [Team Leads](./team-leads/index.md)
+- [Welcome to Status](./welcome-to-status.md)
+- [Our principles](./our-principles.md)
+- [Directory of Core Contributors](./catalog.md)
+- [Settling in](./settling-in/index.md)
+     - [Your autonomy](./settling-in/your-autonomy/index.md)
+        - [Self-time management](./settling-in/your-autonomy/self-time-management.md)
+        - [Downtime FAQs](./settling-in/your-autonomy/downtime-faqs.md)
+        - [Location independence](./settling-in/your-autonomy/location-independence.md)
+     - [The trial period](./settling-in/the-trial-period.md)
+     - [Onboarding buddy](./settling-in/onboarding-buddy.md)
+- [Fundamentals](./fundamentals/index.md)
+     - [Security guidelines](./fundamentals/security-guidelines.md)
+     - [Recommended reading](./fundamentals/essential-reading.md)
+     - [Contributor Code of Conduct](./fundamentals/contributor-code-of-conduct.md)
+     - [Contributor Privacy Policy](./fundamentals/contributor-privacy-policy.md)
 - [Finance](./finance/index.md)
+     - [Getting paid](./finance/getting-paid.md)
+     - [Third-party invoices format](./finance/third-party-invoices-format.md)
+     - [Expense reimbursements](./finance/expense-reimbursements.md)
+- [Perks](./perks/index.md)
+     - [Computers and devices](./perks/computers-and-devices.md)
+     - [Events and meetups](./perks/events-and-meetups.md)
+     - [Health resources for your home office](./perks/health-resources-for-your-home-office.md)
+- [Contributing to Status](./working-here/index.md)
+     - [Traveling for Status](./working-here/traveling-for-status.md)
+          - [How to use TravelPerk](./working-here/how-to-use-travelperk.md)
+- [Your most important role](./hiring/index.md)
+
+*****
+
+- [Contributing to the Contributors Guide](./contributing-to-this-page.md)

src/catalog.md

@@ -1,4 +1,4 @@
-# Catalog
+# ℹ️ Directory of Core Contributors
 
 <style>
 div#content>main {

src/contributing-to-this-page.md

@@ -0,0 +1,27 @@
+# 🚀 Contributing to this guide
+
+Status Contributors Guide is an open living repo built for you. The truth is Status evolves faster than it does the documentation. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit. 
+
+Here are you'll find helpful guidelines on how to contribute to this guide and make it yours!
+
+## 👾 Contributing with pull requests
+
+Whether you'd like to fix typos, update information, add sections, or build new content, you can create a pull request to contribute to the handbook. 
+
+Our current workflow has two main branches: `mater` that deploys to `[contributors.status.im](https://contributors.status.im)` and `develop` that deploys to `[dev-contributors.status.im](https://dev-contributors.status.im)`. 
+
+Before creating a pull request, create a new branch from `develop` and commit your changes to one or multiple PRs. Once finished, assign someone from the People Ops team to review or comment on it. Once merged, we'll delete the branch, and you'll see your contributions on this guide!
+
+## 📌 Leaving feedback with issues
+
+Issues open a world of possibilities: from proposing changes to simply dropping an idea or leaving comments or tasks. 
+
+There are a few ways to create an issue:
+
+   * Go to the `issues` tab in the Status Contributors Guide repo and create one.
+   * From the source code of a file, click the `+` sign at the beginning of a line.
+   * From a comment from a pull request, click `reference in new issue`.
+
+Just like a PR, assign the issue to someone from the People Ops team, and we'll tag/re-assign it accordingly to address it.
+
+The People Ops team keeps this guide's maintenance, but it's really a collective effort. So please help us make it better for you and future readers! 

src/finance/Filing Expenses.md

@@ -1,60 +0,0 @@
-# Filing Expenses
-
-![alt text](https://images.unsplash.com/photo-1521540216272-a50305cd4421?ixlib=rb-0.3.5&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=1080&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ&s=611185f92103f088fb8dfb682f810e19)
-
-
-## How to get reimbursed for expenses?
-In order to be reimbursed for expenses incurred on behalf of Status during the development of the project, you will need to invoice Status and submit a report obtained through Expensify with the details of these expenses.
-
-## Getting set up with Expensify
-We use Expensify to report and store the expense receipts incurred on behalf of Status during the development of the project.
-
-You only need to create an account with your status.im email address and Expensify will ask you to join the Status organization. Please input your full name as it appears in your BambooHR profile when setting up your Expensify account.
-
-You can also download the Expensify mobile app for when you're on the go.
-
-## Submitting an expense report through Expensify
-For the Finance team to be able to approve the expense reimbursements, all expense reports should be submitted by the 10th of the month before submitting the monthly invoice on the 15th.
-
-Please follow these links if you need help with [creating expenses](https://community.expensify.com/discussion/4560/how-to-create-expenses-manually) and [submitting reports](https://community.expensify.com/discussion/4561/how-to-submit-a-report/p1?new=1) on Expensify
-
-If you would need further help with the creation and submission of expense reports, please contact the Finance team and they will be able to guide you through the process.
-
-## Adding the expenses to your monthly invoice
-The finished and approved report from Expensify will show the total for each expense category. For example, if you have several costs in one category, Expensify will show the following:
-
-![alt text](https://people-ops.status.im/content/images/2021/08/Exp-3.png)
-
-## Your invoice should only contain the total per category, not each expense item.
-
-As a guidance, we have added these categories in the invoice template here. To avoid any delays with the expense claim approval, please ensure your invoice has the same category names as the Expensify reports.
-
-If you would like to set up these categories in your accounting software, please ask the Finance team for the complete list of expense categories.
-
-If you need to share the report with your accountant, you can download a PDF report with your expenses by clicking on the top right corner and then on the “Download” icon:
-
-![alt text](https://people-ops.status.im/content/images/2021/08/Exp-1.png)
-
-![alt text](https://people-ops.status.im/content/images/2021/08/Exp-2.png)
-
-## General Guidance
-You will always need to submit a receipt with each expense you log. Make sure to take photos or keep digital receipts handy - missing receipts might end up in your reports not being approved.
-
-Please select a Category for each expense, and include a comment indicating how the expense is business-related, including any additional context that will help the expense reviewer identify that the expense is appropriate. As an example:
-
-* Team Event Expense
-  * Category: Events
-  * Description: "Devcon Conference, Berlin - Taxi from LHR airport to conference with 1 other team member, Joe"
-
-* Another Team Event Expense
-  * Category: Meals & Drinks
-  * Description: "People Ops Meetup - Evening meal on May 26th with 3 others: John, Jane, Joseph"
-
-We suggest submitting an expense reimbursement report only when the total value is above USD 50.
-
-Expense reimbursements are paid together with the monthly compensation invoice. If you have questions or concerns regarding the expense reimbursement date, please contact the Finance team, and they will be happy to help you with that.
-
-For any other questions related to this process, please feel free to ping the Finance team in the #ask-finance channel or through an email to <billing@status.im>.
-
-People Ops
-Read [more posts](https://people-ops.status.im/author/pops/) by this author.

src/finance/expense-reimbursements.md

@@ -0,0 +1,92 @@
+# Expense reimbursements
+
+## How to get reimbursed for expenses?
+
+You can request a reimbursement for expenses incurred on behalf of Status during the project's development. You can read about some of these expenses at:
+   * [Workspace, computers and devices](src/perks/workspace-computers-and-devices.md)
+   * [Events and meetups](src/perks/events-and-meetups.md)
+   * [Traveling for Status](src/remote-at-status/traveling-for-status.md)
+   * [Essential reading](src/welcome-to-status/essential-reading.md)
+
+It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly. The standard expense reimbursement process uses:
+   * [Expensify](https://www.expensify.com/) to report and store the expense receipts, AND
+   * Adding expenses to your monthly invoice sent to `billing@statusm.im` to send the reimbursement.
+
+## How to report expenses through Expensify
+
+We use Expensify to store and report the expense details and receipts incurred on behalf of Status during the project's development.
+
+### Account setup
+
+You'll need to head to the [Expensify](https://www.expensify.com/) web or download the mobile app and sign in using your Status email to get started. Please input your full name as it appears in your Bamboo profile when setting up your Expensify account.
+
+![expensify-login](/src/images/expensify-login.png/)
+
+### Uploading expenses
+
+We kindly ask you to upload expenses as they incur or by the end of a trip to avoid complications like old or lost receipts. 
+
+Go to the `Expense` tab on either the web or mobile apps to upload expenses manually or by scanning them:
+
+![expensify-new-expense](/src/images/expensify-new-expense.png/)
+
+   1. Make sure to fill or review all the fields as the scanning feature isn't always reliable. Pay special attention to amounts and currencies.
+   2. You should claim expenses using the date they incurred. For example: if the purchase happened on Jan 10th and you're uploading or requesting the reimbursement on Jan 14th, the correct expense date would be Jan 10th.
+   3. When paying for a group (i.e., a meal shared with other contributors from Status), please list all those in attendance in the `attendee's` field.
+   4. Choose a category for your expense and add a detailed description of how's it business-related. Include information such as the trip it belongs to, who approved it, what budget it comes from, whether or not you've paid for other contributors (i.e., group meal), and any other data you consider relevant.
+
+     * Team Event Expense
+          * Category: Events
+          * Description: "Devcon Conference, Berlin - Taxi from LHR airport to conference with 1 other team member, Joe"
+
+     * Another Team Event Expense
+          * Category: Meals & Drinks
+          * Description: "People Ops Meetup - Evening meal on May 26th with 3 others: John, Jane, Joseph"
+
+![expensify-expense-details](/src/images/expensify-expense-details.png/)
+
+   5. If it's your first expense of the month, create a new report for all costs incurred during that period. Otherwise, add it to an existing one.
+   6. We suggest submitting an expense reimbursement report only when the total value is above USD 50.
+   7. You **must** submit expenses as expenses rather than an invoice.
+
+![expensify-expenses-expenses](/src/images/expensify-expenses-expenses.png)
+
+> ⚠️ You **always need to submit a receipt with each expense you log.** Make sure to take photos or keep digital receipts handy - missing receipts might result in your reimbursements not being approved. We understand that in some rare cases, this is not possible. When not possible, please provide as much info as possible and why no receipt is possible.
+
+### Submitting an expense report for approval
+
+Uploading expenses and submitting an expense report are different actions within Expensify. Once you've uploaded all your receipts, it's fundamental that you submit the report for Finance's review and approval.
+
+You must submit the expense report by the 10th of the month before submitting the monthly invoice on the 15th. To do that, click the `Reports` tab and `Submit` your report.
+
+![expensify-report](/src/images/expensify-report.png/)
+
+Please follow these links if you need help with [creating expenses](https://community.expensify.com/discussion/4560/how-to-create-expenses-manually) and [submitting reports](https://community.expensify.com/discussion/4561/how-to-submit-a-report/p1?new=1) on Expensify. If you need further help, reach out to the Finance team, and we'll be able to guide you through the process.
+
+### Adding the expenses to your monthly invoice
+
+The finished and approved report from Expensify will show the total for each expense category. For example, if you have several costs in one category, Expensify will show the following:
+
+![expensify-categories.jpg](https://people-ops.status.im/content/images/2021/08/Exp-3.png)
+
+Your invoice should only contain the total per category, not each expense item.
+
+As guidance, we have added these categories in the invoice template here. Please, ensure your invoice has the same category names as the Expensify reports to avoid delays with the expense claim approval.
+
+If you would like to set up these categories in your accounting software, please ask the Finance team for the complete list of expense categories.
+
+If you need to share the report with your accountant, you can download a PDF report with your expenses by clicking on the top right corner and then on the `Download` icon:
+
+![alt text](https://people-ops.status.im/content/images/2021/08/Exp-1.png)
+
+![alt text](https://people-ops.status.im/content/images/2021/08/Exp-2.png)
+
+## When you're going to be reimbursed
+
+Expense reimbursements are paid together with the monthly compensation invoice. If you have questions or concerns regarding the expense reimbursement date, please get in touch with the Finance team, and we'll be happy to help you with that.
+
+If you have other questions related to this process, please feel free to ping the Finance team in the #ask-finance channel or through an email to `billing@status.im`.
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.

src/finance/getting-paid.md

@@ -0,0 +1,112 @@
+# 💰 Getting paid
+
+As a Contributor, you need to send your PDF invoice to the Billing inbox. Here you'll find helpful information about deadlines, formats and other requirements to get compensated correctly on time.
+
+## Invoices due date
+
+Send your invoice in PDF format to `billing@status.im`, latest on the 15th. Your invoicing period is the current calendar month (i.e., invoice by October 15 for your services in October).
+
+## What to include
+
+You need to include your total expenses per category in your invoice (and these should be submitted separately via Expensify). Check out [expense reimbursements](/src/finance/expense-reimbursements.md/) for more details on this topic.
+
+Your invoice should include:
+   * Your legal name and address as per your agreement.
+   * A unique invoice number.
+   * The date the invoice is issued.
+   * Payment due date.
+   * Status legal entity with which you have the services agreement.
+   * The date range of the invoicing period according to your agreement (i.e., "March 1 to March 31").
+   * Description of the service rendered or reference to your contract.
+   * Total per category for expense reimbursements being claimed as per the [expense reimbursements guide](/src/finance/expense-reimbursements.md/).
+   * According to your agreement, the full fee and the fiat currency (in CHF, USD, EUR, or other).
+   * Your contributor number as per your Bamboo profile.
+
+You can use [this template](https://docs.google.com/spreadsheets/d/1FbH0CxLqar0ZyjhiMEA5ceToL2ikv5C-Rv-qCwBNeRA/edit#gid=790763898), but please remember to download the finished invoice as a PDF before sending it and that the exported PDF is on a single page.
+
+Address the invoice to the Status legal entity with which you have your agreement. The primary Status Legal Entities are:
+   * Status Research & Development GmbH, Baarerstrasse 10, 6302 Zug, Switzerland
+   * Status Research & Development Deutschland GmbH, ℅ Cormoran GmbH, Am Zirkus 2, 10117 Berlin, Germany
+   * Status Holdings Pte. Ltd., 160 Robinson Road, #24-09, Singapore 068914
+
+There are exceptional cases where another legal entity applies. Please use the company and address as detailed in your agreement.
+
+## Payment method
+
+### Bank and Wallet details
+
+Please maintain your details on your Bamboo profile if you have one. For simplicity, we only allow the indication of one wallet and one bank account (if you have intermediary accounts, please use the appropriate fields of the Bank Information section). You can edit it directly if you want to change the % paid in ETH, DAI, or SNT. Once you save it, it will send an approval request to the Finance team —the reason is so that we get a notification that something's changed and can update our payment records timely.
+
+Only after we confirm the approval will your changes be reflected in your Bamboo profile, and you can then change your payment split preferences again.
+
+If you need a specific reference to complete this payment, please state it explicitly on your invoice.
+
+> ⚠️ To make sure that your changes are considered for the current month, change your info before the 15th. Remove accented or special characters. We can only correctly upload plain text to the system.
+
+Please be sure that your employment contract or services agreement reflects your registered address for banking purposes, as our bank sometimes asks us to validate that banking details match contract details.
+
+### Getting Paid in Crypto
+
+If you are new to crypto payments and wallets, [this guide](https://support.mycrypto.com/how-to/getting-started) provides a good introduction.
+
+We recommend using a hardware wallet like the Ledger Nano S or a Trezor to secure your assets.
+
+Don't be shy to ask your more experienced colleagues in the #people-ops channel when you have questions about crypto payments and wallets. Not everyone starts with the same level of knowledge, and building it up is part of working with Status.
+
+### Rate Calculation
+
+For determining rates when paying in crypto, we establish the following two rates: using coinmarketcap.com as a price source, and the rate which is most attractive for the individual receiving crypto:
+
+   * The average closing rate across the last five days of the invoiced period, OR
+   * The current rate when payments are being issued.
+
+You can change your split % preference monthly. Just make sure you update your preferences on Bamboo before the 15th of the month.
+
+## Special situations
+
+### December pay
+
+As the holiday season affects the regular working days, we might bring forward the December payment run. Please be aware of date changes for the December payment run.
+
+### Hourly rate contributors
+
+If you're paid on an hourly basis and need to estimate your hours in the remainder of the month and reconcile them in the next invoice (as you'll be invoicing by the 15th of each month), it's ok to do that, or you could carry forward actual hours to your next invoice.
+
+If your fees have been agreed on an hourly rate basis, our monthly cap for hours billed is the lower of either the amount specified in your agreement with us or the number of business days in the month x 8.5 hours per day, i.e.:
+
+A month with 23 workdays has an hourly billing cap of 23 * 8.5 hours = 195.5 hours.
+
+Please discuss with People Ops if you intend to bill over this amount.
+
+### Pro-rating the first month
+
+For your first month (if being paid on an annual or monthly basis), please prorate the amount in your invoice to reflect the number of days from the beginning of your contract to the last day of the month.
+
+*Example: If March has 22 working days (counting Mon-Fri) and you started on a Monday, March 12, your monthly invoice amount will be {your monthly fee amount}/22 x 15.*
+
+Please bill the flat monthly or annual/12 figure for each subsequent month.
+
+*Example: You joined Status on March 12. During April, you took 1 week of vacation. Your April invoice amount will be {your monthly stipend amount in full} or {your annual stipend amount}/12*
+
+Please use the working days shown below for your calculations:
+
+**Working days 2022**
+
+| January - 21 | February - 20 | March - 23 |
+|:---:|:---:|:---:|
+| April - 21 | May - 22 | June - 22 |
+| July - 21 | August - 23 | September - 22 |
+| October - 21 | November - 22 | December - 22 |
+
+### Expense Reimbursements
+
+From time to time, you might need to pay reimbursable expenses for the development of the project. To read more on how to get reimbursed for these expenses, please follow [this link](/src/finance/expense-reimbursements.md).
+
+### Swiss and German employees
+
+You will be paid via monthly payroll as calculated by our outsourced payroll partners. There is no need to submit an invoice for your monthly salary. Please, maintain the percentages you wish to receive in crypto on your Bamboo profile, as we will prepare payments based on the split you indicate there.
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.

src/finance/third-party-invoices-format.md

@@ -0,0 +1,50 @@
+# 🧾 Third-party invoices format
+
+As part of contributing to Status, you might need to submit invoices or engage with service subscriptions or external vendors and contractors. This page has information about what we'll need to provide fully compliant invoices.
+
+Here's a sample of how invoices should look, as well as all the appropriate data points needed. If any data is missing from the invoice, we won't be able to pay it and will ask you to arrange a revision with the vendor.
+
+## Supplier Information
+   * Supplier Name (*);
+   * Supplier Address (*);
+   * Supplier’s tax registration number (if applicable);
+   * Supplier’s telephone number, contact person and email address (optional);
+   * Payment information (optional).
+
+## Status Information
+   * Status legal entity and invoicing address (*).
+
+|  🇨🇭 Status Switzerland |  🇸🇬 Status Singapore |  🇩🇪 Status Germany |
+|:---:|:---:|:---:|
+| Status Research & Development GmbH | Status Holdings Pte. Ltd. | Status Research & Development Deutschland GmbH |
+| Baarerstrasse 10, | 160 Robinson Road, #24-09, | Am Zirkus 2, |
+| 6302 Zug, | 068914, Singapore | 10117 Berlin, |
+| Switzerland | Singapore | Germany |
+| MWST-Nr: CHE-319.159.934 MWST | UEN: 201625575Z | USt-IdNr: DE317300297 |
+
+## Content Information
+   * The word INVOICE or CREDIT NOTE or DEBIT NOTE (*);
+   * Invoice/note number (must be unique) (*);
+   * Invoice/note date (dd/mm/yyyy) (*);
+   * Due date (dd/mm/yyyy) (*);
+   * Payment terms (optional);
+   * Currency (*);
+   * Specification of goods and/or services delivered (*);
+   * Total net amount (if no taxes are applicable) (*).
+**If taxes are applicable**
+   * Tax amount (*);
+   * If multiple taxes are applicable, the tax rate for every net amount should be specified (*);
+   * Total payable amount (*).
+
+*/* Mandatory fields.*
+
+*****
+
+Without this information, we run into issues with properly booking the expense for accounting purposes, which creates extra work hours to resolve on the backend. So thanks in advance for helping us out on this 🙌🏻 
+
+If you have any questions on whether your invoice has the format and information needed, feel free to reach out to the Finance team, and we'll look into it together!
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.

src/fundamentals/contributor-code-of-conduct.md

@@ -0,0 +1,110 @@
+# ⚓️ Contributor Code of Conduct
+
+The Code of Conduct serves to establish guidelines on how to conduct your behavior.
+
+We are all responsible for maintaining and developing this shared environment. We want to have a common productive, collaborative, and socially accountable space.
+
+We hope that all our community members share our views and nurture this spirit and culture in their dealings with the Status community.
+
+This code acts as both a courtesy to the overall community and an effective way of making your interactions with other Status users mutually beneficial.
+
+Familiarising yourself with the guidelines here is an essential precondition to your participation in our community.
+
+This Code of Conduct governs how we behave in public or in private whenever the project will be judged by our actions. We expect it to be honored by everyone who represents the project officially or informally, claims affiliation with the project, or participates directly.
+
+## Respect other users
+
+Status is about showing respect and humanity for one another: the word itself captures the spirit of social esteem in a human community. We want to grow a productive and agile place that can welcome new ideas in a complex field. We wish to improve every process in every development cycle and foster collaboration between groups with very different needs, interests, and skills.
+
+We gain strength from diversity and actively seek participation from those who enhance it. This Code of Conduct exists to ensure that diverse groups collaborate to mutual advantage and enjoyment.
+
+## Reciprocate
+
+Nothing is more important than to show appreciation for every and anyone's contributions, no matter if big or small. We show reciprocation by saying "thank you," contributing ourselves, and paying it forward.
+
+## Be Considerate
+
+Other people will use our work, and we, in turn, depend on the work of others. Any decision we take will affect users and fellow team members, and we should consider them when making decisions.
+
+When somebody leaves or disengages from the project, we ask that they do so in a way that minimizes disruption to the project. They should tell people they are leaving and take the proper steps to ensure others can pick up where they left off.
+
+## Respect the staff
+
+Core contributors have been chosen on a specific basis to have good judgment. The staff will always attempt to implement universally peaceful solutions but are tasked with establishing the most civil solution for the majority of the community.
+
+Therefore, they cannot always please everyone with the decisions made. Please, help out to contribute to a healthy community.
+
+## Responsibility of actions
+
+We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully and work together to resolve the problem. We expect those involved in the project to resolve disagreements constructively.
+
+The participants in the project should be able to accept and give constructive criticism, be it positive or negative. That is how we learn to work better.
+
+## Civility
+
+Uncivil behavior will not be tolerated in our community. Sutton's "No Asshole Rule" has these concise pointers on the kind of behavior that is considered uncivil:
+
+> Two tests are specified for recognition of the asshole.
+> 
+>   1. After encountering the person, do people feel oppressed, humiliated, or otherwise worse about themselves?
+>    2. Does the person target people who are less powerful than them?
+> 
+> Their unpleasant actions are cataloged as The Dirty Dozen:
+> 
+>   * Insults
+>   * Violation of personal space
+>   * Unsolicited touching
+>   * Threats
+>   * Sarcasm
+>   * Flames
+>   * Humiliation
+>   * Shaming
+>   * Interruption
+>   * Backbiting
+>   * Glaring
+>   * Snubbing 
+
+## Feel Free to Ask
+
+If there's something you don't know, do ask. Questions are encouraged. 
+
+Nobody is expected to be perfect in this community. Many newcomers just want to get acquainted with the project, so asking questions early avoids many problems later. The project is fast-paced and ever-evolving, so even people that have been around a long time might have questions.
+Those who are asked or answer a general question should be responsive and helpful. Directing people to the appropriate forums or channels is good, but answering the question is more important.
+
+## Be Collaborative
+
+What we work together to produce is a complex whole made of many parts and is the sum of many dreams. Collaboration between teams that each have their own goal and vision is essential. To be efficient and effective, and for the whole to be more than the sum of its parts, each team must make an effort to understand the system as a whole.
+
+Wherever possible, we work closely with projects in the same space and others in the Ethereum community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible. Collaboration at all levels improves the quality of our work, and we value it both internally and externally.
+
+## Discuss and Communicate
+
+Our community values discussion, information, and decisiveness. We all lead by example, both in discussion and in action. We want to encourage new participants to feel empowered to take action, experiment when they feel like their innovation could improve the project, and lead.
+
+Sometimes not all of the data is available to everyone or a consensus on how to act can't be reached, but a decision must still be made. Not every participant will always agree on everything, but once a decision is made, it should be respected, accepted, and work continued to achieve the common goal.
+
+## Give credit where credit is due
+
+Some members may be more visible than others, but good ones use their visibility to highlight the great work of others. This may be accomplished in various ways, not limited to rewarding community members for their efforts.
+
+## Open Source Community
+
+We invite any and everybody to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required commitment, capacity, and competence.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise, unacceptable behavior may be reported by contacting the Status People Ops team at `people-ops@status.im` or pinging the individual POPs folks for a confidential chat.
+
+All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The People Ops team is obligated to maintain confidentiality regarding the reporter of an incident.
+
+Allegations of misconduct typically require some behind-the-scenes fact-checking to verify what happened. If you're involved in an incident of misconduct, you'll be asked for your observations and recollections of the event. People Ops will follow up with you to let you know the next steps. 
+
+Depending on the severity of the misconduct, this may be a formal warning, through to immediate dismissal.
+
+## License
+
+Status.im is a Free Software project, and the individuals and communities around it are its custodians. We choose not to exclude others from using, understanding, modifying, and distributing our work. In doing so, we trust one another to act in the best interests of the broader human community that Status.im is designed to serve. This license holds the developers to account in the knowledge that the software is a common trust and that it is a privilege and a responsibility to continue to develop it.
+
+*****
+
+*The Status Code of Conduct is licensed under the Creative Commons Attribution-Share Alike 3.0 license and has been adapted from the Ubuntu Code of Conduct v2.0, and the Contributor Covenant v1.4. You may re-use it for your project and modify it as you wish. Please allow others to use your modifications and give credit to Ubuntu, Contributor Covenant, and Status.*

src/fundamentals/contributor-privacy-policy.md

@@ -0,0 +1,72 @@
+# 🔑 Contributor Privacy Policy
+
+As you can see from our [principles](https://our.status.im/our-principles/), we take privacy and transparency seriously. We strive to only request necessary and required data and not to hold that data longer than necessary. 
+
+Here is a quick explanation of what data we obtain, how we use that information, and how to update/control that information.
+
+## Policy brief & purpose
+
+This Core Contributor Privacy Policy refers to our commitment to treat the information of employees, contractors, and contributors with the utmost care and confidentiality.
+
+With this policy, we ensure that we gather, store and handle data fairly, transparently and with respect towards individual rights.
+
+## About
+
+As part of our operations, we need to obtain and process information. 
+
+This information includes any offline or online data that makes a person identifiable such as names, addresses, usernames and passwords, digital footprints, photographs, social security numbers, financial data, etc.
+
+Status collects this information in a transparent way and only with the full cooperation and knowledge of interested parties. Once this information is available to us, the following rules apply.
+
+Our data will be:
+
+   * Accurate and kept up-to-date.
+   * Collected fairly and for lawful purposes only.
+   * Processed by Status within its legal and moral boundaries.
+   * Protected against any unauthorized or illegal access by internal or external parties.
+
+Our data will not be:
+
+   * Communicated informally.
+   * Stored for more than a specified amount of time.
+   * Transferred to organizations that do not have adequate data protection policies.
+   * Distributed to any party other than the ones agreed upon by the data's owner (exempting legitimate requests from law enforcement authorities).
+
+In addition to ways of handling the data, Status has direct obligations towards people to whom the data belongs. Specifically, we will:
+
+   * Let people know which of their data is collected.
+   * Inform people about how we'll process their data.
+   * Inform people about who has access to their information.
+   * Allow people to request that we modify, erase, reduce, or correct data contained in our databases.
+
+## Data
+
+   * **You provide:** as part of the recruitment/onboarding process, we may ask you to provide relevant data such as name, contact details, bank account, or wallet address. We may also request social security, identification, passport, or national insurance details where required by law. Depending on your contract with us, you may also provide us details of hours/days worked so that we can compensate you appropriately or verify that we have fulfilled our compliance obligations as your employer.
+   * **We obtain:** assessments of your performance during the trial period and on an ongoing basis (based on peer feedback and evidence of work), details of periods of leave taken by you, including holiday, sickness absence, family leave, and the reasons for the leave, and notes of our discussions with you. We endeavor to maintain accurate information.
+   * **We store:** pay records, including payslips and invoices; copies of contracts and formal notices/letters relating to your employment/contracting relationship with us.
+
+You can request to see a copy of the data we hold on you. To do so, please get in touch with People Ops to make an access request.
+
+## Use
+
+   * We store most of your data in our HR System (BambooHR). We keep some data (documents, payslips) in a secure Google Drive Folder. We tightly control access to the data to only members of the organization that have a valid reason to access your information (generally - People Ops & Finance).
+   * We share the minimum necessary amounts of your data with the following third-party accounting, payroll, benefits, and compliance partners as applicable for statutory filings, benefits, and reporting:
+        * HMT Partners (Switzerland)
+        * The Friendly Accountants (UK)
+        * Fidura (Switzerland)
+        * Buchhalter Berlin / Lohnstar (Germany)
+        * Pikohana (Singapore)
+        * Atelier Consulting AG (Switzerland)
+        * SwissLife (Switzerland)
+        * Ebner-Stolz (Germany)
+        * 3E Accounting (Singapore)
+        * Yourpension (Switzerland)
+        * Cleverkin S.R.O.
+   * We will request your permission before releasing your data to any other third-party.
+
+We hold your data while you are a contributor. If you're an employee, upon leaving Status, our policy is to store your data for a minimum of six years to comply with international statutory HR information retention legislation. We will delete your data after six years. If you have a question about the data we hold or how we use it, don't hesitate to contact `people-ops@status.im`.
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the Legal team to review it.

src/fundamentals/essential-reading.md

@@ -0,0 +1,38 @@
+# 🎓 Recommended reading
+
+We encourage using some time to learn about things related to your tasks and our collective mission. Make your peers aware of you being on/offline and that the team's progress doesn't get hindered. Feel free to discuss it openly and agree on timing with everyone involved.
+
+We offer an annual learning budget of 170 USD for each core contributor. You can use this budget towards things like books, conferences, or online courses. Speak with your team lead to request additional funding if needed.
+
+> ℹ️ Team leads: if there's room in your budget, you can approve learning requests directly. Otherwise, create a [funding request](./finance/requesting-funding.md).
+
+If you need a reference, a regular contributor could spend their first 1-4 weeks spending 50% of their billed hours to learn and ~2-5 hours p/w after that on an ongoing basis. This is just an example, and we encourage you to figure out a learning cadence that best helps you succeed in contributing to Status.
+
+We've made a selection of readings that can help give you more context of our vision and culture. 
+
+We've added PDFs whenever possible, but you can also order them and [file a reimbursement](/src/finance/expense-reimbursements.md) for books or other applicable learning expenses. Read them at your own pace! We highly recommend you read the first group; the second one is nice to go through but less critical.
+
+## Essential reading
+
+   * [The Starfish and the Spider: The Unstoppable Power of Leaderless Organizations](https://www.goodreads.com/book/show/21314.The_Starfish_and_the_Spider)
+   * [Decentralization by Vitalik Buterin](https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274)
+   * [The Cluetrain Manifesto](https://www.goodreads.com/book/show/81195.The_Cluetrain_Manifesto)
+   * [The Cathedral and the Bazaar (PDF)](https://www.goodreads.com/book/show/134825.The_Cathedral_the_Bazaar)
+   * [Radical Markets: Uprooting Capitalism and Democracy for a Just Society](https://www.goodreads.com/book/show/36515770-radical-markets)
+   * [The Wealth of Networks: How Social Production Transforms Markets and Freedom](https://www.goodreads.com/book/show/14721.The_Wealth_of_Networks)
+   * [The Myth of Leadership: Creating Leaderless Organizations](https://www.goodreads.com/book/show/2406955.The_Myth_of_Leadership)
+   * [Organization after Social Media](https://www.goodreads.com/book/show/41546391-organization-after-social-media)
+   * [Swarmwise](https://falkvinge.net/files/2013/04/Swarmwise-2013-by-Rick-Falkvinge-v1.1-2013Sep01.pdf)
+
+## Recommended reading
+
+   * [Pirate's Dilemma: How Youth Culture Is Reinventing Capitalism](https://www.goodreads.com/book/show/2286633.The_Pirate_s_Dilemma)
+   * [Cyberchiefs: Autonomy and Authority in Online Tribes](https://www.goodreads.com/book/show/6449779-cyberchiefs)
+   * [Capitalism 3.0: A Guide to Reclaiming the Commons](https://www.goodreads.com/book/show/640034.Capitalism_3_0)
+   * [Protocol: How Control Exists after Decentralization](https://www.goodreads.com/book/show/274500.Protocol)
+   * [Pirate Organization: Lessons from the Fringes of Capitalism](https://www.goodreads.com/book/show/13586923-the-pirate-organization)
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/fundamentals/security-guidelines.md

@@ -0,0 +1,53 @@
+# 🔐 Security guidelines
+
+Security is a priority at Status, and we'd like to thank you in advance for taking steps to secure your devices and online accounts. 
+
+Here you'll find helpful links to resources to protect yourself and the organization from attackers. 
+
+> In much the same way we've decentralized the organization and applications, we've done the same for security.
+>
+> It means the vast majority of the attack surface is you, the people that contribute. Furthermore, the controls and information a security specialist has in terms of making decisions and monitoring how things are run is constrained. It also means education takes a forward step in importance across the organization, and personal responsibility of quality security practices become paramount. It is up the people to understand potential threats, take preventative measures, and report any issues they come across to the security team to protect the organization as a whole.
+> – @petty
+
+## Ask for help
+
+Above all else, never be afraid to ask for help, ask questions, or report security concerns. Until we have an official infrastructure for support tickets, drop by:
+
+   * #security for more broad, public questions.
+   * #security-internal for anything that is more private.
+   * Drop an email to `security@status.im` if none of the above channels fit.
+
+All contributors with an onboarding process will have a security touchpoing with the security team during the first month of their onboarding.
+
+## Best practices checklists
+
+Review & follow this [checklist](https://github.com/status-im/status-security/blob/master/process/personal-security-checklist.md) to make sure you are complying with our best practices.
+
+Fancy giving your security a spring clean? Check out [this](https://winter.mycrypto.com/) crypto advent calendar with daily bite-sized security tips.
+
+Phishing attacks are the most common: discord bots, telegram messages, and email, amongst other channels. Take this [phishing test](https://phishingquiz.withgoogle.com/) to see how savvy you are when it comes to detecting phishing.
+
+## Hardware
+
+Check out this [list](https://notes.status.im/zkr20eWFTwGD92xixGX2CA) of essential hardware. Core contributors can expense hardware security keys (yubikeys) and should be used for Github, Gsuite, and Bitwarden.
+
+Here's Corey's Status Learn-Up session about [hardware wallets and best practices](https://www.youtube.com/watch?v=9nzqntuFR44&ab_channel=HashingItOut).
+
+## Password manager
+
+Our password manager is [Bitwarden](https://bitwarden.com/). All organizational passwords should be kept and shared here. So if you plan to store a Status related password, or get access to platforms that require username/passwords/2fa, then it should all be shared using Bitwarden.
+
+You can request an invite in #people-ops. By signing up with the organization, you get the premium features and sign up with any email you like. That way, if you ever leave Status, you can take your password manager secrets with you, and you only lose access to Status related items.
+
+## Security team
+
+Learn more about Security @ Status at:
+
+   * [Status Security](https://status.im/security/)
+   * [status-im/status-security](https://github.com/status-im/status-security)
+   * [status-im/security-internal](https://github.com/status-im/security-internal)
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/hiring/index.md

@@ -0,0 +1 @@
+# Hirign

src/index.md

@@ -1,3 +1,11 @@
 # Introduction
 
-This is a nintroduction to the Status People Ops handbook.
+The Status Network is an open set of projects building peer-to-peer technologies for people to transact securely and communicate freely. We build decentralized technologies ranging from protocol-level infrastructure to consumer applications — forming an open-source peer-to-peer technology stack.
+
+The [Status](https://status.im/get/) app is a secure communication tool that upholds human rights. Designed to enable the free flow of information, protect the right to private, secure conversations, and promote the sovereignty of individuals. [Discover more projects →](https://statusnetwork.com/)
+
+### Contributing
+
+Status is an open community, you don’t need to ask permission to join or become a member. If you see something you think should be improved, you can [make a PR](https://github.com/status-im/),  join our [Discord](https://discord.gg/2HyyjgFHVK) or create a [a proposal](https://discuss.status.im/) and make it happen.
+
+You can also contribute to specific Status Network projects such as [Waku Connect](https://wakuconnect.dev/) or [Nimbus](https://nimbus.team/). As an open-source project, we are location-agnostic and operate fully remote. You can find what profiles each project is looking for [on this page](https://jobs.status.im/). 

src/our-principles.md

@@ -0,0 +1,33 @@
+# 🗿 Our Principles
+These principles act as tools. Tools for thinking, for communication, and for decentralized decision making. They keep us honest about where we are failing short of our vision.
+
+
+### I. Liberty
+We believe in the sovereignty of individuals. As a platform that stands for the cause of personal liberty, we aim to maximize social, political, and economic freedoms. This includes being coercion-resistant.
+
+### II. Censorship Resistance
+We enable free flow of information. No content is under surveillance. We abide by the cryptoeconomic design principle of censorship resistance. Even stronger, Status is an agnostic platform for information.
+
+### III. Security
+We don't compromise on security when building features. We use state-of-the-art technologies, and research new security methods and technologies to make strong security guarantees.
+
+### IV. Privacy
+Privacy is the power to selectively reveal oneself to the world. For us, it's essential to protect privacy in both communications and transactions, as well as being a pseudo-anonymous platform. Additionally, we strive to provide the right of total anonymity.
+
+### V. Transparency
+We strive for complete openness and symmetry of information within the organization, and have no border between our core contributors and our community. We are frank about our shortcomings, especially when making short-term tradeoffs in service of our long-term goals.
+
+### VI. Openness
+The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation.
+
+### VII. Decentralization
+We minimize centralization across both the software and the organization itself. In other words, we maximize the number of physical computers composing the network, and maximize the number of individuals who have control over the system(s) we are building.
+
+### VIII. Inclusivity
+We believe in fair and widespread access to our software, with an emphasis on ease-of-use. This also extends to social inclusivity, permissionless participation, interoperability, and investing in educational efforts.
+
+### IX. Continuance
+We create software incentivized to continue to exist and improve, without the stewardship of a single entity or any of the current team members.
+
+### X. Resourcefulness
+We are relentlessly resourceful. As we grow and have ready access to capital, it is our obligation to token holders to fight bureaucracy and inefficiencies within the organization. This means solving problems in the most effective way possible at lower economic costs (in terms of capital, time and resources).

src/perks/computers-and-devices.md

@@ -0,0 +1,67 @@
+# 🖥 Computers and devices
+
+Having the proper setup is fundamental to ensuring you can work comfortably. Since we're all working remotely, you can choose what suits you best within a budget. If you're a core contributor at Status, we'll provide you with the tools required to succeed in your role during your onboarding. 
+
+Here you'll find helpful information to set yourself up with the computers and devices you need.
+
+## ☑️ Pre-approved equipment
+
+All core contributors have a list of pre-approved equipment budgets previously considered within their team budgets. That means you do not need prior approval from Finance to expense up to the pre-approved amount. Let your team lead know about your equipment purchasing plans. Follow the instructions below to get your computer and other devices.
+
+The standard setup for everyone includes a laptop, headphones, a Keycard, a Yubikey, and a Ledger. 
+
+We defined the amounts to cover a range of options, so you will stay below that budget in most cases. When that happens, note that pre-approved amounts aren't "balances," and you can't spend the difference for other stuff.
+
+   * Laptop: up to 2000 USD
+   * Mic and headphones: up to 100 USD
+   * Keycard: ping the #keycard channel to get a code 
+   * Yubikey: you can reimburse one
+   * Ledger: you can reimburse one
+
+For additional funds per item or other equipment, you need to obtain a previous approval from your team lead and add the approval details to your reimbursement. If your equipment needs fall outside your team's budget, you can [request funds](/src/finance/request-funds.md) for approval. Some examples of other equipment:
+
+   * Testing phones for engineering roles
+   * A printer for an ops role
+   * A digital sketchpad for a design role
+
+> ℹ️ If you're unsure whether or not this applies to you, ping People Ops. We occasionally have loan assets available to all contributors. 
+
+## 🎁 How to get your computers and devices
+
+   1. Let your team lead know prior to purchasing the devices. 
+   2. Choose official or trusted vendors to buy your equipment.
+   3. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
+   4. Once registered, request a refund by adding the expense to Expensify and your next invoice.
+   5. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area. 
+
+## ℹ️ FAQ
+
+   * **What if I'm a German or Swiss employee?**
+
+      If you're a German or Swiss employee, please be sure to buy your devices via an invoice addressed to the [German or Swiss entity](./finance/third-party-invoices-format.md). The invoice should be submitted to billing@status.im.
+
+   * **What if I don't have enough funds to buy the device before reimbursement?**
+   
+      If cash flow is an issue and you'd prefer not to outlay the cash upfront for your new device, please ping People Ops. We'll help you with the purchase.
+   
+   * **What if my devices become outdated?**
+   
+      After 36 months usage or if your device needs an upgrade, ping People Ops.
+      
+   * **What happens if I accidentally damage a device?**
+
+      You should treat the devices as if they were yours. If the damage was due to factors beyond your control, please obtain a quote for a repair and let People Ops know. If the cost is reasonable (i.e., less than ~75% of the trade-in value of the asset), we would ask you to go ahead and get the device repaired. Then, submit the repair expense cost for reimbursement.
+      
+   * **What if I leave Status?**
+
+      Please check out [this offboarding guide](/src/settling-in/offboarding.md) for your options on recycling or buying back your laptop.
+
+
+## Related articles
+
+   * [How to get reimbursed](/src/finance/expense-reimbursements.md)
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/perks/learn-ups/index.md

@@ -1 +0,0 @@
-# 🤓 Learn ups

src/perks/learn-ups/interview-training.md

@@ -1,3 +0,0 @@
-# 🔎 Interview training
-
-DAY TWO TEXT

src/settling-in/index.md

@@ -1 +1,17 @@
+# ⚓️ Settling in
 
+> Status is also more than a product, it is an experiment in organization. 
+> 
+> – Jarrad Hope
+
+None of us truly knows how our future will look. In all the flurry of productivity, it’s easy to overlook that what we are trying to do has never been done before. We are operating in a pretty much-unchartered territory, trying to:
+
+* Create a Public Good that has not been made before,
+* Transition our governance model to being decentralized and autonomous, and
+* Build a community around a movement.
+
+We’re still figuring out how we balance these things.
+
+Joining the Status community of core contributors means you will be working alongside bright and passionate people with a shared vision: a more decentralized future. Status is a transparent and collaborative environment designed to bring the best ideas to fruition. 
+
+The Status Network and the broader Web3 ecosystem are a fast-growing maze. Take time to orientate yourself, don’t rush, and spend time in your first few weeks really connecting with the people you’re working with, as they are the best and most up-to-date sources of information and support that exist. 

src/settling-in/onboarding-buddy.md

@@ -0,0 +1,90 @@
+# 🧭 Onboarding buddy
+
+We've created the buddy program to make the onboarding process in a remote team as warm and welcoming as possible. A buddy is there to connect new joiners, solve doubts as they appear, and immerse new contributors into our culture from the lenses of someone who's helped shape it.
+
+Here you'll find helpful information about what you can expect from your buddy and how to become a successful one.
+
+## How we match buddies
+
+The buddy system is role and location agnostic. We want folks across the organization to have the chance to meet and get to know others outside of those they'd work with regularly. 
+
+That means you may get paired with someone that has an entirely different role to you. The buddying conversations don't need to be technical. New contributors should have a team who will get them set up with a project in their first weeks. The buddy program focuses on the contributor experience, broader community, ecosystem, Status culture, vision, and mission.
+
+Suppose a new contributor still has lots of questions about their work responsibilities or role. In that case, you can help them connect with the right person to solve them.
+
+If the timezone difference makes it hard to pair, please let People Ops know, and we'll reassign a new buddy in a closer region.
+
+
+## For new contributors
+
+As a new contributor, it's not always easy to find a tenured peer to walk you through all things Status. We will match you with a buddy! You can find their username in BambooHR to send them a message to introduce yourself and set up recurrent calls during your first 4-6 weeks. There's nothing for you to prepare or do in advance of the weekly buddy calls:
+
+   * Your buddy will be ready to guide you on contributing to Status.
+   * The buddy chats are a safe space for you to ask whatever you'd like about working at Status --no topic too trivial or complex!
+   * Feel free to note as many questions as you like --you can ask these to your buddy either in your weekly chats or any time via DM.
+
+
+## For buddies
+
+Anyone can signup as a buddy. Normally, People Ops will reach out to propose you to pair with a new contributor prior or during their first days of onboarding.
+
+Offsites are a fantastic way to get to know people, so let's try to give the same vibe even if we're stuck for travel!
+
+
+**Time commitment**
+
+It depends on you and the person you will be buddying, but we expect it to be about 1 hour each week, for the first 4-6 weeks.
+
+
+**What makes a good buddy?**
+
+A good buddy is someone prepared to be a friendly support, an informal source of information on how the project works, and someone ready to share their experience.
+
+There's no set amount of time you should have worked with Status before becoming a buddy --everyone is very welcome to volunteer by reaching out to People Ops.
+
+
+**Roles and responsibilities of a buddy**
+
+   * As a buddy, you are not 'managing' that individual but a supportive colleague and friendly face.
+   * Helping your new colleague to navigate their way around Status.
+   * Answering questions – often more than once. Buddies need to be patient as new starters take in a lot of information, often in a short time, and may need to re-ask questions in the future as events occur.
+   * Provide information, signpost information, and informal support.
+   * Introducing them to other contributors who are relevant to their role.
+   * Helping them to understand the formal and informal culture and structures at Status.
+   * Getting the newbie comfortable with Status products and principles.
+   * Encourage them to ask questions if unsure about any aspects of their role. 
+   * When possible, arrange to meet up for coworking in the area, or introduce them to any other Status team members in their area. 
+   * Flag to People Ops topics or situations that seem confusing for new hires, so we can tackle them better and faster!
+   * Be a general all-round Status legend and share your love and passion for the project.
+
+
+**Guidelines for approaching the first meeting**
+
+If you haven't been a buddy before, don't panic or feel overwhelmed as the new joiner may have similar feelings. Remember every bit of knowledge and advice is valuable to the success of the new starter!
+
+On the new contributor's first few days with Status, People Ops will arrange an onboarding call to get them set up and introduce them to high-level information about working at Status. You are not expected to give them details from scratch or contact them immediately on their first day.
+
+The following checklist will help establish your relationship and decide how you will use the time spent together moving forward. It includes some suggestions for you to cover throughout your chats:
+
+- [ ] Establish frequency / duration of calls over a suggested 4-6 weeks.
+- [ ] Outline your role, experience at Status, what you're working on, and how that ties in with the organization.
+- [ ] Explain to them what the buddy program is, and your role as their buddy, and the type of topics you'll be covering in the weekly chats.
+- [ ] Walk through the Status app, how to contact people, and send each other messages and ETH/SNT.
+- [ ] Find out about their professional background and experience, and what they will be working on/they're excited about contributing.
+- [ ] Ask about their experience/comfort level with remote work, decentralized autonomous organizations, open-source, and community-based working.
+- [ ] Talk about Status's mission and objectives -- the State of Us, decentralization, the Principles, etc.
+- [ ] Discuss the working culture at Status. How is this different from other places the new contributor has contributed?
+- [ ] If relevant, introduce them to key people they may benefit from knowing outside of their immediate team.
+- [ ] Suggest what to read and other valuable resources for their role or get to know the company in general.
+- [ ] Ask them if they're confused about anything and help them figure out the answers they need. If you don't know the answers to some of their questions, it's okay --point them to someone who does, or ping #people-ops so we can look up a solution together.
+- [ ] Share some Status channels that they may find interesting to follow.
+- [ ] Get to know a bit about them as a person outside of work.
+- [ ] Talk about how to dogfood the app, give examples of how they can use it, where to report issues, nightly builds, etc.
+- [ ] Ask about their workstation --do they have a comfortable space to work? Are they aware of our coworking allowance?
+
+Make sure they know they can ask you anything regarding Status, and you will be happy to help. It's important to stress this often as new team members often can be afraid to bother, shy, or reluctant to ask at first!
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/settling-in/the-trial-period.md

@@ -0,0 +1,78 @@
+# 🦾 The trial period
+
+We consider your first 12 weeks of contributing full-time as a trial period. During this time, you'll work alongside and be treated like other Status contributors --you'll have access to the same information, software, (virtual) meetups, and learning opportunities. We're confident that you will be a great addition, or we wouldn't have extended an offer!
+
+However, we have seen that sometimes things don't work out. Working remotely, on new tech, with a super flexible team that's constantly iterating and evolving isn't to everyone's tastes. We want to be very upfront about what we expect from everyone on the team.
+
+A clearly defined initial tryout will allow enough time to get to know each other and fully appreciate how we can work together. It might also be that you decide that Status isn't what you're looking for, and that's okay too.
+
+## What we expect
+
+* We expect you to show us you can prioritize correctly, get things done, and find answers in an increasingly autonomous way. In most teams, there will be a first project scoped out for you. Regardless of that being the case, make sure you ask your lead from where you can start, clarify expectations for your role, or seek feedback on how you're doing, early and regularly.
+* We expect you to be accountable for your goals and deadlines. We don't micromanage - if by any chance you realize you're stuck, make sure to flag it and discuss within your team whether or not it would be best to change course.
+* We don't see each other much, and written communication is what we see the most from each other. We'd like for everyone to be clear, friendly, and helpful to everyone else.
+* We expect a consistent and high volume of communication to keep your fellow contributors updated on your progress. There's no expectation that you reply to each ping immediately. Do your work and avoid interruptions while checking your messages at least a couple of times a day. If you know you won't have time to look into something right away, let the other party know when they can expect to have an answer to organize their work efficiently.
+* Everyone should contribute to the products and our culture. If you see anything that can be improved and have an idea to make it better, bring it up! If you see that a co-contributor is stuck, offer to help or to ping someone who can. We're all in the same boat!
+* Read [this](https://medium.com/remote-work/12-qualities-to-look-for-when-hiring-remote-workers-68243ff351b0) article. It gives a sense of what qualities are most important to succeed in any role here at Status.
+* For those less experienced in the blockchain/crypto space - jump in and immerse yourself in the ecosystem and get to understand our principles and mission better. This is a big topic, and we don't expect everyone to become an expert. Still, we would be super impressed to see that you're committed to continuously learning and developing your knowledge.
+* Try to model our principles in all that you do at Status.
+
+
+## Mid-trial feedback
+
+When you reach the end of your first 6-8 weeks, People Ops will reach out to you and your team lead to get a list of the people you worked with more closely. We will send [this form](https://forms.gle/pvJA1ppVyRuEDi2MA) to collect feedback early to have time to take it on board during the remainder of the trial period.
+
+You'll get an email with the feedback collected that you can use for your mid-trial chat with your team lead to go through it and brainstorm ways to implement it. 
+
+
+## End-trial feedback
+
+At the end of the trial period, People Ops will do feedback rounds and send [this](https://goo.gl/forms/clmw6Klm08OhWgX33) end-trial feedback form to your chosen group of co-contributors.
+
+People Ops will aggregate the results within 1-2 weeks and share these back to you and your team lead in a format similar to the above. At that time, your team lead will make and communicate a decision on whether your trial has been successful.
+
+We hope for all our trials to be successful. Still, we might not see the potential for a productive future collaboration together. In that case, People Ops will then reach out to you about extending your trial or terminating your service agreement with Status and any related logistics.
+
+
+## ❓ FAQs
+
+   * **Who has access to the trial feedback?**
+
+     The People Ops team, your team lead, Carl, Jarrad.
+
+   * **Who decides on the trial outcome?**
+
+     The contributor's team lead, who is responsible for the contracting/staffing decisions on their project. People Ops acts as a facilitator in the process.
+
+   * **Can I give feedback anonymously?**
+
+     Yes --you can leave the Name field blank in the feedback form if you'd like to provide fully anonymous feedback.
+
+   * **How do you evaluate whether a trial is successful?**
+
+     Based on the feedback received via the trial process. We ask a diverse set of questions in the feedback form to get a mix of data points - numerical, qualitative, comparative. We aggregate all responses received. Work output not showing advancement of the Principles, nor important qualities like productivity, autonomy, or visibility, would be indicators of a poor role fit. Contribution not being impactful overall to Status's objectives or developmental feedback not being addressed would also be reasons to end the trial.
+
+   * **Why do you ask so many contributors for feedback?**
+
+     The response rate is typically ~60%. We want to get as many voices and opinions involved to make the process as fair as possible.
+
+   * **How will I know what happens with someone's trial?**
+
+     We want to be sensitive to each person's privacy by not discussing details about their performance with other contributors. As such, we don't (at this point) announce whether trials were successful or not, but we're open to changing that if people would prefer this was made transparent. We'd likely not be able to give specific details of a trial outcome, though.
+
+   * **Can I give trial feedback even if I wasn't directly asked?**
+
+     100%! You can share [trial](https://docs.google.com/forms/d/e/1FAIpQLSf9_P-F36U3ftuhcKkoXZa3yAi9bSRwG9E7pB-O0fHIVN7x6A/viewform) feedback anytime.
+
+   * **This process seems pretty centralized; what's up with that?**
+
+     You're not wrong! The trial feedback process was an interim solution to make contracting/staffing as high quality and consistent across Status, but it has stuck in the absence of better alternatives being identified. It's far from perfect, and we're always looking to adapt and iterate it, so [share your ideas](https://discuss.status.im/t/trial-periods-what-next/795) with People Ops, and we'll incorporate them!
+     
+   * **How do I get feedback after the trial period?**
+
+     We encourage a continuous feedback culture where you give and receive ongoing feedback. These happen recurrently through our internal feedback platform, during your chats with other contributors, and whenever there's feedback to be shared, such as at the end of a project or after a relevant event. 
+
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/settling-in/your-autonomy/downtime-faqs.md

@@ -0,0 +1,43 @@
+# 🔕 Downtime FAQs
+
+### Public holidays
+
+Given the diversity of cultures and locations at Status, we don't have Status-wide days off. We encourage you to book off your home or local public holidays or the ones close to your heart and beliefs. 
+
+### What happens if I'm out sick?
+
+As a general guideline, short-term sick days that don’t affect your capacity to meet your commitments are treated as regular time off and don’t need further action than recording it to Bamboo. 
+
+If you’re going to be unavailable for a prolonged period of time, you need to coordinate with the team lead and People Ops in order to review and adjust your service agreement accordingly. 
+
+### How does the confidentiality work?
+
+You can record your unavailability without explanation. 
+
+If you tell someone in People Ops about a health or personal issue, that information will be shared within the People Ops group, including Carl and Jarrad. Please, let People Ops know of any specific discussion we should keep off the record (i.e., only between you and the People Ops person you're talking with).
+
+People Ops won't tell other core contributors the specifics of your situation. We will be happy to help you communicate your unavailability period if you need help doing that (mentioning that you are offline unwell, giving no further details).
+
+## 🐣 Paternity
+
+First of all, congratulations! 🎊 We're happy about the new addition(s) to your family!
+
+### Next steps
+
+As soon as you're comfortable sharing the news, please ping `people-ops@status.im` to chat about your plans. It'd be great if you could give as much notice as you can –as a rule of thumb, at least equivalent to the number of days you'll be unavailable (i.e., if you want to take four weeks, let us know four weeks in advance).
+
+We'll do our best to accommodate you. Still, it may not always be possible considering your needs, length, and deliverables. We'll review each request on a case by case basis, involving your team lead.
+
+### SNT distributions
+
+We will pause your SNT distributions when you take a prolonged downtime period. In this case, you will forfeit any SNT distributions that occur during that period.
+
+For a short time period, you will still be eligible for your quarterly SNT distributions.
+
+### Access to tools/accounts
+
+In general, we will keep your access to Google and other centralized accounts open during your downtime.
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/settling-in/your-autonomy/index.md

@@ -0,0 +1,16 @@
+# 🦋 Your autonomy
+
+Projects have project leads who coordinate communications and resources. However, contributors don’t have managers, you collaborate directly with other contributors in the project. 
+
+There’s a huge amount of autonomy involved, and no one will give you granular detail about what to do, when to do it, and where to do it from. 
+
+When you first join, people ops will connect you with another contributor to help you get familiar with the Status ecosystem. You’ll have a couple of initial deliverables scoped out by the project lead to ease your onboarding and get you going, but beyond that, you’re expected to define and report on your work, reach out to others to collaborate, and hold yourself accountable to it. 
+
+These are some important areas to successfully collaborate in a remote and asynchronous environment:
+* Autonomy: You’re a self-starter, can handle ambiguity, and you have a good sense of when to start tasks on their own and when to ask for support. 
+* Motivation/Attitude: You take initiative and engage with your projects, you’re helpful towards others, ask questions, and regularly seeking to learn more.
+* Visibility into work: You communicate clearly and proactively update on deliverables progress, others always know what you’re working on.
+
+As a contributor, you have the autonomy to choose in what project, at what capacity, at which times and from what location you’d like to contribute to Status –as long as there’s mutual agreement with the organization. 
+
+Ideally you’re the kind of person that finds that thrilling, and not too terrifying. 

src/settling-in/your-autonomy/location-independence.md

@@ -0,0 +1,23 @@
+# 🌏 Location independence
+
+Status is a fully remote, location-agnostic organization –meaning that we don’t mandate the location where the services are to take place, except if you’re attending a specific event. 
+
+Being location independent means you could decide to move away from where you were first delivering your services, and that's okay. Status can provide you with confirmation of engagement letters if you need them in the process of migrating abroad.
+
+However, we cannot cover the visa/work permit processing or relocation costs as we're location agnostic for work. In case of relocation due to business reasons (i.e., we *really, really* need you to, and you agree to it), we will take care of all the processes and costs involved.
+
+#### What happens if I'm thinking about relocating
+
+Get in touch with People Ops to start a discussion about your relocation plans for potential contract considerations. We are sometimes limited in the number of contracts we can offer to certain locations.
+
+#### If you need company details
+
+If you need to indicate your occupation details on a visa application, please use the Status entity address as your consulting agreement.
+
+Please only refer to Status as your employer if the DE/CH entity formally employs you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.
+
+If you need to indicate a company representative on your application, feel free to contact People Ops for details. 
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/settling-in/your-autonomy/self-time-management.md

@@ -0,0 +1,35 @@
+# ⏳ Self-time management
+
+Status is a results-oriented organization –meaning that we care about your output (services provided), not your input (hours/days worked). 
+
+We don't mandate the days, schedule, or hours that you take to deliver the services –you're free to set your schedule and work from any place (home/coffee shop/coworking space) and timezone as long as they’re delivered within the agreed deadline.
+
+This system might be new to you, and if you'd like some guidance on self-time management or have any concerns about being productive –feel free to chat with anyone on the People Ops team who will be happy to coach you.
+
+## Communicating your availability
+
+If you have a 12-months contract with Status, we recommend being at least 20 days away (plus your local or cultural bank holidays) to disconnect and enjoy time doing things important to you. We expect and encourage you to disconnect as much as you need on top of this. 
+
+There is no need to communicate time off unless it's a full day or longer. Non-linear workdays are fine, as well as traditional schedules. Keep your hours in check for your good, make sure you get proper time away from screens, and turn notifications off your phone when you're offline. You are free to choose your working patterns as long as you meet your deliverables on time at the agreed quality standards. 
+
+Monthly and project rate contractors can invoice us for their agreed amounts in months when they take time off. Your contractor agreement is based on your services provided and does not mandate the time or location where the works are to take place. 
+
+### Create downtime entries
+
+We record contributors' unavailable dates with [Bamboo](https://statusim.bamboohr.com/) to [keep an overview](https://statusim.bamboohr.com/calendar) of who's around in the projects and products to help schedule launches, handoffs, etc.
+
+Bamboo doesn't allow to add an entry directly and insists that all dates entered are 'approved' by People Ops. Please, be assured that that's a workflow we can't amend in the system, and we approve all requests by default. 
+
+You don't need to 'ask' for permission. Just make sure to:
+
+* Communicate to the team lead and people you share in-progress projects with
+* Mark your unavailability on your project’s shared calendar (if there is one)
+* Coordinate appropriately and re-assign or delegate any piece of work that needs to progress in your absence. You can also use this [handover template](https://docs.google.com/spreadsheets/d/15pbTvWJf0luQflw1aRPtX7q00y89_h948Bf3Q861JDk/edit#gid=0) for temporary/short absences.
+
+### Deleting entries in Bamboo
+
+If you change plans and want to cancel or amend an entry, you can follow [these instructions](https://help.bamboohr.com/hc/en-us/articles/227886287-Update-or-Cancel-a-Time-Off-Request). Only People Ops can delete past entries, so please ping someone from the team, and we'll get it sorted right away!
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/welcome-to-status.md

@@ -0,0 +1,34 @@
+# 👋 Welcome to Status
+
+Status was created to:
+
+* Ease the transition to a more open mobile internet.
+* Help anyone, anywhere, interact with Ethereum, requiring no more than a phone.
+* Foster links with the wider Ethereum DApp community and showcase what the ecosystem has to offer.
+
+Check out Jarrad & Carl’s [State of Us podcast](https://our.status.im/state-of-us/), and read more about [how Status got its name](https://blog.status.im/we-are-the-state-of-us-2f0fc20b26d3).
+
+## Vision
+
+Today, when you are first exposed to Status, you might see an instant messenger and wonder, "What's the big deal? After all, it’s just another instant messenger, right? What makes Status different and more importantly why should I bother working on it?"
+
+If I had to answer in one word, I would say Decentralization.
+
+Now, that word might not have much meaning to you - it might even sound like a buzzword - but in our context, Decentralization has the potential fundamentally to change the way we organize socially and to rebuild the Internet as it was originally imagined – a commons for innovation. By decentralizing all the things, we are changing the very foundation of civilization, providing a new infrastructural base that impacts everything else above, from our greatest institutions to our daily social interactions.
+
+Status is our gateway to this new world. Let me explain. [Read the Founder’s Statement →](https://github.com/status-im/legacy-wiki/blob/master/archive/Founder%E2%80%99s_Statement.md)
+
+## A Letter to Status by Jarrad Hope 
+
+This is a draft, published early for the Townhall, still proofreading and adding to it.
+
+So we're getting to an organization level where broadcasting communication is probably the most effective to reach everyone, and often I take it for granted that I've been with the project for longest, and quite frankly there was many years of experience, reading, thinking and research that lead to our project's creation. And I realize now my role should be mostly that of an educator, at least what I (think I) know, and I certainly don't know much at all.
+
+I'm going to take a few weeks off, mostly just to pause and reflect on Status and life, but before I check out I wanted to write up a little bit about the world as I see it and provide some thoughts on various aspects, this is about as close to the strategy/north star document will get from my contributions, I do encourage for you to take these ideas and make them your own.
+
+So here I am, writing a letter to you (and to myself).
+
+Before I continue, you need to know that what I say isn't gospel, Status is just as much yours as it is mine. You are an active participant and I invite you to actively shape it as your own. That is the nature of an open-source project, and that idea extends beyond just code. What I can only do, is do my best to guide and give suggestions. Remember, you via Status are entrusted by the greater community to build a collective good. Let's do right by them and by our own self-determination.
+
+tl;dr: it's a memory dump, read it. [Read Jarrad’s Letter to Status →](https://our.status.im/a-letter-to-status-context-strategy/)
+

src/working-here/immigration-relocation.md

@@ -0,0 +1,23 @@
+# 🌏 Immigration & relocation
+
+Being location independent means you could decide to move away from where we first hired you, and that's okay. Status can provide you with confirmation of employment/engagement letters if you need them in the process of migrating abroad.
+
+However, we cannot cover the visa/work permit processing or relocation costs as we're location agnostic for work. In case of relocation due to business reasons (i.e., we *really, really* need you to, and you agree to it), we will take care of all the processes and costs involved.
+
+## What happens if I'm thinking about relocating
+
+Get in touch with People Ops to start a discussion about your relocation plans for potential contract considerations. We are sometimes limited in the number of local employment contracts we can offer to foreign nationals.
+
+If you're switching to a local employment contract that results in additional employer tax costs to Status (i.e CH/DE), we will offer you an adjusted (decreased) base salary calculated to keep the cost impact for Status neutral.
+
+## If you need company details
+
+If you need to indicate your employment/occupation details on a visa application, please use the Status entity address as your employment contract or consulting agreement.
+
+Please only refer to Status as your employer if the DE/CH entity formally employs you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.
+
+If you need to indicate a company representative on your application, feel free to contact People Ops for details.
+
+*****
+
+✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.

src/working-here/index.md

@@ -0,0 +1 @@
+# Working Here

src/your-role-in-Status-growth/index.md

@@ -1 +0,0 @@
-