Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f86a3f3ec5 | ||
|
|
11de05f541 | ||
|
|
42074876f1 | ||
|
|
59609ee6e9 | ||
|
|
3e9592c6dc | ||
|
|
082ac348ac | ||
|
|
2b8c2bd346 | ||
|
|
fecb2110ab | ||
|
|
cde847bf93 | ||
|
|
3efc572a5a | ||
|
|
176c4d4abb | ||
|
|
50e736e642 | ||
|
|
2bd1d5174d | ||
|
|
21d09fed33 | ||
|
|
b874d8f125 | ||
|
|
cf2705749b | ||
|
|
46589730b1 | ||
|
|
65c8f3c3e7 | ||
|
|
ed862792e1 | ||
|
|
be9ed3d5a8 | ||
|
|
51a7f438fa | ||
|
|
8cac0f4dd3 | ||
|
|
b213830ec5 | ||
|
|
6c51db0401 | ||
|
|
bb73218cfa | ||
|
|
df7d6d0842 | ||
|
|
b0db8c2681 | ||
|
|
61c7fd5ba0 | ||
|
|
5f17e946fd | ||
|
|
8c8bfd7be2 | ||
|
|
64eb1e926a | ||
|
|
4e24edeec8 | ||
|
|
16c8ac3647 | ||
|
|
8b82696c3f | ||
|
|
bddfb3af47 | ||
|
|
94e8c497d1 | ||
|
|
4402e8c7d8 | ||
|
|
816a836f1b | ||
|
|
bf3b9e5ed5 | ||
|
|
15dcfdab1e | ||
|
|
d2bd55e5d5 | ||
|
|
8d8f160b55 | ||
|
|
eedf912f78 | ||
|
|
774bbbb1cc | ||
|
|
66d3b7f72e | ||
|
|
4b7f90bff0 | ||
|
|
a0e332c085 | ||
|
|
efb0a4958c | ||
|
|
2243b2ddec | ||
|
|
5fa0a8105a | ||
|
|
c68ba57ca6 | ||
|
|
af5a2aa06c | ||
|
|
58c23d5fd8 | ||
|
|
268bb5e55c | ||
|
|
a1711c1d99 | ||
|
|
9426c2ef9b | ||
|
|
430e6657fb | ||
|
|
ab0809fd6c | ||
|
|
2b6f692942 | ||
|
|
5ac3abbc5e | ||
|
|
460c955645 | ||
|
|
c7e7e7ef36 | ||
|
|
a569fb9962 | ||
|
|
9af94ab661 | ||
|
|
6efd74f681 | ||
|
|
5c59de78c1 | ||
|
|
fe837b6714 | ||
|
|
312b317b0f | ||
|
|
858d159a3c | ||
|
|
1eb8ce9df7 | ||
|
|
4ee6d046c4 | ||
|
|
7559b20b46 | ||
|
|
87816b26a7 | ||
|
|
3f78467a23 | ||
|
|
548afa4c02 | ||
|
|
0953137447 | ||
|
|
d26fa096be | ||
|
|
bae23db736 | ||
|
|
15063b98a6 | ||
|
|
512344b04e | ||
|
|
45afe54716 | ||
|
|
d9095a08e8 | ||
|
|
50aca555ba | ||
|
|
c5b900c570 | ||
|
|
ad40b39473 | ||
|
|
a08a14afa0 | ||
|
|
6a3b8d1722 | ||
|
|
055e599a37 | ||
|
|
07536552dd | ||
|
|
1aa77148d4 | ||
|
|
ffd88c4db6 | ||
|
|
70531b7ed5 | ||
|
|
68daf68da5 | ||
|
|
53994e9efd | ||
|
|
ca5278fe6d | ||
|
|
7790c835ff | ||
|
|
48cae73897 | ||
|
|
3600b494e8 | ||
|
|
4b1c1a2ca9 | ||
|
|
664b3455a7 | ||
|
|
59dbb82ed8 | ||
|
|
d971636eb5 | ||
|
|
09dd9536b6 | ||
|
|
87fc2e415a | ||
|
|
a77d42dc99 | ||
|
|
fe99b105d2 | ||
|
|
1db61074ea | ||
|
|
a98685cb74 | ||
|
|
7d9a7cb258 | ||
|
|
e24987433c | ||
|
|
893d75beda | ||
|
|
c117853e7e | ||
|
|
124b2d034c | ||
|
|
1bcc66a72f | ||
|
|
2c2336245a | ||
|
|
71c1bebb74 | ||
|
|
4693d8e661 | ||
|
|
0ce703ab28 | ||
|
|
c1d663afec | ||
|
|
5f422cfbcd | ||
|
|
ab47794120 | ||
|
|
6c792ee929 | ||
|
|
b2c46f0197 | ||
|
|
b47ca38713 | ||
|
|
b727fc12f7 | ||
|
|
22bd2e5e19 | ||
|
|
dc27c025bb | ||
|
|
c657e47392 | ||
|
|
b67508e426 | ||
|
|
5d782fbdd3 | ||
|
|
ed12e4cbd7 | ||
|
|
da203099d8 | ||
|
|
865cf5ae8d | ||
|
|
8d1cd5abb2 | ||
|
|
5acc6e4269 | ||
|
|
bfcc47b9f3 | ||
|
|
7bb8a02118 | ||
|
|
d995e41b7d | ||
|
|
55b0484dff |
@@ -1 +1,3 @@
|
||||
book
|
||||
|
||||
.DS_Store
|
||||
|
||||
@@ -21,7 +21,7 @@ pipeline {
|
||||
stages {
|
||||
stage('Build') {
|
||||
steps { script {
|
||||
sh 'mdbook build'
|
||||
nix.shell('mdbook build')
|
||||
jenkins.genBuildMetaJSON('book/build.json')
|
||||
} }
|
||||
}
|
||||
@@ -43,4 +43,4 @@ pipeline {
|
||||
|
||||
def isMasterBranch() { GIT_BRANCH ==~ /.*master/ }
|
||||
def deployBranch() { isMasterBranch() ? 'deploy-master' : 'deploy-develop' }
|
||||
def deployDomain() { isMasterBranch() ? 'contributors.status.im' : 'dev-contributors.status.im' }
|
||||
def deployDomain() { isMasterBranch() ? 'contributors.free.technology' : 'dev-contributors.free.technology' }
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Description
|
||||
|
||||
This repository is the source for https://contributors.status.im/.
|
||||
This repository is the source for https://contributors.free.technology/.
|
||||
|
||||
It is built using [mdBook](https://rust-lang.github.io/mdBook/).
|
||||
|
||||
@@ -16,13 +16,13 @@ A simple alternative to using the GitHub Web UI is using their [Desktop Applicat
|
||||
|
||||
Clone repository locally using [Git](https://git-scm.com/):
|
||||
```
|
||||
git clone https://github.com/status-im/contributors.status.im.git
|
||||
git clone https://github.com/status-im/contributors.free.technology.git
|
||||
```
|
||||
You will need to [install mdBook](https://github.com/rust-lang/mdBook#installation).
|
||||
|
||||
To start a server that also builds the page use:
|
||||
```
|
||||
cd contributors.status.im
|
||||
cd contributors.free.technology
|
||||
mdbook serve
|
||||
```
|
||||
Will expose the built page under http://localhost:3000/.
|
||||
@@ -31,8 +31,8 @@ Will expose the built page under http://localhost:3000/.
|
||||
|
||||
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/>.
|
||||
- [CI builds](https://ci.infra.status.im/job/website/job/contributors.free.technology/) `master` and pushes to `deploy-master` branch, which is hosted at <https://contributors.free.technology/>.
|
||||
- [CI builds](https://ci.infra.status.im/job/website/job/dev-contributors.free.technology/) `develop` and pushes to `deploy-develop` branch, which is hosted at <https://dev-contributors.free.technology/>.
|
||||
|
||||
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).
|
||||
|
||||
|
||||
@@ -3,12 +3,14 @@ authors = ["Jakub Sokołowski"]
|
||||
language = "en"
|
||||
multilingual = false
|
||||
src = "src"
|
||||
title = "Status Contributors Guide"
|
||||
title = "IFT Contributors Guide"
|
||||
|
||||
[preprocessor.emojicodes]
|
||||
|
||||
[output.html]
|
||||
cname = "contributors.status.im"
|
||||
cname = "contributors.free.technology"
|
||||
default-theme = "light"
|
||||
path = "book/"
|
||||
additional-css = ["custom.css"]
|
||||
git-repository-url = "https://github.com/status-im/contributors.status.im"
|
||||
git-repository-url = "https://github.com/status-im/contributors.free.technology"
|
||||
git-branch = "master"
|
||||
|
||||
@@ -6,3 +6,8 @@
|
||||
ol.chapter > li:not(.chapter-item):last-child {
|
||||
visibility: hidden;
|
||||
}
|
||||
|
||||
/* Smaller size of IFT logo. */
|
||||
img[src="./images/IFT_logo.png"] {
|
||||
width: 15em;
|
||||
}
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
{
|
||||
source ? builtins.fetchTarball {
|
||||
url = "https://github.com/NixOS/nixpkgs/archive/614b4613980a522ba49f0d194531beddbb7220d3.tar.gz";
|
||||
sha256 = "sha256:1kipdjdjcd1brm5a9lzlhffrgyid0byaqwfnpzlmw3q825z7nj6w";
|
||||
},
|
||||
pkgs ? import (source) {}
|
||||
}:
|
||||
|
||||
pkgs.mkShell {
|
||||
name = "contributors-docs-shell";
|
||||
|
||||
buildInputs = with pkgs; [
|
||||
mdbook mdbook-emojicodes
|
||||
];
|
||||
}
|
||||
@@ -0,0 +1,5 @@
|
||||
# Hiring
|
||||
|
||||
For all your hiring needs. This is the section that you will need.
|
||||
|
||||
If you feel that we've missed anything or that something is unclear, please reach out to People Ops.
|
||||
@@ -1,6 +1,6 @@
|
||||
# How to request goods or services for the organization
|
||||
|
||||
Status is a rapidly growing organization with multiple moving parts. As a result, core contributors may need to utilize new tools, technologies, or seek support from consultants and other service providers to support our expansion journey.
|
||||
IFT is a rapidly growing organization with multiple moving parts. As a result, core contributors may need to utilize new tools, technologies, or seek support from consultants and other service providers to support our expansion journey.
|
||||
|
||||
To ensure that these needs align with the organizational strategy, priorities, and established policies, it is crucial that each core contributor follows the standard process for requesting goods/services.
|
||||
|
||||
|
||||
@@ -1,30 +1,33 @@
|
||||
# Summary
|
||||
|
||||
- [Introduction](./introduction.md)
|
||||
- [Welcome to Status](./welcome-to-status.md)
|
||||
- [Welcome to IFT](./welcome-to-IFT.md)
|
||||
- [Our principles](./our-principles.md)
|
||||
- [Status Core Contributors](./catalog.md)
|
||||
- [IFT Core Contributors](./catalog.md)
|
||||
- [Settling in](./settling-in/index.md)
|
||||
- [Your autonomy](./settling-in/your-autonomy.md)
|
||||
- [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/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)
|
||||
- [Travelling for Status](./contributing-to-status/travelling-for-status.md)
|
||||
- [Health resources for your working space](./contributing-to-status/health-resources-for-your-working-space.md)
|
||||
- [Referrals](./contributing-to-status/referrals.md)
|
||||
- [Headspace](./contributing-to-status/headspace.md)
|
||||
- [Contributing to IFT](./contributing-to-ift/index.md)
|
||||
- [Journey to your first contribution](./contributing-to-ift/journey-to-your-first-contribution.md)
|
||||
- [Value-creating Behaviours](./contributing-to-ift/value-creating-behaviours.md)
|
||||
- [Laptops and devices](./contributing-to-ift/laptops-and-devices.md)
|
||||
- [Collaboration](./contributing-to-ift/collaboration.md)
|
||||
- [Movement Guidelines](./contributing-to-ift/movement-guidlines.md)
|
||||
- [Coworking allowance](./contributing-to-ift/coworking-allowance.md)
|
||||
- [AI allowance](./contributing-to-ift/ai-allowance.md)
|
||||
- [Location independence](./contributing-to-ift/location-independence.md)
|
||||
- [Events and meetups](./contributing-to-ift/events-and-meetups.md)
|
||||
- [Travelling for IFT](./contributing-to-ift/travelling-for-IFT.md)
|
||||
- [Health resources for your working space](./contributing-to-ift/health-resources-for-your-working-space.md)
|
||||
- [Referrals](./contributing-to-ift/referrals.md)
|
||||
- [Headspace](./contributing-to-ift/headspace.md)
|
||||
- [Fundamentals](./fundamentals/index.md)
|
||||
- [Recommended reading](./fundamentals/essential-reading.md)
|
||||
- [Security guidelines](./fundamentals/security-guidelines.md)
|
||||
@@ -38,14 +41,8 @@
|
||||
- [Expense reimbursements](./finance/expense-reimbursements.md)
|
||||
- [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)
|
||||
- [Hiring]()
|
||||
- [Team Lead Manual](./Hiring/team-lead-manual.md)
|
||||
- [Candidate Tasks](./Hiring/candidate-tasks.md)
|
||||
- [Team Lead Manual]()
|
||||
- [Candidate Tasks](./Team-lead-manual/Candidate-Tasks.md)
|
||||
|
||||
*****
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# ℹ️ Status Core Contributors
|
||||
# ℹ️ IFT Core Contributors
|
||||
|
||||
Directory of Core Contributors
|
||||
|
||||
@@ -16,4 +16,4 @@ div#content>main>iframe.contacts {
|
||||
border: none;
|
||||
}
|
||||
</style>
|
||||
<iframe src="https://contacts.status.im/" class="contacts"></iframe>
|
||||
<iframe src="https://contacts.free.technology/" class="contacts"></iframe>
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
# 🤖 AI Allowance
|
||||
|
||||
To support core contributors in integrating AI tools into their workflow while maintaining flexibility and cost control, we are introducing a monthly expensable allowance for AI services.
|
||||
|
||||
### Benefits
|
||||
|
||||
We are equipping core contributors with a crucial skill set for the future. As AI becomes more integrated into workflows, those who effectively leverage these tools will have a competitive advantage. Key benefits include:
|
||||
|
||||
* Enhancing core contributor productivity by effectively integrating AI into daily work
|
||||
* Improving documentation and knowledge sharing within the organization
|
||||
* Ensuring AI is used responsibly and effectively in alignment with organizational needs
|
||||
|
||||
### Allowance Details
|
||||
|
||||
You can expense up to USD 60 per month for AI-related services. This allows core contributors to choose the tools that best fit their needs without incurring unnecessary costs for those who do not use them.
|
||||
|
||||
### Expense Guidelines
|
||||
|
||||
You can expense:
|
||||
|
||||
* AI service subscriptions, API credits, or tools directly aiding work productivity
|
||||
* AI-powered coding assistants, research tools, and documentation aids
|
||||
|
||||
You cannot expense:
|
||||
|
||||
* Non-work-related AI services
|
||||
* Premium AI features not directly contributing to IFT work
|
||||
* Hardware or devices for AI-related activities
|
||||
|
||||
Please keep receipts and submit your expenses through Expensify under the Software & subscriptions category following expense reimbursement guidelines.
|
||||
|
||||
If your total expense exceeds the allowance, only claim up to the approved amount.
|
||||
|
||||
If you're unsure whether an expense qualifies, reach out to People Ops for clarification.
|
||||
@@ -0,0 +1,19 @@
|
||||
# Collaboration
|
||||
|
||||
We use multiple tools for knowledge management and collaboration across the organisation. The basic platforms you need access to from Day 1 are: Google Suite, ProtonMail and Notion. On top of this, each individual teams may use other platforms such as Miro, CodiMD etc. As you start working with various teams, you will be provided access to these platforms.
|
||||
|
||||
|
||||
## Google Suite
|
||||
|
||||
Google suite is used for emails, various types of document collaboration and video calls. You will be provided with a @status.im email address which will give you access to the whole Gsuite.
|
||||
|
||||
|
||||
## ProtonMail
|
||||
|
||||
Google does not align with our values as an organisation and so there is currently a project to move away from Google and start using ProtonMail as our email provider. You will be getting a secondary email address on-top of your existing @status.im address.
|
||||
|
||||
You can read about this change, [when to use Gmail vs. ProtonMail](https://www.notion.so/Phase-1-Replace-Google-Mail-w-Proton-Mail-34d999eacb27446dacdbb426075fe6da) along with the more details about the project and timelines.
|
||||
|
||||
|
||||
## Notion
|
||||
Notion is a collaborative Wiki, just like Confluence (if you have ever used it). Most teams collaborate on this platform and this is part of knowledge management across the organisation.
|
||||
@@ -11,7 +11,7 @@ You can't use the allowance for:
|
||||
* Your internet/broadband costs.
|
||||
* Covering additional bills arising from you working from home.
|
||||
* Meals or drinks outside working hours or for take-away drinks.
|
||||
* Meals or drinks for people accompanying you that don't contribute to Status.
|
||||
* Meals or drinks for people accompanying you that don't contribute to IFT.
|
||||
* Gratuities.
|
||||
|
||||
>😃 An example of a claimable expense:
|
||||
@@ -19,7 +19,7 @@ USD 200 for coworking space + USD 50 on drinks consumed at the coworking space;
|
||||
or
|
||||
USD 50 consumed on drinks at a space **used for working** outside your home office.
|
||||
|
||||
>😡 An example of a non-claimable expense: USD 0-270 consumed on drinks at a space when you are not contributing to a Status project.
|
||||
>😡 An example of a non-claimable expense: USD 0-270 consumed on drinks at a space when you are not contributing to a IFT project.
|
||||
|
||||
Please keep the invoices/receipts and submit your costs through Expensify as per the [expense reimbursement guidelines](../finance/expense-reimbursements.md), specifying coworking as the category detailing the expense in the comments field of your expense line item.
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
# 🎤 Events and meetups
|
||||
|
||||
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 IFT sponsor
|
||||
|
||||
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 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 IFT.
|
||||
|
||||
> ✨ 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 🙂
|
||||
|
||||
> Always speak to your team lead and discuss the impact going to an event will have on yourself or IFT.
|
||||
|
||||
> 💡Before attending an event, ask your Talent Partner to generate a QR code for our job pages that you can share with anyone interested.
|
||||
|
||||
## Related articles
|
||||
|
||||
👉 Check out [Travelling for IFT](../contributing-to-ift/travelling-for-IFT.md) for commute and accommodation guidelines if you need to travel for the event.
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
|
||||
Headspace is one of the leading apps that focuses on mindfulness, meditation and has a range of tailored workouts for the mind. There's [research](https://www.headspace.com/science/meditation-research) that the app can positively impact stress, focus, mood, and work.
|
||||
|
||||
If you contribute to Status, you can enjoy a premium subscription (free of charge). To use one of the subscriptions, signup with your @status.im email [here](https://work.headspace.com/status/join). If there are no available seats, please reach out to your People Partner and they will purchase a new seat for you.
|
||||
If you contribute to IFT, you can enjoy a premium subscription (free of charge). To use one of the subscriptions, signup with your @status.im email [here](https://work.headspace.com/ift/member-enroll). If there are no available seats, please reach out to your People Partner and they will purchase a new seat for you.
|
||||
|
||||
[Here](https://drive.google.com/drive/folders/122aJjQRK-CCnC0f_y8vWRAhiLQR_f9H9) you can find some helpful resources to help you on your journey.
|
||||
|
||||
While meditation might not be for everyone, we hope that some of you will find Headspace useful.
|
||||
While meditation and mindfulness might not be for everyone, we hope that some of you will find Headspace useful.
|
||||
@@ -1,20 +1,20 @@
|
||||
# Contributing to Status
|
||||
# Contributing to IFT
|
||||
|
||||
## Core contributor standards
|
||||
|
||||
One of the ways People Ops can support reaching our broader organisational goals is by providing frameworks and support to make sure that core contributors are adhering to certain standards in the delivery of their services and/or projects. This is useful for Status and the core contributor to ensure the overarching product and strategy goals are met.
|
||||
One of the ways People Ops can support reaching our broader organisational goals is by providing frameworks and support to make sure that core contributors are adhering to certain standards in the delivery of their services and/or projects. This is useful for IFT and the core contributor to ensure the overarching product and strategy goals are met.
|
||||
|
||||
Our aim is to normalise (self-)evaluations and talk about what’s good and what requires improvement on a continuous basis. Lattice is our performance management platform across Status. It is widely used for mid & end of trial, mid & end of year, as well as ongoing feedback.
|
||||
Our aim is to normalise (self-)evaluations and talk about what’s good and what requires improvement on a continuous basis. Lattice is our performance management platform across Status. It is widely used for end of trial, mid & end of year, as well as ongoing feedback.
|
||||
|
||||
## What we expect
|
||||
|
||||
* We expect you to show us you can prioritise correctly, get things done, and find answers in an increasingly autonomous way. In most projects, there will be a first project scoped out for you. Regardless of that being the case, make sure you ask your lead where you can start, clarify expectations for your role, or seek feedback on how you're doing, early and regularly.
|
||||
* We expect you to be accountable for your goals and deadlines. We don't micromanage - if by any chance you realise you're stuck, make sure to flag it and discuss within your project and project lead whether or not it would be best to change course.
|
||||
* We don't see each other much, and written communication is what we see the most from each other. We'd like for everyone to be clear, friendly, and helpful to everyone else. Great communication is key!
|
||||
* Given that Status is a highly distributed organisation, working with core contributors across multiple time zones and with minimal physical collaboration, we expect a consistent and high volume of communication to keep your fellow core contributors updated on your progress to ensure that the projects can efficiently be coordinated and delivered in the appropriate time frames. There's no expectation that you reply to each ping immediately. Do your work and avoid interruptions while checking your messages at least a couple of times a day. If you know you won't have time to look into something right away, let the other party know when they can expect to have an answer to organise their work efficiently.
|
||||
* Given that IFT is a highly distributed organisation, working with core contributors across multiple time zones and with minimal physical collaboration, we expect a consistent and high volume of communication to keep your fellow core contributors updated on your progress to ensure that the projects can efficiently be coordinated and delivered in the appropriate time frames. There's no expectation that you reply to each ping immediately. Do your work and avoid interruptions while checking your messages at least a couple of times a day. If you know you won't have time to look into something right away, let the other party know when they can expect to have an answer to organise their work efficiently.
|
||||
* Everyone should contribute to the products and our culture. If you see anything that can be improved and have an idea to make it better, bring it up! If you see that a fellow core contributor is stuck, offer to help or ping someone who can. We're all in the same boat trying to achieve the same goals so let's help each other!
|
||||
* Read [this article](https://medium.com/remote-work/12-qualities-to-look-for-when-hiring-remote-workers-68243ff351b0).It gives a sense of what qualities Status expects of the core contributors.
|
||||
* Read [this article](https://medium.com/remote-work/12-qualities-to-look-for-when-hiring-remote-workers-68243ff351b0).It gives a sense of what qualities we expect of our core contributors.
|
||||
* For those less experienced in the blockchain/crypto space - jump in and immerse yourself in the ecosystem and get to understand our principles and mission better. This is a big topic, and we don't expect everyone to become an expert. Still, we would be super impressed to see that you're committed to continuously learning and developing your knowledge.
|
||||
* Try to model our principles in all that you do at Status.
|
||||
* In order to help with what behaviours create value, here you can see a Status-specific list of [value-creating behaviours](../contributing-to-status/value-creating-behaviours.md) and some examples in which they could manifest.
|
||||
* Try to model our principles in all that you do at IFT.
|
||||
* In order to help with what behaviours create value, here you can see a IFT-specific list of [value-creating behaviours](../contributing-to-ift/value-creating-behaviours.md) and some examples in which they could manifest.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# 🌟 Journey to your first contribution...
|
||||
|
||||
Status is developing a number of projects and each project has the freedom to organise themselves however it best sees fit. Throughout your first two weeks, during 1:1s, project weeklies or setting calls specifically for this, get the feel of the specific rituals, dynamics and communication forms within your project and how it connects back with the bigger Status vision.
|
||||
IFT is developing a number of projects and each project has the freedom to organise themselves however it best sees fit. Throughout your first two weeks, during 1:1s, project weeklies or setting calls specifically for this, get the feel of the specific rituals, dynamics and communication forms within your project and how it connects back with the bigger IFT vision.
|
||||
|
||||
## Retros and priorities
|
||||
|
||||
@@ -13,7 +13,7 @@ Read your project last quarter's retro and learnings, and focus on this quarter'
|
||||
- What are the priorities set for this quarter.
|
||||
|
||||
## Figure out your first contribution
|
||||
The first month in a new project can be as exciting as it can be overwhelming with everything that Status is building. For this reason we recommend you to work closely with your project lead or your closest peer to scope what your first contribution will be.
|
||||
The first month in a new project can be as exciting as it can be overwhelming with everything that IFT and our projects are building. For this reason we recommend you to work closely with your project lead or your closest peer to scope what your first contribution will be.
|
||||
|
||||
Try to aim for a small project, something that can help you understand your stack progressively and get something done within your first weeks!
|
||||
|
||||
@@ -0,0 +1,60 @@
|
||||
# 🖥 Laptops and devices
|
||||
|
||||
Having the proper setup is fundamental to ensure you can work comfortably to successfully deliver services to IFT and our projects. We hold our principles dear and support you as a core contributor with some of the tools you might need to succeed in providing services using secure, decentralised devices.
|
||||
|
||||
Here you'll find some helpful information to get yourself set up with the right equipment you may need.
|
||||
|
||||
## ☑️ Available equipment
|
||||
|
||||
Core contributors have the potential option of leasing devices from IFT to ensure that they can provide their services. We have a list of pre-approved equipment considered within their project budgets to the extent that you need certain devices to deliver your services.
|
||||
|
||||
While IFT provides you the flexibility to purchase the appropriate devices in line with the capped amounts stated in this section, IFT ultimately owns such devices. Following your purchase, we will subsequently lease you back the device which you have purchased.
|
||||
|
||||
For the purposes of purchasing devices, reach out to your Project Lead and PeopleOps partner for approval.
|
||||
|
||||
The standard setup for everyone includes a laptop, a Keycard, a Yubikey, and a Ledger.
|
||||
|
||||
For each item we have defined a budget. Your spend will stay below the defined budget, in most cases. When this happens, it is not an option to use the difference towards the cost of other items.
|
||||
|
||||
* Laptop: up to USD 3,000
|
||||
* Mic and headphones: up to USD 120
|
||||
* Keycard: ping the #keycard channel to get a code
|
||||
* Yubikey: you can reimburse one (approx USD 75)
|
||||
* Ledger: you can reimburse one (approx USD 80)
|
||||
|
||||
> Most core contributors should be able to effectively perform their work using standard equipment, but if you're struggling to participate or you need other equipment to perform your role successfully (for example, you need a better quality webcam to record videos or a higher quality mic to record demos for IFT), then please speak to your Project Lead or PeopleOps partner to discuss your needs on a case by case basis. For those that are approved to receive higher quality equipment, we recommend the **Logitech Brio 4K Webcam** and the **Rode NT-USB USB Condenser Microphone**.
|
||||
|
||||
Following the cessation or termination of your services to IFT, you have the option of purchasing from IFT any equipment you purchased in accordance with this section.
|
||||
|
||||
## 🏪 How to get your devices
|
||||
|
||||
1. Choose official or trusted vendors to buy your devices
|
||||
2. Seek approval from your Project Lead or your PeopleOps partner
|
||||
3. Upon getting okays from your Project Lead and PeopleOps partner, proceed with the purchase.
|
||||
4. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
5. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
|
||||
6. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
7. Enter into a leasing agreement with IFT in respect of the device you have purchased.
|
||||
|
||||
## ℹ️ FAQ
|
||||
|
||||
* __Who owns the devices which I’ve purchased__
|
||||
|
||||
IFT is the owner of the devices which you have purchased. IFT will lease back these devices to you in order for you to deliver your services. We have found that this is a flexible and convenient arrangement to ensure that you can obtain the appropriate devices in a timely manner to deliver your services.
|
||||
|
||||
* __What if I don't have enough funds to buy the device before reimbursement?__
|
||||
|
||||
If cash flow is an issue, please ping your People Partner and we'll help come up with a solution!
|
||||
|
||||
* __What if my devices becomes outdated?__
|
||||
|
||||
At the 3 year mark, if your device needs an upgrade, speak to your PeopleOps partner about purchasing a new one.
|
||||
|
||||
* __What happens if I accidentally damage a device?__
|
||||
|
||||
You should treat the devices as if they were yours. If the damage was due to factors beyond your control, please obtain a quote for a repair and let your People Partner know. If the cost is reasonable (i.e., less than ~75% of the trade-in value of the asset), we would ask you to go ahead and get the device repaired. Then, submit the repair expense cost for reimbursement.
|
||||
|
||||
* __What happens if my services agreement with IFT finishes?__
|
||||
|
||||
Please check out [this guide](../offboarding/device-logistics.md) for your options on recycling or buying back devices.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# 🌏 Location independence
|
||||
|
||||
Status is a fully remote, location-agnostic organisation – meaning that we don’t mandate the location where you should provide your services.
|
||||
IFT is a fully remote, location-agnostic organisation – meaning that we don’t mandate the location where you should provide your services.
|
||||
|
||||
Being location independent means you could decide to move away from where you were first delivering your services, and that's okay. Status can provide you with confirmation of a service engagement letter if you need it in the process of migrating abroad.
|
||||
Being location independent means you could decide to move away from where you were first delivering your services, and that's okay. IFT can provide you with confirmation of a service engagement letter if you need it in the process of migrating abroad.
|
||||
|
||||
However, we will not cover the visa/work permit processing or relocation costs as we're location agnostic for work.
|
||||
|
||||
@@ -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.
|
||||
Please only refer to IFT 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.
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
|
||||
# Movement Guidelines
|
||||
|
||||
Movement to a different role within IFT offers many benefits. It is an important process that helps us keep valuable expertise within the organisation, allows core contributors to develop additional skills and enhances the strength and adaptability of our teams.
|
||||
|
||||
|
||||
To ensure fair, transparent, and efficient movement to the new role, we have established the following guidelines for core contributors to follow:
|
||||
|
||||
|
||||
### Open Roles
|
||||
|
||||
All open roles can be found on our websites ([IFT](https://free.technology/jobs), [Logos](https://boards.greenhouse.io/logos), [Status](https://status.app/jobs)) or by checking out the hiring channels in the Logos Discord and Status App.
|
||||
|
||||
For more information regarding the requirements of any roles, we suggest contacting the Talent team directly rather than the hiring lead.
|
||||
|
||||
We believe in transparency and open communication between core contributors, team leads, and People Ops. Before applying for a different role, core contributors should discuss their interests with their current team lead and/or People Partner to evaluate their fit and motivations.
|
||||
|
||||
### Eligibility Criteria
|
||||
|
||||
We expect a core contributor to meet at least the minimum required skills/attributes, which will be clearly described in the role’s description before applying.
|
||||
|
||||
Whilst we don’t have strict rules, as a general guideline, we’d expect someone to have contributed to their current project for 12 months before moving to a different team.
|
||||
|
||||
### Application and Screening Process
|
||||
|
||||
All applications are carefully reviewed based on skills, experience and alignment with the role requirements.
|
||||
|
||||
The screening process varies depending on the role. Some roles may involve a few interviews and possibly a task. The process may be more extensive for other roles, typically including interviews with program leads and Co-Founders.
|
||||
|
||||
The hiring team will likely consult with a core contributor's current team lead to gain insights into their skillset, motivations, and team fit.
|
||||
|
||||
### What happens if a core contributor successfully moves to a new team/project?
|
||||
|
||||
Congratulations! If the decision is favourable, together with the team leads and People Partners, a transition plan will be formed to move the core contributor to the new role. It is important to respect the current team by providing an extensive handover and allowing time for a backfill to be embedded. Overall, the goal is to ensure that the transition into the new internal role is as smooth and successful as possible, setting the core contributor up for success.
|
||||
|
||||
### Is there a trial period for moves?
|
||||
|
||||
Whilst there is no official trial period, we consider the first 12 weeks within the new role as the trial. During this period, the team leads are encouraged to provide ongoing feedback, check in’s and support as necessary.
|
||||
|
||||
|
||||
@@ -1,34 +1,34 @@
|
||||
# 👑 Referrals
|
||||
|
||||
There are many ways you can help Status grow: engaging with the community, interviewing, helping out with events, etc., but referring outstanding people to Status is one of the most direct ways you can make an impact.
|
||||
There are many ways you can help IFT grow: engaging with the community, interviewing, helping out with events, etc., but referring outstanding people to IFT is one of the most direct ways you can make an impact.
|
||||
|
||||
As an organisation, we're reliant on many groups to help us reach our goals: freelancers, community members, testers, researchers, users and more. We need these groups and individuals who make hugely valuable contributions, alongside core contributors who contribute to Status on a full-time basis.
|
||||
|
||||
Engaging with potential core contributors that align with Status' values and excel in their field is essential to us; and we'd love your help! Below, you'll find helpful information to connect the extraordinary people you know, with Status.
|
||||
Engaging with potential core contributors that align with IFT' values and excel in their field is essential to us; and we'd love your help! Below, you'll find helpful information to connect the extraordinary people you know, with IFT.
|
||||
|
||||
## Referral bonus
|
||||
|
||||
If you've worked with someone amazing and think they would be a great fit at Status, not only would we like to know, but we'll also reward you once they've successfully completed their trial period.
|
||||
If you've worked with someone amazing and think they would be a great fit at IFT, not only would we like to know, but we'll also reward you once they've successfully completed their trial period.
|
||||
|
||||
Status will reward you a referral payment of USD 5,000 worth of SNT after they’ve been with Status as a core contributor for three months. At times, we might offer higher rewards for specific critical roles, so stay tuned for updates in the #people-ops channel!
|
||||
IFT will reward you a referral payment of USD 5,000 worth of SNT after a successful trial period. At times, we might offer higher rewards for specific critical roles, so stay tuned for updates in the #people-ops channel!
|
||||
|
||||
### Eligibility criteria
|
||||
|
||||
* You can only refer potential core contributors that have not applied to us independently within the last 90 days.
|
||||
* You can only refer potential core contributors who have not applied to us independently within the last 60 days.
|
||||
* Referrals are for individuals; we are not responsible for any fees related to resumes received from recruitment agencies.
|
||||
* The initial contact between Status and your referral must be facilitated by you. If someone is already known to us or is in the middle of the selection process, we wouldn't consider it a new referral.
|
||||
* The referral payment only applies to engaging core contributors that contribute to Status on 12-month fixed term arrangements. It does not apply to engaging part-time or short-term contractors.
|
||||
* For someone you refer, you would be removed from any interview process involving them (this ensures we are fair and unbiased in our acquisition process).
|
||||
* Unfortunately, if you are the project lead, the referral bonus doesn’t apply if you have hired someone into the role you are leading.
|
||||
* The initial contact between IFT and your referral must be facilitated by you.
|
||||
* The referral payment only applies to engaging core contributors. It does not apply to engaging freelancers.
|
||||
* For someone you refer, you would be removed from any interview process involving them (this ensures we are fair and unbiased in our acquisition. process).
|
||||
* Team Leads should recuse themselves from decision-making if they stand to gain financially. i.e. they can refer someone, and get the bonnus. But the decision to hire should be made by someone impartial, or a team committee.
|
||||
|
||||
Sorry for the many conditions! We want to be fair and apply some common-sense guidelines, but let us know if you have any better ideas! 🙂
|
||||
|
||||
## How to make a referral
|
||||
|
||||
Here are the basics of referring incredible people to join Status. There are a few ways:
|
||||
Here are the basics of referring incredible people to join IFT. There are a few ways:
|
||||
|
||||
* Send the CV, GitHub or LinkedIn URL along with a note detailing why you recommend them, how well you know this person etc to [referrals@status.im](mailto:referrals@status.im) (Talent will upload to Greenhouse adding you as referrer; alongside the notes you provide)
|
||||
* If you are a Greenhouse user, you can also make use of it to make a referral - you’ll find the detailed steps [here](https://docs.google.com/presentation/d/16sg-pgJr7MGndemyBdulaz7sbgFYMp5DKpz30H_g1Xw/edit#slide=id.g131b733a5f9_1_522). Make sure to add their contact information, CV, and where and why you think they'd be great for Status. The project leads your comments when reviewing referrals, so this can help them stand out among other potential core contributors.
|
||||
* Send the CV, GitHub or LinkedIn URL along with a note detailing why you recommend them, how well you know this person etc to [referrals@status.im](mailto:referrals@status.im) (Talent will upload to Greenhouse adding you as referrer; alongside the notes you provide).
|
||||
* If you are a Greenhouse user, you can also make use of it to make a referral - you’ll find the detailed steps [here](https://docs.google.com/presentation/d/16sg-pgJr7MGndemyBdulaz7sbgFYMp5DKpz30H_g1Xw/edit#slide=id.g131b733a5f9_1_522). Make sure to add their contact information, CV, and where and why you think they'd be great for IFT. The project leads your comments when reviewing referrals, so this can help them stand out among other potential core contributors.
|
||||
* Ask the Talent team to give you access to Greenhouse if the URL isn't working for you.
|
||||
* While you should share people whose work you can speak to and are impressed by (i.e., the top 25% of people you've worked with), don't feel pressured to refer everyone who asks. If you feel uncomfortable saying no (we get it; it can be awkward), you can mention it in the notes in the referral form.
|
||||
|
||||
@@ -36,7 +36,7 @@ Here are the basics of referring incredible people to join Status. There are a f
|
||||
|
||||
The Talent team will take good care of them and keep you posted on their progress through the selection process. Still, you can be a critical layer of support to them by:
|
||||
* Help them prepare for interviews or activities, just enough for them to be prepared. But not too much. Why? We’ve had instances in the past where referrals were prepared too well, meaning they did great during the interview process but then struggled once they were onboarded.
|
||||
* Answering questions about working at Status and your experiences as a core contributor.
|
||||
* Answering questions about working at IFT and your experiences as a core contributor.
|
||||
* If they get an offer, help us convince them to accept it!
|
||||
|
||||
> ✨ Diverse perspectives, backgrounds, and experiences lead to better products. When you refer talent from underrepresented groups, particularly into technical positions, you're doing your part to build a diverse workforce across all functions and levels.
|
||||
@@ -49,9 +49,9 @@ We consider a “Personal Relation” to be a core contributor’s spouse or par
|
||||
|
||||
As such, we have set out the following rules for core contributors and their Personal Relations when both are engaged by Status:
|
||||
|
||||
* The core contributor should not work directly for or lead a Personal Relation
|
||||
* The core contributor should not participate in or influence the decision-making process of a Personal Relation (including interviewing, engagement offers or fee negotiations)
|
||||
* The core contributor should not participate in or influence the performance management process of a Personal Relation including trial periods and ongoing performance management or any performance-related issues
|
||||
* The core contributor should not work directly for or lead a Personal Relation.
|
||||
* The core contributor should not participate in or influence the decision-making process of a Personal Relation (including interviewing, engagement offers or fee negotiations).
|
||||
* The core contributor should not participate in or influence the performance management process of a Personal Relation including trial periods and ongoing performance management or any performance-related issues.
|
||||
* The contributor does not have access to sensitive personal information including payroll, compensation, personnel reviews/files, job performance of the Personal Relation.
|
||||
|
||||
To ensure maximum flexibility, fairness, and transparency, please disclose any (potentially) conflicting relationships or relationships that may give rise to favouritism, to your project lead and People Partner at the beginning of the engagement process and we can assess each case individually.
|
||||
@@ -61,17 +61,29 @@ To ensure maximum flexibility, fairness, and transparency, please disclose any (
|
||||
We want to ensure that our engagement process is fair and transparent. As such, best practice for these situations is:
|
||||
|
||||
* No interviewer may interview Personal Relations or referrals
|
||||
* If you, as an interviewer, become aware of any potential conflict of interest, please alert the relevant member of the Talent team immediately.
|
||||
* If you, as an interviewer, become aware of any potential conflict of interest, please alert the relevant member of the Talent team immediately.
|
||||
|
||||
We understand that Personal Relations and referrals may be highly qualified for open positions and we want to ensure that all applicants receive the same level of consideration and respect. We will make sure that any Personal Relation or referral is given the same opportunity as any other applicant by assigning the interview to another interviewer. This applies to all interviewers across Status.
|
||||
We understand that Personal Relations and referrals may be highly qualified for open positions and we want to ensure that all applicants receive the same level of consideration and respect. We will make sure that any Personal Relation or referral is given the same opportunity as any other applicant by assigning the interview to another interviewer. This applies to all interviewers across IFT.
|
||||
|
||||
## Success, your referral is onboard! What's next?
|
||||
|
||||
If the referral is successful and passes their trial period, you are eligible for a bonus of USD 5,000 worth of SNT. The recruiter in charge will contact you to give you the green light to submit the SNT bonus on an invoice.
|
||||
|
||||
* Submit a separate invoice for the referral bonus payment to finance (billing@status.im).
|
||||
* The deadline to submit your invoice is 3 months.
|
||||
* Once submitted, the bonus will be paid with the next monthly payment.
|
||||
|
||||
_Note: Please, make sure that you attach your correct wallet address to the invoice AND have it updated in BambooHR!_
|
||||
|
||||
**Important: In case you are not legally allowed to receive crypto in your country, please reach put to #people-ops team or the recruiter in charge.**
|
||||
|
||||
## It doesn't always work out...why hasn’t my referral been engaged?
|
||||
|
||||
While referrals generally have a much higher success rate than those engaged normally, there may be a chance that your referral doesn't end up being a core contributor engaged by Status (the performance of the core contributor won’t be held against you, after all it’s on the project to interview and come to a decision on whether they deem the referred individual a fit for the role/project). This might happen due to:
|
||||
While referrals generally have a much higher success rate than those engaged via the full recruitment process, there may be a chance that your referral doesn't end up being a core contributor engaged by IFT (the performance of the core contributor won’t be held against you, after all, it’s on the project to interview and come to a decision on whether they deem the referred individual a fit for the role/project). This might happen due to:
|
||||
|
||||
* Timing: their qualifications don't match the roles currently available.
|
||||
* Suitability: they don't meet all of the minimum requirements listed for the role.
|
||||
* Competition: there was someone else who was more qualified.
|
||||
* Demand: the role was reduced or closed.
|
||||
|
||||
|
||||
Thank you for your support in bringing great people into IFT!
|
||||
@@ -1,20 +1,17 @@
|
||||
# 🌍 Travelling for Status
|
||||
# 🌍 Travelling for IFT
|
||||
|
||||
Connecting with people in person is such an essential part of the remote working experience at Status. Magic happens when people get together.
|
||||
Connecting with people in person is such an essential part of the remote working experience at IFT. Magic happens when people get together.
|
||||
|
||||
Here you'll find helpful information to make your travel abroad experience more efficient while being compliant and accountable to project resources. These guidelines apply to anyone travelling for or sponsored by Status away from their usual working location.
|
||||
Here you'll find helpful information to make your travel abroad experience more efficient while being compliant and accountable to project resources. These guidelines apply to anyone travelling for or sponsored by IFT away from their usual working location.
|
||||
|
||||
Some of these points might not apply to offsites as they're usually centrally organised with their particular budget.
|
||||
|
||||
Your travel budget comes from your project's budget. Raise a travel request [SpiffWorkflow](https://prod.mod.spiff.status.im/) and check out [Events and meetups](../contributing-to-status/events-and-meetups.md) before booking your trip.
|
||||
|
||||
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
|
||||
|
||||
Your travel budget comes from your project's budget. Speak to your team lead and check out [Events and meetups](../contributing-to-ift/events-and-meetups.md) before booking your trip. Your team lead will need to approve the budget before you book!
|
||||
|
||||
## Before travelling abroad:
|
||||
|
||||
> * Head to the official government pages to understand the risks in a country and the latest restrictions applicable to you, including re-entry requirements.
|
||||
> * Keep in mind that government guidelines are changing as frequently as every few days and that they can impact your travel plans severely.
|
||||
> * Keep in mind that government guidelines may change frequently and that they can impact your travel plans severely.
|
||||
> * Be aware of and account for any extraordinary events which may impact your travel, such as natural disasters, political unrest, wars, riots, epidemics, pandemics and any other extraordinary events.
|
||||
> * Consider booking timeframes and select cancellation and insurance policies accordingly.
|
||||
|
||||
@@ -23,7 +20,7 @@ Here's the instructions on [how to create a travel request](https://www.notion.s
|
||||
|
||||
It's hard to cover every case within a guide. We trust you to use your best judgement when travelling for company purposes and proactively report back anything you consider relevant.
|
||||
|
||||
Don't go overboard with spending on bookings, food, and drinks. Keep accountability and transparency in mind. Always ask for receipts and keep them organised. Status will reimburse for all reasonable expenses while travelling in accordance with this section.
|
||||
Don't go overboard with spending on bookings, food, and drinks. Keep accountability and transparency in mind. Always ask for receipts and keep them organised. IFT will reimburse for all reasonable expenses while travelling in accordance with this section.
|
||||
|
||||
|
||||
### What are reasonable expenses
|
||||
@@ -31,7 +28,7 @@ Don't go overboard with spending on bookings, food, and drinks. Keep accountabil
|
||||
* Reasonable expenses examples:
|
||||
|
||||
* Flights, ground transportation, accommodation, and workspace, if needed, as described below, as long as these are approved by project leads.
|
||||
* As a general rule, a max trip average of $85/day/person for meals. However, this will depend on the destination. If you're dining together with other core contributors, you can submit one bill - just make sure to add their names in the comments section when you file the expense.
|
||||
* As a general rule, a max trip average of USD $85/day/person for meals. However, this will depend on the destination. If you're dining together with other core contributors, you can submit one bill - just make sure to add their names in the comments section when you file the expense.
|
||||
* Laundry charges for trips longer than five days.
|
||||
* When required and justified for the trip, expedited service fees, travel visas, and inoculation fees necessary for the destination are reimbursable.
|
||||
* Reasonable mobile, roaming, or hotspot connection fees to allow you to work while travelling would be covered. However, we suggest purchasing a local SIM card or eSIM providers, such as [Airalo](https://www.airalo.com/).
|
||||
@@ -41,13 +38,13 @@ Don't go overboard with spending on bookings, food, and drinks. Keep accountabil
|
||||
* Travel programs, airline upgrades, fast tracks, or premium services.
|
||||
* Airline/accommodation no-show, cancellation, or rebooking fees.
|
||||
* Convenience products, alcohol, cigarettes and fees for the use of the gym, spa, and other facilities.
|
||||
* Travelling companions hotel, flights and meals.
|
||||
* Travelling companions' hotel, flights and meals.
|
||||
* Room service (except for meals within the daily limit) or in-room movies/entertainment.
|
||||
* Mobile, roaming, or hotspot connection fees for personal use.
|
||||
* In-flight entertainment
|
||||
* Any personal expenses and fines, custom charges, etc.
|
||||
|
||||
If there are any issues or you believe that you should get reimbursed for any of the expenses above, please speak to your People Partner, who can review your request on a case by case basis. Ultimately, it will be in Status’ sole discretion to determine whether an expense is a “reasonable expense” and whether it will be reimbursed.
|
||||
If there are any issues or you believe that you should get reimbursed for any of the expenses above, please speak to your People Partner, who can review your request on a case by case basis. Ultimately, it will be in IFT’ sole discretion to determine whether an expense is a “reasonable expense” and whether it will be reimbursed.
|
||||
|
||||
Whether using a card or requesting reimbursements, you're responsible for submitting your expenses correctly as a traveller. We currently process expenses together with payroll or invoices. When you're back from your trip, follow the instructions on [How to file expenses or get reimbursed](../finance/expense-reimbursements.md) for uploading your receipts in a compliant and timely manner to keep our finances healthy.
|
||||
|
||||
@@ -59,7 +56,8 @@ 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. 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).
|
||||
* 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 IFT or the event.
|
||||
* 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.
|
||||
@@ -69,7 +67,7 @@ Usually, the earlier you plan your trip, the cheaper and better it's going to be
|
||||
|
||||
You can book your stay at a 3-4 star hotel or an Airbnb. We generally recommend hotels for solo or two person trips and Airbnbs for groups or project travel.
|
||||
|
||||
An Airbnb can be more practical for spending quality time together and setting a coworking space in the dining or living room, than a hotel. It's also more convenient to coordinate meals and share rides to/from the event or airport when we're staying together.
|
||||
An Airbnb can be more practical for spending quality time together and setting up a coworking space in the dining or living room, than a hotel. It's also more convenient to coordinate meals and share rides to/from the event or airport when we're staying together.
|
||||
|
||||
If you are organising a project off-site, reach out to your People Partner who can help with logistics and bookings of an AirBnb.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## 🧘 Focus
|
||||
### Great ✅
|
||||
* Prioritising and deprioritising efforts correctly - most effort on the most important thing for Status’ continuance
|
||||
* Prioritising and deprioritising efforts correctly - most effort on the most important thing for IFT’ continuance
|
||||
* Translate theory into pragmatic decisions
|
||||
* Find ways to increase revenue
|
||||
|
||||
@@ -45,7 +45,7 @@
|
||||
|
||||
## 🤝 Collaboration across other projects
|
||||
### Great ✅
|
||||
* Cross-functional projects or ideas that can improve Status as a whole
|
||||
* Cross-functional projects or ideas that can improve IFT as a whole
|
||||
* Reading/being active on channels outside of the immediate area of work
|
||||
* Supporting with events/community
|
||||
* Helping communication flow/easing misunderstandings
|
||||
@@ -1,46 +0,0 @@
|
||||
# 🎤 Events and meetups
|
||||
|
||||
As a Status 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
|
||||
|
||||
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:
|
||||
|
||||
* 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.
|
||||
* Internal events and meetups to prepare a product/project launch or work together.
|
||||
* Moderating or speaking opportunities related to Status.
|
||||
|
||||
> ✨ 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 🙂
|
||||
|
||||
> 💡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).
|
||||
|
||||
## Once you have your travel details ready
|
||||
|
||||
Submit your individual travel request via [SpiffWorkflow](https://prod.mod.spiff.status.im/).
|
||||
|
||||
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
|
||||
|
||||
## Related articles
|
||||
|
||||
👉 Check out [Travelling for Status](../contributing-to-status/travelling-for-status.md) for commute and accommodation guidelines if you need to travel for the event.
|
||||
|
||||
@@ -1,60 +0,0 @@
|
||||
# 🖥 Laptops and devices
|
||||
|
||||
Having the proper setup is fundamental to ensure you can work comfortably to successfully deliver services to Status. We hold our principles dear and support you as a core contributor with some of the tools you might need to succeed in providing services to Status using secure, decentralised devices.
|
||||
|
||||
Here you'll find some helpful information to get yourself set up with the right equipment you may need.
|
||||
|
||||
## ☑️ Available equipment
|
||||
|
||||
Core contributors have the potential option of leasing devices from Status to ensure that they can provide their services. Status has a list of pre-approved equipment considered within their project budgets to the extent that you need certain devices to deliver your services.
|
||||
|
||||
While Status provides you the flexibility to purchase the appropriate devices in line with the capped amounts stated in this section, Status ultimately owns such devices. Following your purchase, Status will subsequently lease you back the device which you have purchased.
|
||||
|
||||
For the purposes of purchasing devices, you need to raise the request via [SpiffWorkflow](https://prod.mod.spiff.status.im/) to get okays from your Project Lead and PeopleOps partner.
|
||||
|
||||
The standard setup for everyone includes a laptop, a Keycard, a Yubikey, and a Ledger.
|
||||
|
||||
For each item we have defined a budget. Your spend will stay below the defined budget, in most cases. When this happens, it is not an option to use the difference towards the cost of other items.
|
||||
|
||||
* Laptop: up to USD 3,000
|
||||
* Mic and headphones: up to USD 120
|
||||
* Keycard: ping the #keycard channel to get a code
|
||||
* Yubikey: you can reimburse one (approx USD 50)
|
||||
* Ledger: you can reimburse one (approx USD 80)
|
||||
|
||||
> Most core contributors should be able to effectively perform their work using standard equipment, but if you're struggling to participate or you need other equipment to perform your role successfully (for example, you need a better quality webcam to record videos or a higher quality mic to record demos for Status), then please raise the request via [SpiffWorkflow](https://prod.mod.spiff.status.im/) and People Partner can support you with your needs on a case by case basis. For those that are approved to receive higher quality equipment, we recommend the **Logitech Brio 4K Webcam** and the **Rode NT-USB USB Condenser Microphone**.
|
||||
|
||||
Following the cessation or termination of your services to Status, you have the option of purchasing from Status any equipment you purchased in aordance with this section.
|
||||
|
||||
## 🏪 How to get your devices
|
||||
|
||||
1. Choose official or trusted vendors to buy your devices
|
||||
2. Raise a request for goods/services via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a) prior to purchasing the devices.
|
||||
3. Upon getting okays from your Project Lead and PeopleOps partner, proceed with the purchase.
|
||||
4. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
5. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
|
||||
6. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
7. Enter into a leasing agreement with Status in respect of the device you have purchased.
|
||||
|
||||
## ℹ️ FAQ
|
||||
|
||||
* __Who owns the devices which I’ve purchased__
|
||||
|
||||
Status is the owner of the devices which you have purchased. Status will lease back these devices to you in order for you to deliver your services. We have found that this is a flexible and convenient arrangement to ensure that you can obtain the appropriate devices in a timely manner to deliver your services.
|
||||
|
||||
* __What if I don't have enough funds to buy the device before reimbursement?__
|
||||
|
||||
If cash flow is an issue, please mention it in the request (select "Payment method" <> "Reimbursement") and ping your People Partner and we'll help come up with a solution!
|
||||
|
||||
* __What if my devices becomes outdated?__
|
||||
|
||||
At the 3 year mark, if your device needs an upgrade, just raise a new request via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a).
|
||||
|
||||
* __What happens if I accidentally damage a device?__
|
||||
|
||||
You should treat the devices as if they were yours. If the damage was due to factors beyond your control, please obtain a quote for a repair and let your People Partner know. If the cost is reasonable (i.e., less than ~75% of the trade-in value of the asset), we would ask you to go ahead and get the device repaired. Then, submit the repair expense cost for reimbursement.
|
||||
|
||||
* __What happens if my services agreement with Status finishes?__
|
||||
|
||||
Please check out [this guide](../offboarding/device-logistics.md) for your options on recycling or buying back devices.
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# 🚀 Contributing to this guide
|
||||
|
||||
Status' Contributors Guide is an open living repo built for you. The truth is, Status evolves faster than it can keep the documentation updated. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit.
|
||||
The Contributors Guide is an open living repo built for you. The truth is, the organisation evolves faster than it can keep the documentation updated. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit.
|
||||
|
||||
Here you'll find helpful guidelines on how to contribute to this guide and make it yours!
|
||||
|
||||
_Note: You can start contributing only once access to status-im organization is provided to you by people-ops. Prior to that, the github link will not be working._
|
||||
_Note: You can start contributing only once access to the organisation is provided to you by people-ops. Prior to that, the github link will not be working._
|
||||
|
||||
## 👾 Contributing with pull requests
|
||||
|
||||
Whether you'd like to fix typos, update information, add sections, or build new content, you can create a pull request to contribute to the guide.
|
||||
|
||||
Our current workflow has two main branches: `master` that deploys to `[contributors.status.im](https://contributors.status.im)` and `develop` that deploys to `[dev-contributors.status.im](https://dev-contributors.status.im)`.
|
||||
Our current workflow has two main branches: `master` that deploys to `[contributors.free.technology](https://contributors.free.technology)` and `develop` that deploys to `[dev-contributors.free.technology](https://dev-contributors.free.technology)`.
|
||||
|
||||
Before creating a pull request, create a new branch from `develop` and commit your changes to one or multiple PRs. Once finished, assign someone from the People Ops team to review or comment on it. Once merged, we'll delete the branch, and you'll see your contributions on this handbook!
|
||||
|
||||
@@ -20,7 +20,7 @@ Issues open a world of possibilities: from proposing changes to simply dropping
|
||||
|
||||
There are a few ways to create an issue:
|
||||
|
||||
* Go to the `issues` tab in the Status Contributor guide repo and create one.
|
||||
* Go to the `issues` tab in the Contributor guide repo and create one.
|
||||
* From the source code of a file, click the `+` sign at the beginning of a line.
|
||||
* From a comment from a pull request, click `reference in new issue`.
|
||||
|
||||
|
||||
@@ -2,118 +2,134 @@
|
||||
|
||||
## 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:
|
||||
* [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)
|
||||
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-ift/laptops-and-devices.md)
|
||||
* [Events and meetups](../contributing-to-ift/events-and-meetups.md)
|
||||
* [Travelling for IFT](../contributing-to-ift/travelling-for-IFT.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.
|
||||
In order to get your expenses reimbursed correctly and in time:
|
||||
- ensure that your purchase or travel request in [SpiffWorkflow](https://prod.mod.spiff.status.im/) gets approved before you purchase goods or services
|
||||
- after the purchase or travel, submit the expense receipts to [Expensify](https://www.expensify.com/)
|
||||
- add these expenses to your monthly invoice sent to `billing@status.im`
|
||||
It's essential that you carefully read the following instructions to get reimbursed so we can file expenses correctly.
|
||||
To get your expenses reimbursed correctly and on time:
|
||||
- Ensure that you get your purchase or travel request approved by your budget owner via Discord, email, or other means of communication.
|
||||
- After the purchase or travel, submit the expense receipts to [Expensify](https://www.expensify.com/)
|
||||
- Add these expenses to your monthly invoice sent to `billing@status.im`
|
||||
|
||||
In addition to these notes, you can find a guide [here](https://docs.google.com/document/d/1UX9uizHnJDXZjghiXiBGUexrQxxaiyv3-KpyKfHYJKU/edit#) and you can also view our video walkthrough [here](https://youtu.be/04YB_Xz48E8).
|
||||
|
||||
## 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. Please note that this guide is based on the current version of Expensify and not the new Expensify experience.
|
||||
|
||||
### Account setup
|
||||
|
||||
You'll need to head to the [Expensify](https://www.expensify.com/) web or download the mobile app and sign in using your Status email to get started. Please input your full name as it appears in your BambooHR profile when setting up your Expensify account.
|
||||
You'll need to head to the [Expensify](https://www.expensify.com/) web or download the mobile app and sign in using your Status (@status.im) email to get started. Please input your full name as it appears in your BambooHR profile when setting up your Expensify account.
|
||||
|
||||
If you don’t have access to your account, please reach out to the Finance team to create or update your account.
|
||||
|
||||
|
||||
### 1. Log into Expensify.com
|
||||
|
||||

|
||||
|
||||
### Selecting the right policy
|
||||
If you don’t have access to your account, message us on our `#finance` channel to create or update your account.
|
||||
Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct project for example "IFT - Finance" or "Status-Mobile"
|
||||
|
||||
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.
|
||||

|
||||
|
||||

|
||||
### 2. Go to Reports
|
||||
|
||||
### Uploading expenses
|
||||
Please use the ‘Reports’ tab instead of the ‘Expenses’ tab as this will allow you to submit multiple claims together. This makes it easier for you and Finance to approve and track your expense claims.
|
||||
|
||||
We kindly ask you to upload expenses as they incur or by the end of a trip to avoid complications like old or lost receipts.
|
||||

|
||||
|
||||
Go to the `Expense` tab on either the web or mobile apps to upload expenses manually or by scanning them:
|
||||
### 3. New Report
|
||||
|
||||

|
||||
Create a new report for your expenses. One report can include multiple expenses hence it is important for you to submit this as a report and not as an individual expense claim.
|
||||
|
||||
1. Make sure to fill or review all the fields as the scanning feature isn't always reliable. Pay special attention to amounts and currencies.
|
||||
2. You should claim expenses using the date they incurred. For example: if the purchase happened on Jan 10th and you're uploading or requesting the reimbursement on Jan 14th, the correct expense date would be Jan 10th.
|
||||
3. When paying for a group (i.e., a meal shared with other contributors from Status), please list all those in attendance in the `attendee's` field.
|
||||
4. Choose a category for your expense and add a detailed description of how's it business-related. Include information such as the trip it belongs to, who approved it, what budget it comes from, whether or not you've paid for other contributors (i.e., group meal), and any other data you consider relevant.
|
||||

|
||||
|
||||
#### Example
|
||||
* Project Event Expense
|
||||
* Category: Events
|
||||
* Description: "Devcon Conference, Berlin - Taxi from LHR airport to conference with 1 other project member, Joe"
|
||||
|
||||
* Another project Event Expense
|
||||
* Category: Meals & Drinks
|
||||
* Description: "People Ops Meetup - Evening meal on May 26th with 3 others: John, Jane, Joseph"
|
||||
### 4. Add Expenses
|
||||
Click ‘Add Expenses’ to start adding claims to your report.
|
||||
|
||||

|
||||

|
||||
|
||||
5. If it's your first expense of the month, create a new report for all costs incurred during that period. Otherwise, add it to an existing one.
|
||||
6. We suggest submitting an expense reimbursement report only when the total value is above USD 50.
|
||||
7. You **must** submit expenses as an expense report. An invoice with the amounts will not suffice for reimbursement.
|
||||
|
||||

|
||||
### 5. New Expense
|
||||
Create a new expense. Do not use previously created expenses from the available list. It’s important to create a new expense even for recurring expenses as we need up-to-date information for each claim. Any outdated expense claims will be rejected.
|
||||
|
||||
> ⚠️ You **always need to submit a receipt with each expense you log.** Make sure to take photos or keep digital receipts handy - missing receipts might result in your reimbursements not being approved. We understand that in some rare cases, this is not possible. When not possible, please provide as much info as possible and why no receipt is possible.
|
||||

|
||||
|
||||
### Submitting an expense report for approval
|
||||
|
||||
Uploading expenses and submitting an expense report are different actions within Expensify. Once you've uploaded all your receipts, it's fundamental that you submit the report for Finance's review and approval.
|
||||
### 6. Fill in the expense claim
|
||||
|
||||
Finance checks the submitted expenses against your purchase/travel requests raised in [SpiffWorkflow](https://prod.mod.spiff.status.im/), and if the expenses follow the approved by Project Leads amounts, no additional approval will be required.
|
||||
<b> It is mandatory to complete all of these fields according to the requirements below! Please ensure that you complete a separate claim for each expense. Joint expenses will be rejected and will require 2nd submission. </b>
|
||||
|
||||
<i> Merchant (Field 1) </i> - The name of the company/brand/service provider used for the expense claim
|
||||
|
||||
You must submit the expense report and get it approved before being able to include it in your invoice. To do that, click the `Reports` tab and `Submit` your report.
|
||||
<i> Date (Field 2) </i> - Date when the expense took place. This needs to match the date that is on the expense invoice/receipt which you will attach in ‘Field 8’
|
||||
|
||||
> ⚠️ Only **approved** expense reports should be included in the monthly contributor invoice.
|
||||
<i> Total (Field 3) </i> - Either the total amount spent or the maximum allowable amount per claim (e.g. for coworking or hardware expenses). If you are claiming the expense in full, please record the exact amount as seen on the invoice/receipt which you will attach in ‘Field 8’
|
||||
|
||||

|
||||
<i> Currency (Field 4) </i> - Choose the same currency as on the receipt/invoice of your expense (shown in ‘Field 8’). Expensify will automatically calculate the correct exchange rate for your invoicing currency.
|
||||
|
||||
Please follow these links if you need help with [creating expenses](https://community.expensify.com/discussion/4560/how-to-create-expenses-manually) and [submitting reports](https://community.expensify.com/discussion/4561/how-to-submit-a-report/p1?new=1) on Expensify. If you need further help, reach out to the Finance team, and we'll be able to guide you through the process.
|
||||
<i> Category (Field 5) </i> - Choose the category of your expenses (e.g Hardware, Travel…)
|
||||
|
||||
### Adding the expenses to your monthly invoice
|
||||
<i> Attendees (Field 6) </i> - If this is your own expense, then please leave it as it is; however, if you attend a team meal and you paid for everyone else’s meal as well, please tag them in the attendee's fees as this expense covers multiple contributors.
|
||||
|
||||
The finished and approved report from Expensify will show the total for each expense category. For example, if you have several costs in one category, Expensify will show the following:
|
||||
<i> Description (Field 7) </i> - Please specify the event you are attending and the reason/additional information for the expenses. This is an important field and will enable us to track event spending.
|
||||
|
||||

|
||||
<i> Document (Field 8) </i> - attach an invoice/receipt that proves your expense claim and confirms the details shown in fields 1-7.
|
||||
|
||||
Your invoice should only contain the total per category, not each expense item.
|
||||
<i> Events (Field 9) </i> - for all travel expenses select the event you are attending. If the event you are going to is not available, please message us on our Discord #ask-finance channel.
|
||||
|
||||

|
||||
|
||||
### 7. If you have multiple expense claims repeat steps 4 - 6.
|
||||
|
||||
### 8. Submit Expense Report
|
||||
|
||||
8.1 Click ‘Submit’
|
||||
8.2 Check you are submitting to your correct <b> budget owner </b>
|
||||
8.3 Your approval will be sent to the budget owner for review and approval. Once it is approved, you will be able to add it to your monthly contributor invoice.
|
||||
8.4 Submit the report
|
||||
|
||||

|
||||
|
||||
|
||||
### 9. Adding expenses to your monthly contributor invoice
|
||||
|
||||
Your final expense report will be presented in USD so please convert this to your invoicing currency. Please use the FX rates available on https://www.xe.com/currencytables/
|
||||
|
||||
Only approved expenses should be included on your monthly invoice. If your expense has not been approved, it is the Budget Owner who will need to do this before Finance can reimburse your expenses.
|
||||
|
||||
Ensure that each Category of expense is recorded as a separate item on a separate line. For example, all hardware expenses can be recorded together on your monthly invoice however, travel expenses would require a separate line/item for each category of travel expenses (Flights/accommodation/meals, etc). For travel and event expenses, please state the event on your invoice.
|
||||
|
||||
As guidance, we have added these categories in the invoice template [here](https://docs.google.com/spreadsheets/d/1B3x3vNVFHB8S9r0ylFLTugH9iTHpyx52/edit?usp=sharing&ouid=112284182777623149574&rtpof=true&sd=true). Please, ensure your invoice has the same category names as the Expensify reports to avoid delays with the expense claim approval.
|
||||
|
||||
Your expenses claimed on Expensify <b>must</b> match the expenses claimed on your monthly invoice. An example of this is shown below:
|
||||
|
||||

|
||||
|
||||
<b> If you have any questions about the process, feel free to post a question on Discord in the `#finance` channel. </b>
|
||||
|
||||
As guidance, we have added these categories in the invoice template here. Please, ensure your invoice has the same category names as the Expensify reports to avoid delays with the expense claim approval.
|
||||
|
||||
If you would like to set up these categories in your accounting software, please ask the Finance team for the complete list of expense categories.
|
||||
|
||||
If you need to share the report with your accountant, you can download a PDF report with your expenses by clicking on the top right corner and then on the `Download` icon:
|
||||
|
||||

|
||||
|
||||

|
||||
If you need to share the report with your accountant, you can download a PDF report with your expenses by clicking on the top right corner and then on the `Download` icon.
|
||||
|
||||
## When are you getting reimbursed
|
||||
|
||||
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 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.
|
||||
|
||||
Example Scenarios:
|
||||
### Example Scenarios:
|
||||
|
||||
Scenario 1:David submits an invoice on the 16th February. This invoice was received after the payment cut-off date for February, so it will be paid in the following payment run.
|
||||
Scenario 1:David submits an invoice on the 16th of February. This invoice was received after the payment cut-off date for February, so it will be paid in the following payment run.
|
||||
|
||||
Scenario 2: David submits an invoice on the 14th February, and he includes an expense claim that shows as not approved in Expensify. The Finance team will reach out to David, to amend the invoice. If the invoice is not amended on time before the payment cut-off date, it will not be included in the payment run.
|
||||
|
||||
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`.
|
||||
Scenario 2: David submits an invoice on the 14th of February, and he includes an expense claim that shows as not approved in Expensify. The Finance team will reach out to David, to amend the invoice. If the invoice is not amended on time before the payment cut-off date, it will not be included in the payment run.
|
||||
|
||||
Scenario 3: David submits an invoice on the 15th of 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 `#finance` channel or through an email to `billing@status.im`.
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
# 💰 Getting paid
|
||||
|
||||
As a core contributor, you need to send your PDF invoice to the Billing inbox (billing@status.im). Here you'll find helpful information about deadlines, formats and other requirements to get compensated correctly on time.
|
||||
As a core contributor and those with services agreements with IFT, you'll need to send your PDF invoice to the Billing inbox (billing@status.im). Here, you'll find helpful information about deadlines, formats and other requirements to ensure your invoices are processed correctly and you receive timely payment.
|
||||
|
||||
## Invoices due date
|
||||
|
||||
Send your invoice in a PDF format to (billing@status.im), latest on the 15th of every month. Your invoicing period is the current calendar month (i.e., invoice by October 15 for your services from 1 - 31 October).
|
||||
Send your invoice in a PDF format to (`billing@status.im`), **latest on the 15th of every month**. Your invoicing period is the current calendar month (i.e., invoice by October 15 for your services from 1 - 31 October).
|
||||
|
||||
## What to include
|
||||
|
||||
@@ -12,12 +12,12 @@ You need to include your total approved expenses per category in your invoice (a
|
||||
|
||||

|
||||
|
||||
Your invoice should include:
|
||||
Your invoice must include:
|
||||
|
||||
* Your legal name (or legal entity) and address as per your agreement.
|
||||
* A unique invoice number (this number should be sequential based on your invoice numbering, if you have any questions, please reach out to the Finance and Accounting team, or your accountant, if you have one).
|
||||
* The date the invoice is issued.
|
||||
* Payment due date.
|
||||
* Status legal entity with which you have the services agreement.
|
||||
* The payment due date.
|
||||
* The date range of the invoicing period according to your agreement (i.e., "March 1 to March 31").
|
||||
* Description of the service rendered or reference to your contract.
|
||||
* Total approved expense reimbursements per category as per the [expense reimbursements guide](../finance/expense-reimbursements.md/).
|
||||
@@ -28,10 +28,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:
|
||||
* 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
|
||||
Address the invoice to **IFT Studio Pte. Ltd, 160 Robinson Road, #24-09, Singapore 068914.**
|
||||
|
||||
There are exceptional cases where another legal entity applies. Please use the company and address as detailed in your agreement.
|
||||
|
||||
@@ -39,7 +36,7 @@ There are exceptional cases where another legal entity applies. Please use the c
|
||||
|
||||
### Bank and Wallet details
|
||||
|
||||
Please maintain your details on your BambooHR profile if you have one. For simplicity, we only allow the indication of one wallet and one bank account (if you have intermediary accounts, please use the appropriate fields of the Bank Information section). You can edit it directly if you want to change the % paid in ETH, DAI, or SNT. Once you save it, BambooHR will send an approval request to the Finance team —the reason is so that we get a notification that something has changed and can update our payment records timely.
|
||||
Please maintain your details on your BambooHR profile if you have one. For simplicity, we only allow the indication of one wallet and one bank account (if you have intermediary accounts, please use the appropriate fields of the Bank Information section). You can edit it directly if you want to change the % paid in ETH, DAI, or SNT. Once you save it, BambooHR will send an approval request to the Finance team. The reason for this approval step is so that the Finance team get a notification that something has changed and can ensure we're using the correct payment details in subsequent payment runs.
|
||||
|
||||
Only after we confirm the approval, will your changes be reflected in your BambooHR profile. If you need to change your bank details or payment preference, any pending changes will need to be approved first, in order for you to be able to make a new change.
|
||||
|
||||
@@ -55,7 +52,7 @@ If you are new to crypto payments and wallets, [this guide](https://support.mycr
|
||||
|
||||
We recommend using a hardware wallet like the Ledger Nano S or a Trezor to secure your assets.
|
||||
|
||||
Don't be shy to ask your more experienced core contributors in the #ask-finance channel when you have questions about crypto payments and wallets. Not everyone starts with the same level of knowledge, and building it up is part of working with Status.
|
||||
Don't be shy to ask your more experienced core contributors in the `#finance` channel on logos discord or Status app when you have questions about crypto payments and wallets. Not everyone starts with the same level of knowledge, and building it up is part of working with IFT.
|
||||
|
||||
### Rate Calculation
|
||||
|
||||
@@ -64,52 +61,28 @@ For determining rates when paying in crypto, we establish the following two rate
|
||||
* The average closing rate across the last five days of the invoiced period, OR
|
||||
* The current rate when payments are being issued.
|
||||
|
||||
You can change your crypto split % preference monthly. Just make sure you update your preferences before the 15th of each month.
|
||||
You can change your crypto split % preference monthly. Just make sure you update your preferences in BambooHR before the 15th of each month.
|
||||
|
||||
## Special situations
|
||||
|
||||
### December pay
|
||||
|
||||
As the holiday season affects the regular working days, we might bring forward the December payment run. Please be aware of date changes for the December payment run.
|
||||
Due to operational considerations in December, we might bring forward the December payment run. Please be aware of date changes for the December payment run.
|
||||
|
||||
### Hourly rate contributors
|
||||
|
||||
If you're paid on an hourly basis and need to estimate your hours in the remainder of the month and reconcile them in the next invoice (as you'll be invoicing by the 15th of each month), it's ok to do that, or you could carry forward actual hours to your next invoice.
|
||||
|
||||
If your fees have been agreed on an hourly rate basis, our monthly cap for hours billed is the lower of either the amount specified in your agreement with us or the number of business days in the month x 8.5 hours per day, i.e.:
|
||||
|
||||
A month with 23 workdays has an hourly billing cap of 23 * 8.5 hours = 195.5 hours.
|
||||
If your fees have been agreed on an hourly rate basis, the monthly cap for hours billed is the fee equivalent to a monthly amount (or the calculated monthly equivalent) specified in your agreement with IFT.
|
||||
|
||||
Please discuss with People Ops if you intend to bill over this amount.
|
||||
|
||||
### Pro-rating the first month
|
||||
### During your first month
|
||||
|
||||
For your first month (if being paid on an annual or monthly basis), please prorate the amount in your invoice to reflect the number of days from the beginning of your contract to the last day of the month.
|
||||
For your first month (if your Fee is stated as a (maximum) annual or monthly amount), please only state the amount in your invoice to reflect the period of time you actually contributed.
|
||||
|
||||
*Example: If March has 22 working days (counting Mon-Fri) and you started on a Monday, March 12, your monthly invoice amount will be {your monthly fee amount}/22 x 15.*
|
||||
*Example: If after you started providing your services, you contributed 10 (ten) days in March, your monthly invoice amount will be {your monthly fee amount}/30 x 10.*
|
||||
|
||||
Please bill the flat monthly or annual/12 figure for each subsequent month.
|
||||
|
||||
*Example: You joined Status on March 12. During April, you took 1 week of vacation. Your April invoice amount will be {your monthly stipend amount in full} or {your annual stipend amount}/12*
|
||||
|
||||
Please use the working days shown below for your calculations:
|
||||
|
||||
**Working days 2023**
|
||||
|
||||
| Month | Working days |
|
||||
|:---:|:---:|
|
||||
| January | 23 |
|
||||
| February | 21 |
|
||||
| March | 21 |
|
||||
| April | 22 |
|
||||
| May | 23 |
|
||||
| June | 20 |
|
||||
| July | 23 |
|
||||
| August | 22 |
|
||||
| September | 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
|
||||
|
||||
|
||||
@@ -2,18 +2,18 @@
|
||||
|
||||
## 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.
|
||||
* 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 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);
|
||||
#### 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 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;
|
||||
* 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.
|
||||
@@ -27,5 +27,5 @@
|
||||
|
||||
## 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
|
||||
* 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
|
||||
|
||||
@@ -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.*
|
||||
|
||||
@@ -2,39 +2,25 @@
|
||||
|
||||
This Privacy Notice is effective as of February 2022.
|
||||
|
||||
This Privacy Notice refers to our commitment to treat all Personal Data (as defined below) of the
|
||||
relevant individuals, including contractors, employees and candidates for any such roles at Status
|
||||
(“Data Subjects”), with the utmost care and confidentiality.
|
||||
This Privacy Notice refers to our commitment to treat all Personal Data (as defined below) of the relevant individuals, including contractors, and Provider’s Workers providing services to the Beneficiary (“Data Subjects”), with the utmost care and confidentiality.
|
||||
|
||||
With this Privacy Notice, we ensure that we gather, store, protect and handle Personal Data
|
||||
fairly, transparently and with respect towards individual rights, even after the termination of the
|
||||
contractual relationship with Status, where applicable.
|
||||
With this Privacy Notice, we ensure that we gather, store, protect and handle Personal Data fairly, transparently and with respect towards individual rights, even after the termination of the contractual relationship with the Beneficiary, where applicable.
|
||||
|
||||
As can be seen from our [principles](https://our.status.im/our-principles/), we take privacy and
|
||||
transparency seriously. We process Personal Data lawfully, fairly, securely and in a transparent
|
||||
manner. We only collect and process Personal Data that is adequate, relevant and limited to what
|
||||
is necessary for specified, explicit and legitimate purposes and we do not further process such
|
||||
Personal Data in a manner that is incompatible with those purposes. We keep Personal Data
|
||||
accurate and up to date and keep it in a form which permits identification of Data Subjects for no
|
||||
longer than is necessary.
|
||||
We process Personal Data lawfully, fairly, securely and in a transparent manner. We only collect and process Personal Data that is adequate, relevant and limited to what is necessary for specified, explicit and legitimate purposes and we do not further process such Personal Data in a manner that is incompatible with those purposes. We keep Personal Data accurate and up to date and keep it in a form which permits identification of Data Subjects for no longer than is necessary.
|
||||
|
||||
This Privacy Notice is issued by the Company, to explain how we process Personal Data before,
|
||||
during and after any contractual relationship with us and in connection with affiliation with us.
|
||||
We process Personal Data, in accordance with the applicable data protection laws, including the
|
||||
EU General Data Protection Regulation 2016/679 (the “GDPR”) where applicable. The
|
||||
Company is the entity that is considered the controller with respect to Personal Data processed
|
||||
by us.
|
||||
This Privacy Notice is issued by the Beneficiary, to explain how we process Personal Data before, during and after any contractual relationship with us and in connection with affiliation with us. We process Personal Data, in accordance with the applicable data protection laws, including the EU General Data Protection Regulation 2016/679 (the “GDPR”) where applicable. The Beneficiary is the entity that is considered the controller with respect to Personal Data processed by us.
|
||||
|
||||
In this Privacy Notice where we refer to "Status", "we" or "us", we mean the Company.
|
||||
|
||||
In this Privacy Notice where we refer to "we" or "us", we mean the Beneficiary.
|
||||
|
||||
## What data do we collect?
|
||||
Status will process certain Personal Data related to Data Subjects. "Personal Data" means any
|
||||
The Beneficiary will process certain Personal Data related to Data Subjects. "Personal Data" means any
|
||||
information relating to an individual and processed by us, including any information through
|
||||
which an individual can be identified or identifiable, directly or indirectly, which may include:
|
||||
|
||||
* Contact and general information, such as name, surname, postal and/or email address,
|
||||
phone number, date of birth, gender, marital status, and photo (if such is provided to us).
|
||||
* A resume and any other information required to apply for the role at Status.
|
||||
* A resume and any other information required to apply for the role with the Beneficiary.
|
||||
* Professional information, such as education credentials and professional experience and
|
||||
qualifications, professional networks, training employment history, board memberships
|
||||
and employment status.
|
||||
@@ -51,21 +37,10 @@ details of periods of leave taken, and notes of relevant discussions as applicab
|
||||
endeavour to maintain accurate information.
|
||||
|
||||
## How do we collect Personal Data?
|
||||
Sometimes individuals directly provide us with most of their Personal Data we process. We
|
||||
collect and process Personal Data when someone registers online, or applies for a position
|
||||
through any online site where Status posts a new role and when they enter into a contractual
|
||||
relationship with us. Sometimes we will obtain Personal Data from alternative sources, including
|
||||
but not limited to: other affiliates and service providers (such as recruitment agents and
|
||||
background checking services to the extent permitted by applicable law) and government bodies
|
||||
where required by law (such as tax authorities). If the requested information is not provided, we
|
||||
may be unable to conduct certain business operations or comply with the applicable legislation.
|
||||
We may also receive Personal Data indirectly from sources such as Greenhouse, Callstack or
|
||||
others.
|
||||
Sometimes individuals directly provide us with most of their Personal Data we process. We collect and process Personal Data when someone registers online or applies for a position through any online site where the Beneficiary posts a new role and when they enter into a contractual relationship with us. Sometimes we will obtain Personal Data from alternative sources, including but not limited to: other affiliates and service providers (such as recruitment agents and background checking services to the extent permitted by applicable law) and government bodies where required by law (such as tax authorities). If the requested information is not provided, we may be unable to conduct certain business operations or comply with the applicable legislation. We may also receive Personal Data indirectly from sources such as Greenhouse, or others.
|
||||
|
||||
Exceptionally, we might process sensitive information and only for limited and strictly defined purposes, such as equal opportunities monitoring and diversity monitoring and initiatives may involve us using race or ethnicity data such as information contained in the passport or other citizenship document.
|
||||
|
||||
Exceptionally, we might process sensitive information and only for limited and strictly defined
|
||||
purposes, such as equal opportunities monitoring and diversity monitoring and initiatives may
|
||||
involve us using race or ethnicity data such as information contained in the passport or other
|
||||
citizenship document.
|
||||
|
||||
## How will we use Personal Data?
|
||||
We will process Personal Data for the following purposes:
|
||||
@@ -80,13 +55,7 @@ of Personal Data.
|
||||
Where relevant, we will only process Personal Data with an express prior consent of the Data
|
||||
Subjects.
|
||||
|
||||
We store most of Personal Data in our internal systems. We keep some data in a secure Google
|
||||
Drive folder. Between Status entities we only grant access to Personal Data on a need-to-know
|
||||
basis, necessary for the purposes for which such access is granted. In some cases, Status uses
|
||||
third parties located in various countries to collect, use, analyse, and otherwise process Personal
|
||||
Data on its behalf. We tightly control access to the data to only members of the organisation that
|
||||
have a valid reason to access the information (generally - Legal, People Ops, Talent, Finance and
|
||||
the Status founders).
|
||||
We store most of Personal Data in our internal systems. We keep some data in a secure Google Drive folder. Between affiliates of the Beneficiary we only grant access to Personal Data on a need-to-know basis, necessary for the purposes for which such access is granted. In some cases, the Beneficiary uses third parties located in various countries to collect, use, analyse, and otherwise process Personal Data on its behalf. We tightly control access to the data to only members of the organisation that have a valid reason to access the information (generally - Legal, People Ops and Finance).
|
||||
|
||||
We maintain records of processing of Personal Data in accordance with the applicable laws,
|
||||
including obligations established by the GDPR.
|
||||
@@ -130,22 +99,16 @@ We may share the minimum necessary amounts of Personal Data with the following t
|
||||
partners as required and applicable for statutory filings, benefits, and reporting, these include:
|
||||
|
||||
1. Greenhouse
|
||||
2. Odiin LTD
|
||||
2. Juro Online Limited
|
||||
3. Google LLC
|
||||
4. Bamboo HR LLC
|
||||
5. Juro Online Limited
|
||||
6. Greenhouse Software, Inc.
|
||||
|
||||
|
||||
There might be other third-party providers we will use in the future. If necessary, we will request
|
||||
the relevant Data Subjects’ permission before releasing Personal Data to any other third-party.
|
||||
|
||||
## How do we secure Personal Data?
|
||||
Status takes the protection of Personal Data seriously and we intend to protect Personal Data and
|
||||
to maintain its accuracy. We process Personal Data in a manner that ensures such data undergoes
|
||||
appropriate security (including protection against unauthorised or unlawful processing and
|
||||
against accidental loss, destruction damage, unauthorised access, use and disclosure etc.) using
|
||||
appropriate technical or organisational measures to achieve this. We also require that our
|
||||
suppliers and providers protect such information from unauthorised access, use and disclosure.
|
||||
The Beneficiary takes the protection of Personal Data seriously and we intend to protect Personal Data and to maintain its accuracy. We process Personal Data in a manner that ensures such data undergoes appropriate security (including protection against unauthorised or unlawful processing and against accidental loss, destruction damage, unauthorised access, use and disclosure etc.) using appropriate technical or organisational measures to achieve this. We also require that our suppliers and providers protect such information from unauthorised access, use and disclosure.
|
||||
|
||||
## How long will we store Personal Data?
|
||||
We will not retain Personal Data longer than necessary to fulfil the purposes for which it is
|
||||
@@ -185,24 +148,17 @@ subject to a decision based solely on automated processing, including profiling,
|
||||
legal effects concerning individuals or similarly significantly affecting them.
|
||||
|
||||
The additional rights pursuant to local laws applicable to the processing of Personal Data.
|
||||
For more information on how to exercise any of these rights, please contact us at email people-
|
||||
ops@status.im. After receiving a request, we have one month to respond.
|
||||
|
||||
For more information on how to exercise any of these rights, please contact us at email legal@free.technology.
|
||||
After receiving a request, we have one month to respond.
|
||||
|
||||
## How to lodge a complaint?
|
||||
In the event anyone considers our processing of their Personal Data not to be compliant with the
|
||||
applicable data protection laws, a complaint can be lodged directly with Status by contacting us
|
||||
via legal@status.im or with the competent data protection authority. The name and contact
|
||||
details of the Data Protection Authorities in the European Union can be found at:
|
||||
In the event anyone considers our processing of their Personal Data not to be compliant with the applicable data protection laws, a complaint can be lodged directly with the Beneficiary by contacting us via legal@free.technology or with the competent data protection authority. The name and contact details of the Data Protection Authorities in the European Union can be found at:
|
||||
|
||||
http://ec.europa.eu/justice/data-protection/article-29/structure/data-protection-
|
||||
authorities/index_en.htm.
|
||||
http://ec.europa.eu/justice/data-protection/article-29/structure/data-protection-authorities/index_en.htm.
|
||||
|
||||
In case of breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise processed, we have the mechanisms and policies in place in order to identify it and assess the details of the breach promptly. Depending on the outcome of our assessment, we will make the necessary notifications to the supervisory authorities and communications to the affected Data Subjects.
|
||||
|
||||
In case of breach of security leading to the accidental or unlawful destruction, loss, alteration,
|
||||
unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise
|
||||
processed, we have the mechanisms and policies in place in order to identify it and assess the
|
||||
details of the breach promptly. Depending on the outcome of our assessment, we will make the
|
||||
necessary notifications to the supervisory authorities and communications to the affected Data
|
||||
Subjects.
|
||||
|
||||
## Changes to Privacy Notice
|
||||
We may occasionally make changes to this Privacy Notice, as well as any other specific privacy
|
||||
@@ -213,5 +169,4 @@ believe are significant, we will inform the relevant Data Subjects and seek the
|
||||
consent where applicable.
|
||||
|
||||
## How to contact us?
|
||||
In case of any questions related to this Privacy Notice, don't hesitate to contact us via email at
|
||||
people-ops@status.im.
|
||||
In case of any questions related to this Privacy Notice, don't hesitate to contact us via email at legal@free.technology
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -4,9 +4,9 @@ We encourage using some time to learn about things related to your tasks and our
|
||||
|
||||
We offer an annual learning budget of USD 170 for each core contributor. You can use this budget towards things like books, conferences, or online courses.
|
||||
|
||||
For the purpose of purchasing learning & development items (learning platforms, courses, online conferences), you need to raise the request via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a) to get okays from your Project Lead and/or PeopleOps partner.
|
||||
For the purpose of purchasing learning & development items (learning platforms, courses, online conferences), you need to get approval from your Project Lead and/or PeopleOps partner.
|
||||
|
||||
If you need a reference, a core contributor could spend their first 1-3 weeks spending 50% of their billed hours to learn and ~2 hours p/w after that on an ongoing basis. This is just an example, and we encourage you to figure out a learning cadence that best helps you succeed in contributing to Status.
|
||||
If you need a reference, a core contributor could spend their first 1-3 weeks spending 50% of their billed hours to learn and ~2 hours p/w after that on an ongoing basis. This is just an example, and we encourage you to figure out a learning cadence that best helps you succeed in contributing to IFT.
|
||||
|
||||
We've made a selection of readings that can help give you more context of our vision and culture.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -13,7 +13,7 @@ Here you'll find helpful links to resources to protect yourself and the organisa
|
||||
|
||||
Above all else, never be afraid to ask for help, ask questions, or report security concerns. Until we have an official infrastructure for support tickets, drop by:
|
||||
|
||||
* #security for more broad, public questions, or
|
||||
* [#security](https://discord.com/channels/973324189794697286/1078729684168233090) for more broad, public questions, or
|
||||
* Drop an email to `security@status.im`.
|
||||
|
||||
All contributors with an onboarding process will have a security touchpoint with the security team during the first month of their onboarding.
|
||||
@@ -28,21 +28,31 @@ Phishing attacks are the most common: discord bots, telegram messages, and email
|
||||
|
||||
## Hardware
|
||||
|
||||
Check out this [list](https://notes.status.im/zkr20eWFTwGD92xixGX2CA) of essential hardware. Core contributors can expense hardware security keys (yubikeys) and should be used for Github, Gsuite, and Bitwarden.
|
||||
Here's a list of recommended hardware for protecting accounts, crypto assets, and data:
|
||||
|
||||
* Security Keys (e.g., YubiKey, Google Titan, OnlyKey) – Provides phishing-resistant 2FA login, useful against remote attacks and credential leaks.
|
||||
* Hardware Crypto Wallets (e.g., Ledger, Trezor, Coldcard) – Stores private keys offline.
|
||||
* Encrypted External Storage (e.g., IronKey) – Secures private key backups and sensitive data with hardware encryption for added protection.
|
||||
* Privacy-Focused Phone (e.g., GrapheneOS Pixel) – Enhances privacy and security with encrypted communication and minimal data tracking.
|
||||
* Faraday Bag (e.g., Mission Darkness) – Shields devices from remote hacking and tracking by blocking all wireless signals.
|
||||
|
||||
Core contributors can expense hardware security keys (yubikeys) and should be used for Github, Gsuite, and Bitwarden.
|
||||
|
||||
Here's Corey's Status Learn-Up session about [hardware wallets and best practices](https://www.youtube.com/watch?v=9nzqntuFR44&ab_channel=HashingItOut).
|
||||
|
||||
## Password manager
|
||||
|
||||
Our password manager is [Bitwarden](https://bitwarden.com/). All 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/)
|
||||
* [Notion Security homepage](https://www.notion.so/bee2c4d28567424fae21c3c97e733e46?v=fdc44ecba717474fae7ae65f3097b315)
|
||||
* [status-im/status-security](https://github.com/status-im/status-security)
|
||||
* [status-im/security-internal](https://github.com/status-im/security-internal)
|
||||
|
||||
|
||||
|
||||
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 175 KiB |
|
After Width: | Height: | Size: 461 KiB |
|
After Width: | Height: | Size: 188 KiB |
|
After Width: | Height: | Size: 396 KiB |
|
After Width: | Height: | Size: 187 KiB |
|
After Width: | Height: | Size: 54 KiB |
|
After Width: | Height: | Size: 65 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 33 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 40 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 41 KiB |
|
After Width: | Height: | Size: 66 KiB |
|
After Width: | Height: | Size: 183 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 46 KiB |
|
After Width: | Height: | Size: 135 KiB |
@@ -1 +0,0 @@
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
# 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.
|
||||
# 🚀 Introduction
|
||||
|
||||
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/)
|
||||
### Institute of Free Technology
|
||||
|
||||
### Contributing
|
||||
#### Fostering innovation, defending digital liberties
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
@@ -6,9 +6,9 @@ Once you have made a decision whether you are buying or returning your device, s
|
||||
|
||||
## Buying back your devices
|
||||
|
||||
The buyback value should be included on your last invoice to Status, and can be deduced from your last service fee. We're using a 36-month useful life formula for laptops and mobiles to calculate the buy back value:
|
||||
The buyback value should be included on your last invoice to IFT, and can be deduced from your last service fee. We're using a 36-month useful life formula for laptops and mobiles to calculate the buy back value:
|
||||
|
||||
purchase value - purchase value * contract duration / 36 months.
|
||||
Purchase value - purchase value * contract duration / 36 months.
|
||||
|
||||
| ❗Example |
|
||||
|:----------------------------------------|
|
||||
@@ -17,7 +17,7 @@ The buyback value should be included on your last invoice to Status, and can be
|
||||
| 2000 - (2000*23/36)|
|
||||
|
||||
|
||||
## Returning your devices back to Status
|
||||
## Returning your devices back to IFT
|
||||
|
||||
Your devices could still be used by someone else at Status so please check with your People Partner on how best to return your device prior to your last day.
|
||||
Your devices could still be used by someone else at IFT so please check with your People Partner on how best to return your device prior to your last day.
|
||||
|
||||
|
||||
@@ -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,11 +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 specific (i.e addresses to a specific person or organisation) 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.
|
||||
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.
|
||||
|
||||
@@ -83,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.
|
||||
|
||||
|
||||
@@ -1,21 +1,20 @@
|
||||
## 💥 Self Evaluation Guide
|
||||
|
||||
_This document is intended to be a supporting document to help you complete the 2023 lightweight Self Evaluation Process._
|
||||
_This document is intended to be a supporting document to help Core Contributors complete the 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.
|
||||
Think of a self-evaluation as an opportunity to reflect and deep dive into your contributions and impact on IFT’ 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.
|
||||
Try to be honest about your contributions and impact on IFT’ projects, especially in relation to how your contributions align with IFT’ 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>**
|
||||
@@ -1,12 +1,12 @@
|
||||
# 🔕 AFK FAQs
|
||||
|
||||
### 🏖️ How do public holidays work at Status?
|
||||
### 🏖️ How do public holidays work at IFT?
|
||||
|
||||
Given the diversity of cultures and locations among the core contributors at Status, we don't have Status-wide days off. We encourage you to book off your home or local public holidays or the ones close to your heart or beliefs.
|
||||
Given the diversity of cultures and locations among the core contributors at IFT, we don't have org-wide days off. We encourage you to book off your home or local public holidays or the ones close to your heart or beliefs.
|
||||
|
||||
### 😷 What happens if I'm out sick?
|
||||
|
||||
As a general guideline, short-term unavailability due to sickness that doesn't affect your capacity to meet your commitments are treated as regular time off and doesn't need further action than recording it in BambooHR.
|
||||
As a general guideline, short-term unavailability due to sickness that doesn't affect your capacity to meet your commitments doesn't need further action other than recording it in BambooHR.
|
||||
|
||||
If you’re going to be unavailable for a prolonged period of time, you need to coordinate with the project lead and your People Partner in order to review and adjust your service agreement accordingly.
|
||||
|
||||
@@ -14,7 +14,7 @@ If you’re going to be unavailable for a prolonged period of time, you need to
|
||||
|
||||
You can record your unavailability without explanation.
|
||||
|
||||
If you tell your People Partner about a health or personal issue, that information will be shared only within the People Ops group and to the extent required, Carl and Jarrad. Please, let your People Partner know of any specific discussion that should be kept off the record (i.e., only between you and the People Partner you're talking with).
|
||||
If you tell your People Partner about a health or personal issue, that information will be shared only within the People Ops group and to the extent required, Carl and Jarrad. Please let your People Partner know of any specific discussion that should be kept off the record (i.e., only between you and the People Partner you're talking with).
|
||||
|
||||
Your People Partner won't tell other core contributors the specifics of your situation. We will be happy to help you communicate your unavailability period if you need help doing that (mentioning that you are offline unwell, giving no further details).
|
||||
|
||||
@@ -22,11 +22,11 @@ Your People Partner won't tell other core contributors the specifics of your sit
|
||||
|
||||
#### 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:
|
||||
First of all, congratulations! 🎊 We're happy about the new addition(s) to your family! We understand the importance of family during this exciting time in your lives, and 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. In this regard, IFT 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.
|
||||
All core contributors who have passed their trial period 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.
|
||||
|
||||
@@ -43,22 +43,22 @@ The secondary caregiver is the person who takes on a supporting role in caregivi
|
||||
|
||||
#### 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.
|
||||
While traditional parental leave policies are not available to independent contractors, nonetheless, we wish to ensure that core contributors are able to immediately resume the provision of their services 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.
|
||||
We recognise, however, that the core contributor will incur certain costs and expenses during their unavailability to maintain a certain level of readiness and wish to compensate them to remain on standby. In this regard, we 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.
|
||||
We will make such payments in accordance with section 8 of this Contributor Guide. As indicated above, our 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, we are 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.
|
||||
We understand that a core contributor resuming their services to IFT 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.
|
||||
For this extended period of unavailability, we will not provide any additional standby compensation.
|
||||
|
||||
#### How do I make use of this arrangement?
|
||||
|
||||
@@ -68,7 +68,7 @@ We’ll further discuss the above arrangement with you, your period of unavailab
|
||||
|
||||
#### 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.
|
||||
At IFT, we are committed to supporting our core contributors who become new parents. We believe that creating this arrangement is essential to creating a supportive environment for contributors to thrive as well as the confidence that they can resume the provision of their services to IFT with the necessary readiness and capacity.
|
||||
|
||||
### 📒 What happens to any SNT distributions?
|
||||
|
||||
|
||||
@@ -2,130 +2,77 @@
|
||||
|
||||
## 📥 Downloading Status
|
||||
|
||||
First you will need to download the latest release of Status Desktop from [here](https://github.com/status-im/status-desktop/releases).
|
||||
First you will need to download the latest release of Status Desktop.
|
||||
|
||||
### On Windows:
|
||||
- Locate and double-click the .exe file. (It will usually be in your Downloads folder.)
|
||||
- Follow the instructions to install the software.
|
||||
|
||||
### On Linux
|
||||
- Extract the contents of the tarball with `tar –xvzf StatusIm-Desktop-<version>.tar.gz`
|
||||
- Run the extracted `StatusIm-Desktop-<version>.AppImage`
|
||||
|
||||
### On Mac:
|
||||
- Open Status.dmg
|
||||
- Copy Status.app to the Applications folder
|
||||
- You will need to "right click -> open" when running it for the first time (due to new Apple requirements for notarization). You may need to "right click -> open" twice.
|
||||
|
||||
It is strongly recommended that you follow the “I’m new to Status” path in the onboarding screens to generate a new seed phrase. After you have signed in for the first time, make sure you back up your seed phase securely. You can do this by clicking on the red 'back up seed phrase' banner that will appear at the top of the window.
|
||||
|
||||
If you use a seed phrase that you have previously used with Status, you are guaranteed to run into some known issues. It is recommend that you don't do this.
|
||||
Follow instructions for your OS:
|
||||
- [Download Status for Windows](https://status.app/help/getting-started/download-status-for-windows)
|
||||
- [Download Status for Mac](https://status.app/help/getting-started/download-status-for-mac)
|
||||
- [Download Status for Linux](https://status.app/help/getting-started/download-status-for-linux)
|
||||
|
||||
_Note: Status Desktop is currently in beta and meant for testing by core contributors only. It's not yet ready for real use and makes no claims of security or integrity of funds or data in these builds._ DO NOT USE IT TO STORE ANY ASSETS OF VALUE.
|
||||
|
||||
When you open Status Desktop for the first time or when you upgrade to 2.32, you’ll be prompted to “Help us improve Status”. This is the opt-in metrics we collect to know how users navigate.
|
||||
|
||||
Please decline by pressing “Do not share”
|
||||
|
||||
Follow [Run Status app for the first time](https://status.app/help/getting-started/run-the-status-app-for-the-first-time#run-the-status-app-for-the-first-time) and create a profile.
|
||||
|
||||
When choosing a username, it is recommended that you use the same username you are using in Discord / Github (this will make it easier for other CC’s to recognise you).
|
||||
|
||||
## 🤝 How to join the Status Internal community
|
||||
|
||||
1. Click the “Start chat” button
|
||||
1. Go in the Community Portal
|
||||

|
||||
|
||||

|
||||
2. Once the Status Community loads, click on its card (For any loading issues, restart the app)
|
||||

|
||||
|
||||
4. This will open the Status Community in spectator mode. You’ll be able to see some of the previous messages and any new messages coming in the public channels.
|
||||

|
||||
|
||||
2. This will open a view to start a new chat. Enter Iuri’s chat key into the “To:” field:
|
||||
5. Click the “Join Community” button on the top left.
|
||||

|
||||
|
||||
Iuri’s chat key - zQ3shdkzLTUx5s98XRXenEwPX56RhxGWjLnihcx79dhNai4wW
|
||||
6. This will open a dialogue that shows you a welcome message plus some rules you might need to follow within this community. Click the “Share all addresses to join” button. You can also customize which addresses you want to share. Those addresses are used to check if you have the required tokens to access the private channels. A TokenMaster (they are like admins) will also use that address to airdrop you those tokens:
|
||||

|
||||
|
||||

|
||||
7. You should be automatically added to the Community after a few minutes.
|
||||
|
||||
You will get access to the private channels once you receive the needed tokens, like the StatusCC token. People Ops will let the TokenMasters know that you joined and it should be done in the next days.
|
||||
|
||||
3. Status should recognize this key is Iuri’s and immediately open the "send contact request" dialog so you can send a contact request to him:
|
||||
You can still chat in the public channels with other contributors and community members.
|
||||
|
||||

|
||||
However, you are not done yet, there is one more thing we need to ask you to do.
|
||||
|
||||
7. Go to the “Settings” section in Status Desktop by clicking on the cog wheel in the left hand navigation bar:
|
||||

|
||||
|
||||
4. Send Iuri a nice message while you’re at it, something that will make him smile. Also let Iuri know you’re a new Status CC and mention your full name and the name of the team you have just joined. Click the “Send Contact Request” button to send the contact request.
|
||||
|
||||
|
||||
5. Iuri should have a pending contact request from yourself. You need to wait for Iuri to accept your request.
|
||||
|
||||
|
||||
6. Once Iuri has accepted your request (congrats, you’re now friends with Iuri), he will send you a link to Status Internal community (if you don’t receive this link, ping @helium__ on Discord).
|
||||
|
||||

|
||||
|
||||
|
||||
7. Click the “Go to Community” button:
|
||||
|
||||

|
||||
|
||||
|
||||
8. This will take you to the Status Internal community. Click the “Request to join” button:
|
||||
|
||||

|
||||
|
||||
|
||||
9. This will open a dialog that shows you a welcome message + some rules you might need to follow within this community. Check the “I agree with the above” box and click the “Request to join” button:
|
||||
|
||||

|
||||
|
||||
|
||||
10. You’ve just sent a request to join the community! Iuri has to manually approve your request, so depending on your waking hours and time zone, this request might be pending for a bit. (if your request to join is not accepted within 48hrs ping @helium on Discord).
|
||||
|
||||

|
||||
|
||||
|
||||
11. Once Iuri has accepted your request, the Status Internal community will automatically unlock and you’ll be able to chat with your dearest friends and colleagues using Status 🙂 But you are not done yet, there is one more thing we need to ask you to do.
|
||||
|
||||

|
||||
|
||||
|
||||
12. Go to the “Settings” section in Status Desktop by clicking on the cog wheel in the left hand navigation bar:
|
||||
|
||||

|
||||
|
||||
|
||||
13. Select “Advanced” in the settings menu:
|
||||
|
||||

|
||||
|
||||
|
||||
14. Scroll down until you see the “Telemetry” setting. Turn it on by clicking the toggle switch. This will open a dialog that asks you to confirm this action. Confirm this action.
|
||||
It’s really important that all CCs do this so that we can monitor Waku v2’s reliability as part of this dogfooding effort.
|
||||
|
||||

|
||||
9. Select “Advanced” in the settings menu
|
||||
|
||||
10. Scroll down until you see the “Debug” and “Telemetry” settings. Turn them on by clicking the toggle switches. This will open a dialog that asks you to confirm this action. Confirm this action. It’s really important that all CCs do this so that we can monitor Waku v2’s reliability as part of this dogfooding effort.
|
||||

|
||||
|
||||
15. Congrats, you are now a Status user, as well as a Status CC 🎉
|
||||
|
||||
Now let’s get this product polished to the point where we all enjoy using it - please report any bugs you encounter and suggest improvements or new features that you personally need. Instructions for this are below.
|
||||
|
||||
Also, don’t forget to read the list of “Known bugs” below, otherwise you won’t know about some important things you should or should not do with this release of Status Desktop, like not suspending your computer (because suspending your computer with Status running will result in missing messages).
|
||||
11. Congrats, you are now a Status user, as well as an IFT core contributor 🎉
|
||||
|
||||
Now let’s get this product polished to the point where we all enjoy using it - please report any bugs you encounter and suggest improvements or new features that you personally need. Instructions for this are below.
|
||||
|
||||
## 👋 Contact requests and ad-hoc group chat
|
||||
|
||||
Because Status is a fully p2p network that is not under the control of any authority (including ourselves! 🙂), there are a number of mechanisms we have introduced to mitigate spam.
|
||||
|
||||
One of these mechanisms is ‘mutual contacts’. What this means is that in order to start a 1on1 conversation with another person, or to add somebody to an ad-hoc group chat, you first need to be a mutual contact with that person. So it is recommended that you send ‘Contact requests’ in Status to all the other CCs that you may need to chat with outside of the Status Internal community space.
|
||||
|
||||
[Here](https://contacts.status.im) is a useful link to the Status CC’s contact list which contains everyone's chat keys (and names/emails etc).
|
||||
|
||||
Like Discord, Status also supports small ad-hoc group chats. Unlike Discord, which only supports 10 participants in each ad-hoc group chat, Status currently supports 20 participants and hopefully we can further increase this number in the future. So if you need to have a small private group chat about something, give this functionality a try!
|
||||
One of these mechanisms is ‘mutual contacts’. What this means is that in order to start a 1on1 conversation with another person, or to add somebody to an ad-hoc group chat, you first need to be a mutual contact with that person. So it is recommended that you send ‘Contact requests’ in Status to all the other core contributors that you may need to chat with outside of the Status Internal community space.
|
||||
|
||||
|
||||
## 🐞 How to report bugs
|
||||
Like Discord, Status also supports small ad-hoc group chats. Unlike Discord, which only supports 10 participants in each ad-hoc group chat, Status currently supports 20 participants and hopefully, we can further increase this number in the future. So if you need to have a small private group chat about something, give this functionality a try!
|
||||
|
||||
## 🐞 How to report bugs
|
||||
(If you are already experienced with reporting bugs you can skip this section)
|
||||
|
||||
One of the reasons we dogfood is to identify bugs! So if you think you have run into a bug, it would be much appreciated if you follow these instructions to report the issue:
|
||||
|
||||
1. Go to the [Status Desktop repo](https://github.com/status-im/status-desktop/issues) on GitHub and have a quick look to see if the issue has already been reported. If you see that the issue has already been reported, you can leave a comment on the issue saying “I’ve experienced this bug” and add any additional information (if any) from your experience that’s not already in the bug report.
|
||||
|
||||
1. Go to the [Status Desktop repo](https://github.com/status-im/status-desktop/issues) on GitHub and have a quick look to see if the issue has already been reported. If you see that the issue has already been reported, you can leave a comment on the issue saying “I’ve experienced this bug” and add any additional information (if any) from your experience that’s not already in the bug report.
|
||||
Don’t worry about accidentally creating a duplicate bug, this happens all the time and the Desktop team will deduplicate any duplicate bugs reported.
|
||||
|
||||
2. If after a quick skim you can’t see a bug report that matches the issue you’ve encountered, click the green ‘New issue’ button to create a bug report. In the bug report, try to include the following:
|
||||
|
||||
- the version of Status Desktop you are using (you can see this by going to Settings / About in the app).
|
||||
- the OS version you are using e.g. Windows 10, Ubuntu 20.04, etc…
|
||||
- If possible, numbered steps of what to do to reproduce the bug.
|
||||
@@ -134,15 +81,11 @@ Don’t worry about accidentally creating a duplicate bug, this happens all the
|
||||
|
||||
And that’s it, if you follow these steps you’ve written a highly descriptive and informative bug report that’s better than 95% of bug reports 🙂
|
||||
|
||||
|
||||
## ⬆️ How to request a new feature or an improvement to an existing feature
|
||||
|
||||
Many of us use group chats on various platforms (Discord, Telegram, Whatsapp etc.) for work or as part of our hobbies and personal lives. This means that everybody who works at Status is an expert group chat user, and as such your input on what improvements and new features we need to build is extremely valuable.
|
||||
## How to request a new feature or an improvement to an existing feature
|
||||
Many of us use group chats on various platforms (Discord, Telegram, Whatsapp etc.) for work or as part of our hobbies and personal lives. This means that everybody who works at IFT is an expert group chat user, and as such your input on what improvements and new features we need to build is extremely valuable.
|
||||
|
||||
To gather and prioritise this feedback, we have set up a ‘User Voice board’ for Status Desktop on Feature UpVote. We plan to use a user voice board like this (but obvs. styled nicer to be on-brand 😉 ) with external users to capture their feedback after we launch our MVP, so now is a great opportunity to give this method of collecting user feedback a trial run on ourselves.
|
||||
|
||||
The idea behind a user voice board is simple - anybody can post an improvement idea or feature request, everybody can upvote requests that are important to them, and designers and developers working on the desktop product can respond to these suggestions.
|
||||
|
||||
Give [Feature UpVote](https://status-desktop.featureupvote.com) a go 🙂 Just upvoting (or not upvoting) requests helps build a prioritised backlog to feed into the product development roadmap.
|
||||
|
||||
|
||||
Give [Feature UpVote](https://status-desktop.featureupvote.com/) a go 🙂 Just upvoting (or not upvoting) requests helps build a prioritised backlog to feed into the product development roadmap.
|
||||
|
||||
@@ -1,9 +1,5 @@
|
||||
# ⚓️ Settling in
|
||||
|
||||
> Status is more than a product, it is also an experiment in organisation.
|
||||
>
|
||||
> – Jarrad Hope
|
||||
|
||||
None of us truly knows how our future will look. In all the flurry of productivity, it’s easy to overlook that what we are trying to do has never been done before. We are operating in a pretty much-unchartered territory, trying to:
|
||||
|
||||
* Create a public good that has not been made before,
|
||||
@@ -12,6 +8,6 @@ None of us truly knows how our future will look. In all the flurry of productivi
|
||||
|
||||
We’re still figuring out how we balance these things.
|
||||
|
||||
Joining the Status community of core contributors means you will be working alongside bright and passionate people with a shared vision: a more decentralised future. Status is a transparent and collaborative environment designed to bring the best ideas to fruition.
|
||||
Joining this community of core contributors means you will be working alongside bright and passionate people with a shared vision: a more decentralised future. We have a transparent and collaborative environment designed to bring the best ideas to fruition.
|
||||
|
||||
The Status projects and the broader Web3 ecosystem are a fast-growing maze. Take time to orientate yourself, don’t rush, and spend time in your first few weeks really connecting with the people you’re working with, as they are the best and most up-to-date sources of information and support that exist.
|
||||
The IFT projects and the broader Web3 ecosystem are a fast-growing maze. Take time to orientate yourself, don’t rush, and spend time in your first few weeks really connecting with the people you’re working with, as they are the best and most up-to-date sources of information and support that exist.
|
||||
|
||||
@@ -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!
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# 🌟 Your People team
|
||||
|
||||
Status is a non-conventional organisation, and as such it's important that you - our core contributors - have everything you need to be successful and help deliver the organisations' goals. We want to make sure you get the attention and support you need at Status.
|
||||
IFT is a non-conventional organisation, and as such, it's important that you - our core contributors - have everything you need to be successful and help deliver the organisations' goals. We want to make sure you get the attention and support you need at IFT.
|
||||
|
||||
With that in mind, People Ops is here for you as someone you can turn to when you need advice or just want to chat. No topic too big or too trivial!
|
||||
|
||||
@@ -8,9 +8,9 @@ DM us anytime :) We’ll also be checking in with you from time to time too, to
|
||||
|
||||
## Mission statement
|
||||
|
||||
### 🎉 Make Status a top place to work.
|
||||
### 🎉 Make IFT a top place to work.
|
||||
|
||||
Not living up to that ideal? Tell us! We aim to make your experience with Status as positive and productive as possible.
|
||||
Not living up to that ideal? Tell us! We aim to make your experience with IFT as positive and productive as possible.
|
||||
|
||||
We’ll keep asking you how we can improve, and we welcome your feedback at any time.
|
||||
|
||||
@@ -38,6 +38,8 @@ Each project will be paired with one People Partner who will provide end-to-end
|
||||
Outside of the core People Ops work, we’re also available for ad hoc tasks like:
|
||||
|
||||
- Managing events, recurring calls, hosting webinars.
|
||||
- 1-1 coaching and mentorship
|
||||
- Travel booking
|
||||
- Administrative support.
|
||||
- Bouncing ideas / venting / general catch-up chats.
|
||||
- Coordination, project management.
|
||||
@@ -49,8 +51,8 @@ The Talent team supports the selection of wonderful core contributors like you f
|
||||
|
||||
This includes:
|
||||
- Support on defining the core contributor requirements and developing the required parameters and specifications.
|
||||
- Sourcing, identifying and engaging potential core contributors for projects and services required by Status.
|
||||
- Advertising roles, such as using our Status social media presence to attract core contributors.
|
||||
- Sourcing, identifying and engaging potential core contributors for projects and services required by IFT.
|
||||
- Advertising roles, such as using our social media presence to attract core contributors.
|
||||
- Reviewing and short-listing suitable potential core contributors.
|
||||
- Conducting initial potential core contributor screenings.
|
||||
- Scheduling any potential core contributor’ interviews during the selection process.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# ⏳ Self-time management
|
||||
|
||||
For every year that you may be engaged with Status, we recommend being away from your keyboard (“AFK”) for at least 20 days a year (plus your local or cultural bank holidays) to disconnect and enjoy time doing things important to you. We encourage you to disconnect as much as you need on top of this.
|
||||
For every year that you may be engaged with one of our projects, we recommend being away from your keyboard (“AFK”) for at least 20 days a year (plus your local or cultural bank holidays) to disconnect and enjoy time doing things important to you. We encourage you to disconnect as much as you need on top of this.
|
||||
|
||||
We don't mandate the days, schedule, or hours that you take to deliver the services –you're free to set your schedule and work from any place (home/coffee shop/coworking space) and time zone as long as they’re delivered within the agreed timeframe.
|
||||
|
||||
@@ -8,9 +8,9 @@ This system might be new to you, and if you'd like some guidance on self-time ma
|
||||
|
||||
## 📣 Communicating your availability
|
||||
|
||||
There is no need to communicate time off to Status unless it's a full day or longer. Non-linear workdays are fine, as well as traditional schedules. Keep your hours in check for your own good, make sure you get proper time away from screens, and turn notifications off on your phone when you're offline. You are free to choose your working patterns as long as you meet your deliverables on time at the agreed quality standards.
|
||||
There is no need to communicate AFK unless it's a half day or longer. Non-linear workdays are fine, as well as traditional schedules. Keep your hours in check for your own good, make sure you get proper time away from screens, and turn notifications off on your phone when you're offline. You are free to choose your working patterns as long as you meet your deliverables on time at the agreed quality standards.
|
||||
|
||||
Monthly and project rate contractors can invoice Status for their agreed amounts in months when they take time off. The contractor / entity agreement is based on services provided and does not mandate the time or location where the services will take place.
|
||||
The contractor / entity agreement is based on the services provided and does not mandate the time or location where the services will take place.
|
||||
|
||||
### 📆 Create AFK entries
|
||||
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# 🦾 The trial period
|
||||
|
||||
We consider your first 12 weeks of contributing as a trial period. During this time, you'll work alongside and be treated like other Status core contributors - you'll have access to the same information, software, (virtual) meetups, and learning opportunities. We're confident that you will be a great addition, or we wouldn't have extended an offer!
|
||||
We consider your first 12 weeks of contributing as a trial period. During this time, you'll work alongside and be treated like other IFT core contributors - you'll have access to the same information, software, (virtual) meetups, and learning opportunities. We're confident that you will be a great addition, or we wouldn't have extended an offer!
|
||||
|
||||
However, we have seen that sometimes things don't work out. Working remotely, on new tech, with a super flexible organisation that's constantly evolving isn't to everyone's taste. We want to be very upfront about what we expect from each core contributor.
|
||||
|
||||
A clearly defined initial tryout will allow enough time to get to know each other and fully appreciate how we can work together. It might also be that you decide that Status isn't what you're looking for, and that's okay too.
|
||||
A clearly defined initial tryout will allow enough time to get to know each other and fully appreciate how we can work together. It might also be that you decide that IFT isn't what you're looking for, and that's okay too.
|
||||
|
||||
👉 Check out [Contributing to Status](../contributing-to-status/index.md) and [Value creating behaviours](../contributing-to-status/value-creating-behaviours.md) as a guide to help you along your journey
|
||||
👉 Check out [Contributing to IFT](../contributing-to-ift/index.md) and [Value creating behaviours](../contributing-to-ift/value-creating-behaviours.md) as a guide to help you along your journey
|
||||
|
||||
## Mid-trial feedback
|
||||
## End-trial feedback
|
||||
|
||||
Within your first few weeks, you will automatically be invited to join the Lattice platform to set up your user profile. After 40 days of being engaged with Status, you will be prompted to select 3-6 other core contributors for your feedback circle and complete your own self-assessment of your contributions. Think carefully about who you would like to include, it should be people who are familiar with your work and the contributions you have made so far.
|
||||
Within your first few weeks, you will automatically be invited to join the Lattice platform to set up your user profile. Around week 8 of being engaged with IFT, you will be prompted to select 3-6 other core contributors for your feedback circle and complete your own self-assessment of your contributions. Think carefully about who you would like to include, it should be core contributors who are familiar with your work and the contributions you have made so far.
|
||||
|
||||
💡 Top Tip - If you are in a services project, include core contributors within the programs or projects you support.
|
||||
|
||||
@@ -18,13 +18,9 @@ This feedback circle will be approved by your project lead who is also a reviewe
|
||||
|
||||
Feedback will be collected automatically and aggregated into a report for you to discuss with your project lead during your next 1-1.
|
||||
|
||||
## End-trial feedback
|
||||
|
||||
After 85 days of being engaged with Status, you will need to repeat the process of selecting your feedback circle and complete your self-assessment. Your feedback scores and comments will be aggregated and your project lead will share the feedback results within 1-2 weeks. At that time, your project lead will make and communicate a decision on whether your trial has been successful.
|
||||
|
||||
Once you have passed your trial period, we expect feedback to be regularly shared through either the Lattice platform or via your project lead on an ongoing basis.
|
||||
|
||||
We hope that all of our trials will be successful. Still, we may not see the potential for a productive future collaboration together. In that case, People Ops or your project lead will reach out to you about extending your trial or terminating your service agreement with Status and any related logistics.
|
||||
We hope that all of our trials will be successful. Still, we may not see the potential for a productive future collaboration together. In that case, People Ops or your project lead will reach out to you about extending your trial or terminating your service agreement with IFT and any related logistics.
|
||||
|
||||
## ❓ FAQs
|
||||
|
||||
@@ -45,7 +41,7 @@ We hope that all of our trials will be successful. Still, we may not see the pot
|
||||
|
||||
Based on the feedback received via the trial process we can assess whether a trial has been successful. We ask a diverse set of questions in the feedback form to get a mix of data points - numerical, qualitative, and comparative and aggregate all responses and scores received.
|
||||
|
||||
Important standards like productivity, autonomy, visibility, the quality of output and showing advancement of the Principles would be indicators to how successful a core contributor has been during this trial period. Contributions not being impactful to Status's overall objectives or developmental feedback, not being addressed would be reasons (among others) to end the trial.
|
||||
Important standards like productivity, autonomy, visibility, the quality of output and showing advancement of the Principles would be indicators to how successful a core contributor has been during this trial period. Contributions not being impactful to IFT's overall objectives or developmental feedback, not being addressed would be reasons (among others) to end the trial.
|
||||
|
||||
* **Why do you ask so many contributors for feedback?**
|
||||
|
||||
|
||||
@@ -2,15 +2,15 @@
|
||||
|
||||
Projects have project leads who coordinate communications and resources. Instead of core contributors having a manager, core contributors collaborate directly with other core contributors in the project.
|
||||
|
||||
Core contributors have a huge amount of autonomy, and no one will give you granular detail about what to do, when to do it, or where you do it from.
|
||||
Core contributors have a huge amount of autonomy, and no one will give you granular details about what to do, when to do it, or where you do it from.
|
||||
|
||||
When you first join, your People Partner will connect you with another core contributor to help you get familiar with the Status organisation. You’ll have a couple of initial deliverables scoped out by the project lead to ease your onboarding and get you going. Beyond that, you’re expected to define and report on the status of your deliverables, reach out to others to collaborate, and hold yourself accountable to it.
|
||||
When you first join, your People Partner will connect you with another core contributor to help you get familiar with the organisation. You’ll have a couple of initial deliverables scoped out by the project lead to ease your onboarding and get you going. Beyond that, you’re expected to define and report on the status of your deliverables, reach out to others to collaborate, and hold yourself accountable to it.
|
||||
|
||||
The following are some important attributes to successfully collaborate in a remote and asynchronous environment:
|
||||
* Autonomy: You’re a self-starter, can handle ambiguity, and you have a good sense of when to start tasks on your own and when to ask for support.
|
||||
* Motivation/Attitude: You take initiative and engage with your projects, you’re helpful towards others, ask questions, and regularly seek to learn more.
|
||||
* Visibility into work: You communicate clearly and know when to update your project leads and other core contributors on the progress of your deliverables.
|
||||
|
||||
As a core contributor, you have the autonomy to choose which project, in what capacity, at which times and from which location you’d like to contribute to Status –as long as it fulfils the needs and goals of Status.
|
||||
As a core contributor, you have the autonomy to choose which project, in what capacity, at which times and from which location – as long as it fulfils the needs and goals of the IFT.
|
||||
|
||||
Ideally, you’re the kind of person that finds this autonomy thrilling, and not too terrifying.
|
||||
Ideally, you’re the kind of person who finds this autonomy thrilling and not too terrifying.
|
||||
|
||||
@@ -6,15 +6,15 @@ There's no prescriptive recipe for success in your first few months but the foll
|
||||
|
||||
- Take a look through the action items assigned to you in BambooHR, these will help you get familiarised and get access to essential tools.
|
||||
|
||||
- Download the Status app and ping in #general or #people-ops and say hello then drop into the #intros channel and tell us about yourself by posting an intro video. We're always excited when new core contributors join and we love to get to know you more.
|
||||
- Join the project Discords and download the Status app and ping in #general or #people-ops and say hello then drop into the #intros channel and tell us about yourself by posting an intro video. We're always excited when new core contributors join and we love to get to know you more.
|
||||
|
||||
Some great topics to cover are:
|
||||
|
||||
- Who you are and where you are located
|
||||
- What excites you about Status
|
||||
- What did you do prior to joining Status
|
||||
- What excites you about IFT and our projects
|
||||
- What did you do prior to joining IFT
|
||||
- What are your passions/hobbies
|
||||
- Bonus points for fun facts about yourself.
|
||||
- Bonus points for fun facts about yourself
|
||||
|
||||
The video can be between 1-3 minutes max.
|
||||
|
||||
@@ -22,13 +22,13 @@ Some great topics to cover are:
|
||||
|
||||
- Find your project, drop by their channel, and see what work is scoped out for you in your first few weeks.
|
||||
|
||||
- Have a read through resources like this site, Discuss, Docs, Notion and Our Status, to get a feel for the latest happenings and key info.
|
||||
- Have a read through resources like this site, Discuss, Docs, Notion and Miro to get a feel for the latest happenings and key info.
|
||||
|
||||
- Watch the latest all hands strategy call hosted by our Co-founder Jarrad.
|
||||
|
||||
- Join your onboarding call with your People Partner to go over all your onboarding questions and ideas.
|
||||
|
||||
- Join the new starter intro monthly calls hosted by Status to meet other new core contributors to help build up your internal network
|
||||
- Join the new starter intro monthly calls hosted by IFT to meet other new core contributors to help build up your internal network
|
||||
|
||||
## 🤙 Getting to know your fellow core contributors...
|
||||
|
||||
@@ -37,9 +37,9 @@ It’s hard to get to know everyone straight away. Here are some helpful ways to
|
||||
- Ask your project lead about who the important people are relevant to your work and connect with them
|
||||
- Schedule a 20 mins coffee break chat with everyone in your project!
|
||||
- Chat with someone who's also recently joined by checking out the #intro channel on the status app and connect with them. They will have recently gone through the onboarding process and may have some great hints and tips and shared experiences.
|
||||
- Ask your buddy about their experience so far: how do they describe Status and our structure?
|
||||
- Ask your buddy about their experience so far: how do they describe IFT and our structure?
|
||||
- Check out the org chart in BambooHR. Bear in mind that we are a flat-ish organisation, so the BambooHR hierarchy might be arbitrary and probably doesn't represent the ways people cross-collaborate normally in day-to-day working but you'll get a feel of who's who.
|
||||
- Feel free to ping anyone at Status to say hey and have a chat - we're an open bunch and enjoy getting to know our new fellow core contributors. Some project members may reach out to you to introduce themselves, too.
|
||||
- Feel free to ping anyone at IFT to say hey and have a chat - we're an open bunch and enjoy getting to know our new fellow core contributors. Some project members may reach out to you to introduce themselves, too.
|
||||
|
||||
...and if you have any questions, ping your People Partner. They're more than happy to help you navigate through the chaos and welcome you with a virtual coffee!
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
|
||||
@@ -0,0 +1,76 @@
|
||||
# 👋 Welcome to IFT
|
||||
|
||||
The Institute of Free Technology emerged from Status, which Jarrad Hope and Carl Bennetts founded to enable the free flow of information and protect the right to private, secure conversations in 2017.
|
||||
|
||||
Over time, gaps in the infrastructure required to deliver Status in a form that fully reflects its founders’, contributors’, and users’ values became apparent, and the project’s scope widened. IFT and the startups it incubates are the product of this expanded scope.
|
||||
|
||||
|
||||
## 🔭 Mission
|
||||
|
||||
We support the development, adoption, and accessibility of solutions to digital age problems and are guided by our principles: liberty, censorship resistance, security, privacy, and inclusivity. We seek to connect with and support those innovating to defend our digital rights.
|
||||
|
||||
|
||||
## IFT Services
|
||||
|
||||
Learn more about IFT and its programs [here](https://free.technology/).
|
||||
|
||||
### Vac
|
||||
|
||||
Vac is a principle-driven research and development group that provides technical support to each IFT startup. It comprises elite specialists in distributed systems, zero-knowledge proofs, and P2P networking, produces specifications for IFT startups, and undertakes comprehensive protocol testing. Like the IFT and the startups with which it works, a commitment to liberty, censorship resistance, security, privacy, decentralisation, and inclusivity guides Vac’s R&D efforts.
|
||||
|
||||
Learn more [here](https://vac.dev/).
|
||||
|
||||
### Finance
|
||||
|
||||
Our startups benefit from IFT capital to fund their research and development efforts. Meanwhile, the IFT nurtures relationships with investors who share our values and commitment to world-changing tech. Besides funding and investment, the IFT handles payment of fees to contributors, and potential expenses incurred by the contributors working with us via our in-house finance department.
|
||||
|
||||
### Legal
|
||||
|
||||
A specialist and highly experienced legal department led by Dr Agata Ferreira helps our startups navigate the often confusing and ever-changing blockchain legal landscape while providing the legal support to allow them to achieve their project aims. Supporting Agata is a team of two with backgrounds in a wide range of legal areas, including, among others, crypto finance and blockchain. The department assists our startups identify and prevent or mitigate potential (legal) risks.
|
||||
|
||||
### People Operations
|
||||
|
||||
Our PeopleOps department ensures that our startups have the most valuable asset they need — highly engaged and productive contributors — to focus on developing and supporting the innovations we incubate. The team handles talent scouting, recruiting, onboarding, travel, administrative support, and other initiatives to keep those working with us happy, engaged, and productive.
|
||||
|
||||
### Brand & Awareness
|
||||
|
||||
The studio works with our startups to deploy high-impact campaigns, raising brand awareness among their target markets both within the web3 ecosystem and beyond it. IFT startups enjoy full access to the studio, which comprises marketing, digital communications, design, web development, and events management specialists.
|
||||
|
||||
## Programs
|
||||
|
||||
### [Logos](https://logos.co/manifesto)
|
||||
|
||||
A movement supporting the development of the decentralised web. Logos technologies lay the foundations for a freer internet upon which communities can evolve into network states. Each protocol in the Logos stack seeks to empower its users while upholding civil liberties and fundamental freedoms.
|
||||
|
||||
#### [Waku](http://waku.org/)
|
||||
|
||||
A family of generalised P2P communications protocols. The messaging layer of the Logos stack. Waku is private, censorship resistant, modular, and scalable by design. This combination of features makes Waku suitable to run in a wide range of environments, including phones and browsers, while upholding its users’ rights to private communications.
|
||||
|
||||
#### [Codex](https://codex.storage/)
|
||||
|
||||
A decentralised storage engine with strong censorship resistance and durability guarantees. The data archiving layer of the Logos stack. Codex leverages a novel combination of cutting-edge features, including erasure coding, a lazy repair system, ZK-based remote auditing, and incentivisation mechanisms to ensure reliability, data durability, efficiency, and cost effectiveness.
|
||||
|
||||
#### [Nomos](https://nomos.tech/)
|
||||
|
||||
A sovereign, modular, zk-encrypted network of blockchains. The trustless agreements layer of the Logos stack. The forthcoming Nomos network will provide a common infrastructure layer upon which communities and aspiring network states can build social, governance, and financial services that uphold their community members’ fundamental rights and values.
|
||||
|
||||
### [Status](https://status.im/)
|
||||
|
||||
A blockchain-based super app that combines private messaging, a wallet, a DApp browser, and tools for web3 community management. Status aims to be a truly decentralised communication tool and, since its founding in 2017, has been progressively removing reliance on centralised infrastructure. The application leverages Waku and other technologies developed under the IFT umbrella.
|
||||
|
||||
#### [Keycard](https://keycard.tech/)
|
||||
|
||||
A discreet, convenient, affordable hardware security solution for crypto assets. Taking the form of a credit card, Keycard offers comparable crypto security at a fraction of the cost of others in the hardware wallet niche. Keycard is in production, and the team is working on a full hardware wallet, which will be entirely open-source and compatible with existing Keycards while offering a familiar user experience.
|
||||
|
||||
### [Nimbus](https://nimbus.team/)
|
||||
|
||||
A lightweight Ethereum client implementation designed to reduce hardware requirements for solo stakers and increase efficiency for institutional staking service operators. Nimbus’ mission is to make staking accessible, thus promoting maximum network decentralisation. The Nimbus consensus client is in production, and an execution client is in development. By offering lightweight implementations for both consensus and execution layers, Nimbus simplifies operating an Ethereum node for hobbyists and institutional stakers alike.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
# 👋 Welcome to Status
|
||||
|
||||
The Status app was created to:
|
||||
|
||||
* Ease the transition to a more open mobile internet.
|
||||
* Help anyone, anywhere, interact with Ethereum, requiring no more than a phone.
|
||||
* Foster links with the wider Ethereum DApp community and showcase what the ecosystem has to offer.
|
||||
|
||||
## 🔭 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?"
|
||||
|
||||
In one simple word, Decentralisation.
|
||||
|
||||
Now, that word might not have much meaning to you - it might even sound like a buzzword - but in our context, decentralisation has the potential to fundamentally change the way we organise socially and to rebuild the Internet as it was originally imagined – a commons for innovation. By decentralising all the things, we are changing the very foundation of civilisation, providing a new infrastructural base that impacts everything else above, from our greatest institutions to our daily social interactions
|
||||
|
||||
Status is our gateway to this new world. Let me explain. [Read the Founder’s Statement →](https://github.com/status-im/legacy-wiki/blob/master/archive/Founder%E2%80%99s_Statement.md)
|
||||
|
||||
## 🗒️: A Letter to Status by Jarrad Hope 30 July 2018
|
||||
|
||||
So we're getting to an organisation level where broadcasting communication is probably the most effective to reach everyone, and often I take it for granted that I've been with the project for longest, and quite frankly there was many years of experience, reading, thinking and research that lead to our project's creation. And I realise now my role should be mostly that of an educator, at least what I (think I) know, and I certainly don't know much at all.
|
||||
|
||||
I'm going to take a few weeks off, mostly just to pause and reflect on Status and life, but before I check out I wanted to write up a little bit about the world as I see it and provide some thoughts on various aspects, this is about as close to the strategy/north star document will get from my contributions, I do encourage for you to take these ideas and make them your own.
|
||||
|
||||
So here I am, writing a letter to you (and to myself).
|
||||
|
||||
Before I continue, you need to know that what I say isn't gospel, Status is just as much yours as it is mine. You are an active participant and I invite you to actively shape it as your own. That is the nature of an open-source project, and that idea extends beyond just code. What I can only do, is do my best to guide and give suggestions. Remember, you via Status are entrusted by the greater community to build a collective good. Let's do right by them and by our own self-determination.
|
||||
|
||||
tl;dr: it's a memory dump, read it. [Read Jarrad’s Letter to Status →](https://our.status.im/a-letter-to-status-context-strategy/)
|
||||
|
||||