Rename IFT_Logos3Asset_42x-8.png to IFT_Logo.png

Add files via upload
Update location-independence.md (#167 )
2024-03-18 17:18:28 +00:00 · 2024-03-18 17:10:42 +00:00 · 2024-03-18 11:40:00 +00:00 · 2024-03-18 11:16:26 +00:00 · 2024-03-18 10:33:16 +00:00 · 2024-03-15 16:39:14 +00:00
38 changed files with 518 additions and 186 deletions
@@ -0,0 +1,101 @@
+# Candidate Tasks in Recruitment
+
+<img width="617" alt="Screenshot 2023-12-19 at 12 35 38" src="https://github.com/status-im/contributors.status.im/assets/32337207/431f3b3a-4bd2-44f0-bcf6-ad251ecc967c">
+
+## 1. What is a task: 
+It is a practical assessment to evaluate candidate skills. 
+
+## 2. Why do we use tasks in the hiring process? 
+We use them to:
+- Get a better assessment beyond CVs, portfolios, github repos and interviews.
+- Gain a deeper understanding of someone's abilities (technical & non-technical) for the role at hand.
+- Give candidates a chance to showcase their working style & communication, it’s common to set up a Discord chat so the candidate & task reviewers can chat, ask/answer questions and also provide updates.
+
+## 3. How to design a task
+Step 1: Understand the role's requirements.
+
+Step 2: Design a task that aligns with the expected output of the role.
+
+Step 3: Clearly communicate task instructions, expectations, and deadline.
+
+What does a good task look like:
+- Has clear instructions & expectations
+- Has a deadline that’s realistic (usually 1 week is enough)
+- Has a recommended timeframe in which to complete the task i.e 2-4hrs (this keeps all candidates 'fair' in terms of time dedicated to the task)
+- Is aligned with the day-to-day responsibilities of the role
+- It is tackling a real problem the team face, some teams use a bounties approach
+
+Examples:
+- UX/UI Designer: Create a mobile app prototype/feature based on the target audience.
+- Sales: Create a presentation on selling a complex product to a potential client.
+- Engineer: Assess problem-solving skills by tasking them with debugging code.
+- Customer Support: A simulated chat interaction to assess their communication skills.
+- Financial Analyst: Analyze an investment portfolio to gauge forecasting abilities.
+- Content Writer: Create a blog post on a specified topic.
+
+## 4. Time restrictions & compensation: 
+We want to see a glimpse of what they can do within the allocated time, this shouldn’t be seen as their full potential since they are not integrated into the working styles of the team or the full context of the team.
+
+A simple and effective approach is:	
+- A flat rate for completion of the task; ie. $200
+- A set time allowing completing the task; ie. 2-4hrs (some teams have longer, rule of thumb is allow enough time for the task to be completed)
+… The longer the task, the more time you/your team have to spend reviewing it
+
+## 5. Materials for Candidates: 
+Ensure candidates have all the reference materials needed to perform and succeed on the task.
+
+Examples:
+- A digital marketer may need access to Google Analytics data.
+- A data scientist may need to be provided a dataset and access to statistical software.
+- A content creator may need a brand style guide and existing content for reference.
+- A Mobile UI Engineer will need access to Figma
+
+## 6. Evaluating Tasks: 
+Setting clear evaluation standards is important so everyone is assessed fairly and we don’t let personal biases get in the way of hiring people who perform well during tasks. We should determine the criteria for task evaluation prior to seeing the first task submitted by a candidate.
+
+Examples:
+- Evaluate a coding task based on criteria like code quality, efficiency, and adherence to project requirements.
+- Assess customer service interactions based on responsiveness, problem-solving, and professionalism.
+- Evaluate a design task considering creativity, usability, and alignment with brand guidelines.
+
+
+## 7. Effective Communication: 
+Maintain transparent and professional candidate communication.
+
+- Clearly inform candidates of the evaluation timeline and when they can expect feedback.
+- Use the Discord chat to interact with the candidate throughout their task
+
+## 8. Feedback and Improvement: 
+Use candidate feedback to refine task instructions and evaluation criteria.
+
+## 9. Sample Tasks:
+
+- Engineering: [Vac Pair Programming Task](https://notes.status.im/Jvd03lPKSMiDI_eo9Dq9xw)
+- Communications: [Activist Event Manager](https://drive.google.com/file/d/1TsIbMduelr_TjbwfEcT-AnXnVco1GejC/view?usp=sharing)  
+- Recruitment: [Sourcing Task](https://docs.google.com/document/d/1ICiYpsvT6sh6akyM6RxQX1tu_D3tq3bVgLWEIpj1aOM/edit?usp=sharing)
+- Pops: [People Ops Partner](https://docs.google.com/document/d/1nLFu6sQvfqCqfdlWP8kVTBzBDLTIZknNRc8FMCw9vrA/edit?usp=sharing)
+
+## FAQs
+
+Q: How long should candidates typically spend on the task?
+A: We recommend 2-4 hours to avoid impacting the candidate's current job and any family commitments. 
+
+Q: How long should the task take to complete?
+A: 1-week max (unless the candidate has let us know they have something that won’t allow them to complete the task, ie. health conditions, family, personal, ect.)
+
+Q: What happens if a candidate encounters issues during the task?
+A: You can communicate with them via the discord chat created by the recruiter.
+
+Q: Is there room for negotiation on compensation for exceptionally well-performed tasks?
+A: No.
+
+Q: What if I can’t think of any tasks?
+A: Then check out the tasks templates above as inspiration or/and think of a daily task someone in your team does that you would expect this candidate to be competent with, for example, in recruitment we would expect someone to show their competency & creativity sourcing candidates, so that is what the task is based around.
+
+Q: My team doesn't have time to review every task, what do we do?
+
+A: The number of tasks to review should be minimal as you don’t need to send a task to every candidate, only the good ones that stand out as potential hires.
+
+
+_If that is still too much, revert to a technical discussion, so long as you’re confident you can accurately assess a candidate's suitability this way._
+
@@ -1,3 +1,6 @@
+#!/usr/bin/env groovy
+library 'status-jenkins-lib@v1.8.8'
+
 pipeline {
  agent { label 'linux' }

@@ -11,41 +14,33 @@ pipeline {
  }

  environment {
-    CNAME = 'contributors.status.im'
    GIT_COMMITTER_NAME = 'status-im-auto'
    GIT_COMMITTER_EMAIL = 'auto@status.im'
-    /* dev page settings */
-    DEV_SITE = 'dev-contributors.status.im'
-    DEV_HOST = 'jenkins@node-01.do-ams3.sites.misc.statusim.net'
-    SCP_OPTS = 'StrictHostKeyChecking=no'
  }

  stages {
    stage('Build') {
-      steps {
+      steps { script {
        sh 'mdbook build'
-      }
+        jenkins.genBuildMetaJSON('book/build.json')
+      } }
    }

-    stage('Publish Prod') {
-      when { expression { env.GIT_BRANCH ==~ /.*master/ } }
+    stage('Publish') {
      steps {
        sshagent(credentials: ['status-im-auto-ssh']) {
-          sh "ghp-import -p book"
-        }
-      }
-    }
-
-    stage('Publish Devel') {
-      when { expression { env.GIT_BRANCH ==~ /.*develop/ } }
-      steps {
-        sshagent(credentials: ['jenkins-ssh']) {
          sh """
-            rsync -e 'ssh -o ${SCP_OPTS}' -r --delete book/. \
-              ${env.DEV_HOST}:/var/www/${env.DEV_SITE}/
+            ghp-import \
+              -b ${deployBranch()} \
+              -c ${deployDomain()} \
+              -p book
          """
        }
      }
    }
  }
 }
+
+def isMasterBranch() { GIT_BRANCH ==~ /.*master/ }
+def deployBranch() { isMasterBranch() ? 'deploy-master' : 'deploy-develop' }
+def deployDomain() { isMasterBranch() ? 'contributors.status.im' : 'dev-contributors.status.im' }
@@ -29,9 +29,11 @@ Will expose the built page under http://localhost:3000/.

 # Continuous Integration

-Two branches are built by [our Jenkins instance](https://ci.infra.status.im/):
-
-* `master` branch is deployed to https://contributors.status.im/ by [CI](https://ci.infra.status.im/job/website/job/contributors.status.im/).
-* `develop` branch is deployed to https://dev-contributors.status.im/ by [CI](https://ci.infra.status.im/job/website/job/dev-contributors.status.im/).
-
 PRs should be made for `develop` branch and `master` should be [rebased](https://git-scm.com/book/en/v2/Git-Branching-Rebasing) on `develop` once changes are verified.
+
+- [CI builds](https://ci.infra.status.im/job/website/job/contributors.status.im/) `master` and pushes to `deploy-master` branch, which is hosted at <https://contributors.status.im/>.
+- [CI builds](https://ci.infra.status.im/job/website/job/dev-contributors.status.im/) `develop` and pushes to `deploy-develop` branch, which is hosted at <https://dev-contributors.status.im/>.
+
+The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
+
+Information about deployed build can be also found in `/build.json` available on the website.
@@ -1 +1,8 @@
-/* Placeholder for custom page-wide CSS. */
+/* Hack to hide the last sub-element under "License" link in SUMMARY.md.
+ * Currently that's only "2023 Lead evaluation guide".
+ * Necessary due to lack of support for hidden chapters:
+ * https://github.com/rust-lang/mdBook/issues/1821
+ * https://github.com/rust-lang/mdBook/issues/2176 */
+ol.chapter > li:not(.chapter-item):last-child {
+    visibility: hidden;
+}
@@ -10,6 +10,7 @@ Please carefully read the following instructions to ensure a smooth and timely p
 - **Software & Licenses**: (new tools, apps, subscriptions, etc.)
 - **Consulting fees**: (consultants, freelancers)
 - **Other fees**: (bounties)
+- **Events**: (rent, insurance, sponsorship, entertainment, etc.)

 > For instructions on how to raise a request, please refer to this [guide](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a).

@@ -17,7 +18,7 @@ If you are unsure about the categories or how to proceed with your specific case

 2. Your request will be reviewed by a Budget Owner (usually the Project Lead) and, where required, by the relevant Service Units. The approval process will be handled automatically. Please ensure that you provide all necessary details regarding your request, as these are crucial for the Project Leads and Service Units to review and make the necessary arrangements.

-> Note: The [Approval strategy](https://www.notion.so/Approval-strategy-9c15269bbb184ec9909dfd900bcf0b91?pvs=21) for each request may vary based on several variables:
+> Note: The [Approval strategy](https://www.notion.so/769ae660ac2240e9b1daf7b3ba4bb49c?v=ed50eb29a825492eab8623f9973d7886&pvs=4) for each request may vary based on several variables:
 > - **Category/sub-category**: Different sets of approvers may be required based on the category/sub-category of the request. For example, PeopleOps partners need to review requests for learning & development but not for consulting fees or software & licenses.
 > - **Amount**: In some cases, a simplified approval strategy may be triggered if the amount is below a certain threshold.
 > - **Project**: The Budget Owner is determined based on the selected project in the request. If the Budget Owner is the one raising the request, the L2 Budget Owner will be required to provide approval.
@@ -34,4 +35,4 @@ If you are unsure about the categories or how to proceed with your specific case
 6. When Finance processes your payment requests or third-party invoices, they will check for approved requests in SpiffWorkflow. If there are no approved requests or if the amounts differ, they may request additional approval from the Budget Owner and Service Units.


-If you are a Budget Owner or a member of the Service Units team, you may find the [report](https://superset.infra.status.im/superset/dashboard/p/W351qlbzmdj/) useful.
+If you are a Budget Owner or a member of the Service Units team, you may find the [report](https://superset.bi.status.im/superset/dashboard/p/BzMqY16qXGd/) useful.
@@ -5,7 +5,7 @@ Superset is an open-source data exploration and visualization platform powered b

 Step 1: Accessing Superset

- Open your web browser and enter the URL Superset is hosted. https://superset.infra.status.im/superset/welcome/
+- Open your web browser and enter the URL Superset is hosted. https://superset.bi.status.im/superset/welcome/
 - Enter your Github username and password to log in to Superset. If this is your first time using Superset it will create a brand new user for you
 - If this is your first time, you'll need access to dashboards you need. You can contact laloanaya through discord or at lalo@status.im to get access to these resources.

@@ -9,14 +9,16 @@
     - [Self-time management](./settling-in/self-time-management.md)
     - [AFK FAQs](./settling-in/afk-faqs.md)
     - [The trial period](./settling-in/the-trial-period.md)
-     - [Onboarding buddy](./settling-in/onboarding-buddy.md)
+     - [Evaluation Guide](./settling-in/2023-Self-Evaluation-Guide.md) 
     - [Your first day, week, month…](./settling-in/your-first-day-week-month.md)
+     - [Onboarding buddy](./settling-in/onboarding-buddy.md)
     - [People Operations](./settling-in/people-operations.md)
     - [Download Status Desktop](./settling-in/download-status-desktop.md)
 - [Contributing to Status](./contributing-to-status/index.md)
     - [Journey to your first contribution](./contributing-to-status/journey-to-your-first-contribution.md)
     - [Value-creating Behaviours](./contributing-to-status/value-creating-behaviours.md)
     - [Laptops and devices](./contributing-to-status/laptops-and-devices.md)
+     - [Collaboration](./contributing-to-status/collaboration.md)
     - [Coworking allowance](./contributing-to-status/coworking-allowance.md)
     - [Location independence](./contributing-to-status/location-independence.md)   
     - [Events and meetups](./contributing-to-status/events-and-meetups.md)
@@ -25,11 +27,12 @@
     - [Referrals](./contributing-to-status/referrals.md)
     - [Headspace](./contributing-to-status/headspace.md)
 - [Fundamentals](./fundamentals/index.md)
-     - [Security guidelines](./fundamentals/security-guidelines.md)
     - [Recommended reading](./fundamentals/essential-reading.md)
+     - [Security guidelines](./fundamentals/security-guidelines.md)
+     - [In case of a dispute](./fundamentals/In-case-of-a-dispute.md)
+     - [In case of emergency](./fundamentals/emergencies.md)
     - [Code of Conduct](./fundamentals/code-of-conduct.md)
     - [Contributor Privacy Policy](./fundamentals/contributor-privacy-policy.md)
-     - [In case of emergency](./fundamentals/emergencies.md)
 - [Finance](./finance/index.md)
     - [Getting paid](./finance/getting-paid.md)
     - [Third-party invoices format](./finance/third-party-invoices-format.md)
@@ -37,11 +40,16 @@
 - [Offboarding](./offboarding/index.md)
     - [Device Logistics](./offboarding/device-logistics.md)
 - [Playbooks](./Playbooks/index.md)
+     - [2023 self-evaluation guide](./Playbooks/2023-Self-Evaluation-Guide.md)
     - [How to request goods and services](./Playbooks/How-to-request-goods-or-services.md)
     - [Spiffworkflow](./Playbooks/Spiffworkflow.md)
     - [Superset](./Playbooks/Superset.md)
+- [Team Lead Manual]()
+     - [Candidate Tasks](./Team-lead-manual/Candidate-Tasks.md)

 *****

 - [Contributing to the Contributors Guide](./contributing-to-this-guide.md)
 - [License](./LICENSE.md)
+    <!-- # This is hidden using custom.css file. -->
+    - [2023 Lead evaluation guide](./Playbooks/2023-Lead-Evaluation-Guide.md)
@@ -0,0 +1,48 @@
+## ✨ Lead Evaluation Guide
+
+_This document is intended to be a supporting document to help Core Contributors complete the 2023 Lightweight Evaluation Process._
+
+This guide has been created to assist you in providing constructive and meaningful feedback to Core Contributors regarding their impact on Status. The  evaluation will be structured in two parts. The first section will have specific questions about the Core Contributor’s contribution, collaboration and autonomy. Following that, there will be a short answer section that will give you an opportunity to provide more detailed feedback about the Core Contributors in the team you lead. 
+
+**Writing Meaningful Feedback**
+
+There are two questions in the evaluation process designed to be more freeform qualitative questions to give you the opportunity to provide specific feedback to the core contributors in your team - these are: 
+
+1. What is (at least) one thing the contributor does well?
+2. What is (at least) the one thing the contributor could improve on? 
+
+With these questions, we suggest. 
+
+1. Provide clear and specific examples to support your feedback.
+2. Focus on addressing behaviors, not personality traits, for objective and action-oriented feedback
+3. Maintain a respectful and empathetic tone to ensure your contributors feel supported
+
+There are a variety of frameworks and guides that are useful in helping write and deliver feedback. For more on giving feedback, please see [here](https://www.forbes.com/sites/forbeshumanresourcescouncil/2021/12/02/how-to-give-feedback-to-freelancers-contractors-and-remote-workers/?sh=d753b074d5b4).
+
+Additionally, here are examples of effective and ineffective feedback for the Core Contributors in your team:
+
+> 😃 _Effective:_
+“Over the past year, the contributor has shown exceptional collaboration skills within our team. One particular instance to highlight was their collaboration skills during our recent project with Team X and Team Y. In this project, the contributor took the initiative to organize and lead discussions among the teams and consistently encouraged participation from others. The contributor helped to facilitate open conversations and create safe spaces for such collaboration which made a really positive impact on the project’s success. We were able to make better and more informed decisions as a result of this (for example, as a result, we decided to prioritise feature z) - the contributor played a significant role in making this happen.”
+
+> 😔 _Ineffective:_
+“Excellent collaboration skills”. 
+
+**Quantitative Assessment**
+
+It’s important to approach the quantitative section of this process with fairness and objectivity. The expectation is that not all of your Core Contributors in your team will receive an “Outstanding” rating. Instead, the aim is to offer honest and well-balanced feedback that reflects each Core Contributor’s actual performance. Keep in mind that most Core Contributors will likely receive a “Meets Expectations” rating. This will ensure that our evaluations are realistic and meaningful.
+
+**Rating Guide**
+
+The evaluation process requires you to provide a rating of the Core Contributors in your team - please use the guidance below:
+
+* **Does Not Meet Expectations:** Core Contributor consistently fails to meet role expectations. 
+* **Partially Meets Expectations:** Core Contributor sometimes meets role expectations but has room for improvement
+* **Meets Expectations:** Core Contributor consistently meets expectations for their role - likely the majority of Core Contributors will fall into this category (it’s a good rating that demonstrates they are meeting our high expectations). 
+* **Exceeds Expectations:** Core Contributor consistently goes above and beyond what is expected in their role
+* **Outstanding:** Core Contributor consistently has exceptional performance and contributions. Would expect this to be awarded to only a very small group of Core Contributors. 
+
+**Distribution of ratings** 
+
+Whilst there’s no forced distribution of ratings, it’s natural to expect (with 200+ core contributors) we’ll use the full scale of ratings. It is likely that most CCs will fall into the “meets expectations” category, but that we will also have some (a smaller amount) that are distributed in the higher, and lower, categories. 
+
+Please reach out to your People Ops Partner if you have any questions.
@@ -0,0 +1,101 @@
+# Candidate Tasks in Recruitment
+
+![skills-assessment](../images/skills-assessment.png)
+
+## 1. What is a task: 
+It is a practical assessment to evaluate candidate skills. 
+
+## 2. Why do we use tasks in the hiring process? 
+We use them to:
+- Get a better assessment beyond CVs, portfolios, github repos and interviews.
+- Gain a deeper understanding of someone's abilities (technical & non-technical) for the role at hand.
+- Give candidates a chance to showcase their working style & communication, it’s common to set up a Discord chat so the candidate & task reviewers can chat, ask/answer questions and also provide updates.
+
+## 3. How to design a task
+Step 1: Understand the role's requirements.
+
+Step 2: Design a task that aligns with the expected output of the role.
+
+Step 3: Clearly communicate task instructions, expectations, and deadline.
+
+What does a good task look like:
+- Has clear instructions & expectations
+- Has a deadline that’s realistic (usually 1 week is enough)
+- Has a recommended timeframe in which to complete the task i.e 2-4hrs (this keeps all candidates 'fair' in terms of time dedicated to the task)
+- Is aligned with the day-to-day responsibilities of the role
+- It is tackling a real problem the team face, some teams use a bounties approach
+
+Examples:
+- UX/UI Designer: Create a mobile app prototype/feature based on the target audience.
+- Sales: Create a presentation on selling a complex product to a potential client.
+- Engineer: Assess problem-solving skills by tasking them with debugging code.
+- Customer Support: A simulated chat interaction to assess their communication skills.
+- Financial Analyst: Analyze an investment portfolio to gauge forecasting abilities.
+- Content Writer: Create a blog post on a specified topic.
+
+## 4. Time restrictions & compensation: 
+We want to see a glimpse of what they can do within the allocated time, this shouldn’t be seen as their full potential since they are not integrated into the working styles of the team or the full context of the team.
+
+A simple and effective approach is:	
+- A flat rate for completion of the task; ie. $200
+- A set time allowing completing the task; ie. 2-4hrs (some teams have longer, rule of thumb is allow enough time for the task to be completed)
+… The longer the task, the more time you/your team have to spend reviewing it
+
+## 5. Materials for Candidates: 
+Ensure candidates have all the reference materials needed to perform and succeed on the task.
+
+Examples:
+- A digital marketer may need access to Google Analytics data.
+- A data scientist may need to be provided a dataset and access to statistical software.
+- A content creator may need a brand style guide and existing content for reference.
+- A Mobile UI Engineer will need access to Figma
+
+## 6. Evaluating Tasks: 
+Setting clear evaluation standards is important so everyone is assessed fairly and we don’t let personal biases get in the way of hiring people who perform well during tasks. We should determine the criteria for task evaluation prior to seeing the first task submitted by a candidate.
+
+Examples:
+- Evaluate a coding task based on criteria like code quality, efficiency, and adherence to project requirements.
+- Assess customer service interactions based on responsiveness, problem-solving, and professionalism.
+- Evaluate a design task considering creativity, usability, and alignment with brand guidelines.
+
+
+## 7. Effective Communication: 
+Maintain transparent and professional candidate communication.
+
+- Clearly inform candidates of the evaluation timeline and when they can expect feedback.
+- Use the Discord chat to interact with the candidate throughout their task
+
+## 8. Feedback and Improvement: 
+Use candidate feedback to refine task instructions and evaluation criteria.
+
+## 9. Sample Tasks:
+
+- Engineering: [Vac Pair Programming Task](https://notes.status.im/Jvd03lPKSMiDI_eo9Dq9xw)
+- Communications: [Activist Event Manager](https://drive.google.com/file/d/1TsIbMduelr_TjbwfEcT-AnXnVco1GejC/view?usp=sharing)  
+- Recruitment: [Sourcing Task](https://docs.google.com/document/d/1ICiYpsvT6sh6akyM6RxQX1tu_D3tq3bVgLWEIpj1aOM/edit?usp=sharing)
+- Pops: [People Ops Partner](https://docs.google.com/document/d/1nLFu6sQvfqCqfdlWP8kVTBzBDLTIZknNRc8FMCw9vrA/edit?usp=sharing)
+
+## FAQs
+
+Q: How long should candidates typically spend on the task?
+A: We recommend 2-4 hours to avoid impacting the candidate's current job and any family commitments. 
+
+Q: How long should the task take to complete?
+A: 1-week max (unless the candidate has let us know they have something that won’t allow them to complete the task, ie. health conditions, family, personal, ect.)
+
+Q: What happens if a candidate encounters issues during the task?
+A: You can communicate with them via the discord chat created by the recruiter.
+
+Q: Is there room for negotiation on compensation for exceptionally well-performed tasks?
+A: No.
+
+Q: What if I can’t think of any tasks?
+A: Then check out the tasks templates above as inspiration or/and think of a daily task someone in your team does that you would expect this candidate to be competent with, for example, in recruitment we would expect someone to show their competency & creativity sourcing candidates, so that is what the task is based around.
+
+Q: My team doesn't have time to review every task, what do we do?
+
+A: The number of tasks to review should be minimal as you don’t need to send a task to every candidate, only the good ones that stand out as potential hires.
+
+
+_If that is still too much, revert to a technical discussion, so long as you’re confident you can accurately assess a candidate's suitability this way._
+
@@ -1,38 +1,24 @@
 # 🎤 Events and meetups

-As a Status core contributor, you may have the opportunity to speak at or attend external online or in-person events. 
+As a IFT core contributor, you may have the opportunity to speak at or attend external online or in-person events. 

 The community is an essential part of the Web3 ecosystem. Ecosystem, domain-specific, and internal events and meetups are networking and growth opportunities. And we strongly encourage you to be part of them!

 Here you'll find helpful information to make the most out of organising, speaking, or attending events.

-## What events does Status sponsor
+## What events does IFT sponsor

-Status will sponsor and cover the costs for any online or in-person event with a clear purpose. That means it must align with our company's strategy and goals. This includes, but is not limited to:
+IFT will consider sponsoring and covering the costs for any online or in-person event with a clear purpose. That means it must align with IFT's strategy and goals. This includes, but is not limited to:

   * Ecosystem events such as DevCon, ETH[city], ETHCC, Hackathons, blockchain weeks, etc.
   * Domain-specific events for your role for career purposes.
-   * Events and meetups to promote Status to potential new core contributors.
+   * Events and meetups to promote IFT or our projects to potential new core contributors.
   * Internal events and meetups to prepare a product/project launch or work together.
-   * Moderating or speaking opportunities related to Status.
+   * Moderating or speaking opportunities related to IFT.

-> ✨ Remember that when you're at an event, you're an ambassador for Status’ project and everyone who shares our values. Don't forget that and spread the word! Who knows who's listening and might contribute to or join Status thanks to you 🙂
+> ✨ Remember that when you're at an event, you're an ambassador for IFT’ projects and everyone who shares our values. Don't forget that and spread the word! You never know who's listening and might contribute to IFT thanks to you 🙂

-> 💡Before attending an event, ask your Talent Partner to generate a QR code for the Status job page that you can share with anyone interested. 
-
-## How to communicate an event
-
-The events and travel budgets come from your project's budget. As a first step, you should check with your project lead about the event or meetup.
-
-As per our transparency and resourcefulness principles, we ask everyone to post their event plans and goals to Discuss or the #travel-requests channel in Status app. The post should include:
-
-   * Event details: where, when, who's attending, one line about the event.
-   * Whether or not Status is an official sponsor and why.
-   * What are the goals of attending the event and a project brief, if it makes sense.
-   * Who you'll need support from the project for design, comms, documentation, etc.
-   * Anything else you consider relevant!
-
-Here's an event [post example](https://discuss.status.im/t/ethdenver-feb-15-17-2019/922).
+> 💡Before attending an event, ask your Talent Partner to generate a QR code for our job pages that you can share with anyone interested. 

 ## Once you have your travel details ready

@@ -14,5 +14,5 @@ Get in touch with your People Partner to start the discussion about your relocat

 If you need to indicate your working status/occupation details on a visa application, please contact your People Partner who can assist with the relevant information.

-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.
+You should only refer to DE/CH as your employer, if those entities formally employ you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.

@@ -59,7 +59,7 @@ Usually, the earlier you plan your trip, the cheaper and better it's going to be
 ### Commuting rates and guidelines

 * Sometimes it's more convenient to travel by train or bus within Europe. So keep that in mind as an option when you're looking at routes.
-* We travel in economy class with carry-on luggage included. You can add one checked luggage for trips longer than 5 days or when you're carrying additional baggage for Status.
+* We travel in economy class with carry-on luggage included. You can add one checked luggage for trips longer than 5 days or when you're carrying additional baggage for Status. For flights that are 12+ hours, premium economy is permitted but please ensure that the overall cost is still reasonable (if the price is more than 2x the economy price please do consider alternate options). 
 * For moving around, choose the most affordable ground transportation option. In some places, traffic is unpredictable, and public transport is more reliable. In others, car rental, and ride-sharing, such as Uber or local equivalents, are better to move from/to the airport and share the ride with others travelling with you.

 > 💡 Pro-tip: in-flight entertainment might be limited. You might want to bring a book or download media, music, or documents offline beforehand. For some people, commutes are a great way to disconnect or do some reading or focus work.
@@ -97,3 +97,4 @@ International prepaid SIM cards:
 * [Holafly](https://holafly.com)
 * [Airalo](https://www.airalo.com/)

+If you are a Budget Owner or a member of the Service Units team, you may find this [Travel report](https://superset.bi.status.im/superset/dashboard/p/Mgvrd5R3Z4Q/) useful.
@@ -2,10 +2,10 @@

 ## How to get reimbursed for expenses?

-You can request a reimbursement for reasonable expenses incurred on behalf of Status during the project's development. You can read about some of these expenses at:
+You can request a reimbursement for reasonable expenses incurred on behalf of IFT during the project's development. You can read about some of these expenses at:
   * [Computers and devices](../contributing-to-status/laptops-and-devices.md)
   * [Events and meetups](../contributing-to-status/events-and-meetups.md)
-   * [Travelling for Status](../contributing-to-status/travelling-for-status.md)
+   * [Travelling for IFT](../contributing-to-status/travelling-for-status.md)
   * [Essential reading](../fundamentals/essential-reading.md)

 It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly.
@@ -18,7 +18,7 @@ In addition to these notes, you can find a guide [here](https://docs.google.com/

 ## 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.
+We use Expensify to store and report the expense details and receipts incurred on behalf of IFT during the project's development.

 ### Account setup

@@ -30,7 +30,7 @@ If you don’t have access to your account, please reach out to the Finance team

 ### Selecting the right policy

-Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct Status entity and your invoicing currency.
+Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct IFT entity and your invoicing currency.

 ![expensify-policy](../images/expensify-policy.png)

@@ -44,7 +44,7 @@ Go to the `Expense` tab on either the web or mobile apps to upload expenses manu

   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.
+   3. When paying for a group (i.e., a meal shared with other contributors from IFT), 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.

 #### Example
@@ -102,7 +102,7 @@ If you need to share the report with your accountant, you can download a PDF rep

 In order to reduce delays in payments, invoices received after the invoice deadline (15th of the month), will be paid in the payment run of the following month. This applies to all invoices (contributors and third-party suppliers). We will still issue the normal reminder before the cut-off date, but we will not chase invoices after that date.

-Expense claims are submitted via Expensify as usual, but each report should span a calendar month and only expenses marked as approved on Expensify should be included on your invoices. This will allow Fiance to review and approve expense claims as soon as they arrive. This means that the sooner you submit your expense claim, the sooner it will be reviewed by the Finance team.
+Expense claims are submitted via Expensify as usual, but each report should span a calendar month and only expenses marked as approved on Expensify should be included on your invoices. This will allow Finance to review and approve expense claims as soon as they arrive. This means that the sooner you submit your expense claim, the sooner it will be reviewed by the Finance team.

 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.

@@ -114,6 +114,6 @@ Scenario 2:  David submits an invoice on the 14th February, and he includes an e

 Scenario 3: David submits an invoice on the 15th February, and he includes an expense claim that shows as approved in Expensify. The Finance team will include it in the payment run as usual.

-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`.
+If you have other questions related to this process, please feel free to ping the Finance team in the #finance channel or through an email to `billing@status.im`.


@@ -29,7 +29,7 @@ Your invoice should include:
 You can create an invoice by downloading/copying [this template](https://docs.google.com/spreadsheets/d/1FbH0CxLqar0ZyjhiMEA5ceToL2ikv5C-Rv-qCwBNeRA/). 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 Holdings Pte. Ltd., 160 Robinson Road, #24-09, Singapore 068914
+   * IFT Studio Pte Ltd, 160 Robinson Road, #24-09, Singapore 068914
   * Status Research & Development GmbH, Baarerstrasse 10, 6302 Zug, Switzerland
   * Status Research & Development Deutschland GmbH, ℅ Cormoran GmbH, Am Zirkus 2, 10117 Berlin, Germany

@@ -94,22 +94,22 @@ Please bill the flat monthly or annual/12 figure for each subsequent month.

 Please use the working days shown below for your calculations:

-**Working days 2023**
+**Working days 2024**

 | Month | Working days |
 |:---:|:---:|
-| January | 22 |
-| February | 20 |
-| March | 23 |
-| April | 20 |
+| January | 23 |
+| February | 21 |
+| March | 21 |
+| April | 22 |
 | May | 23 |
-| June | 22 |
-| July | 21 |
-| August | 23 |
+| June | 20 |
+| July | 23 |
+| August | 22 |
 | September | 21 |
-| October | 22 |
-| November | 22 |
-| December | 21 |
+| October | 23 |
+| November | 21 |
+| December | 22 |

 ### Expense Reimbursements

@@ -1,6 +1,6 @@
 # 🧾 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.
+As part of contributing to IFT, 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.

@@ -21,26 +21,15 @@ Here's a sample of how invoices should look, as well as all the appropriate data
   * Supplier’s telephone number, contact person and email address (optional);
   * Payment information (optional).

-### Status Information
-   * One of the Status' legal entities and invoicing address (mandatory).
+### IFT Information
+   * Invoicing address (mandatory).

-##### Status Switzerland
-Status Research & Development GmbH<br>
-Baarerstrasse 10, <br>
-6302 Zug, Switzerland<br>
-MWST-Nr: CHE-319.159.934 MWST
-
-##### Status Singapore
-Status Holdings Pte. Ltd. <br>
-160 Robinson Road, #24-09,<br>
-068914, Singapore<br>
+##### IFT Singapore
+IFT Studio Pte. Ltd.
+160 Robinson Road, #24-09,
+068914, Singapore
 UEN: 201625575Z

-##### Status Germany
-Status Research & Development Deutschland GmbH<br>
-Am Zirkus 2, <br>
-10117 Berlin, Germany<br>
-USt-IdNr: DE317300297

 ## Invoice Content

@@ -0,0 +1,31 @@
+# In case of a dispute
+
+## Background
+
+* While we hope that you may never have to run into this issue, and for the most part it is relatively exceptional, IFT, like any other organisation, faces the risk of entering into disputes, whether they are arising from internal or external events, within or outside of IFT’ control and with different types of counterparties, from service provides to (former) core contributors (“Counterparty”).
+* Therefore we have developed this guidance for core contributors on how you can help prevent and mitigate potential disputes, protect IFT’ interests and how to best collaborate with Legal to resolve any disputes in the most peaceful and amicable manner possible. 
+
+## Guidance
+
+#### When to involve Legal - the earlier, the better. However, please contact Legal immediately if:
+* It is more than likely that IFT will fail to fulfil its obligation(s) towards a Counterparty or if IFT has already failed on its obligation(s) towards a Counterparty (doesn’t matter if the Counterparty is aware about this or not). For example, 
+  * IFT failed to pay, or failed to pay on time any amounts due (e.g. an invoice has been unpaid past the stated due date); 
+  * Breached a term of a contract in any way, for example, by inappropriate use of services (e.g. a service is being used contrary to a service’s acceptable use policy); or
+  * Breached confidentiality (e.g. a core contributor inadvertently shares confidential information with another third party that is not compliant with the contract). 
+* If a Counterparty claims that IFT is not fulfilling its obligations (whether this is accurate or not) or threatens legal action against IFT in this respect;  or
+* if a legal counsel or a law firm has taken over communications with IFT;
+
+#### If any of the above takes place - the following should be observed:
+* Follow good practices: Preserve all communications with the Counterparty, such as discord chats, emails, any social media chats  (e.g. Telegram), calls and meeting notes.
+
+## After you contact Legal: 
+
+* Do not let the Counterparty know you are involving Legal, (for example, do not include Legal in -cc to an email with a Counterparty) unless Legal has advised you to do so. In our experience, if a Counterparty becomes aware that Legal is being involved, it may escalate an already sensitive situation or unnecessarily provoke hostility. 
+* Communicate with the Counterparty only in consultation with Legal and other internal stakeholders as relevant, for example, your team lead.
+* Any communication with the Counterparty must be screened and approved by Legal.
+* Any strategy or potential proposals/compromises must also be discussed with Legal. 
+
+## After the dispute has been resolved: 
+
+* Rectify/Monitor - Legal and core contributors should continue to monitor for any potential signs that the dispute may resume or re-escalate and ensure that events or factors which led to the dispute have been adequately addressed (e.g. has IFT’ failure to perform an obligation now being rectified?) 
+* Lessons learned - Legal, core contributors, relevant team lead, and any other relevant internal stakeholders should form a “lessons learned” group to review the events and factors, which led up to the dispute and determine whether any changes to procedure or practices should be made to prevent or mitigate the chance of such a dispute arising again. Notes and conclusions should be well documented for future reference
@@ -1,31 +0,0 @@
-# Guidance from Legal perspective regarding (potential) disputes
-
-## Background
-
-* While we hope that you may never have to run into this issue, and for the most part it is relatively exceptional, Status, like any other organisation, faces the risk of entering into disputes, whether they are arising from internal or external events, within or outside of Status’ control and with different types of counterparties, from service provides to (former) CCs (“Counterparty”).
-* Therefore we have developed this guidance for CCs on how you can help prevent and mitigate potential disputes, protect Status’ interests and how to best collaborate with Legal to resolve any disputes in the most peaceful and amicable manner possible. 
-
-## Guidance
-
-#### When to involve Legal - the earlier the better. However, please contact Legal immediately if:
-* It is more than likely that Status will fail to fulfil its obligation(s) towards a Counterparty or if Status has already failed on its obligation(s) towards a Counterparty (doesn’t matter if the Counterparty is aware about this or not). For example, 
-  * Status failed to pay, or failed to pay on time any amounts due (e.g. an invoice has been unpaid past the stated due date); 
-  * Breached a term of a contract in any way, for example, by inappropriate use of services (e.g. a service is being used contrary to a service’s acceptable use policy); or
-  * Breached confidentiality (e.g. a CC inadvertently shares confidential information with another third party that is not compliant with the contract). 
-* If a Counterparty claims that Status is not fulfilling its obligations (whether this is accurate or not) or threatens legal action against Status in this respect;  or
-* if a legal counsel or a law firm has taken over communications with Status;
-
-#### If any of the above takes place - the following should be observed:
-* Follow good practices: Preserve all communications with the Counterparty, such as discord chats, emails, any social media chats  (e.g. Telegram), calls and meeting notes.
-
-## After you contact Legal: 
-
-* Do not let the Counterparty know you are involving Legal, (for example, do not include Legal in -cc to an email with a Counterparty) unless Legal has advised you to do so. In our experience, if a Counterparty becomes aware that Legal is being involved, it may escalate an already sensitive situation or unnecessarily provoke hostility. 
-* Communicate with the Counterparty only in consultation with Legal and other internal stakeholders as relevant, for example, your team lead.
-* Any communication with the Counterparty must be screened and approved by Legal.
-* Any strategy or potential proposals/compromises must also be discussed with Legal. 
-
-## After the dispute has been resolved: 
-
-* Rectify/Monitor - Legal and CC should continue to monitor for any potential signs that the dispute may resume or re-escalate and ensure that events or factors which led to the dispute have been adequately addressed (e.g. has Status’ failure to perform an obligation now being rectified?) 
-* Lessons learned - Legal, CC, relevant team lead and any other relevant internal stakeholders should form a “lessons learned” group to review the events and factors, which led up to the dispute and determine whether any changes to procedure or practices should be made to prevent or mitigate the chance of such a dispute arising again. Notes and conclusions should be well documented for future reference
@@ -4,17 +4,18 @@ The Code of Conduct serves to establish guidelines on how to conduct your behavi

 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.
+We hope that all our community members share our views and nurture this spirit and culture in their dealings within the organisation and the  wider 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.
+This code acts as both a courtesy to the overall organisation and an effective way of making your interactions with other core contributors  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 honoured 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.
+IFT 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.

@@ -93,7 +94,7 @@ We invite any and everybody to participate in any aspect of the project. Our com

 ## Enforcement

-Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting the Status People Ops team at `people-ops@status.im` or pinging your People Partner for a confidential chat.
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting the People Ops team at `people-ops@status.im` or pinging your People Partner 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.

@@ -103,8 +104,8 @@ Depending on the severity of the misconduct, this may be a formal warning, throu

 ## licence

-Status creates software to be a public good and makes use of free and open-source licences in this regard.  This ensures that 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 is designed to serve. This open-source licence 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.
+IFT creates software to be a public good and makes use of free and open-source licences in this regard.  This ensures that 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 IFT is designed to serve. This open-source licence 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.*
+*The 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 IFT.*
@@ -9,13 +9,14 @@ We'll use your emergency contact info in [Bamboo](https://statusim.bamboohr.com/

 It's also helpful to review your contact phone number and email address from time to time if we need to reach you directly.

-## Status emergency contacts
+## IFT emergency contacts

 In all emergencies and only after you are safe and out of harm’s way and/or in a secure location contact people-ops@status.im or ping your People Partner directly via DM (or phone for urgent matters) for immediate attention. Your People Partner will use their reasonable efforts to coordinate with others (i.e., legal or security) on your behalf to the extent required.

 ## Reporting a potential legal claim or dispute 

-As a responsible organisation, we take all potential legal claims or disputes against Status very seriously. 
+As a responsible organisation, we take all potential legal claims or disputes against the IFT very seriously.
+
+We would ask all core contributors to promptly report to the Legal team and your project lead about any (potential) legal claims or disputes against the IFT, once you have become aware about it. If you suspect or become aware of an incident that may be likely to develop into a legal claim or dispute, please also promptly bring this to the attention of the Legal team and your project lead. The earlier we identify and address any of these issues will allow the IFT to take the appropriate steps to minimise any potential negative impact on the IFT.

-We would ask all core contributors to promptly report to the Legal team and your project lead about any (potential) legal claims or disputes against Status, once you have become aware about it. If you suspect or become aware of an incident that may be likely to develop into a legal claim or dispute, please also promptly bring this to the attention of the Legal team and your project lead. The earlier we identify and address any of these issues will allow Status to take the appropriate steps to minimise any potential negative impact on Status. 
 
@@ -1,6 +1,6 @@
 # Fundamentals

-In this section you will find some information on the fundamentals of Status such as our legal and security frameworks.
+In this section you will find some information on the fundamentals of IFT such as our legal and security frameworks.

 If you have any questions, please reach out to People Ops who can help navigate your questions or concerns.
 
@@ -1,6 +1,6 @@
 # 🔐 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. 
+Security is a priority at IFT, 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 organisation from attackers. 

@@ -34,13 +34,13 @@ Here's Corey's Status Learn-Up session about [hardware wallets and best practice

 ## Password manager

-Our password manager is [Bitwarden](https://bitwarden.com/). All organisational 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.
+Our password manager is [Bitwarden](https://bitwarden.com/). All organisational passwords should be kept and shared here. So if you plan to store an IFT 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 organisation, 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.
+You can request an invite in #people-ops. By signing up with the organisation, you get the premium features and sign up with any email you like. That way, if you ever leave the IFT, you can take your password manager secrets with you, and you only lose access to IFT related items.

 ## Security team

-Learn more about Security @ Status at:
+Learn more about Security @ IFT at:

   * [Status Security](https://status.im/security/)
   * [status-im/status-security](https://github.com/status-im/status-security)
@@ -1,11 +1,8 @@
 # Introduction

-Status is developing  an open set of projects utilising peer-to-peer technologies that will facilitate people’s ability to transact securely and communicate freely. We build decentralised technologies ranging from protocol-level infrastructure to application software — forming an open-source peer-to-peer technology stack.
+### Institute of Free Technology 
+#### Fostering innovation, defending digital liberties

-Status strives to develop open-source software (for example, the [Status](https://status.im/get/) app) that can be utilised by people as a secure communication tool to uphold human rights. The Status app is designed to facilitate the free flow of information, protect the right to private, secure conversations, and promote the sovereignty of individuals. [Discover more projects →](https://statusnetwork.com/)
+The Institute of Free Technology ‘IFT’ is a mission-driven tech startup studio, taking ideas from the drawing board to market with financial, technical, legal, people operations, and brand-building support at every step.

-### Contributing
-
-The development of the Status app 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 [proposal](https://discuss.status.im/) and make it happen.
-
-You can also contribute to specific Status projects such as [Waku](https://waku.org/) or [Nimbus](https://nimbus.team/). As an open-source project, we are location-agnostic and operate fully remotely. You can find which profiles each project is looking for [on this page](https://jobs.status.im/). 
+IFT curates, incubates and builds startups using shared resources and infrastructure. IFT is focused on building public goods to safeguard civil liberties in the digital age, and we support and grow programs that share this goal by providing capital, services and other resources.
@@ -1,6 +1,6 @@
 # 💠 Offboarding

-We’re sorry that you’re leaving our project and wish you the best of luck in your next endeavours ☘️ - thanks for everything you brought to Status during the time we had together! 🙌
+We’re sorry that you’re leaving the IFT and wish you the best of luck in your next endeavours ☘️ - thanks for everything you brought to IFT during the time we had together! 🙌

 Your People Partner will help facilitate this process with various other stakeholders such as your project lead, Legal and Finance. 

@@ -18,7 +18,7 @@ There's a lot to do before you leave so please follow the steps assigned to you

 * ### Letter of Termination 

-  Your People Partner will share a confirmation of termination with you confirming your last day of service with Status.
+  Your People Partner will share a confirmation of termination with you, confirming your last day of service with IFT.

 * ### Offboarding Agreement 

@@ -26,11 +26,11 @@ There's a lot to do before you leave so please follow the steps assigned to you

 * ### Returning or buying back devices 

-  Check out this [guide](./device-logistics.md) to finalise purchasing or returning any Status-owned devices. 
+  Check out this [guide](./device-logistics.md) to finalise purchasing or returning any IFT-owned devices. 

 * ### Last invoice & Expenses 

-  Please submit your final invoice & expense report within one day of your final working day. Send your final invoice to Billing@status.im. Your final invoice should     include any equipment buy backs and expenses. 
+  Please submit your final invoice & expense report within one day of your final working day. Send your final invoice to Billing@status.im. Your final invoice should     include any equipment buybacks and expenses. 

 * ### Verify your payment details in BambooHR are accurate 

@@ -42,15 +42,15 @@ There's a lot to do before you leave so please follow the steps assigned to you

 * ### Announcing your departure 

-  We’d like to be transparent with all core contributors when someone leaves the project. Please post a goodbye message in #general, or let People Ops know if you’d prefer   that they post a general departure message on your behalf (this won’t share any personal details, but will confirm that you are not going to be around, along with     your expected last day). You may also want to ping fellow core contributors within other projects directly to let them know about your departure.
+  We’d like to be transparent with all core contributors when someone leaves the project. Please post a goodbye message, or let People Ops know if you’d prefer   that they post a general departure message on your behalf (this won’t share any personal details, but will confirm that you are not going to be around, along with     your expected last day). You may also want to ping fellow core contributors within other projects directly to let them know about your departure.

-* ### Forthcoming Status travel 
+* ### Forthcoming IFT travel 

-  Should you have any future Status-sponsored travel/conference arrangements in place, please cancel them and obtain a refund for your bookings if possible. Expenses     will only be reimbursed for non-refundable travel bookings. Cancellation fees (where incurred) can be added to your final expense report for reimbursement (please     attach proof of payment).
+  Should you have any future IFT-sponsored travel/conference arrangements in place, please cancel them and obtain a refund for your bookings if possible. Expenses     will only be reimbursed for non-refundable travel bookings. Cancellation fees (where incurred) can be added to your final expense report for reimbursement (please     attach proof of payment).

 * ### Private keys 

-  If you have any hardware related to Status wallets or bank accounts (e.g. Ledgers, Trezors, security keys), mnemonic phrases, or any other resource granting you       access to (or control of) Status's funds (fiat or crypto), please make arrangements with @finance to return them.
+  If you have any hardware related to IFT wallets or bank accounts (e.g. Ledgers, Trezors, security keys), mnemonic phrases, or any other resource granting you       access to (or control of) IFT's funds (fiat or crypto), please make arrangements with @finance to return them.

 * ### Access to organisation-wide tools 

@@ -58,7 +58,7 @@ There's a lot to do before you leave so please follow the steps assigned to you

 * ### Passwords 

-  Please clear your password vault of any passwords relating to tools/software licences belonging to Status.
+  Please clear your password vault of any passwords relating to tools/software licences belonging to IFT.

 * ### Tools 

@@ -70,16 +70,11 @@ There's a lot to do before you leave so please follow the steps assigned to you

 * ### Letter of reference 

-  We’ll be happy to provide a letter of reference confirming your contributions to Status. Should you ever need a reference letter, please email people-ops@status.im     at any time, and we’ll get a letter to you within 5 - 10 working days.
-
-* ### Holiday (For core contributors only only) 
-
-  You are entitled to be paid out for any accrued but not taken holidays. Your People Partner will calculate the payout amount and pay this out to you with your final   payment. You can choose to take any accrued holiday as time off during your notice period - if you want to do so, please book the time in BambooHR.
-
+  We’ll be happy to provide a specific (i.e addresses to a specific person or organisation) letter of reference confirming your contributions to IFT. Should you ever need a reference letter, please email people-ops@status.im     at any time, and we’ll get a letter to you within 5 - 10 working days.

 ## "Offboarding" chats

-We're not a traditional organisation, but we try to hold 'offboarding' chats with every departing core contributor. This chat is a chance for you to reflect on your time with Status, and share your feedback on your experience. The feedback we collect from these interviews will be used to improve the way we work with contributors moving forward.
+We're not a traditional organisation, but we try to hold 'offboarding' chats with every departing core contributor. This chat is a chance for you to reflect on your time with us, and share your feedback on your experience. The feedback we collect from these interviews will be used to improve the way we work with contributors moving forward.

 We’ll share your feedback with relevant project members we think may benefit from hearing your reflections. If you’d prefer the conversation to be 100% private, that’s totally ok - just let us know what you’re comfortable with being shared further.

@@ -88,11 +83,11 @@ Feel free to prepare notes in advance, or send us your feedback async if you’d
 ## Coming back?

 We’re open to working with former core contributors again, and we’d consider each situation on an individual basis.
-As Status develops capabilities for permissionless participation, our role as a gatekeeper to contribution will fall away, and anyone (former core contributor or not) will be free to contribute to Status.
+As IFT develops capabilities for permissionless participation, our role as a gatekeeper to contribution will fall away, and anyone (former core contributor or not) will be free to contribute to IFT.

 We hope to see you again in the community or ecosystem! It's been a blast and know that you will always be missed!

 ## Questions?
 Please ping your People Partner or ask in the #people-ops channel
-For any invoice/expenses questions, please ping the finance team in #ask-finance
+For any invoice/expenses questions, please ping the finance team in the #finance channel.

@@ -21,7 +21,7 @@ We strive for complete openness and symmetry of information within the organisat
 ### VI. Openness
 The software we create is a public good. It is made available via a free and open source licence, for anyone to share, modify and benefit from. We believe in permission-less participation.

-### VII. decentralisation
+### VII. Decentralization
 We minimise centralization across both the software and the organisation itself. In other words, we maximise the number of physical computers composing the network, and maximise the number of individuals who have control over the system(s) we are building.

 ### VIII. Inclusivity
@@ -0,0 +1,57 @@
+## 💥 Self Evaluation Guide
+
+_This document is intended to be a supporting document to help you complete the 2023 lightweight Self Evaluation Process._
+
+
+### Writing a self-evaluation
+
+Think of a self-evaluation as an opportunity to reflect and deep dive into your contributions and impact on Status’ projects.  It’s your moment to share **_WHAT_** you do and **_HOW_** you do it. 
+
+The **_WHAT_** = contribution/impact 
+
+The **_HOW_** = behaviours 
+
+Try to be honest about your contributions and impact on Status’ projects, especially in relation to how your contributions align with Status’ values and mission. It is also important to acknowledge areas where you may need further development or support, and that’s okay. 
+
+Aim to provide a balanced evaluation of yourself based on the following attributes and questions.  
+
+
+### Question Specific Guidance
+
+**<span style="text-decoration:underline;">Contribution</span>**
+
+* Think about specific projects, tasks or initiatives you have worked on, highlighting your contributions, accomplishments, and the outcomes of your efforts. 
+* Be specific and provide measurable results whenever possible, such as deadlines met, efficiency improvements, and projects delivered. 
+
+**<span style="text-decoration:underline;">Collaboration</span>**
+
+* Assess your ability to work collaboratively with Core Contributor both within your team and other projects. 
+* Describe instances where you effectively collaborated or supported others in achieving common goals. 
+* Acknowledge any areas where you faced challenges in collaboration and how you dealt with it. 
+
+**<span style="text-decoration:underline;">Autonomy</span>**
+
+* Discuss your level of autonomy as a Core Contributor and how you've taken initiative. 
+* Share examples of times when you proactively identified opportunities for improvement or took on additional responsibilities. 
+* Highlight your ability to work independently and make decisions when needed.
+
+**<span style="text-decoration:underline;">What is (at least) one thing you do well?</span>**
+
+* Be specific, highlighting your impact on your team/project. 
+* Identify your strengths, skills or qualities that you excel at in your role.
+* Discuss a time when / if you exceeded expectations or made a significant positive impact on your team or project.
+* Highlight any skills or areas where you’ve shown improvement and growth over time.
+* Take time to look back on your 1:1’s and retros to help you identify past accomplishments
+
+**<span style="text-decoration:underline;">What is (at least) one thing you could improve upon?</span>**
+
+* Be self-aware. Acknowledge areas where you may have room for improvement.
+* Focus on something specific and prioritise a meaningful commitment to improvements. 
+* Offer context for the areas you want to improve. Explain why these aspects are important and how they impact your role.
+
+**Next steps:**
+
+Please log into Lattice, and complete your self-evaluation. 
+
+Reach out to your People Ops Partner if you have any questions. 
+
@@ -20,11 +20,55 @@ Your People Partner won't tell other core contributors the specifics of your sit

 ### 🐣 Are you or your partner / spouse expecting a new baby?

-First of all, congratulations! 🎊 We're happy about the new addition(s) to your family!
+#### Introduction
+
+First of all, congratulations! 🎊 We're happy about the new addition(s) to your family! At Status, we understand the importance of family during this exciting time in your lives. We believe all parents should have the necessary time to care for their newborn or newly adopted child. As such, this may result in a period of time when you will be unavailable to provide your services to Status. In this regard, Status has developed the following arrangement:   
+
+#### Eligibility
+
+All core contributors who have passed their trial period at Status and are performing well are eligible to participate in this arrangement. If a core contributor is still in their trial period, they will **not** be eligible to participate in this arrangement. 
+
+Furthermore, the core contributor’s service agreement must still be in effect prior to and for the duration of their unavailability. 
+
+#### Duration
+
+Core contributors who become new parents, either through birth or adoption, are able to make use of the following periods of unavailability and this arrangement:   
+
+* Primary caregiver - A period of up to sixteen (16) weeks
+* Secondary caregiver - A period of up to three (3) weeks 
+
+The primary caregiver is typically the person who takes on the main responsibility for looking after a child. This role is often most commonly associated with the mother.  The primary caregiver is typically the one who spends the most time with the child, providing daily care, nurturing, and meeting their needs. They will have given up work to carry out their duties. 
+
+The secondary caregiver is the person who takes on a supporting role in caregiving responsibilities. The secondary caregiver provides assistance and support to the primary caregiver, sharing the responsibilities of caring for the child.
+
+#### Standby compensation
+
+While traditional parental leave policies are not available to independent contractors, Status nonetheless wishes to ensure that core contributors are able to immediately resume the provision of their services for Status following this period of unavailability at full capacity and without delay. 
+
+Status recognises however that the core contributor will incur certain costs and expenses during their unavailability to maintain a certain level of readiness and wishes to compensate them to remain on standby. In this regard, Status will pay the core contributor a monthly ‘standby’ payment for the period of eligible unavailability.
+
+Status will make such payments in accordance with section 8 of this Status Contributor Guide.  As indicated above, Status’ payment of standby compensation is subject to the core contributor’s services agreement being in effect during their unavailability. If such agreement terminates during their unavailability, Status is not obliged to make any standby compensation payments to the core contributor. 
+
+#### Flexible work arrangements
+
+We understand that a core contributor resuming their services to Status after this period of unavailability given their parental duties can be challenging. Therefore, we also have flexible arrangements available to new parents who intend to resume providing their services. 
+
+This may include a reduced schedule or a staggered return. In addition, the core contributor may further extend their period of unavailability as follows: 
+
+* Primary caregiver - a period of up to eight (8) weeks 
+* Secondary caregiver - up to three (3) weeks 
+
+For this extended period of unavailability, Status will not provide any additional standby compensation. 
+
+#### How do I make use of this arrangement?

 As soon as you're comfortable sharing the news, please ping your People Partner to chat about your plans. It'd be great if you could give as much notice as you can.

-We'll do our best to accommodate you and we'll discuss with you each request on a case by case basis, involving your project lead, taking into account your needs, your planned unavailability and deliverables.
+We’ll further discuss the above arrangement with you, your period of unavailability and also share with you some additional paperwork to formalise this arrangement. 
+
+#### Conclusion
+
+At Status, we are committed to supporting our core contributors who become new parents. We believe that creating this arrangement  is essential to promoting work-life balance and creating a supportive environment for contributors to thrive as well as the confidence that they can resume the provision of their services to Status with the necessary readiness and capacity.

 ### 📒 What happens to any SNT distributions? 

@@ -1,6 +1,6 @@
 # 🧭 Buddy program

-We've created the buddy program to facilitate your integration to Status’ projects as warm and welcoming as possible. A buddy is there to connect new joiners, solve doubts as they appear, and immerse new core contributors into our culture from the lenses of someone who's helped shape it.
+We've created the buddy program to facilitate your integration into IFT and our projects as warm and welcoming as possible. A buddy is there to connect new joiners, solve doubts as they appear, and immerse new core 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.

@@ -8,7 +8,7 @@ Here you'll find helpful information about what you can expect from your buddy a

 The buddy system is role and location agnostic. We want folks across the organisation to have the chance to meet and get to know others outside of those they'd work with regularly. 

-That means that buddies may be paired together from entirely different roles / projects to each other. The buddying conversations don't need to be technical. New core contributors should have a project lead who will get them set up with a project in their first weeks, while the buddy program focuses on the core contributor experience, broader community, ecosystem, Status culture, vision, and mission.
+That means that buddies may be paired together from entirely different roles / projects to each other. The buddying conversations don't need to be technical. New core contributors should have a project lead who will get them set up with a project in their first weeks, while the buddy program focuses on the core contributor experience, broader community, ecosystem, culture, vision, and mission.

 Suppose a new core contributor still has lots of questions about their work responsibilities or role; in that case, a buddy can help them connect with the right people  to solve them.

@@ -16,10 +16,10 @@ If the time zone difference makes it hard to pair, please let your People Partne

 ## For new core contributors

-As a new core contributor, it's not always easy to find a tenured peer to walk you through all things Status. So, to make your first few months more enjoyable, we’ll match you with a buddy!  You can find their username in your BambooHR profile, so shoot them a message to introduce yourself and set up recurring calls during your first 4-6 weeks. There's nothing for you to prepare or do in advance of the weekly buddy calls:
+As a new core contributor, it's not always easy to find a tenured peer to walk you through all things IFT. So, to make your first few months more enjoyable, we’ll match you with a buddy!  You can find their username in your BambooHR profile, so shoot them a message to introduce yourself and set up recurring 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!
+   * Your buddy will be ready to guide you on contributing to IFT.
+   * The buddy chats are a safe space for you to ask whatever you'd like about working at IFT - no topic is too trivial.
   * 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
@@ -41,40 +41,40 @@ There's no set amount of time you should have worked with Status before becoming
 **Roles and responsibilities of a buddy**

   * As a buddy, you are not 'managing' the core contributor but act as a supportive and friendly face.
-   * Helping a new core contributor navigate their way around Status.
+   * Helping a new core contributor navigate their way around IFT.
   * 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 offer informal support.
   * Introducing them to other core contributors who are relevant to their role.
-   * Helping them to understand the formal and informal culture and structures at Status.
-   * Getting the core contributor comfortable with Status products and principles.
+   * Helping them to understand the formal and informal culture and structures at IFT.
+   * Getting the core contributor comfortable with IFT projects 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 project members in their current location. 
-   * Flag to your People Partner, any topics or situations that seem confusing for new core contributors, so we can tackle them better and faster at the onboarding stage!
-   * Be a general all-round Status legend and share your love and passion for the project.
+   * When possible, arrange to meet up for coworking in the area, or introduce them to any other core contributors in their current location. 
+   * Flag to your People Partner, any topics or situations that seem confusing for new core contributors so we can tackle them better and faster at the onboarding stage!
+   * Be a general all-round legend and share your love and passion for the IFT and our projects.

 **Guidelines for approaching the first meeting**

 If you haven't been a buddy before, don't panic or feel overwhelmed as the new core contributor may have similar feelings. Remember every bit of knowledge and advice is valuable to the success of the core contributor! 

-On the new core contributor's first few days with Status, their People Partner will arrange an onboarding call to get them set up and introduce them to high-level information about engaging with Status. You are not expected to give them details from scratch or contact them immediately on their first day.
+On the new core contributor's first few days, their People Partner will arrange an onboarding call to get them set up and introduce them to high-level information about engaging with IFT. 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 week timeframe.
- [ ] Outline your role, experience at Status, what you're working on, and how that ties in with the organisation.
+- [ ] Outline your role, experience at IFT, what you're working on, and how that ties in with the organisation.
 - [ ] 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.
 - [ ] 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, decentralised autonomous organisations, open-source, and community-based working.
- [ ] Talk about Status's mission and objectives -- the State of Us, decentralisation, the Principles, etc.
- [ ] Discuss the working culture at Status. How is this different from other places the new core contributor has contributed?
+- [ ] Talk about IFT's mission and objectives -- decentralisation, our Principles, etc.
+- [ ] Discuss the working culture at IFT. How is this different from other places the new core contributor has contributed?
 - [ ] If relevant, introduce them to key people they may benefit from knowing outside of their immediate project.
- [ ] Suggest what to read and other valuable resources for their role or get to know the company in general.
+- [ ] Suggest what to read and other valuable resources for their role or get to know the org 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.
+- [ ] Share some discord or Status app channels that they may find interesting to follow.
 - [ ] Get to know a bit about them as a person, their hobbies etc.
 - [ ] 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 - are they aware of our coworking allowance?

-Make sure the core contributor knows they can ask you anything regarding Status, and you will be happy to help. It's important to stress this as new core contributors can often be afraid to bother people, shy, or reluctant to ask at first!
+Make sure the core contributor knows they can ask you anything regarding IFT, and you will be happy to help. It's important to stress this as new core contributors can often be afraid to bother people, shy, or reluctant to ask at first!

@@ -17,7 +17,7 @@ We’ll keep asking you how we can improve, and we welcome your feedback at any
 ## Who we are...

 - Head of People Operations: Jonathan Barker (aka JB)
- People Partners: Terry Tobin & Riccardo Caselli
+- People Partners: Terry Tobin & Melanie Davis
 - Talent Partners: Pepper Lea, Maya Krumova, Catia Sousa & Angel Gutierrez

 ### People Partners
@@ -6,8 +6,6 @@ The Status app was created to:
 * 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 catch up on our awesome [blog posts](https://blog.status.im/we-are-the-state-of-us-2f0fc20b26d3).
-
 ## 🔭 Vision

 Today, when you are first exposed to the Status app, you might see an instant messenger and wonder, "What's the big deal? After all, it’s just another instant messenger, right? What makes the Status app different and more importantly why should I bother working on it?"
Author	SHA1	Message	Date
Terrytobin	384fcaa88e	Rename IFT_Logos3Asset_42x-8.png to IFT_Logo.png	2024-03-18 17:18:28 +00:00
Terrytobin	09dd9536b6	Add files via upload	2024-03-18 17:10:42 +00:00
Terrytobin	87fc2e415a	Update location-independence.md (#167 ) Updated wording re: employment	2024-03-18 11:40:00 +00:00
Terrytobin	a77d42dc99	Update events-and-meetups.md (#168 ) Updated wording	2024-03-18 11:16:26 +00:00
Terrytobin	fe99b105d2	Update In-case-of-a-dispute.md (#171 ) Updated wording Status <>IFT	2024-03-18 10:33:16 +00:00
Terrytobin	1db61074ea	Update introduction.md (#148 ) Updating working to about IFT	2024-03-15 16:39:14 +00:00
Terrytobin	a98685cb74	Update third-party-invoices-format.md (#175 ) update wording Status <>IFT and IFT address	2024-03-15 16:38:02 +00:00
Terrytobin	7d9a7cb258	Update emergencies.md (#172 ) updated wording	2024-03-15 16:36:51 +00:00
Terrytobin	e24987433c	Update expense-reimbursements.md (#176 ) update wording Status <> IFT	2024-03-15 16:36:11 +00:00
Terrytobin	893d75beda	Update code-of-conduct.md (#173 ) Updated wording	2024-03-14 16:15:47 +00:00
Terrytobin	c117853e7e	Update index.md (#177 ) Updated wording	2024-03-14 16:13:28 +00:00
Terrytobin	124b2d034c	Update security-guidelines.md	2024-03-13 17:54:44 +00:00
Terrytobin	1bcc66a72f	Update index.md	2024-03-13 17:49:33 +00:00
Terrytobin	2c2336245a	Update onboarding-buddy.md (#156 ) Update wording Status <> IFT	2024-03-13 15:45:41 +00:00
Terrytobin	71c1bebb74	Update getting-paid.md	2024-03-12 16:37:29 +00:00
jakub	4693d8e661	add files/Candidate_-_Privacy_Notice.pdf Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-03-04 13:39:08 +01:00
Terrytobin	0ce703ab28	Update SUMMARY.md removed evaluation guide from summary page until its updated	2024-02-28 14:16:11 +00:00
jakub	c1d663afec	remove merge stuff from summary Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-02-28 15:03:24 +01:00
Terrytobin	5f422cfbcd	Merge branch 'develop'	2024-02-28 13:55:59 +00:00
Terrytobin	ab47794120	fix (#147 )	2024-02-28 13:55:31 +00:00
Terrytobin	6c792ee929	fix	2024-02-28 13:51:21 +00:00
Terrytobin	b2c46f0197	Merge branch 'develop'	2024-02-28 13:50:44 +00:00
Terrytobin	b47ca38713	Update SUMMARY.md (#145 )	2024-02-28 13:50:04 +00:00
Terrytobin	b727fc12f7	Merge branch 'develop'	2024-02-28 13:40:21 +00:00
jakub	22bd2e5e19	recover Playbooks/2023-Lead-Evaluation-Guide.md Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-02-28 14:39:04 +01:00
Terrytobin	dc27c025bb	Merge branch 'develop'	2024-02-28 13:36:07 +00:00
Terrytobin	c657e47392	fixlink (#144 ) fixlink	2024-02-28 13:35:13 +00:00
Terrytobin	b67508e426	Update SUMMARY.md	2024-02-28 12:59:59 +00:00
Terrytobin	5d782fbdd3	Rename Candidate-Tasks.md to Candidate-Tasks	2024-02-28 12:58:55 +00:00
Terrytobin	ed12e4cbd7	Update SUMMARY.md	2024-02-28 12:58:06 +00:00
Terrytobin	da203099d8	Update SUMMARY.md	2024-02-28 12:57:01 +00:00
Terrytobin	865cf5ae8d	Rename the-team-lead-role.md to the-team-lead-role	2024-02-28 12:56:05 +00:00
Terrytobin	8d1cd5abb2	Update SUMMARY.md	2024-02-28 12:51:27 +00:00
Terrytobin	5acc6e4269	Update SUMMARY.md	2024-02-28 12:50:42 +00:00
Terrytobin	bfcc47b9f3	Update SUMMARY.md	2024-02-28 12:49:16 +00:00
Terrytobin	7bb8a02118	Rename Candidate Tasks.md to Candidate-Tasks.md	2024-02-28 12:46:32 +00:00
Terrytobin	e7a764a4e5	Update SUMMARY.md	2024-02-28 12:42:54 +00:00
Terrytobin	6182c2969d	Update SUMMARY.md	2024-02-28 12:42:08 +00:00
Terrytobin	3fd2084d04	Rename team-lead-manual.md to Candidate Tasks.md	2024-02-28 12:40:25 +00:00
jakub	64b3bb1344	remove unused file Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-02-27 12:25:32 +01:00
jakub	18ae4e2fac	fix Hiring/Team Lead Manual, remove duplicates Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-02-27 12:25:10 +01:00
LilChiChiandCatia Sousa	ffe816cc09	Hiring manager section (#139 ) * Add files via upload * Create Best Practice Guide: Candidate Tasks in Recruitment * Update Best Practice Guide: Candidate Tasks in Recruitment Added a picture * Rename Best Practice Guide: Candidate Tasks in Recruitment to Best Practice Guide: Candidate Tasks in Recruitment.md * Update Best Practice Guide: Candidate Tasks in Recruitment.md * Update Best Practice Guide: Candidate Tasks in Recruitment.md --------- Co-authored-by: Catia Sousa <catiasousa.recruitment@gmail.com>	2024-02-27 10:49:43 +01:00
jakub	55f23ac516	feat: use two deploy branches for CI builds This way we have two branches on GitHub that reflect the state of the website after CI build has finished and pushed. See README. Also adds `build.json` file at site root for see currently deployed version. Signed-off-by: Jakub Sokołowski <jakub@status.im>	2024-02-26 15:57:46 +01:00
Terrytobin	d995e41b7d	Merge branch 'develop'	2024-02-13 17:26:19 +00:00
LilChiChiandCatia Sousa	55b0484dff	Hiring manager section (#139 ) * Add files via upload * Create Best Practice Guide: Candidate Tasks in Recruitment * Update Best Practice Guide: Candidate Tasks in Recruitment Added a picture * Rename Best Practice Guide: Candidate Tasks in Recruitment to Best Practice Guide: Candidate Tasks in Recruitment.md * Update Best Practice Guide: Candidate Tasks in Recruitment.md * Update Best Practice Guide: Candidate Tasks in Recruitment.md --------- Co-authored-by: Catia Sousa <catiasousa.recruitment@gmail.com>	2024-02-13 17:22:59 +00:00
Catia Sousa	18b472f655	Update getting-paid.md (#140 ) Changed from Status Holding...to IFT Studio Pte Ltd	2024-02-13 17:16:27 +00:00
harmeet-status	7b0c70e0d6	Update SUMMARY.md (#135 ) Adding in collaboration.md into the navigation.	2024-02-13 14:45:39 +00:00
Sasha	f9a43e03fd	Update travelling-for-status.md (#130 ) added a link to the new travel dashboard (new Superset instance)	2024-02-13 13:00:46 +00:00
Sasha	4ebd7acee4	Update How-to-request-goods-or-services.md (#129 ) Updated broken links, added "Events" category	2024-02-13 13:00:13 +00:00
Sasha	0c885d10ca	Update Superset.md (#128 ) new instance of Superset	2024-02-13 12:59:41 +00:00
Priedins15	e849b8e915	Update getting-paid.md (#132 ) Updated working days per month	2024-02-13 12:59:08 +00:00
LilChiChi	9cf4b7a2b6	Created Hiring section & added candidate task file (#137 )	2024-02-08 18:29:47 +00:00
jonathanbarker	dc37b801a5	Update index.md (#136 ) Updated language around reference letters	2024-02-06 19:37:30 +01:00
harmeet-status	63903227da	Create collabration.md (#134 ) * Create collabration.md Creating a new collaboration section which includes ProtonMail. * Update collabration.md Added proton mail to Day 1 platforms in 1st paragraph.	2024-02-05 10:10:53 +01:00
jonathanbarker	4232e2aca7	Update travelling-for-status.md (#133 ) Change to flight travel policy	2024-01-31 15:52:12 +01:00
Terrytobin	12d1d9183a	Update index.md	2023-11-23 18:43:10 +00:00
Terrytobin	4655afbb08	Update index.md	2023-11-23 15:14:15 +00:00
jonathanbarker	f55ddaa503	Update welcome-to-status.md (#127 ) Removed link to podcast and blog, since both are very out of date.	2023-11-02 12:59:36 +00:00
jakub	1b9166b4cb	custom.css: fix hiding rule to not affect articles Signed-off-by: Jakub Sokołowski <jakub@status.im>	2023-10-24 19:42:19 +02:00
MayitaK	15baec2330	Update 2023-Lead-Evaluation-Guide.md (#126 )	2023-10-24 18:19:34 +01:00
jakub	b6388d133f	use custom CSS to hide sub-elements at the end of list There currently are no built-in ways to do this. This hack is horrible and should be removed when possible. It doesn't actually remove the link, it just hides it. Signed-off-by: Jakub Sokołowski <jakub@status.im>	2023-10-17 11:11:29 +02:00
Terrytobin	9e13e86f6e	Update SUMMARY.md	2023-10-16 20:55:24 +01:00
Terrytobin	2627971de8	Update SUMMARY.md	2023-10-16 20:36:45 +01:00
Terrytobin	15eda018c3	Update 2023-Self-Evaluation-Guide.md	2023-10-16 13:58:05 +01:00
Terrytobin	6afaf28328	Update 2023-Lead-Evaluation-Guide.md	2023-10-16 13:56:45 +01:00
Terrytobin	0d03aec66a	Update 2023-Lead-Evaluation-Guide.md	2023-10-16 13:53:43 +01:00
Terrytobin	61d8298425	Update 2023-Lead-Evaluation-Guide.md (#125 )	2023-10-16 13:38:36 +01:00
Terrytobin	6c93d9638f	Update SUMMARY.md	2023-10-12 13:43:18 +01:00
Terrytobin	3aa1b29bc0	Create 2023-Lead-Evaluation-Guide.md	2023-10-12 13:34:39 +01:00
Terrytobin	5e9cc776e8	Update and rename 2023_Self_Evaluation_Guide.md to 2023-Self-Evaluation-Guide.md (#124 )	2023-10-12 13:14:32 +01:00
Terrytobin	c7051841d6	Create 2023_Self_Evaluation_Guide.md	2023-10-12 12:57:52 +01:00
Melanie	e151f6fc11	Update people-operations.md (#123 )	2023-10-12 12:35:22 +01:00
AdamDynamic	b24b48ad92	Corrected minor typo. (#122 )	2023-09-28 13:37:49 +01:00
Terrytobin	36445ee2b3	Update afk-faqs.md (#120 )	2023-09-28 10:25:59 +01:00
Terrytobin	972f55b38d	Update SUMMARY.md	2023-09-21 19:09:54 +01:00
Terrytobin	56ea24e4b3	Update In-case-of-a-dispute.md	2023-09-20 15:38:28 +01:00
Terrytobin	de5351449c	Update In-case-of-a-dispute.md	2023-09-20 14:34:08 +01:00
Terrytobin	326691da9d	Rename Legal-guidelines.md to In-case-of-a-dispute.md	2023-09-20 14:23:44 +01:00
Terrytobin	11d220ba29	Rename Legal guidelines to Legal-guidelines.md	2023-09-20 11:54:10 +01:00