Compare commits

...
Author SHA1 Message Date
Terrytobin 624569747d Update SUMMARY.md 2024-03-19 08:43:10 +00:00
Terrytobin 50aca555ba Rename welcome-to-status.md to welcome-to-IFT.md 2024-03-19 08:42:40 +00:00
jakub c5b900c570 reduce size of IFT logo
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-03-18 19:36:21 +01:00
jakub ad40b39473 ci: add nix shell and support for emojicodes
Adds support for writing emojis like `:cat:` the same way it works on GitHub.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-03-18 19:29:33 +01:00
Terrytobin a08a14afa0 Update catalog.md (#150)
Change name to IFT Core Contributors
2024-03-18 19:00:55 +01:00
Terrytobin 6a3b8d1722 Update index.md (#151)
update Status / IFT wording
2024-03-18 19:00:30 +01:00
Terrytobin 055e599a37 Update your-autonomy.md (#152) 2024-03-18 19:00:05 +01:00
Terrytobin 07536552dd Update self-time-management.md (#153)
Updated wording Status <>IFT
2024-03-18 18:59:30 +01:00
Terrytobin 1aa77148d4 Update afk-faqs.md (#154) 2024-03-18 18:58:58 +01:00
Terrytobin ffd88c4db6 Update your-first-day-week-month.md (#157)
Update wording Status <> IFT
2024-03-18 18:58:23 +01:00
Terrytobin 70531b7ed5 Update download-status-desktop.md (#158)
Update wording Status <>IFT
2024-03-18 18:57:06 +01:00
Terrytobin 68daf68da5 Update index.md (#159)
Update wording Status <>IFT
2024-03-18 18:56:36 +01:00
Terrytobin 53994e9efd Update journey-to-your-first-contribution.md (#160)
Update wording Status<>IFT
2024-03-18 18:55:51 +01:00
Terrytobin ca5278fe6d Update people-operations.md (#155)
Update wording Status<>IFT
2024-03-18 18:54:46 +01:00
Terrytobin 7790c835ff Update introduction.md 2024-03-18 17:52:47 +00:00
Terrytobin 48cae73897 Update welcome-to-status.md (#149)
Added IFT wording and info about programs
2024-03-18 18:49:08 +01:00
Terrytobin 3600b494e8 Update introduction.md 2024-03-18 17:47:34 +00:00
Terrytobin 4b1c1a2ca9 Update essential-reading.md (#170)
Updated wording Status <>IFT
2024-03-18 18:47:11 +01:00
Terrytobin 664b3455a7 Update getting-paid.md (#174)
update wording Status <>IFT
2024-03-18 18:46:54 +01:00
Terrytobin 59dbb82ed8 Update introduction.md 2024-03-18 17:22:51 +00:00
Terrytobin d971636eb5 Rename IFT_Logos3Asset_42x-8.png to IFT_logo.png 2024-03-18 17:18:55 +00:00
Terrytobin 09dd9536b6 Add files via upload 2024-03-18 17:10:42 +00:00
Terrytobin 87fc2e415a Update location-independence.md (#167)
Updated wording re: employment
2024-03-18 11:40:00 +00:00
Terrytobin a77d42dc99 Update events-and-meetups.md (#168)
Updated wording
2024-03-18 11:16:26 +00:00
Terrytobin fe99b105d2 Update In-case-of-a-dispute.md (#171)
Updated wording Status <>IFT
2024-03-18 10:33:16 +00:00
Terrytobin 1db61074ea Update introduction.md (#148)
Updating working to about IFT
2024-03-15 16:39:14 +00:00
Terrytobin a98685cb74 Update third-party-invoices-format.md (#175)
update wording Status <>IFT and IFT address
2024-03-15 16:38:02 +00:00
Terrytobin 7d9a7cb258 Update emergencies.md (#172)
updated wording
2024-03-15 16:36:51 +00:00
Terrytobin e24987433c Update expense-reimbursements.md (#176)
update wording Status <> IFT
2024-03-15 16:36:11 +00:00
Terrytobin 893d75beda Update code-of-conduct.md (#173)
Updated wording
2024-03-14 16:15:47 +00:00
Terrytobin c117853e7e Update index.md (#177)
Updated wording
2024-03-14 16:13:28 +00:00
Terrytobin 124b2d034c Update security-guidelines.md 2024-03-13 17:54:44 +00:00
Terrytobin 1bcc66a72f Update index.md 2024-03-13 17:49:33 +00:00
Terrytobin 2c2336245a Update onboarding-buddy.md (#156)
Update wording Status <> IFT
2024-03-13 15:45:41 +00:00
Terrytobin 71c1bebb74 Update getting-paid.md 2024-03-12 16:37:29 +00:00
jakub 4693d8e661 add files/Candidate_-_Privacy_Notice.pdf
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-03-04 13:39:08 +01:00
Terrytobin 0ce703ab28 Update SUMMARY.md
removed evaluation guide from summary page until its updated
2024-02-28 14:16:11 +00:00
jakub c1d663afec remove merge stuff from summary
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-28 15:03:24 +01:00
Terrytobin 5f422cfbcd Merge branch 'develop' 2024-02-28 13:55:59 +00:00
Terrytobin ab47794120 fix (#147) 2024-02-28 13:55:31 +00:00
Terrytobin 6c792ee929 fix 2024-02-28 13:51:21 +00:00
Terrytobin b2c46f0197 Merge branch 'develop' 2024-02-28 13:50:44 +00:00
Terrytobin b47ca38713 Update SUMMARY.md (#145) 2024-02-28 13:50:04 +00:00
Terrytobin b727fc12f7 Merge branch 'develop' 2024-02-28 13:40:21 +00:00
jakub 22bd2e5e19 recover Playbooks/2023-Lead-Evaluation-Guide.md
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-28 14:39:04 +01:00
Terrytobin dc27c025bb Merge branch 'develop' 2024-02-28 13:36:07 +00:00
Terrytobin c657e47392 fixlink (#144)
fixlink
2024-02-28 13:35:13 +00:00
Terrytobin b67508e426 Update SUMMARY.md 2024-02-28 12:59:59 +00:00
Terrytobin 5d782fbdd3 Rename Candidate-Tasks.md to Candidate-Tasks 2024-02-28 12:58:55 +00:00
Terrytobin ed12e4cbd7 Update SUMMARY.md 2024-02-28 12:58:06 +00:00
Terrytobin da203099d8 Update SUMMARY.md 2024-02-28 12:57:01 +00:00
Terrytobin 865cf5ae8d Rename the-team-lead-role.md to the-team-lead-role 2024-02-28 12:56:05 +00:00
Terrytobin 8d1cd5abb2 Update SUMMARY.md 2024-02-28 12:51:27 +00:00
Terrytobin 5acc6e4269 Update SUMMARY.md 2024-02-28 12:50:42 +00:00
Terrytobin bfcc47b9f3 Update SUMMARY.md 2024-02-28 12:49:16 +00:00
Terrytobin 7bb8a02118 Rename Candidate Tasks.md to Candidate-Tasks.md 2024-02-28 12:46:32 +00:00
Terrytobin e7a764a4e5 Update SUMMARY.md 2024-02-28 12:42:54 +00:00
Terrytobin 6182c2969d Update SUMMARY.md 2024-02-28 12:42:08 +00:00
Terrytobin 3fd2084d04 Rename team-lead-manual.md to Candidate Tasks.md 2024-02-28 12:40:25 +00:00
jakub 64b3bb1344 remove unused file
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-27 12:25:32 +01:00
jakub 18ae4e2fac fix Hiring/Team Lead Manual, remove duplicates
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-27 12:25:10 +01:00
LilChiChiandCatia Sousa ffe816cc09 Hiring manager section (#139)
* Add files via upload

* Create Best Practice Guide: Candidate Tasks in Recruitment

* Update Best Practice Guide: Candidate Tasks in Recruitment

Added a picture

* Rename Best Practice Guide: Candidate Tasks in Recruitment to Best Practice Guide: Candidate Tasks in Recruitment.md

* Update Best Practice Guide: Candidate Tasks in Recruitment.md

* Update Best Practice Guide: Candidate Tasks in Recruitment.md

---------

Co-authored-by: Catia Sousa <catiasousa.recruitment@gmail.com>
2024-02-27 10:49:43 +01:00
jakub 55f23ac516 feat: use two deploy branches for CI builds
This way we have two branches on GitHub that reflect the state of the
website after CI build has finished and pushed. See README.

Also adds `build.json` file at site root for see currently deployed version.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-02-26 15:57:46 +01:00
Terrytobin d995e41b7d Merge branch 'develop' 2024-02-13 17:26:19 +00:00
LilChiChiandCatia Sousa 55b0484dff Hiring manager section (#139)
* Add files via upload

* Create Best Practice Guide: Candidate Tasks in Recruitment

* Update Best Practice Guide: Candidate Tasks in Recruitment

Added a picture

* Rename Best Practice Guide: Candidate Tasks in Recruitment to Best Practice Guide: Candidate Tasks in Recruitment.md

* Update Best Practice Guide: Candidate Tasks in Recruitment.md

* Update Best Practice Guide: Candidate Tasks in Recruitment.md

---------

Co-authored-by: Catia Sousa <catiasousa.recruitment@gmail.com>
2024-02-13 17:22:59 +00:00
Catia Sousa 18b472f655 Update getting-paid.md (#140)
Changed from Status Holding...to IFT Studio Pte Ltd
2024-02-13 17:16:27 +00:00
harmeet-status 7b0c70e0d6 Update SUMMARY.md (#135)
Adding in collaboration.md into the navigation.
2024-02-13 14:45:39 +00:00
Sasha f9a43e03fd Update travelling-for-status.md (#130)
added a link to the new travel dashboard (new Superset instance)
2024-02-13 13:00:46 +00:00
Sasha 4ebd7acee4 Update How-to-request-goods-or-services.md (#129)
Updated broken links, added "Events" category
2024-02-13 13:00:13 +00:00
Sasha 0c885d10ca Update Superset.md (#128)
new instance of Superset
2024-02-13 12:59:41 +00:00
Priedins15 e849b8e915 Update getting-paid.md (#132)
Updated working days per month
2024-02-13 12:59:08 +00:00
LilChiChi 9cf4b7a2b6 Created Hiring section & added candidate task file (#137) 2024-02-08 18:29:47 +00:00
jonathanbarker dc37b801a5 Update index.md (#136)
Updated language around reference letters
2024-02-06 19:37:30 +01:00
harmeet-status 63903227da Create collabration.md (#134)
* Create collabration.md

Creating a new collaboration section which includes ProtonMail.

* Update collabration.md

Added proton mail to Day 1 platforms in 1st paragraph.
2024-02-05 10:10:53 +01:00
jonathanbarker 4232e2aca7 Update travelling-for-status.md (#133)
Change to flight travel policy
2024-01-31 15:52:12 +01:00
Terrytobin 12d1d9183a Update index.md 2023-11-23 18:43:10 +00:00
Terrytobin 4655afbb08 Update index.md 2023-11-23 15:14:15 +00:00
jonathanbarker f55ddaa503 Update welcome-to-status.md (#127)
Removed link to podcast and blog, since both are very out of date.
2023-11-02 12:59:36 +00:00
jakub 1b9166b4cb custom.css: fix hiding rule to not affect articles
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-10-24 19:42:19 +02:00
MayitaK 15baec2330 Update 2023-Lead-Evaluation-Guide.md (#126) 2023-10-24 18:19:34 +01:00
jakub b6388d133f use custom CSS to hide sub-elements at the end of list
There currently are no built-in ways to do this.
This hack is horrible and should be removed when possible.
It doesn't actually remove the link, it just hides it.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-10-17 11:11:29 +02:00
Terrytobin 9e13e86f6e Update SUMMARY.md 2023-10-16 20:55:24 +01:00
Terrytobin 2627971de8 Update SUMMARY.md 2023-10-16 20:36:45 +01:00
Terrytobin 15eda018c3 Update 2023-Self-Evaluation-Guide.md 2023-10-16 13:58:05 +01:00
Terrytobin 6afaf28328 Update 2023-Lead-Evaluation-Guide.md 2023-10-16 13:56:45 +01:00
Terrytobin 0d03aec66a Update 2023-Lead-Evaluation-Guide.md 2023-10-16 13:53:43 +01:00
Terrytobin 61d8298425 Update 2023-Lead-Evaluation-Guide.md (#125) 2023-10-16 13:38:36 +01:00
Terrytobin 6c93d9638f Update SUMMARY.md 2023-10-12 13:43:18 +01:00
Terrytobin 3aa1b29bc0 Create 2023-Lead-Evaluation-Guide.md 2023-10-12 13:34:39 +01:00
Terrytobin 5e9cc776e8 Update and rename 2023_Self_Evaluation_Guide.md to 2023-Self-Evaluation-Guide.md (#124) 2023-10-12 13:14:32 +01:00
Terrytobin c7051841d6 Create 2023_Self_Evaluation_Guide.md 2023-10-12 12:57:52 +01:00
Melanie e151f6fc11 Update people-operations.md (#123) 2023-10-12 12:35:22 +01:00
AdamDynamic b24b48ad92 Corrected minor typo. (#122) 2023-09-28 13:37:49 +01:00
Terrytobin 36445ee2b3 Update afk-faqs.md (#120) 2023-09-28 10:25:59 +01:00
Terrytobin 972f55b38d Update SUMMARY.md 2023-09-21 19:09:54 +01:00
Terrytobin 56ea24e4b3 Update In-case-of-a-dispute.md 2023-09-20 15:38:28 +01:00
Terrytobin de5351449c Update In-case-of-a-dispute.md 2023-09-20 14:34:08 +01:00
Terrytobin 326691da9d Rename Legal-guidelines.md to In-case-of-a-dispute.md 2023-09-20 14:23:44 +01:00
Terrytobin 11d220ba29 Rename Legal guidelines to Legal-guidelines.md 2023-09-20 11:54:10 +01:00
Terrytobin c148d8b4d4 Update Legal guidelines 2023-09-20 11:53:17 +01:00
Terrytobin 8b0831378e Create Legal guidelines 2023-09-20 11:34:48 +01:00
Anton Iakimov 4f7547f29d fix travelling link (#121)
* fix travelling link

* another link to fix
2023-09-20 11:31:18 +01:00
Anton Iakimov 4be21e63d6 Revert "Rename Spiffworkflow.md to SpiffWorkflow.md (#119)"
This reverts commit ca7da7d1b6.
2023-07-31 10:54:27 +02:00
MayitaK da603b1809 Update download-status-desktop.md (#118)
@imagiMary
2023-07-26 10:13:12 +01:00
harmeet-status ca7da7d1b6 Rename Spiffworkflow.md to SpiffWorkflow.md (#119)
Capital W for Workflow.
2023-07-26 10:12:44 +01:00
Terrytobin 4997bbb1b3 Update SUMMARY.md 2023-07-25 16:12:30 +01:00
harmeet-status 83b85bf2ec Update Superset.md (#117) 2023-07-25 10:15:30 +01:00
Terrytobin 599cf0bb46 Update SUMMARY.md 2023-07-25 09:54:00 +01:00
Terrytobin 81d622f081 Rename How to request goods or services.md to How-to-request-goods-or-services.md 2023-07-25 09:52:45 +01:00
Alexis Pentori e56f37a08d Updating directory for How to Request Goods or services.md
Signed-off-by: Alexis Pentori <alexis@status.im>
2023-07-25 10:42:41 +02:00
Sasha 8fb1273bcb Update expense-reimbursements.md (#108)
Updating the CC Guide articles to accommodate process changes - implementation of SpiffWorkflow and processes (Request Goods/Services, Request Travel)

The changes should be published by the 25th of July (SpiffWorfklow org-wide go-live).
2023-07-25 09:21:57 +01:00
Sasha 2c9089e8dc Create How to procure for the org.md (#110)
* Create How to procure for the org.md

Added "How to" for Request Goods/Services process, categories which are not covered but the CC Guide

* Update How to procure for the org.md

* Update and rename How to procure for the org.md to How to request goods or services.md

* Update How to request goods or services.md
2023-07-25 09:21:12 +01:00
Sasha 7240cfb29d Update laptops-and-devices.md (#102)
* Update laptops-and-devices.md

Updating the CC Guide articles to accommodate process changes - implementation of SpiffWorkflow and Request Goods/Services process

* Update laptops-and-devices.md
2023-07-24 10:15:35 +01:00
Sasha 28311bef1d Update events-and-meetups.md (#105)
* Update events-and-meetups.md

Updating the CC Guide articles to accommodate process changes - implementation of SpiffWorkflow and Request Travel process

The changes should be published by the 25th of July (SpiffWorfklow org-wide go-live).

* Update events-and-meetups.md
2023-07-24 10:14:47 +01:00
Sasha 89312c13c7 Update essential-reading.md (#103)
Updating the CC Guide articles to accommodate process changes - implementation of SpiffWorkflow and Request Goods/Services process
2023-07-24 09:40:58 +01:00
Sasha f334f0816e Update travelling-for-status.md (#106)
Updating the CC Guide articles to accommodate process changes - implementation of SpiffWorkflow and Request Travel process

The changes should be published by the 25th of July (SpiffWorfklow org-wide go-live).
2023-07-24 09:37:21 +01:00
José Anaya b06d31906b Update Superset Tutorial File (#113)
Added guide for basic usage of superset in Playbook
2023-07-24 09:20:39 +01:00
harmeet-status 45ae3195d5 new heading and some text change (#115) 2023-07-24 09:19:36 +01:00
harmeet-status 5bdd0602be adding a spiff heading (#116) 2023-07-24 09:18:14 +01:00
jakub bdc3d45717 fix desktop screenshot filename
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-07-20 15:42:16 +02:00
Terrytobin 09121fd419 Update download-status-desktop.md 2023-07-20 13:33:18 +01:00
jakub 46ccf7a1f4 fix folder name for spiffworkflow
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-07-19 19:27:59 +02:00
jakub b312fbadd1 rename Playbook folder to Playbooks
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-07-19 19:17:09 +02:00
Terrytobin 16216aecfe Create index.md 2023-07-19 18:14:37 +01:00
Terrytobin 175ac74c42 Rename Superset to Superset.md 2023-07-19 18:11:19 +01:00
Terrytobin ce427fc471 Update SUMMARY.md
Update index
2023-07-19 18:09:26 +01:00
harmeet-status 4299bf664f Update and rename Spiffworkflow to Spiffworkflow.md (#107)
Adding user guide into this.
2023-07-19 16:17:25 +01:00
Mary 4a29ffd658 Update download-status-desktop.md (#98)
Update to image 3
2023-07-19 13:13:48 +01:00
Mary de5beca1b4 Hyperlink update (#97) 2023-07-19 13:13:20 +01:00
Terrytobin 29ed1b66b1 Create Superset 2023-07-13 13:20:01 +01:00
Terrytobin 8fae2d4f39 Create playbook 2023-07-13 13:18:41 +01:00
Terrytobin 1c3b994d1c New folder 2023-07-13 13:08:08 +01:00
Terrytobin d3bb6e63fe Delete Congrats on your offer 2023-07-12 09:56:36 +01:00
Terrytobin 6eaaaa14be Create Congrats on your offer 2023-07-12 09:52:50 +01:00
Prem Chaitanya Prathi 6611c8757b Minor updates noticed from a newcomer perspective (#99)
* Update download-status-desktop.md

Updating discord username to @helium__ as @helium is someone else on discord.

* Update contributing-to-this-guide.md

Adding a note indicating that commits can be done only once org access is provided on github.
2023-07-12 09:48:37 +01:00
jonathanbarker 166ba68ea3 Update travelling-for-status.md (#100)
Updated per diem to 85 (from 75)
2023-07-06 09:19:04 +01:00
Terrytobin b8ece3bc05 Add files via upload 2023-06-13 12:19:59 +01:00
Terrytobin 663529d5aa Update expense-reimbursements.md 2023-05-30 12:00:39 +01:00
Terrytobin 75a25d5cf1 Update onboarding-buddy.md 2023-04-25 13:53:36 +01:00
Terrytobin bc32bd938b Update onboarding-buddy.md 2023-04-25 13:45:56 +01:00
Mary b405ad5f15 Update download-status-desktop.md (#96)
Changes should hopefully fix the broken links.
2023-04-18 16:20:18 +01:00
jonathanbarker 1ea2d85ed4 Fixed broken link for download desktop 2023-04-13 18:17:16 +01:00
jonathanbarker fcd930e170 Fixed broken link for download status desktop link 2023-04-13 18:16:30 +01:00
jonathanbarker ab94712ba6 Rename download-status-desktop to download-status-desktop.md (#95) 2023-04-13 15:28:17 +01:00
jonathanbarker e6174bfd4b Add link to Download Status Desktop (#94) 2023-04-13 12:35:32 +01:00
LilChiChi bc0ddd77b4 Update onboarding buddy (#89)
From line 63-77 there were both bullet points & the blocks, which looked messy / like a mistake.

I removed the bullet points & left the blocks there.
2023-04-13 12:30:27 +01:00
Maryandjonathanbarker e5766822e1 Create download-status-desktop (#92)
* Create download-status-desktop

Instructions on how to get started with using Status Desktop. 

Images still need to be added.

* Update download-status-desktop

Images added.

---------

Co-authored-by: jonathanbarker <41283474+jonathanbarker@users.noreply.github.com>
2023-04-13 12:22:32 +01:00
jonathanbarker 1a1bdd87bd Images for CC Status Desktop download (#93) 2023-04-12 18:08:56 +02:00
Terrytobin 3788f444b8 Update expense-reimbursements.md 2023-03-28 19:11:21 +01:00
LilChiChi 506eb757f3 Spelling (#87)
Updated line 15, took out the hashtags before decentralisation
2023-03-26 11:06:49 +01:00
LilChiChi 49e338f38b Added some emojis (#90)
Added emojis to each title
Added standard good/bad emoji to represent great & not great
2023-03-26 11:05:26 +01:00
Pepper Lea 84a0eb77b2 edit and comma (#85)
added comma and changed wording on "Status evolves faster than it can keep the documentation updated"
2023-03-26 11:04:32 +01:00
Catia Sousa 34e2d56daa Added moe detail on expense reimbursements (#91)
added and adjusted last update post by Deivids on reimbursement deadline and process
2023-03-24 17:15:08 +00:00
Catia Sousa 66e33cfd29 "employees" and "For" fix (#86)
changed "Holiday (For employees only)" to "Holiday (For core contributors only)"

changed "For any invoice/expenses" to "for any invoice/expenses"
2023-03-24 10:53:48 +00:00
jonathanbarker 50bf653569 Updated language for visa processing (#83)
Changed from "cannot" to "will not".
2023-03-24 10:51:08 +00:00
68 changed files with 1002 additions and 268 deletions
Vendored
BIN
View File
Binary file not shown.
@@ -0,0 +1,101 @@
# Candidate Tasks in Recruitment
<img width="617" alt="Screenshot 2023-12-19 at 12 35 38" src="https://github.com/status-im/contributors.status.im/assets/32337207/431f3b3a-4bd2-44f0-bcf6-ad251ecc967c">
## 1. What is a task:
It is a practical assessment to evaluate candidate skills.
## 2. Why do we use tasks in the hiring process?
We use them to:
- Get a better assessment beyond CVs, portfolios, github repos and interviews.
- Gain a deeper understanding of someone's abilities (technical & non-technical) for the role at hand.
- Give candidates a chance to showcase their working style & communication, its common to set up a Discord chat so the candidate & task reviewers can chat, ask/answer questions and also provide updates.
## 3. How to design a task
Step 1: Understand the role's requirements.
Step 2: Design a task that aligns with the expected output of the role.
Step 3: Clearly communicate task instructions, expectations, and deadline.
What does a good task look like:
- Has clear instructions & expectations
- Has a deadline thats realistic (usually 1 week is enough)
- Has a recommended timeframe in which to complete the task i.e 2-4hrs (this keeps all candidates 'fair' in terms of time dedicated to the task)
- Is aligned with the day-to-day responsibilities of the role
- It is tackling a real problem the team face, some teams use a bounties approach
Examples:
- UX/UI Designer: Create a mobile app prototype/feature based on the target audience.
- Sales: Create a presentation on selling a complex product to a potential client.
- Engineer: Assess problem-solving skills by tasking them with debugging code.
- Customer Support: A simulated chat interaction to assess their communication skills.
- Financial Analyst: Analyze an investment portfolio to gauge forecasting abilities.
- Content Writer: Create a blog post on a specified topic.
## 4. Time restrictions & compensation:
We want to see a glimpse of what they can do within the allocated time, this shouldnt be seen as their full potential since they are not integrated into the working styles of the team or the full context of the team.
A simple and effective approach is:
- A flat rate for completion of the task; ie. $200
- A set time allowing completing the task; ie. 2-4hrs (some teams have longer, rule of thumb is allow enough time for the task to be completed)
… The longer the task, the more time you/your team have to spend reviewing it
## 5. Materials for Candidates:
Ensure candidates have all the reference materials needed to perform and succeed on the task.
Examples:
- A digital marketer may need access to Google Analytics data.
- A data scientist may need to be provided a dataset and access to statistical software.
- A content creator may need a brand style guide and existing content for reference.
- A Mobile UI Engineer will need access to Figma
## 6. Evaluating Tasks:
Setting clear evaluation standards is important so everyone is assessed fairly and we dont let personal biases get in the way of hiring people who perform well during tasks. We should determine the criteria for task evaluation prior to seeing the first task submitted by a candidate.
Examples:
- Evaluate a coding task based on criteria like code quality, efficiency, and adherence to project requirements.
- Assess customer service interactions based on responsiveness, problem-solving, and professionalism.
- Evaluate a design task considering creativity, usability, and alignment with brand guidelines.
## 7. Effective Communication:
Maintain transparent and professional candidate communication.
- Clearly inform candidates of the evaluation timeline and when they can expect feedback.
- Use the Discord chat to interact with the candidate throughout their task
## 8. Feedback and Improvement:
Use candidate feedback to refine task instructions and evaluation criteria.
## 9. Sample Tasks:
- Engineering: [Vac Pair Programming Task](https://notes.status.im/Jvd03lPKSMiDI_eo9Dq9xw)
- Communications: [Activist Event Manager](https://drive.google.com/file/d/1TsIbMduelr_TjbwfEcT-AnXnVco1GejC/view?usp=sharing)
- Recruitment: [Sourcing Task](https://docs.google.com/document/d/1ICiYpsvT6sh6akyM6RxQX1tu_D3tq3bVgLWEIpj1aOM/edit?usp=sharing)
- Pops: [People Ops Partner](https://docs.google.com/document/d/1nLFu6sQvfqCqfdlWP8kVTBzBDLTIZknNRc8FMCw9vrA/edit?usp=sharing)
## FAQs
Q: How long should candidates typically spend on the task?
A: We recommend 2-4 hours to avoid impacting the candidate's current job and any family commitments.
Q: How long should the task take to complete?
A: 1-week max (unless the candidate has let us know they have something that wont allow them to complete the task, ie. health conditions, family, personal, ect.)
Q: What happens if a candidate encounters issues during the task?
A: You can communicate with them via the discord chat created by the recruiter.
Q: Is there room for negotiation on compensation for exceptionally well-performed tasks?
A: No.
Q: What if I cant think of any tasks?
A: Then check out the tasks templates above as inspiration or/and think of a daily task someone in your team does that you would expect this candidate to be competent with, for example, in recruitment we would expect someone to show their competency & creativity sourcing candidates, so that is what the task is based around.
Q: My team doesn't have time to review every task, what do we do?
A: The number of tasks to review should be minimal as you dont need to send a task to every candidate, only the good ones that stand out as potential hires.
_If that is still too much, revert to a technical discussion, so long as youre confident you can accurately assess a candidate's suitability this way._
Vendored
+16 -21
View File
@@ -1,3 +1,6 @@
#!/usr/bin/env groovy
library 'status-jenkins-lib@v1.8.8'
pipeline {
agent { label 'linux' }
@@ -11,41 +14,33 @@ pipeline {
}
environment {
CNAME = 'contributors.status.im'
GIT_COMMITTER_NAME = 'status-im-auto'
GIT_COMMITTER_EMAIL = 'auto@status.im'
/* dev page settings */
DEV_SITE = 'dev-contributors.status.im'
DEV_HOST = 'jenkins@node-01.do-ams3.sites.misc.statusim.net'
SCP_OPTS = 'StrictHostKeyChecking=no'
}
stages {
stage('Build') {
steps {
sh 'mdbook build'
}
steps { script {
nix.shell('mdbook build')
jenkins.genBuildMetaJSON('book/build.json')
} }
}
stage('Publish Prod') {
when { expression { env.GIT_BRANCH ==~ /.*master/ } }
stage('Publish') {
steps {
sshagent(credentials: ['status-im-auto-ssh']) {
sh "ghp-import -p book"
}
}
}
stage('Publish Devel') {
when { expression { env.GIT_BRANCH ==~ /.*develop/ } }
steps {
sshagent(credentials: ['jenkins-ssh']) {
sh """
rsync -e 'ssh -o ${SCP_OPTS}' -r --delete book/. \
${env.DEV_HOST}:/var/www/${env.DEV_SITE}/
ghp-import \
-b ${deployBranch()} \
-c ${deployDomain()} \
-p book
"""
}
}
}
}
}
def isMasterBranch() { GIT_BRANCH ==~ /.*master/ }
def deployBranch() { isMasterBranch() ? 'deploy-master' : 'deploy-develop' }
def deployDomain() { isMasterBranch() ? 'contributors.status.im' : 'dev-contributors.status.im' }
+7 -5
View File
@@ -29,9 +29,11 @@ Will expose the built page under http://localhost:3000/.
# Continuous Integration
Two branches are built by [our Jenkins instance](https://ci.infra.status.im/):
* `master` branch is deployed to https://contributors.status.im/ by [CI](https://ci.infra.status.im/job/website/job/contributors.status.im/).
* `develop` branch is deployed to https://dev-contributors.status.im/ by [CI](https://ci.infra.status.im/job/website/job/dev-contributors.status.im/).
PRs should be made for `develop` branch and `master` should be [rebased](https://git-scm.com/book/en/v2/Git-Branching-Rebasing) on `develop` once changes are verified.
- [CI builds](https://ci.infra.status.im/job/website/job/contributors.status.im/) `master` and pushes to `deploy-master` branch, which is hosted at <https://contributors.status.im/>.
- [CI builds](https://ci.infra.status.im/job/website/job/dev-contributors.status.im/) `develop` and pushes to `deploy-develop` branch, which is hosted at <https://dev-contributors.status.im/>.
The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
Information about deployed build can be also found in `/build.json` available on the website.
Binary file not shown.
+2
View File
@@ -5,6 +5,8 @@ multilingual = false
src = "src"
title = "Status Contributors Guide"
[preprocessor.emojicodes]
[output.html]
cname = "contributors.status.im"
default-theme = "light"
+13 -1
View File
@@ -1 +1,13 @@
/* Placeholder for custom page-wide CSS. */
/* Hack to hide the last sub-element under "License" link in SUMMARY.md.
* Currently that's only "2023 Lead evaluation guide".
* Necessary due to lack of support for hidden chapters:
* https://github.com/rust-lang/mdBook/issues/1821
* https://github.com/rust-lang/mdBook/issues/2176 */
ol.chapter > li:not(.chapter-item):last-child {
visibility: hidden;
}
/* Smaller size of IFT logo. */
img[src="./images/IFT_logo.png"] {
width: 15em;
}
+15
View File
@@ -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
];
}
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
@@ -0,0 +1,38 @@
# 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.
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.
Please carefully read the following instructions to ensure a smooth and timely process:
1. When you need to request goods/services falling under the categories listed below, please raise a [request for goods/services](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4) in [SpiffWorkflow](https://prod.mod.spiff.status.im/).
- **Software & Licenses**: (new tools, apps, subscriptions, etc.)
- **Consulting fees**: (consultants, freelancers)
- **Other fees**: (bounties)
- **Events**: (rent, insurance, sponsorship, entertainment, etc.)
> For instructions on how to raise a request, please refer to this [guide](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a).
If you are unsure about the categories or how to proceed with your specific case, you can get in touch with the Finance team.
2. Your request will be reviewed by a Budget Owner (usually the Project Lead) and, where required, by the relevant Service Units. The approval process will be handled automatically. Please ensure that you provide all necessary details regarding your request, as these are crucial for the Project Leads and Service Units to review and make the necessary arrangements.
> Note: The [Approval strategy](https://www.notion.so/769ae660ac2240e9b1daf7b3ba4bb49c?v=ed50eb29a825492eab8623f9973d7886&pvs=4) for each request may vary based on several variables:
> - **Category/sub-category**: Different sets of approvers may be required based on the category/sub-category of the request. For example, PeopleOps partners need to review requests for learning & development but not for consulting fees or software & licenses.
> - **Amount**: In some cases, a simplified approval strategy may be triggered if the amount is below a certain threshold.
> - **Project**: The Budget Owner is determined based on the selected project in the request. If the Budget Owner is the one raising the request, the L2 Budget Owner will be required to provide approval.
> - **Requestor name**: The approval process ensures that Requestors cannot approve their own requests.
3. You can monitor the progress of the approval process in SpiffWorkflow. For instructions on how to check your process instances, please refer to this [guide](https://www.notion.so/Quick-start-user-guide-SpiffWorkflow-0e2dd1fbe3584a8981b3acb36834b2c2?pvs=4#caff0b729d2246dc8b80a30c274a7dd9).
4. To stay informed about the approval outcomes, please check your StatusApp Desktop notifications from the [SpiffWorkflow contact](https://join.status.im/u/zQ3shqpayoq1MeWZK8XkEsD6fECvnWzBZAPmV5DwgxnexkKgu). Reviewers may request additional information about your request, so please be prepared to address their questions.
> How to submit additional information - pls refer to this[ guide](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#307fa3bb9d4241da955aeeb6e534f21d).
5. Once your request is approved, you can proceed with the purchasing and payments. To access the approval history and other details regarding your request, please navigate to your request in SpiffWorkflow.
6. When Finance processes your payment requests or third-party invoices, they will check for approved requests in SpiffWorkflow. If there are no approved requests or if the amounts differ, they may request additional approval from the Budget Owner and Service Units.
If you are a Budget Owner or a member of the Service Units team, you may find the [report](https://superset.bi.status.im/superset/dashboard/p/BzMqY16qXGd/) useful.
+30
View File
@@ -0,0 +1,30 @@
# SpiffWorkflow
### What is SpiffWorkflow
SpiffWorkflow is a workflow engine which enables our organisation to define their processes in [BPMN format](https://www.ibm.com/cloud/blog/bpmn) (looks like a flowchart) and then allows the orchestration and execution of these processes within the platform. The workflow orchestration can be simple such as allowing multiple people to review and approve a request within the platform, or it could also be super complex orchestration integrated with multiple systems and driving a workflow between them. SpiffWorkflow has a simple interface for the end user to interact with and raise requests.
### When to use SpiffWorkflow
Most of the time, you will be using the platform to raise requests which need to be reviewed and approved. E.g. requesting a laptop, hardware/software, permission to travel etc. The full list of processes that are active in the platform can be found [here](https://www.notion.so/SpiffWorkflow-9873a17b6cb744ef996d860e27b774eb?pvs=4#59c2e4b668b046a6a3f2acefcaf5c37c).
### Getting setup with SpiffWorkflow
As a new joiner, you will have received an email in your status inbox from "[Logos.co](http://logos.co/) Keycloak" which will get you to set your password and OTP. You will have 5 days to action this otherwise the link in the email will expire. If this happens, please contact PeopleOps and they will send you a new email. Once you have logged in, let's make sure that you can receive notifications to your Status Desktop app.
1. Login to [SpiffWorkflow](http://prod.mod.spiff.status.im)
2. Go to “Start New+” and click “start” button on “Set up Status App (Desktop) notifications”
3. Follow the instructions and then accept the contact request from SpiffWorkflow. That's it.
You can read the full instructions with images [here](https://www.notion.so/0e2dd1fbe3584a8981b3acb36834b2c2?pvs=21).
### How to raise a request in SpiffWorkflow
1. On the home page of SpiffWorkflow, navigate to "Start New+". Here you will find all the processes which you have permission to start
2. Click "start" button on the process you wish to start. You will be redirected to a form which you can fill out and submit
If you are halfway through a process and are not sure what you need to fill in the field, you can come back to this process later. Just go down the bottom and "Save and Close". To come back to this process later, you can see this on your home page under "In Progress" -> "Started by me". To resume the process, click the "Go" button.
### Useful links
1. [SpiffWorkflow landing page](https://www.notion.so/SpiffWorkflow-9873a17b6cb744ef996d860e27b774eb)
2. [User guide](https://www.notion.so/0e2dd1fbe3584a8981b3acb36834b2c2?pvs=21)
+56
View File
@@ -0,0 +1,56 @@
# Superset
### Basics Tutorial
Superset is an open-source data exploration and visualization platform powered by Apache Superset. It provides a user-friendly interface for data analysts and business users to interact with their data and create interactive visualizations, charts, and dashboards. With Superset, users can connect to various data sources, including databases, and more, to explore and analyze their data in a visually appealing and intuitive manner. Superset offers a wide range of visualization options, such as bar charts, line charts, maps, and heatmaps, allowing users to gain valuable insights and make data-driven decisions. It also supports the use of filters and drill-down capabilities to dive deeper into the data. Overall, Superset empowers users to effectively explore and communicate their data through interactive and dynamic visualizations.
Step 1: Accessing Superset
- Open your web browser and enter the URL Superset is hosted. https://superset.bi.status.im/superset/welcome/
- Enter your Github username and password to log in to Superset. If this is your first time using Superset it will create a brand new user for you
- If this is your first time, you'll need access to dashboards you need. You can contact laloanaya through discord or at lalo@status.im to get access to these resources.
Step 2: Exploring the Superset Home Page
- After logging in, you'll be directed to the Superset home page.
- The home page contains a menu bar at the top and various sections with options to explore dashboards.
Step 3: Navigating the Menu Bar
- The menu bar at the top provides different options for managing and exploring data.
- Click on the "Dashboards" option in the menu bar to access the available dashboards.
Step 4: Viewing a Dashboard
- On the Dashboards page, you'll see a list of available dashboards.
- Click on the name of the dashboard you want to visualize.
Step 5: Interacting with Filters (if available)
- If the dashboard has filters, you can interact with them to refine the displayed data.
- Look for filter options on the dashboard interface, such as drop-downs, sliders, or text inputs.
- Select the desired options or adjust the filters as necessary.
Step 6: Exploring the Dashboard
- Once the filters are set (if applicable), explore the dashboard to view the visualizations.
- The dashboard will display various charts, graphs, and data visualizations relevant to the chosen topic.
Step 7: Analyzing the Dashboard
- Take time to analyze and interpret the visualizations on the dashboard.
- Pay attention to trends, patterns, and any insights the data may reveal.
- Use the interactive elements (if available) to drill down into specific data points or explore different dimensions.
Step 8: Navigating Between Dashboards (if applicable)
- If there are multiple dashboards available, you can navigate between them using the menu or designated links.
- Go back to the Dashboards page or use the provided navigation options to switch between different dashboards.
### Requesting Changes or New Dashboard
- If you need to request changes to an existing dashboard or create a new one, please reach out to Lalo Anaya.
- You can contact Lalo Anaya through Discord by sending a message to his username (laloanaya) or email him at [lalo@status.im](mailto:lalo@status.im).
- Clearly communicate your requirements, including the specific changes or details for the new dashboard you would like to create.
- Lalo will assist you in making the necessary updates or work with you to design and develop a new dashboard based on your needs.
That's it! You've now learned how to access Superset, navigate the home page, view dashboards, interact with filters (if available), explore the visualizations, and analyze the data presented on the dashboards. Enjoy exploring the insights provided by the visualizations! If you have questions or suggestions you can contact laloanaya through discord or at lalo@status.im
+5
View File
@@ -0,0 +1,5 @@
# Playbook
In this section, you will find information and guides on platforms, processes and frameworks we have at Status.
If you have any questions, please reach out to People Ops who can help navigate your questions.
+17 -5
View File
@@ -1,7 +1,7 @@
# Summary
- [Introduction](./introduction.md)
- [Welcome to Status](./welcome-to-status.md)
- [Welcome to Status](./welcome-to-IFT.md)
- [Our principles](./our-principles.md)
- [Status Core Contributors](./catalog.md)
- [Settling in](./settling-in/index.md)
@@ -9,13 +9,16 @@
- [Self-time management](./settling-in/self-time-management.md)
- [AFK FAQs](./settling-in/afk-faqs.md)
- [The trial period](./settling-in/the-trial-period.md)
- [Onboarding buddy](./settling-in/onboarding-buddy.md)
- [Evaluation Guide](./settling-in/2023-Self-Evaluation-Guide.md)
- [Your first day, week, month…](./settling-in/your-first-day-week-month.md)
- [Onboarding buddy](./settling-in/onboarding-buddy.md)
- [People Operations](./settling-in/people-operations.md)
- [Download Status Desktop](./settling-in/download-status-desktop.md)
- [Contributing to Status](./contributing-to-status/index.md)
- [Journey to your first contribution](./contributing-to-status/journey-to-your-first-contribution.md)
- [Value-creating Behaviours](./contributing-to-status/value-creating-behaviours.md)
- [Laptops and devices](./contributing-to-status/laptops-and-devices.md)
- [Collaboration](./contributing-to-status/collaboration.md)
- [Coworking allowance](./contributing-to-status/coworking-allowance.md)
- [Location independence](./contributing-to-status/location-independence.md)
- [Events and meetups](./contributing-to-status/events-and-meetups.md)
@@ -24,20 +27,29 @@
- [Referrals](./contributing-to-status/referrals.md)
- [Headspace](./contributing-to-status/headspace.md)
- [Fundamentals](./fundamentals/index.md)
- [Security guidelines](./fundamentals/security-guidelines.md)
- [Recommended reading](./fundamentals/essential-reading.md)
- [Security guidelines](./fundamentals/security-guidelines.md)
- [In case of a dispute](./fundamentals/In-case-of-a-dispute.md)
- [In case of emergency](./fundamentals/emergencies.md)
- [Code of Conduct](./fundamentals/code-of-conduct.md)
- [Contributor Privacy Policy](./fundamentals/contributor-privacy-policy.md)
- [In case of emergency](./fundamentals/emergencies.md)
- [Finance](./finance/index.md)
- [Getting paid](./finance/getting-paid.md)
- [Third-party invoices format](./finance/third-party-invoices-format.md)
- [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)
- [Team Lead Manual]()
- [Candidate Tasks](./Team-lead-manual/Candidate-Tasks.md)
*****
- [Contributing to the Contributors Guide](./contributing-to-this-guide.md)
- [License](./LICENSE.md)
<!-- # This is hidden using custom.css file. -->
- [2023 Lead evaluation guide](./Playbooks/2023-Lead-Evaluation-Guide.md)
BIN
View File
Binary file not shown.
@@ -0,0 +1,48 @@
## ✨ Lead Evaluation Guide
_This document is intended to be a supporting document to help Core Contributors complete the 2023 Lightweight Evaluation Process._
This guide has been created to assist you in providing constructive and meaningful feedback to Core Contributors regarding their impact on Status. The evaluation will be structured in two parts. The first section will have specific questions about the Core Contributors contribution, collaboration and autonomy. Following that, there will be a short answer section that will give you an opportunity to provide more detailed feedback about the Core Contributors in the team you lead.
**Writing Meaningful Feedback**
There are two questions in the evaluation process designed to be more freeform qualitative questions to give you the opportunity to provide specific feedback to the core contributors in your team - these are:
1. What is (at least) one thing the contributor does well?
2. What is (at least) the one thing the contributor could improve on?
With these questions, we suggest.
1. Provide clear and specific examples to support your feedback.
2. Focus on addressing behaviors, not personality traits, for objective and action-oriented feedback
3. Maintain a respectful and empathetic tone to ensure your contributors feel supported
There are a variety of frameworks and guides that are useful in helping write and deliver feedback. For more on giving feedback, please see [here](https://www.forbes.com/sites/forbeshumanresourcescouncil/2021/12/02/how-to-give-feedback-to-freelancers-contractors-and-remote-workers/?sh=d753b074d5b4).
Additionally, here are examples of effective and ineffective feedback for the Core Contributors in your team:
> 😃 _Effective:_
“Over the past year, the contributor has shown exceptional collaboration skills within our team. One particular instance to highlight was their collaboration skills during our recent project with Team X and Team Y. In this project, the contributor took the initiative to organize and lead discussions among the teams and consistently encouraged participation from others. The contributor helped to facilitate open conversations and create safe spaces for such collaboration which made a really positive impact on the projects success. We were able to make better and more informed decisions as a result of this (for example, as a result, we decided to prioritise feature z) - the contributor played a significant role in making this happen.”
> 😔 _Ineffective:_
“Excellent collaboration skills”.
**Quantitative Assessment**
Its important to approach the quantitative section of this process with fairness and objectivity. The expectation is that not all of your Core Contributors in your team will receive an “Outstanding” rating. Instead, the aim is to offer honest and well-balanced feedback that reflects each Core Contributors actual performance. Keep in mind that most Core Contributors will likely receive a “Meets Expectations” rating. This will ensure that our evaluations are realistic and meaningful.
**Rating Guide**
The evaluation process requires you to provide a rating of the Core Contributors in your team - please use the guidance below:
* **Does Not Meet Expectations:** Core Contributor consistently fails to meet role expectations.
* **Partially Meets Expectations:** Core Contributor sometimes meets role expectations but has room for improvement
* **Meets Expectations:** Core Contributor consistently meets expectations for their role - likely the majority of Core Contributors will fall into this category (its a good rating that demonstrates they are meeting our high expectations).
* **Exceeds Expectations:** Core Contributor consistently goes above and beyond what is expected in their role
* **Outstanding:** Core Contributor consistently has exceptional performance and contributions. Would expect this to be awarded to only a very small group of Core Contributors.
**Distribution of ratings**
Whilst theres no forced distribution of ratings, its natural to expect (with 200+ core contributors) well use the full scale of ratings. It is likely that most CCs will fall into the “meets expectations” category, but that we will also have some (a smaller amount) that are distributed in the higher, and lower, categories.
Please reach out to your People Ops Partner if you have any questions.
+101
View File
@@ -0,0 +1,101 @@
# Candidate Tasks in Recruitment
![skills-assessment](../images/skills-assessment.png)
## 1. What is a task:
It is a practical assessment to evaluate candidate skills.
## 2. Why do we use tasks in the hiring process?
We use them to:
- Get a better assessment beyond CVs, portfolios, github repos and interviews.
- Gain a deeper understanding of someone's abilities (technical & non-technical) for the role at hand.
- Give candidates a chance to showcase their working style & communication, its common to set up a Discord chat so the candidate & task reviewers can chat, ask/answer questions and also provide updates.
## 3. How to design a task
Step 1: Understand the role's requirements.
Step 2: Design a task that aligns with the expected output of the role.
Step 3: Clearly communicate task instructions, expectations, and deadline.
What does a good task look like:
- Has clear instructions & expectations
- Has a deadline thats realistic (usually 1 week is enough)
- Has a recommended timeframe in which to complete the task i.e 2-4hrs (this keeps all candidates 'fair' in terms of time dedicated to the task)
- Is aligned with the day-to-day responsibilities of the role
- It is tackling a real problem the team face, some teams use a bounties approach
Examples:
- UX/UI Designer: Create a mobile app prototype/feature based on the target audience.
- Sales: Create a presentation on selling a complex product to a potential client.
- Engineer: Assess problem-solving skills by tasking them with debugging code.
- Customer Support: A simulated chat interaction to assess their communication skills.
- Financial Analyst: Analyze an investment portfolio to gauge forecasting abilities.
- Content Writer: Create a blog post on a specified topic.
## 4. Time restrictions & compensation:
We want to see a glimpse of what they can do within the allocated time, this shouldnt be seen as their full potential since they are not integrated into the working styles of the team or the full context of the team.
A simple and effective approach is:
- A flat rate for completion of the task; ie. $200
- A set time allowing completing the task; ie. 2-4hrs (some teams have longer, rule of thumb is allow enough time for the task to be completed)
… The longer the task, the more time you/your team have to spend reviewing it
## 5. Materials for Candidates:
Ensure candidates have all the reference materials needed to perform and succeed on the task.
Examples:
- A digital marketer may need access to Google Analytics data.
- A data scientist may need to be provided a dataset and access to statistical software.
- A content creator may need a brand style guide and existing content for reference.
- A Mobile UI Engineer will need access to Figma
## 6. Evaluating Tasks:
Setting clear evaluation standards is important so everyone is assessed fairly and we dont let personal biases get in the way of hiring people who perform well during tasks. We should determine the criteria for task evaluation prior to seeing the first task submitted by a candidate.
Examples:
- Evaluate a coding task based on criteria like code quality, efficiency, and adherence to project requirements.
- Assess customer service interactions based on responsiveness, problem-solving, and professionalism.
- Evaluate a design task considering creativity, usability, and alignment with brand guidelines.
## 7. Effective Communication:
Maintain transparent and professional candidate communication.
- Clearly inform candidates of the evaluation timeline and when they can expect feedback.
- Use the Discord chat to interact with the candidate throughout their task
## 8. Feedback and Improvement:
Use candidate feedback to refine task instructions and evaluation criteria.
## 9. Sample Tasks:
- Engineering: [Vac Pair Programming Task](https://notes.status.im/Jvd03lPKSMiDI_eo9Dq9xw)
- Communications: [Activist Event Manager](https://drive.google.com/file/d/1TsIbMduelr_TjbwfEcT-AnXnVco1GejC/view?usp=sharing)
- Recruitment: [Sourcing Task](https://docs.google.com/document/d/1ICiYpsvT6sh6akyM6RxQX1tu_D3tq3bVgLWEIpj1aOM/edit?usp=sharing)
- Pops: [People Ops Partner](https://docs.google.com/document/d/1nLFu6sQvfqCqfdlWP8kVTBzBDLTIZknNRc8FMCw9vrA/edit?usp=sharing)
## FAQs
Q: How long should candidates typically spend on the task?
A: We recommend 2-4 hours to avoid impacting the candidate's current job and any family commitments.
Q: How long should the task take to complete?
A: 1-week max (unless the candidate has let us know they have something that wont allow them to complete the task, ie. health conditions, family, personal, ect.)
Q: What happens if a candidate encounters issues during the task?
A: You can communicate with them via the discord chat created by the recruiter.
Q: Is there room for negotiation on compensation for exceptionally well-performed tasks?
A: No.
Q: What if I cant think of any tasks?
A: Then check out the tasks templates above as inspiration or/and think of a daily task someone in your team does that you would expect this candidate to be competent with, for example, in recruitment we would expect someone to show their competency & creativity sourcing candidates, so that is what the task is based around.
Q: My team doesn't have time to review every task, what do we do?
A: The number of tasks to review should be minimal as you dont need to send a task to every candidate, only the good ones that stand out as potential hires.
_If that is still too much, revert to a technical discussion, so long as youre confident you can accurately assess a candidate's suitability this way._
+1
View File
@@ -0,0 +1 @@
+1 -1
View File
@@ -1,4 +1,4 @@
# Status Core Contributors
# IFT Core Contributors
Directory of Core Contributors
@@ -1,42 +1,30 @@
# 🎤 Events and meetups
As a Status core contributor, you may have the opportunity to speak at or attend external online or in-person events.
As a IFT core contributor, you may have the opportunity to speak at or attend external online or in-person events.
The community is an essential part of the Web3 ecosystem. Ecosystem, domain-specific, and internal events and meetups are networking and growth opportunities. And we strongly encourage you to be part of them!
Here you'll find helpful information to make the most out of organising, speaking, or attending events.
## What events does Status sponsor
## What events does IFT sponsor
Status will sponsor and cover the costs for any online or in-person event with a clear purpose. That means it must align with our company's strategy and goals. This includes, but is not limited to:
IFT will consider sponsoring and covering the costs for any online or in-person event with a clear purpose. That means it must align with IFT's strategy and goals. This includes, but is not limited to:
* Ecosystem events such as DevCon, ETH[city], ETHCC, Hackathons, blockchain weeks, etc.
* Domain-specific events for your role for career purposes.
* Events and meetups to promote Status to potential new core contributors.
* Events and meetups to promote IFT or our projects to potential new core contributors.
* Internal events and meetups to prepare a product/project launch or work together.
* Moderating or speaking opportunities related to Status.
* Moderating or speaking opportunities related to IFT.
> ✨ Remember that when you're at an event, you're an ambassador for Status project and everyone who shares our values. Don't forget that and spread the word! Who knows who's listening and might contribute to or join Status thanks to you 🙂
> ✨ Remember that when you're at an event, you're an ambassador for IFT projects and everyone who shares our values. Don't forget that and spread the word! You never know who's listening and might contribute to IFT thanks to you 🙂
> 💡Before attending an event, ask your Talent Partner to generate a QR code for the Status job page that you can share with anyone interested.
> 💡Before attending an event, ask your Talent Partner to generate a QR code for our job pages that you can share with anyone interested.
## How to communicate an event
## Once you have your travel details ready
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.
Submit your individual travel request via [SpiffWorkflow](https://prod.mod.spiff.status.im/).
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).
## If it falls outside your project's budget
Submit the request in the #travel-requests channel and tag (as cc) your project lead. From there, your project lead can give a simple 👍 to confirm the request makes sense or ask additional questions; and People Ops & Finance can ask any necessary questions or suggest adjustments.
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
## Related articles
+7 -7
View File
@@ -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 whats 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 whats 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-status/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!
@@ -10,7 +10,7 @@ Core contributors have the potential option of leasing devices from Status to en
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 can expense up to the below amount but just let your project lead know about your device purchasing plans.
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.
@@ -22,18 +22,19 @@ For each item we have defined a budget. Your spend will stay below the defined b
* Yubikey: you can reimburse one (approx USD 50)
* Ledger: you can reimburse one (approx USD 80)
> Most 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 speak to your project lead and People Partner and they 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**.
> 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 accordance with this section.
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. Let your project lead & People Partner know prior to purchasing the devices
2. Choose official or trusted vendors to buy your devices.
3. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
4. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
5. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
6. Enter into a leasing agreement with Status in respect of the device you have purchased.
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
@@ -43,11 +44,11 @@ Following the cessation or termination of your services to Status, you have the
* __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!
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, ping your People Partner.
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?__
@@ -4,7 +4,7 @@ Status is a fully remote, location-agnostic organisation meaning that we don
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.
However, we cannot cover the visa/work permit processing or relocation costs as we're location agnostic for work.
However, we will not cover the visa/work permit processing or relocation costs as we're location agnostic for work.
## What happens if I'm thinking about relocating
@@ -14,5 +14,5 @@ Get in touch with your People Partner to start the discussion about your relocat
If you need to indicate your working status/occupation details on a visa application, please contact your People Partner who can assist with the relevant information.
Please only refer to Status as your employer if the DE/CH entity formally employs you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.
You should only refer to DE/CH as your employer, if those entities formally employ you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.
@@ -6,9 +6,9 @@ Here you'll find helpful information to make your travel abroad experience more
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. If you don't have previous approval or haven't posted your travel plans yet, check out [Events and meetups](../contributing-to-status/events-and-meetups.md) before booking your trip.
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.
If the travel falls outside your project's budget, talk with your project lead about the event or meeting you're attending and [create a travel request](../contributing-to-status/events-and-meetups.md).
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
## Before travelling abroad:
@@ -31,7 +31,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 $75/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 $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/).
@@ -49,7 +49,7 @@ Don't go overboard with spending on bookings, food, and drinks. Keep accountabil
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.
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](../expense-reimbursements.md) for uploading your receipts in a compliant and timely manner to keep our finances healthy.
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.
## 🛩 Getting there
@@ -59,7 +59,7 @@ Usually, the earlier you plan your trip, the cheaper and better it's going to be
### Commuting rates and guidelines
* Sometimes it's more convenient to travel by train or bus within Europe. So keep that in mind as an option when you're looking at routes.
* We travel in economy class with carry-on luggage included. You can add one checked luggage for trips longer than 5 days or when you're carrying additional baggage for Status.
* We travel in economy class with carry-on luggage included. You can add one checked luggage for trips longer than 5 days or when you're carrying additional baggage for Status. For flights that are 12+ hours, premium economy is permitted but please ensure that the overall cost is still reasonable (if the price is more than 2x the economy price please do consider alternate options).
* For moving around, choose the most affordable ground transportation option. In some places, traffic is unpredictable, and public transport is more reliable. In others, car rental, and ride-sharing, such as Uber or local equivalents, are better to move from/to the airport and share the ride with others travelling with you.
> 💡 Pro-tip: in-flight entertainment might be limited. You might want to bring a book or download media, music, or documents offline beforehand. For some people, commutes are a great way to disconnect or do some reading or focus work.
@@ -97,3 +97,4 @@ International prepaid SIM cards:
* [Holafly](https://holafly.com)
* [Airalo](https://www.airalo.com/)
If you are a Budget Owner or a member of the Service Units team, you may find this [Travel report](https://superset.bi.status.im/superset/dashboard/p/Mgvrd5R3Z4Q/) useful.
@@ -1,17 +1,17 @@
# 🌟 Value-creating behaviours
## Focus
### Great
## 🧘 Focus
### Great
* Prioritising and deprioritising efforts correctly - most effort on the most important thing for Status continuance
* Translate theory into pragmatic decisions
* Find ways to increase revenue
### Not great
### Not great
* Spending huge amounts of time on lower priority work
* Getting sidetracked
## Good communication
### Great
## 🗣️ Good communication
### Great
* Explaining clearly and calmly in text/Discord/ Status app
* Asking questions and explanations
* Good technical documentation
@@ -20,15 +20,15 @@
* Asking for feedback, timely
* Showing empathy
### Not great
### Not great
* Giving feedback months later/out of context
* Not daring to give direct feedback, but being critical to others behind their backs
* Shipping things without seeking feedback
* Jerky, impatient remarks in writing
* Requests lacking context or clarity
## Collaboration with projects
### Great
## 🤝 Collaboration with projects
### Great
* Supporting project rituals
* Offering a hand/helping other core contributors
* Helping new core contributors adjust to the project
@@ -37,36 +37,36 @@
* Improving internal processes
* Flagging issues
### Not great
### Not great
* Going invisible
* Not documenting what youre working on
* Delaying others work
* Being late to meetings/project rituals
## Collaboration across other projects
### Great
## 🤝 Collaboration across other projects
### Great
* Cross-functional projects or ideas that can improve Status as a whole
* Reading/being active on channels outside of the immediate area of work
* Supporting with events/community
* Helping communication flow/easing misunderstandings
* Replying to questions from other core contributors outside your project
### Not great
### Not great
* Remaining silent when someone from outside your project asks a question that you could answer
* Relying on others in your project to communicate with folks outside your project.
* Not reaching out to somebody outside your project when their expertise could be useful.
## Proactiveness
### Great
### Great
* Picking up on things that need to happen, and jumping in to make them happen
* Looking outside of what weve always done, taking inspiration from the wider world
### Not great
### Not great
* Waiting for instructions at all times
* Raising issues without follow up action
## Productivity
### Great
## 💪 Productivity
### Great
* Being accountable and responsible for your own results.
* First things first - nail the basics of your role before branching out.
* Keeping a consistent level of effort
@@ -77,15 +77,14 @@
* Bursts of efficiency when is most needed or visible/barely coasting the rest of the time
* Getting sidetracked/spending excessive time on side ideas or projects/neglecting priorities.
## Visibility in (Ethereum) ecosystem
### Great
## 👀 Visibility in (Ethereum) ecosystem
### Great
* Speaking at events
* Being an ambassador
* Contributing to discussions on EIP and other ecosystem developments (Github, Discourse, Twitter, etc)
## Master own skill/speciality
### Great
## 🛠️ Master own skill/speciality
### Great
* Delivering your project or providing your services at the best of your ability
* Always be learning
* Striving for quality
+3 -1
View File
@@ -1,9 +1,11 @@
# 🚀 Contributing to this guide
Status' Contributors Guide is an open living repo built for you. The truth is Status evolves faster than it does the documentation. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit.
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.
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._
## 👾 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.
Binary file not shown.
+26 -8
View File
@@ -2,19 +2,23 @@
## How to get reimbursed for expenses?
You can request a reimbursement for reasonable expenses incurred on behalf of Status during the project's development. You can read about some of these expenses at:
You can request a reimbursement for reasonable expenses incurred on behalf of IFT during the project's development. You can read about some of these expenses at:
* [Computers and devices](../contributing-to-status/laptops-and-devices.md)
* [Events and meetups](../contributing-to-status/events-and-meetups.md)
* [Travelling for Status](../contributing-to-status/traveling-for-status.md)
* [Travelling for IFT](../contributing-to-status/travelling-for-status.md)
* [Essential reading](../fundamentals/essential-reading.md)
It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly. In order to get your expenses reimbursed correctly and in time you will need [Expensify](https://www.expensify.com/) to report and store the expense receipts, and add these expenses to your monthly invoice sent to `billing@statusm.im`.
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`
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.
### Account setup
@@ -26,7 +30,7 @@ If you dont have access to your account, please reach out to the Finance team
### Selecting the right policy
Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct Status entity and your invoicing currency.
Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct IFT entity and your invoicing currency.
![expensify-policy](../images/expensify-policy.png)
@@ -40,7 +44,7 @@ Go to the `Expense` tab on either the web or mobile apps to upload expenses manu
1. Make sure to fill or review all the fields as the scanning feature isn't always reliable. Pay special attention to amounts and currencies.
2. You should claim expenses using the date they incurred. For example: if the purchase happened on Jan 10th and you're uploading or requesting the reimbursement on Jan 14th, the correct expense date would be Jan 10th.
3. When paying for a group (i.e., a meal shared with other contributors from Status), please list all those in attendance in the `attendee's` field.
3. When paying for a group (i.e., a meal shared with other contributors from IFT), please list all those in attendance in the `attendee's` field.
4. Choose a category for your expense and add a detailed description of how's it business-related. Include information such as the trip it belongs to, who approved it, what budget it comes from, whether or not you've paid for other contributors (i.e., group meal), and any other data you consider relevant.
#### Example
@@ -66,6 +70,8 @@ Go to the `Expense` tab on either the web or mobile apps to upload expenses manu
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.
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.
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.
> ⚠️ Only **approved** expense reports should be included in the monthly contributor invoice.
@@ -78,7 +84,7 @@ Please follow these links if you need help with [creating expenses](https://comm
The finished and approved report from Expensify will show the total for each expense category. For example, if you have several costs in one category, Expensify will show the following:
![expensify-categories.jpg](https://people-ops.status.im/content/images/2021/08/Exp-3.png)
![expensify-categories.jpg](../images/2021/08/Exp-3.png)
Your invoice should only contain the total per category, not each expense item.
@@ -94,8 +100,20 @@ If you need to share the report with your accountant, you can download a PDF rep
## 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 Finance to review and approve expense claims as soon as they arrive. This means that the sooner you submit your expense claim, the sooner it will be reviewed by the Finance team.
Expense reimbursements are paid together with the monthly compensation invoice. If you have questions or concerns regarding the expense reimbursement date, please get in touch with the Finance team, and we'll be happy to help you with that.
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`.
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 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 #finance channel or through an email to `billing@status.im`.
+15 -18
View File
@@ -1,6 +1,6 @@
# 💰 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 get compensated correctly on time.
## Invoices due date
@@ -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:
* Status Holdings 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.
@@ -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 Status.
### Rate Calculation
@@ -90,26 +87,26 @@ For your first month (if being paid on an annual or monthly basis), please prora
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*
*Example: You joined IFT 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**
**Working days 2024**
| Month | Working days |
|:---:|:---:|
| January | 22 |
| February | 20 |
| March | 23 |
| April | 20 |
| January | 23 |
| February | 21 |
| March | 21 |
| April | 22 |
| May | 23 |
| June | 22 |
| July | 21 |
| August | 23 |
| June | 20 |
| July | 23 |
| August | 22 |
| September | 21 |
| October | 22 |
| November | 22 |
| December | 21 |
| October | 23 |
| November | 21 |
| December | 22 |
### Expense Reimbursements
+7 -18
View File
@@ -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
* Suppliers 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
+31
View File
@@ -0,0 +1,31 @@
# In case of a dispute
## Background
* While we hope that you may never have to run into this issue, and for the most part it is relatively exceptional, IFT, like any other organisation, faces the risk of entering into disputes, whether they are arising from internal or external events, within or outside of IFT control and with different types of counterparties, from service provides to (former) core contributors (“Counterparty”).
* Therefore we have developed this guidance for core contributors on how you can help prevent and mitigate potential disputes, protect IFT interests and how to best collaborate with Legal to resolve any disputes in the most peaceful and amicable manner possible.
## Guidance
#### When to involve Legal - the earlier, the better. However, please contact Legal immediately if:
* It is more than likely that IFT will fail to fulfil its obligation(s) towards a Counterparty or if IFT has already failed on its obligation(s) towards a Counterparty (doesnt 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 services acceptable use policy); or
* Breached confidentiality (e.g. a core contributor inadvertently shares confidential information with another third party that is not compliant with the contract).
* If a Counterparty claims that IFT is not fulfilling its obligations (whether this is accurate or not) or threatens legal action against IFT in this respect; or
* if a legal counsel or a law firm has taken over communications with IFT;
#### If any of the above takes place - the following should be observed:
* Follow good practices: Preserve all communications with the Counterparty, such as discord chats, emails, any social media chats (e.g. Telegram), calls and meeting notes.
## After you contact Legal:
* Do not let the Counterparty know you are involving Legal, (for example, do not include Legal in -cc to an email with a Counterparty) unless Legal has advised you to do so. In our experience, if a Counterparty becomes aware that Legal is being involved, it may escalate an already sensitive situation or unnecessarily provoke hostility.
* Communicate with the Counterparty only in consultation with Legal and other internal stakeholders as relevant, for example, your team lead.
* Any communication with the Counterparty must be screened and approved by Legal.
* Any strategy or potential proposals/compromises must also be discussed with Legal.
## After the dispute has been resolved:
* Rectify/Monitor - Legal and core contributors should continue to monitor for any potential signs that the dispute may resume or re-escalate and ensure that events or factors which led to the dispute have been adequately addressed (e.g. has IFT failure to perform an obligation now being rectified?)
* Lessons learned - Legal, core contributors, relevant team lead, and any other relevant internal stakeholders should form a “lessons learned” group to review the events and factors, which led up to the dispute and determine whether any changes to procedure or practices should be made to prevent or mitigate the chance of such a dispute arising again. Notes and conclusions should be well documented for future reference
+7 -6
View File
@@ -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.*
+4 -3
View File
@@ -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 harms 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 -2
View File
@@ -2,9 +2,11 @@
We encourage using some time to learn about things related to your tasks and our collective mission. Make your fellow project core contributors aware of you being on/offline and that the project's progress doesn't get hindered. Feel free to discuss it openly and agree on timing with everyone involved.
We offer an annual learning budget of USD 170 for each core contributor. You can use this budget towards things like books, conferences, or online courses. Speak with your project lead to request additional funding if needed.
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.
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.
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.
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 -1
View File
@@ -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.
+4 -4
View File
@@ -1,6 +1,6 @@
# 🔐 Security guidelines
Security is a priority at Status, and we'd like to thank you in advance for taking steps to secure your devices and online accounts.
Security is a priority at IFT, and we'd like to thank you in advance for taking steps to secure your devices and online accounts.
Here you'll find helpful links to resources to protect yourself and the organisation from attackers.
@@ -34,13 +34,13 @@ Here's Corey's Status Learn-Up session about [hardware wallets and best practice
## Password manager
Our password manager is [Bitwarden](https://bitwarden.com/). All organisational passwords should be kept and shared here. So if you plan to store a Status related password, or get access to platforms that require username/passwords/2fa, then it should all be shared using Bitwarden.
Our password manager is [Bitwarden](https://bitwarden.com/). All organisational passwords should be kept and shared here. So if you plan to store an IFT related password, or get access to platforms that require username/passwords/2fa, then it should all be shared using Bitwarden.
You can request an invite in #people-ops. By signing up with the organisation, you get the premium features and sign up with any email you like. That way, if you ever leave Status, you can take your password manager secrets with you, and you only lose access to Status related items.
You can request an invite in #people-ops. By signing up with the organisation, you get the premium features and sign up with any email you like. That way, if you ever leave the IFT, you can take your password manager secrets with you, and you only lose access to IFT related items.
## Security team
Learn more about Security @ Status at:
Learn more about Security @ IFT at:
* [Status Security](https://status.im/security/)
* [status-im/status-security](https://github.com/status-im/status-security)
Binary file not shown.

After

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 140 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 114 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 101 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 129 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 135 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 120 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 308 KiB

+6 -6
View File
@@ -1,11 +1,11 @@
# Introduction
![IFT_Logo](./images/IFT_logo.png)
Status is developing an open set of projects utilising peer-to-peer technologies that will facilitate peoples 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 dont 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.
+13 -18
View File
@@ -1,6 +1,6 @@
# 💠 Offboarding
Were sorry that youre 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! 🙌
Were sorry that youre 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
Wed 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 youd prefer that they post a general departure message on your behalf (this wont 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.
Wed like to be transparent with all core contributors when someone leaves the project. Please post a goodbye message, or let People Ops know if youd prefer that they post a general departure message on your behalf (this wont share any personal details, but will confirm that you are not going to be around, along with your expected last day). You may also want to ping fellow core contributors within other projects directly to let them know about your departure.
* ### Forthcoming Status travel
* ### Forthcoming IFT travel
Should you have any future Status-sponsored travel/conference arrangements in place, please cancel them and obtain a refund for your bookings if possible. Expenses will only be reimbursed for non-refundable travel bookings. Cancellation fees (where incurred) can be added to your final expense report for reimbursement (please attach proof of payment).
Should you have any future IFT-sponsored travel/conference arrangements in place, please cancel them and obtain a refund for your bookings if possible. Expenses will only be reimbursed for non-refundable travel bookings. Cancellation fees (where incurred) can be added to your final expense report for reimbursement (please attach proof of payment).
* ### Private keys
If you have any hardware related to Status wallets or bank accounts (e.g. Ledgers, Trezors, security keys), mnemonic phrases, or any other resource granting you access to (or control of) Status's funds (fiat or crypto), please make arrangements with @finance to return them.
If you have any hardware related to IFT wallets or bank accounts (e.g. Ledgers, Trezors, security keys), mnemonic phrases, or any other resource granting you access to (or control of) IFT's funds (fiat or crypto), please make arrangements with @finance to return them.
* ### Access to organisation-wide tools
@@ -58,7 +58,7 @@ There's a lot to do before you leave so please follow the steps assigned to you
* ### Passwords
Please clear your password vault of any passwords relating to tools/software licences belonging to Status.
Please clear your password vault of any passwords relating to tools/software licences belonging to IFT.
* ### Tools
@@ -70,16 +70,11 @@ There's a lot to do before you leave so please follow the steps assigned to you
* ### Letter of reference
Well be happy to provide a letter of reference confirming your contributions to Status. Should you ever need a reference letter, please email people-ops@status.im at any time, and well get a letter to you within 5 - 10 working days.
* ### Holiday (For employees only)
You are entitled to be paid out for any accrued but not taken holidays. Your People Partner will calculate the payout amount and pay this out to you with your final payment. You can choose to take any accrued holiday as time off during your notice period - if you want to do so, please book the time in BambooHR.
Well 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 well 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.
Well share your feedback with relevant project members we think may benefit from hearing your reflections. If youd prefer the conversation to be 100% private, thats totally ok - just let us know what youre comfortable with being shared further.
@@ -88,11 +83,11 @@ Feel free to prepare notes in advance, or send us your feedback async if youd
## Coming back?
Were open to working with former core contributors again, and wed 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 -1
View File
@@ -21,7 +21,7 @@ We strive for complete openness and symmetry of information within the organisat
### VI. Openness
The software we create is a public good. It is made available via a free and open source licence, for anyone to share, modify and benefit from. We believe in permission-less participation.
### VII. decentralisation
### VII. Decentralization
We minimise centralization across both the software and the organisation itself. In other words, we maximise the number of physical computers composing the network, and maximise the number of individuals who have control over the system(s) we are building.
### VIII. Inclusivity
@@ -0,0 +1,57 @@
## 💥 Self Evaluation Guide
_This document is intended to be a supporting document to help you complete the 2023 lightweight Self Evaluation Process._
### Writing a self-evaluation
Think of a self-evaluation as an opportunity to reflect and deep dive into your contributions and impact on Status projects. Its 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 thats okay.
Aim to provide a balanced evaluation of yourself based on the following attributes and questions.
### Question Specific Guidance
**<span style="text-decoration:underline;">Contribution</span>**
* Think about specific projects, tasks or initiatives you have worked on, highlighting your contributions, accomplishments, and the outcomes of your efforts.
* Be specific and provide measurable results whenever possible, such as deadlines met, efficiency improvements, and projects delivered.
**<span style="text-decoration:underline;">Collaboration</span>**
* Assess your ability to work collaboratively with Core Contributor both within your team and other projects.
* Describe instances where you effectively collaborated or supported others in achieving common goals.
* Acknowledge any areas where you faced challenges in collaboration and how you dealt with it.
**<span style="text-decoration:underline;">Autonomy</span>**
* Discuss your level of autonomy as a Core Contributor and how you've taken initiative.
* Share examples of times when you proactively identified opportunities for improvement or took on additional responsibilities.
* Highlight your ability to work independently and make decisions when needed.
**<span style="text-decoration:underline;">What is (at least) one thing you do well?</span>**
* Be specific, highlighting your impact on your team/project.
* Identify your strengths, skills or qualities that you excel at in your role.
* Discuss a time when / if you exceeded expectations or made a significant positive impact on your team or project.
* Highlight any skills or areas where youve shown improvement and growth over time.
* Take time to look back on your 1:1s and retros to help you identify past accomplishments
**<span style="text-decoration:underline;">What is (at least) one thing you could improve upon?</span>**
* Be self-aware. Acknowledge areas where you may have room for improvement.
* Focus on something specific and prioritise a meaningful commitment to improvements.
* Offer context for the areas you want to improve. Explain why these aspects are important and how they impact your role.
**Next steps:**
Please log into Lattice, and complete your self-evaluation.
Reach out to your People Ops Partner if you have any questions.
+49 -5
View File
@@ -1,8 +1,8 @@
# 🔕 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?
@@ -14,17 +14,61 @@ If youre 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).
### 🐣 Are you or your partner / spouse expecting a new baby?
First of all, congratulations! 🎊 We're happy about the new addition(s) to your family!
#### Introduction
First of all, congratulations! 🎊 We're happy about the new addition(s) to your family! 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 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 contributors service agreement must still be in effect prior to and for the duration of their unavailability.
#### Duration
Core contributors who become new parents, either through birth or adoption, are able to make use of the following periods of unavailability and this arrangement:
* Primary caregiver - A period of up to sixteen (16) weeks
* Secondary caregiver - A period of up to three (3) weeks
The primary caregiver is typically the person who takes on the main responsibility for looking after a child. This role is often most commonly associated with the mother. The primary caregiver is typically the one who spends the most time with the child, providing daily care, nurturing, and meeting their needs. They will have given up work to carry out their duties.
The secondary caregiver is the person who takes on a supporting role in caregiving responsibilities. The secondary caregiver provides assistance and support to the primary caregiver, sharing the responsibilities of caring for the child.
#### Standby compensation
While traditional parental leave policies are not available to independent contractors, 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.
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.
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 contributors 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 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, we will not provide any additional standby compensation.
#### How do I make use of this arrangement?
As soon as you're comfortable sharing the news, please ping your People Partner to chat about your plans. It'd be great if you could give as much notice as you can.
We'll do our best to accommodate you and we'll discuss with you each request on a case by case basis, involving your project lead, taking into account your needs, your planned unavailability and deliverables.
Well further discuss the above arrangement with you, your period of unavailability and also share with you some additional paperwork to formalise this arrangement.
#### Conclusion
At IFT, 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 IFT with the necessary readiness and capacity.
### 📒 What happens to any SNT distributions?
+148
View File
@@ -0,0 +1,148 @@
# Downloading and installing Status Desktop
## 📥 Downloading Status
First you will need to download the latest release of Status Desktop from [here](https://github.com/status-im/status-desktop/releases).
### 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 “Im 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.
_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 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 CCs to recognise you).
## 🤝 How to join the Status Internal community
1. Click the “Start chat” button
![download-status-desktop-1](../images/download-status-desktop-1.png)
2. This will open a view to start a new chat. Enter Iuris chat key into the “To:” field:
Iuris chat key - zQ3shdkzLTUx5s98XRXenEwPX56RhxGWjLnihcx79dhNai4wW
![download-status-desktop-2](../images/download-status-desktop-2.png)
3. Status should recognize this key is Iuris and immediately open the "send contact request" dialog so you can send a contact request to him:
![download-status-desktop-3-updated](../images/download-status-desktop-3-updated.png)
4. Send Iuri a nice message while youre at it, something that will make him smile. Also let Iuri know youre a new IFT core contributor 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, youre now friends with Iuri), he will send you a link to Status Internal community (if you dont receive this link, ping @helium__ on Discord).
![download-status-desktop-6](../images/download-status-desktop-6.png)
7. Click the “Go to Community” button:
![download-status-desktop-7](../images/download-status-desktop-7.png)
8. This will take you to the Status Internal community. Click the “Request to join” button:
![download-status-desktop-8](../images/download-status-desktop-8.png)
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:
![download-status-desktop-9](../images/download-status-desktop-9.png)
10. Youve 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).
![download-status-desktop-10](../images/download-status-desktop-10.png)
11. Once Iuri has accepted your request, the Status Internal community will automatically unlock and youll 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.
![download-status-desktop-11](../images/download-status-desktop-11.png)
12. Go to the “Settings” section in Status Desktop by clicking on the cog wheel in the left hand navigation bar:
![download-status-desktop-12](../images/download-status-desktop-12.png)
13. Select “Advanced” in the settings menu:
![download-status-desktop-13](../images/download-status-desktop-13.png)
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.
Its really important that all CCs do this so that we can monitor Waku v2s reliability as part of this dogfooding effort.
![download-status-desktop-14](../images/download-status-desktop-14.png)
15. Congrats, you are now a Status user, as well as a IFT core contributor 🎉
Now lets 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, dont forget to read the list of “Known bugs” below, otherwise you wont 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).
## 👋 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 core contributors 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 IFT core contributors' 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!
## 🐞 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 “Ive experienced this bug” and add any additional information (if any) from your experience thats not already in the bug report.
Dont 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 cant see a bug report that matches the issue youve 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.
- What is currently incorrectly happening, and what you think is supposed to happen.
- Screenshots are always useful. If you are set up to make screencasts, a screencast of you reproducing the bug is always appreciated.
And thats it, if you follow these steps youve written a highly descriptive and informative bug report thats 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 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.
+2 -6
View File
@@ -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, its 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
Were 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, dont rush, and spend time in your first few weeks really connecting with the people youre 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, dont rush, and spend time in your first few weeks really connecting with the people youre working with, as they are the best and most up-to-date sources of information and support that exist.
+18 -18
View File
@@ -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, well 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, well 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!
+7 -5
View File
@@ -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!
@@ -10,14 +10,14 @@ DM us anytime :) Well also be checking in with you from time to time too, to
### 🎉 Make Status 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.
Well keep asking you how we can improve, and we welcome your feedback at any time.
## Who we are...
- Head of People Operations: Jonathan Barker (aka JB)
- People Partners: Terry Tobin & Riccardo Caselli
- People Partners: Terry Tobin & Melanie Davis
- Talent Partners: Pepper Lea, Maya Krumova, Catia Sousa & Angel Gutierrez
### People Partners
@@ -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, were 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.
+3 -3
View File
@@ -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 theyre 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.
Monthly and project rate contractors can invoice IFT for their agreed amounts in months when they take time off. 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
+4 -4
View File
@@ -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. Youll have a couple of initial deliverables scoped out by the project lead to ease your onboarding and get you going. Beyond that, youre 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. Youll have a couple of initial deliverables scoped out by the project lead to ease your onboarding and get you going. Beyond that, youre 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: Youre 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, youre 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 youd 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, youre the kind of person that finds this autonomy thrilling, and not too terrifying.
Ideally, youre the kind of person who finds this autonomy thrilling and not too terrifying.
+6 -6
View File
@@ -11,10 +11,10 @@ There's no prescriptive recipe for success in your first few months but the foll
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.
@@ -28,7 +28,7 @@ Some great topics to cover are:
- 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 @@ Its 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!
+76
View File
@@ -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 projects 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 Vacs 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.
-32
View File
@@ -1,32 +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.
Check out Jarrad & Carls [State of Us podcast](https://our.status.im/state-of-us/), and catch up on our awesome [blog posts](https://blog.status.im/we-are-the-state-of-us-2f0fc20b26d3).
## 🔭 Vision
Today, when you are first exposed to the Status app, you might see an instant messenger and wonder, "What's the big deal? After all, its 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 Founders 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 Jarrads Letter to Status →](https://our.status.im/a-letter-to-status-context-strategy/)