Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0cacde1ed8 | ||
|
|
f86a3f3ec5 | ||
|
|
21a8bf5076 | ||
|
|
11de05f541 | ||
|
|
2c41051fba | ||
|
|
42074876f1 | ||
|
|
70d8d4cd7e | ||
|
|
59609ee6e9 | ||
|
|
3e9592c6dc | ||
|
|
082ac348ac | ||
|
|
2b8c2bd346 | ||
|
|
56aea721c3 | ||
|
|
fecb2110ab | ||
|
|
cd887f7f92 | ||
|
|
39c54ee535 | ||
|
|
7ed6b71f48 | ||
|
|
30be5a1943 | ||
|
|
cde847bf93 | ||
|
|
2c182a6f84 | ||
|
|
3efc572a5a | ||
|
|
176c4d4abb | ||
|
|
3c3bb07a5a | ||
|
|
50e736e642 | ||
|
|
2bd1d5174d | ||
|
|
f86e0cf448 | ||
|
|
21d09fed33 | ||
|
|
b874d8f125 | ||
|
|
bf6d5adf64 | ||
|
|
cf2705749b | ||
|
|
46589730b1 | ||
|
|
9cd499a6f4 | ||
|
|
65c8f3c3e7 | ||
|
|
3b3f5eae90 | ||
|
|
ed862792e1 | ||
|
|
be9ed3d5a8 | ||
|
|
146b21168b | ||
|
|
51a7f438fa | ||
|
|
8cac0f4dd3 | ||
|
|
b213830ec5 | ||
|
|
a007d7413e | ||
|
|
6c51db0401 | ||
|
|
bb73218cfa | ||
|
|
df7d6d0842 | ||
|
|
b0db8c2681 | ||
|
|
5935250b58 | ||
|
|
61c7fd5ba0 | ||
|
|
5f17e946fd | ||
|
|
8c8bfd7be2 | ||
|
|
64eb1e926a | ||
|
|
4e24edeec8 | ||
|
|
16c8ac3647 | ||
|
|
8b82696c3f | ||
|
|
bddfb3af47 | ||
|
|
94e8c497d1 | ||
|
|
4402e8c7d8 | ||
|
|
816a836f1b | ||
|
|
bf3b9e5ed5 | ||
|
|
15dcfdab1e | ||
|
|
d2bd55e5d5 | ||
|
|
8d8f160b55 | ||
|
|
eedf912f78 | ||
|
|
774bbbb1cc | ||
|
|
66d3b7f72e | ||
|
|
4b7f90bff0 | ||
|
|
a0e332c085 | ||
|
|
efb0a4958c | ||
|
|
2243b2ddec | ||
|
|
5fa0a8105a | ||
|
|
c68ba57ca6 | ||
|
|
af5a2aa06c | ||
|
|
58c23d5fd8 | ||
|
|
268bb5e55c | ||
|
|
a1711c1d99 | ||
|
|
9426c2ef9b | ||
|
|
430e6657fb | ||
|
|
ab0809fd6c | ||
|
|
2b6f692942 | ||
|
|
5ac3abbc5e | ||
|
|
460c955645 | ||
|
|
c7e7e7ef36 | ||
|
|
a569fb9962 | ||
|
|
9af94ab661 | ||
|
|
6efd74f681 | ||
|
|
5c59de78c1 | ||
|
|
fe837b6714 | ||
|
|
312b317b0f | ||
|
|
858d159a3c | ||
|
|
1eb8ce9df7 | ||
|
|
4ee6d046c4 | ||
|
|
7559b20b46 | ||
|
|
87816b26a7 | ||
|
|
3f78467a23 | ||
|
|
548afa4c02 | ||
|
|
0953137447 | ||
|
|
d26fa096be | ||
|
|
bae23db736 | ||
|
|
15063b98a6 | ||
|
|
512344b04e | ||
|
|
45afe54716 | ||
|
|
d9095a08e8 | ||
|
|
50aca555ba | ||
|
|
c5b900c570 | ||
|
|
ad40b39473 | ||
|
|
a08a14afa0 | ||
|
|
6a3b8d1722 | ||
|
|
055e599a37 | ||
|
|
07536552dd | ||
|
|
1aa77148d4 | ||
|
|
ffd88c4db6 | ||
|
|
70531b7ed5 | ||
|
|
68daf68da5 | ||
|
|
53994e9efd | ||
|
|
ca5278fe6d | ||
|
|
7790c835ff | ||
|
|
48cae73897 | ||
|
|
3600b494e8 | ||
|
|
4b1c1a2ca9 | ||
|
|
664b3455a7 | ||
|
|
59dbb82ed8 | ||
|
|
d971636eb5 | ||
|
|
09dd9536b6 | ||
|
|
87fc2e415a | ||
|
|
a77d42dc99 | ||
|
|
fe99b105d2 | ||
|
|
1db61074ea | ||
|
|
a98685cb74 | ||
|
|
7d9a7cb258 | ||
|
|
e24987433c | ||
|
|
893d75beda | ||
|
|
c117853e7e | ||
|
|
124b2d034c | ||
|
|
1bcc66a72f | ||
|
|
2c2336245a | ||
|
|
71c1bebb74 | ||
|
|
4693d8e661 | ||
|
|
0ce703ab28 | ||
|
|
c1d663afec | ||
|
|
5f422cfbcd | ||
|
|
ab47794120 | ||
|
|
6c792ee929 | ||
|
|
b2c46f0197 | ||
|
|
b47ca38713 | ||
|
|
b727fc12f7 | ||
|
|
22bd2e5e19 | ||
|
|
dc27c025bb | ||
|
|
c657e47392 | ||
|
|
b67508e426 | ||
|
|
5d782fbdd3 | ||
|
|
ed12e4cbd7 | ||
|
|
da203099d8 | ||
|
|
865cf5ae8d | ||
|
|
8d1cd5abb2 | ||
|
|
5acc6e4269 | ||
|
|
bfcc47b9f3 | ||
|
|
7bb8a02118 | ||
|
|
e7a764a4e5 | ||
|
|
6182c2969d | ||
|
|
3fd2084d04 | ||
|
|
64b3bb1344 | ||
|
|
18ae4e2fac | ||
|
|
ffe816cc09 | ||
|
|
55f23ac516 | ||
|
|
d995e41b7d | ||
|
|
55b0484dff | ||
|
|
18b472f655 | ||
|
|
7b0c70e0d6 | ||
|
|
f9a43e03fd | ||
|
|
4ebd7acee4 | ||
|
|
0c885d10ca | ||
|
|
e849b8e915 | ||
|
|
9cf4b7a2b6 | ||
|
|
dc37b801a5 | ||
|
|
63903227da | ||
|
|
4232e2aca7 | ||
|
|
12d1d9183a | ||
|
|
4655afbb08 | ||
|
|
f55ddaa503 | ||
|
|
1b9166b4cb | ||
|
|
15baec2330 | ||
|
|
b6388d133f | ||
|
|
9e13e86f6e | ||
|
|
2627971de8 | ||
|
|
15eda018c3 | ||
|
|
6afaf28328 | ||
|
|
0d03aec66a | ||
|
|
61d8298425 | ||
|
|
6c93d9638f | ||
|
|
3aa1b29bc0 | ||
|
|
5e9cc776e8 | ||
|
|
c7051841d6 | ||
|
|
e151f6fc11 | ||
|
|
b24b48ad92 | ||
|
|
36445ee2b3 | ||
|
|
972f55b38d | ||
|
|
56ea24e4b3 | ||
|
|
de5351449c | ||
|
|
326691da9d | ||
|
|
11d220ba29 | ||
|
|
c148d8b4d4 | ||
|
|
8b0831378e | ||
|
|
4f7547f29d | ||
|
|
4be21e63d6 | ||
|
|
da603b1809 | ||
|
|
ca7da7d1b6 | ||
|
|
4997bbb1b3 | ||
|
|
83b85bf2ec | ||
|
|
599cf0bb46 | ||
|
|
81d622f081 | ||
|
|
e56f37a08d | ||
|
|
8fb1273bcb | ||
|
|
2c9089e8dc | ||
|
|
7240cfb29d | ||
|
|
28311bef1d | ||
|
|
89312c13c7 | ||
|
|
f334f0816e | ||
|
|
b06d31906b | ||
|
|
45ae3195d5 | ||
|
|
5bdd0602be | ||
|
|
bdc3d45717 | ||
|
|
09121fd419 | ||
|
|
46ccf7a1f4 | ||
|
|
b312fbadd1 | ||
|
|
16216aecfe | ||
|
|
175ac74c42 | ||
|
|
ce427fc471 | ||
|
|
4299bf664f | ||
|
|
4a29ffd658 | ||
|
|
de5beca1b4 | ||
|
|
29ed1b66b1 | ||
|
|
8fae2d4f39 | ||
|
|
1c3b994d1c | ||
|
|
d3bb6e63fe | ||
|
|
6eaaaa14be | ||
|
|
6611c8757b | ||
|
|
166ba68ea3 | ||
|
|
b8ece3bc05 | ||
|
|
663529d5aa | ||
|
|
75a25d5cf1 | ||
|
|
bc32bd938b | ||
|
|
b405ad5f15 | ||
|
|
1ea2d85ed4 | ||
|
|
fcd930e170 | ||
|
|
ab94712ba6 | ||
|
|
e6174bfd4b | ||
|
|
bc0ddd77b4 | ||
|
|
e5766822e1 | ||
|
|
1a1bdd87bd | ||
|
|
3788f444b8 | ||
|
|
506eb757f3 | ||
|
|
49e338f38b | ||
|
|
84a0eb77b2 | ||
|
|
34e2d56daa | ||
|
|
66e33cfd29 | ||
|
|
50bf653569 | ||
|
|
daf24ec26a | ||
|
|
0aa90a7c72 | ||
|
|
c591077158 | ||
|
|
b1c477d25e | ||
|
|
3f6cb58553 | ||
|
|
459c800750 | ||
|
|
6dcb188375 | ||
|
|
afbc215fa1 | ||
|
|
cba89335c3 | ||
|
|
2d5202eaee | ||
|
|
9917fa41fd | ||
|
|
a495465654 | ||
|
|
0d8a4e9224 | ||
|
|
70a738ab5d | ||
|
|
53e19cd3e8 | ||
|
|
0950c1d224 | ||
|
|
c80a17b61f | ||
|
|
18a9951670 | ||
|
|
7dbd8b1c40 | ||
|
|
533c4ae582 | ||
|
|
95d5dc53c9 | ||
|
|
eacd3b62b8 | ||
|
|
09e3cd8f2d | ||
|
|
9ba81a5901 | ||
|
|
841f314c7a | ||
|
|
7a447b99e4 | ||
|
|
60507babce | ||
|
|
59e2604d0f | ||
|
|
13915d6dc2 | ||
|
|
bfccadd05d | ||
|
|
881ff066f1 | ||
|
|
d4a9b23c03 | ||
|
|
bfa06a573f | ||
|
|
5bc7c8d123 | ||
|
|
b4f802f6cd | ||
|
|
ac9ad28937 | ||
|
|
c44f890235 | ||
|
|
1d56af6ea4 | ||
|
|
4cdd3f3bcd | ||
|
|
3495a36789 | ||
|
|
8297945aee | ||
|
|
988854ca0e | ||
|
|
2cd73688f6 | ||
|
|
071cc7787f | ||
|
|
5e981430b7 | ||
|
|
d5d68cb6ed | ||
|
|
5fac33649a | ||
|
|
2fe3de51db | ||
|
|
b1dd03153c | ||
|
|
867527aec9 | ||
|
|
ab6bf04528 | ||
|
|
44286a2562 | ||
|
|
07aed45102 | ||
|
|
2f73c5448f | ||
|
|
60acbe3dfa | ||
|
|
15315b0eb6 | ||
|
|
e00e9209c1 | ||
|
|
95d80f40ca | ||
|
|
e856954ccc | ||
|
|
673eff9c41 | ||
|
|
547bff4c76 | ||
|
|
cec924bb8f | ||
|
|
7e9f2c2088 | ||
|
|
772f148b10 | ||
|
|
424179b3c3 | ||
|
|
9a9fb858d8 | ||
|
|
1d2ac7ae53 | ||
|
|
cf66b9ef55 | ||
|
|
eaa5b30d2a | ||
|
|
a2824bbdbb | ||
|
|
42af929233 | ||
|
|
6d96d7042c | ||
|
|
d22735ec6d | ||
|
|
787103ddf9 | ||
|
|
1be111dc3f | ||
|
|
e97c4baa12 | ||
|
|
7194053076 | ||
|
|
e071cc88df | ||
|
|
3edd821540 | ||
|
|
aab4c715b9 | ||
|
|
2f0496add6 | ||
|
|
7739cd6864 | ||
|
|
b033bb257c | ||
|
|
65a0123344 | ||
|
|
dd26bb7115 | ||
|
|
5a738efe6b | ||
|
|
257a18b274 | ||
|
|
dfb5f53440 | ||
|
|
dc322665ef | ||
|
|
68e5a21cfd | ||
|
|
fe84b85722 | ||
|
|
99f608ba3c | ||
|
|
dacbf1f92a | ||
|
|
6b31226958 | ||
|
|
c823928fbb | ||
|
|
87b84e2877 | ||
|
|
e4f6d4297b | ||
|
|
9cc4586bff | ||
|
|
783f95a58d | ||
|
|
e7b447e048 | ||
|
|
1b67a7f41f | ||
|
|
4af8111619 | ||
|
|
3e4fc939a9 | ||
|
|
340fe8c400 | ||
|
|
05a9eab0b4 | ||
|
|
2f21043e9e | ||
|
|
003ab11cc1 | ||
|
|
d199b0e653 | ||
|
|
8bafdf2979 | ||
|
|
5c9ac0043d | ||
|
|
5fc97f0475 | ||
|
|
312b53271f | ||
|
|
12ec46eba8 | ||
|
|
3845716d4b | ||
|
|
36a3c1ff79 | ||
|
|
74e0a52b9c | ||
|
|
226861f595 | ||
|
|
2dd11859d7 | ||
|
|
e2efd06558 | ||
|
|
d17a122e45 | ||
|
|
0a48ad7acb | ||
|
|
2ef05c5d92 | ||
|
|
8cd4504e36 | ||
|
|
aa88d9828b | ||
|
|
f7d6c01b27 | ||
|
|
df638c8394 | ||
|
|
c68815acef | ||
|
|
576fe43146 | ||
|
|
d0e00f5fa0 | ||
|
|
dd8bac1ea6 | ||
|
|
2644ccc411 | ||
|
|
413224754e | ||
|
|
0aead53fbb | ||
|
|
5784a9d3ca | ||
|
|
cdab20d8ae | ||
|
|
18b6649af7 | ||
|
|
cf185e439f | ||
|
|
58cf2235cc | ||
|
|
16b7da64f6 | ||
|
|
2c7b52b10a | ||
|
|
cdd89f004f | ||
|
|
145c446e94 | ||
|
|
46f374031b | ||
|
|
cee663060d | ||
|
|
5f337cf668 | ||
|
|
a190cd046b | ||
|
|
6328b18bc7 | ||
|
|
08f5fdfea8 | ||
|
|
681f8b4367 | ||
|
|
cbf5937f9f | ||
|
|
de2accfb8d | ||
|
|
fe5e9bbfa6 | ||
|
|
8980c468a0 | ||
|
|
940619ffec | ||
|
|
747940c42a | ||
|
|
5cdfb44cb8 | ||
|
|
ecf1185ee0 | ||
|
|
90ade50397 | ||
|
|
76a6160960 | ||
|
|
0b0fcd54e4 | ||
|
|
5eee1dc8c0 | ||
|
|
ca5b1748dd | ||
|
|
76327483cb | ||
|
|
392f28c09a | ||
|
|
6afcec309c | ||
|
|
4aca0bc34f | ||
|
|
8f7fbbf4b4 | ||
|
|
1a6f1b06c7 | ||
|
|
61d7bb3ab7 | ||
|
|
add791f7f2 | ||
|
|
522699e3fe | ||
|
|
c099ce1d37 | ||
|
|
56619dc3a0 | ||
|
|
e4a2cb3190 | ||
|
|
b0db29a9c6 | ||
|
|
3c5aeb1cbc | ||
|
|
21683f68d3 | ||
|
|
8c91ac97a2 | ||
|
|
82fd785c92 | ||
|
|
c65ee8b07e | ||
|
|
637f25b921 | ||
|
|
12f00e58ee | ||
|
|
1952ad42ab | ||
|
|
3e019b248c | ||
|
|
244268f67b | ||
|
|
b3b6f0d3ec | ||
|
|
5e81ab1b6d | ||
|
|
74465abe52 | ||
|
|
47f1b6c950 | ||
|
|
4dcb19e514 | ||
|
|
377f2d3c4f | ||
|
|
d3ee5b9c39 | ||
|
|
79d995d8e1 | ||
|
|
5bb7e805cf | ||
|
|
778bd3b052 | ||
|
|
4d911f8a57 | ||
|
|
fc2032a4b4 | ||
|
|
148274550b | ||
|
|
ccbe87667b | ||
|
|
8c9aa5e5f8 | ||
|
|
11c2f215de | ||
|
|
4f463722c2 | ||
|
|
5e4f240350 | ||
|
|
406068ef53 | ||
|
|
10e04a8664 | ||
|
|
83e676ddfb | ||
|
|
f560bc14ed | ||
|
|
c3e7e3817b | ||
|
|
14dce09cc6 | ||
|
|
1cd48bc797 | ||
|
|
d5d1fc6a26 | ||
|
|
857d5c486c | ||
|
|
bba15064ef | ||
|
|
70a9de6286 | ||
|
|
15b33584ff | ||
|
|
5194b8fc30 | ||
|
|
6a1d035853 | ||
|
|
630de1c9db | ||
|
|
e96103d928 | ||
|
|
6fa001b33e | ||
|
|
fad763b1ea | ||
|
|
7e5010405d | ||
|
|
c2f2843472 | ||
|
|
5bfdcf71fe | ||
|
|
4e08c45b67 | ||
|
|
b0abaaeff1 | ||
|
|
d42ae434c5 | ||
|
|
08188f3a89 | ||
|
|
6d6b67be91 | ||
|
|
439eaeadbe | ||
|
|
f06cfc0f71 | ||
|
|
87e559d71f | ||
|
|
7f4f55f837 | ||
|
|
4084e3b767 | ||
|
|
42a740a91d | ||
|
|
86a7f49f0f | ||
|
|
8b16fc24e5 | ||
|
|
0359e38c87 | ||
|
|
d082104072 | ||
|
|
bab14a7bcc | ||
|
|
b0986e0d9f | ||
|
|
7c110b5591 | ||
|
|
d69dc0bd30 | ||
|
|
3e46b4182e | ||
|
|
9ede39c0c1 | ||
|
|
0df79df377 | ||
|
|
94b99d17b3 | ||
|
|
60bb1cec9c | ||
|
|
7ccb3c1aca | ||
|
|
12980570f2 | ||
|
|
bd7e34e3f7 | ||
|
|
2581bc01f4 | ||
|
|
017ea6a611 | ||
|
|
746a2c196b | ||
|
|
96887ae32d | ||
|
|
1bdabc633f | ||
|
|
91c69d98c9 | ||
|
|
41b89f9c50 | ||
|
|
7847324b9c | ||
|
|
c2e976f8ee | ||
|
|
2d03b0326d | ||
|
|
f24acc4a21 | ||
|
|
8f1b7ef6c1 | ||
|
|
6fb966270b | ||
|
|
64bb81a9af | ||
|
|
ff41b596f3 | ||
|
|
89214a4929 | ||
|
|
241159a2e0 | ||
|
|
fac6697b66 | ||
|
|
9bd447bb94 | ||
|
|
7bde6fd5ca | ||
|
|
4812eeda1c | ||
|
|
7a566d7219 | ||
|
|
304f7cae0f | ||
|
|
d7a5a66218 | ||
|
|
fe00dc81b4 | ||
|
|
736c51c2d9 | ||
|
|
5e91631038 | ||
|
|
77070fba0c | ||
|
|
3c68e5a846 | ||
|
|
f84bdba561 | ||
|
|
0e62ad3b17 | ||
|
|
5c34bd0ba9 | ||
|
|
0430460e17 | ||
|
|
6468b3d8fd | ||
|
|
3f9820c7c7 | ||
|
|
62b799366a | ||
|
|
ac67929653 | ||
|
|
05d9021302 | ||
|
|
51820c0ae2 | ||
|
|
a0dd07f780 | ||
|
|
a85944ee4c | ||
|
|
ec827367fe | ||
|
|
d6854c89a3 | ||
|
|
99a3d7c756 | ||
|
|
d8b5f66cb5 | ||
|
|
cd50310ec1 | ||
|
|
9b4ba088dc | ||
|
|
44eca5c2bf | ||
|
|
f862c64017 | ||
|
|
00dc0e51d9 | ||
|
|
289aebf7e9 | ||
|
|
92f51e3f63 | ||
|
|
2e03409bab | ||
|
|
85928a75da | ||
|
|
dd58d8b5b8 | ||
|
|
c2b7d76849 | ||
|
|
c64a767d72 | ||
|
|
9f6e808989 | ||
|
|
3eb4f88770 | ||
|
|
867827e070 | ||
|
|
a4cd76ecb1 | ||
|
|
f6b4eaecc8 | ||
|
|
1d1deeab73 | ||
|
|
d8b2c02e87 | ||
|
|
e2905ef6fe | ||
|
|
246e328a05 | ||
|
|
659005f552 | ||
|
|
c8aa87bae2 | ||
|
|
4fda84b7cb | ||
|
|
2fcc84b637 | ||
|
|
9db3b1eb4d | ||
|
|
396acb9ea1 | ||
|
|
18182fdf8c | ||
|
|
5ac69d57e2 | ||
|
|
42fd3b0957 | ||
|
|
7b8ce782ec | ||
|
|
c0e3da4b2f | ||
|
|
bcaebf5fab | ||
|
|
9c0ebe9fbb | ||
|
|
2a0376852b | ||
|
|
2f45328120 | ||
|
|
2cfe3d9ad0 | ||
|
|
c7e60b0a74 | ||
|
|
1c1711fa6e | ||
|
|
b3310d8ff4 | ||
|
|
a6e261a831 | ||
|
|
b229688dc8 | ||
|
|
6622270339 | ||
|
|
96aa94414e | ||
|
|
239925df1e | ||
|
|
b0dc71a456 | ||
|
|
6d8251d42a | ||
|
|
d77ef30991 | ||
|
|
6799c6aff1 | ||
|
|
e0bcf0089d | ||
|
|
434e5c6ea1 | ||
|
|
b8133d09f3 | ||
|
|
abc8a1e100 | ||
|
|
34e4121469 | ||
|
|
473a4c0785 | ||
|
|
52f9576bf2 | ||
|
|
83c71e6034 | ||
|
|
fabf60d8a8 | ||
|
|
0f0559a6c5 | ||
|
|
48bb11762c | ||
|
|
243283f5df | ||
|
|
e90cd180ee | ||
|
|
0c24e96e82 | ||
|
|
79326681cd | ||
|
|
7f79644844 | ||
|
|
7eaed5aae2 | ||
|
|
cc70084dba | ||
|
|
beb4d92697 | ||
|
|
d9cad8f78f | ||
|
|
fbf8740a7b | ||
|
|
362baced4c | ||
|
|
93cd7e4a89 | ||
|
|
6d94faf29c | ||
|
|
3c258bd965 | ||
|
|
b0b4d06168 | ||
|
|
9e05c8470f | ||
|
|
06a8f2f41e | ||
|
|
9bf0d794db | ||
|
|
eb12d1dda4 | ||
|
|
2b6adceebe | ||
|
|
a4305e864e | ||
|
|
0facf1be00 | ||
|
|
15e4d5ef88 | ||
|
|
ad03c70c0c | ||
|
|
8d1c1c960a | ||
|
|
5dec1841c8 | ||
|
|
5c9308a25f |
@@ -1 +1,3 @@
|
||||
book
|
||||
|
||||
.DS_Store
|
||||
|
||||
@@ -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 = 'handbook.status.im'
|
||||
GIT_COMMITTER_NAME = 'status-im-auto'
|
||||
GIT_COMMITTER_EMAIL = 'auto@status.im'
|
||||
/* dev page settings */
|
||||
DEV_SITE = 'dev-handbook.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.free.technology' : 'dev-contributors.free.technology' }
|
||||
|
||||
@@ -0,0 +1,437 @@
|
||||
Attribution-NonCommercial-ShareAlike 4.0 International
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons Corporation ("Creative Commons") is not a law firm and
|
||||
does not provide legal services or legal advice. Distribution of
|
||||
Creative Commons public licenses does not create a lawyer-client or
|
||||
other relationship. Creative Commons makes its licenses and related
|
||||
information available on an "as-is" basis. Creative Commons gives no
|
||||
warranties regarding its licenses, any material licensed under their
|
||||
terms and conditions, or any related information. Creative Commons
|
||||
disclaims all liability for damages resulting from their use to the
|
||||
fullest extent possible.
|
||||
|
||||
Using Creative Commons Public Licenses
|
||||
|
||||
Creative Commons public licenses provide a standard set of terms and
|
||||
conditions that creators and other rights holders may use to share
|
||||
original works of authorship and other material subject to copyright
|
||||
and certain other rights specified in the public license below. The
|
||||
following considerations are for informational purposes only, are not
|
||||
exhaustive, and do not form part of our licenses.
|
||||
|
||||
Considerations for licensors: Our public licenses are
|
||||
intended for use by those authorized to give the public
|
||||
permission to use material in ways otherwise restricted by
|
||||
copyright and certain other rights. Our licenses are
|
||||
irrevocable. Licensors should read and understand the terms
|
||||
and conditions of the license they choose before applying it.
|
||||
Licensors should also secure all rights necessary before
|
||||
applying our licenses so that the public can reuse the
|
||||
material as expected. Licensors should clearly mark any
|
||||
material not subject to the license. This includes other CC-
|
||||
licensed material, or material used under an exception or
|
||||
limitation to copyright. More considerations for licensors:
|
||||
wiki.creativecommons.org/Considerations_for_licensors
|
||||
|
||||
Considerations for the public: By using one of our public
|
||||
licenses, a licensor grants the public permission to use the
|
||||
licensed material under specified terms and conditions. If
|
||||
the licensor's permission is not necessary for any reason--for
|
||||
example, because of any applicable exception or limitation to
|
||||
copyright--then that use is not regulated by the license. Our
|
||||
licenses grant only permissions under copyright and certain
|
||||
other rights that a licensor has authority to grant. Use of
|
||||
the licensed material may still be restricted for other
|
||||
reasons, including because others have copyright or other
|
||||
rights in the material. A licensor may make special requests,
|
||||
such as asking that all changes be marked or described.
|
||||
Although not required by our licenses, you are encouraged to
|
||||
respect those requests where reasonable. More considerations
|
||||
for the public:
|
||||
wiki.creativecommons.org/Considerations_for_licensees
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
|
||||
Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree
|
||||
to be bound by the terms and conditions of this Creative Commons
|
||||
Attribution-NonCommercial-ShareAlike 4.0 International Public License
|
||||
("Public License"). To the extent this Public License may be
|
||||
interpreted as a contract, You are granted the Licensed Rights in
|
||||
consideration of Your acceptance of these terms and conditions, and the
|
||||
Licensor grants You such rights in consideration of benefits the
|
||||
Licensor receives from making the Licensed Material available under
|
||||
these terms and conditions.
|
||||
|
||||
|
||||
Section 1 -- Definitions.
|
||||
|
||||
a. Adapted Material means material subject to Copyright and Similar
|
||||
Rights that is derived from or based upon the Licensed Material
|
||||
and in which the Licensed Material is translated, altered,
|
||||
arranged, transformed, or otherwise modified in a manner requiring
|
||||
permission under the Copyright and Similar Rights held by the
|
||||
Licensor. For purposes of this Public License, where the Licensed
|
||||
Material is a musical work, performance, or sound recording,
|
||||
Adapted Material is always produced where the Licensed Material is
|
||||
synched in timed relation with a moving image.
|
||||
|
||||
b. Adapter's License means the license You apply to Your Copyright
|
||||
and Similar Rights in Your contributions to Adapted Material in
|
||||
accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. BY-NC-SA Compatible License means a license listed at
|
||||
creativecommons.org/compatiblelicenses, approved by Creative
|
||||
Commons as essentially the equivalent of this Public License.
|
||||
|
||||
d. Copyright and Similar Rights means copyright and/or similar rights
|
||||
closely related to copyright including, without limitation,
|
||||
performance, broadcast, sound recording, and Sui Generis Database
|
||||
Rights, without regard to how the rights are labeled or
|
||||
categorized. For purposes of this Public License, the rights
|
||||
specified in Section 2(b)(1)-(2) are not Copyright and Similar
|
||||
Rights.
|
||||
|
||||
e. Effective Technological Measures means those measures that, in the
|
||||
absence of proper authority, may not be circumvented under laws
|
||||
fulfilling obligations under Article 11 of the WIPO Copyright
|
||||
Treaty adopted on December 20, 1996, and/or similar international
|
||||
agreements.
|
||||
|
||||
f. Exceptions and Limitations means fair use, fair dealing, and/or
|
||||
any other exception or limitation to Copyright and Similar Rights
|
||||
that applies to Your use of the Licensed Material.
|
||||
|
||||
g. License Elements means the license attributes listed in the name
|
||||
of a Creative Commons Public License. The License Elements of this
|
||||
Public License are Attribution, NonCommercial, and ShareAlike.
|
||||
|
||||
h. Licensed Material means the artistic or literary work, database,
|
||||
or other material to which the Licensor applied this Public
|
||||
License.
|
||||
|
||||
i. Licensed Rights means the rights granted to You subject to the
|
||||
terms and conditions of this Public License, which are limited to
|
||||
all Copyright and Similar Rights that apply to Your use of the
|
||||
Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
j. Licensor means the individual(s) or entity(ies) granting rights
|
||||
under this Public License.
|
||||
|
||||
k. NonCommercial means not primarily intended for or directed towards
|
||||
commercial advantage or monetary compensation. For purposes of
|
||||
this Public License, the exchange of the Licensed Material for
|
||||
other material subject to Copyright and Similar Rights by digital
|
||||
file-sharing or similar means is NonCommercial provided there is
|
||||
no payment of monetary compensation in connection with the
|
||||
exchange.
|
||||
|
||||
l. Share means to provide material to the public by any means or
|
||||
process that requires permission under the Licensed Rights, such
|
||||
as reproduction, public display, public performance, distribution,
|
||||
dissemination, communication, or importation, and to make material
|
||||
available to the public including in ways that members of the
|
||||
public may access the material from a place and at a time
|
||||
individually chosen by them.
|
||||
|
||||
m. Sui Generis Database Rights means rights other than copyright
|
||||
resulting from Directive 96/9/EC of the European Parliament and of
|
||||
the Council of 11 March 1996 on the legal protection of databases,
|
||||
as amended and/or succeeded, as well as other essentially
|
||||
equivalent rights anywhere in the world.
|
||||
|
||||
n. You means the individual or entity exercising the Licensed Rights
|
||||
under this Public License. Your has a corresponding meaning.
|
||||
|
||||
|
||||
Section 2 -- Scope.
|
||||
|
||||
a. License grant.
|
||||
|
||||
1. Subject to the terms and conditions of this Public License,
|
||||
the Licensor hereby grants You a worldwide, royalty-free,
|
||||
non-sublicensable, non-exclusive, irrevocable license to
|
||||
exercise the Licensed Rights in the Licensed Material to:
|
||||
|
||||
a. reproduce and Share the Licensed Material, in whole or
|
||||
in part, for NonCommercial purposes only; and
|
||||
|
||||
b. produce, reproduce, and Share Adapted Material for
|
||||
NonCommercial purposes only.
|
||||
|
||||
2. Exceptions and Limitations. For the avoidance of doubt, where
|
||||
Exceptions and Limitations apply to Your use, this Public
|
||||
License does not apply, and You do not need to comply with
|
||||
its terms and conditions.
|
||||
|
||||
3. Term. The term of this Public License is specified in Section
|
||||
6(a).
|
||||
|
||||
4. Media and formats; technical modifications allowed. The
|
||||
Licensor authorizes You to exercise the Licensed Rights in
|
||||
all media and formats whether now known or hereafter created,
|
||||
and to make technical modifications necessary to do so. The
|
||||
Licensor waives and/or agrees not to assert any right or
|
||||
authority to forbid You from making technical modifications
|
||||
necessary to exercise the Licensed Rights, including
|
||||
technical modifications necessary to circumvent Effective
|
||||
Technological Measures. For purposes of this Public License,
|
||||
simply making modifications authorized by this Section 2(a)
|
||||
(4) never produces Adapted Material.
|
||||
|
||||
5. Downstream recipients.
|
||||
|
||||
a. Offer from the Licensor -- Licensed Material. Every
|
||||
recipient of the Licensed Material automatically
|
||||
receives an offer from the Licensor to exercise the
|
||||
Licensed Rights under the terms and conditions of this
|
||||
Public License.
|
||||
|
||||
b. Additional offer from the Licensor -- Adapted Material.
|
||||
Every recipient of Adapted Material from You
|
||||
automatically receives an offer from the Licensor to
|
||||
exercise the Licensed Rights in the Adapted Material
|
||||
under the conditions of the Adapter's License You apply.
|
||||
|
||||
c. No downstream restrictions. You may not offer or impose
|
||||
any additional or different terms or conditions on, or
|
||||
apply any Effective Technological Measures to, the
|
||||
Licensed Material if doing so restricts exercise of the
|
||||
Licensed Rights by any recipient of the Licensed
|
||||
Material.
|
||||
|
||||
6. No endorsement. Nothing in this Public License constitutes or
|
||||
may be construed as permission to assert or imply that You
|
||||
are, or that Your use of the Licensed Material is, connected
|
||||
with, or sponsored, endorsed, or granted official status by,
|
||||
the Licensor or others designated to receive attribution as
|
||||
provided in Section 3(a)(1)(A)(i).
|
||||
|
||||
b. Other rights.
|
||||
|
||||
1. Moral rights, such as the right of integrity, are not
|
||||
licensed under this Public License, nor are publicity,
|
||||
privacy, and/or other similar personality rights; however, to
|
||||
the extent possible, the Licensor waives and/or agrees not to
|
||||
assert any such rights held by the Licensor to the limited
|
||||
extent necessary to allow You to exercise the Licensed
|
||||
Rights, but not otherwise.
|
||||
|
||||
2. Patent and trademark rights are not licensed under this
|
||||
Public License.
|
||||
|
||||
3. To the extent possible, the Licensor waives any right to
|
||||
collect royalties from You for the exercise of the Licensed
|
||||
Rights, whether directly or through a collecting society
|
||||
under any voluntary or waivable statutory or compulsory
|
||||
licensing scheme. In all other cases the Licensor expressly
|
||||
reserves any right to collect such royalties, including when
|
||||
the Licensed Material is used other than for NonCommercial
|
||||
purposes.
|
||||
|
||||
|
||||
Section 3 -- License Conditions.
|
||||
|
||||
Your exercise of the Licensed Rights is expressly made subject to the
|
||||
following conditions.
|
||||
|
||||
a. Attribution.
|
||||
|
||||
1. If You Share the Licensed Material (including in modified
|
||||
form), You must:
|
||||
|
||||
a. retain the following if it is supplied by the Licensor
|
||||
with the Licensed Material:
|
||||
|
||||
i. identification of the creator(s) of the Licensed
|
||||
Material and any others designated to receive
|
||||
attribution, in any reasonable manner requested by
|
||||
the Licensor (including by pseudonym if
|
||||
designated);
|
||||
|
||||
ii. a copyright notice;
|
||||
|
||||
iii. a notice that refers to this Public License;
|
||||
|
||||
iv. a notice that refers to the disclaimer of
|
||||
warranties;
|
||||
|
||||
v. a URI or hyperlink to the Licensed Material to the
|
||||
extent reasonably practicable;
|
||||
|
||||
b. indicate if You modified the Licensed Material and
|
||||
retain an indication of any previous modifications; and
|
||||
|
||||
c. indicate the Licensed Material is licensed under this
|
||||
Public License, and include the text of, or the URI or
|
||||
hyperlink to, this Public License.
|
||||
|
||||
2. You may satisfy the conditions in Section 3(a)(1) in any
|
||||
reasonable manner based on the medium, means, and context in
|
||||
which You Share the Licensed Material. For example, it may be
|
||||
reasonable to satisfy the conditions by providing a URI or
|
||||
hyperlink to a resource that includes the required
|
||||
information.
|
||||
3. If requested by the Licensor, You must remove any of the
|
||||
information required by Section 3(a)(1)(A) to the extent
|
||||
reasonably practicable.
|
||||
|
||||
b. ShareAlike.
|
||||
|
||||
In addition to the conditions in Section 3(a), if You Share
|
||||
Adapted Material You produce, the following conditions also apply.
|
||||
|
||||
1. The Adapter's License You apply must be a Creative Commons
|
||||
license with the same License Elements, this version or
|
||||
later, or a BY-NC-SA Compatible License.
|
||||
|
||||
2. You must include the text of, or the URI or hyperlink to, the
|
||||
Adapter's License You apply. You may satisfy this condition
|
||||
in any reasonable manner based on the medium, means, and
|
||||
context in which You Share Adapted Material.
|
||||
|
||||
3. You may not offer or impose any additional or different terms
|
||||
or conditions on, or apply any Effective Technological
|
||||
Measures to, Adapted Material that restrict exercise of the
|
||||
rights granted under the Adapter's License You apply.
|
||||
|
||||
|
||||
Section 4 -- Sui Generis Database Rights.
|
||||
|
||||
Where the Licensed Rights include Sui Generis Database Rights that
|
||||
apply to Your use of the Licensed Material:
|
||||
|
||||
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
|
||||
to extract, reuse, reproduce, and Share all or a substantial
|
||||
portion of the contents of the database for NonCommercial purposes
|
||||
only;
|
||||
|
||||
b. if You include all or a substantial portion of the database
|
||||
contents in a database in which You have Sui Generis Database
|
||||
Rights, then the database in which You have Sui Generis Database
|
||||
Rights (but not its individual contents) is Adapted Material,
|
||||
including for purposes of Section 3(b); and
|
||||
|
||||
c. You must comply with the conditions in Section 3(a) if You Share
|
||||
all or a substantial portion of the contents of the database.
|
||||
|
||||
For the avoidance of doubt, this Section 4 supplements and does not
|
||||
replace Your obligations under this Public License where the Licensed
|
||||
Rights include other Copyright and Similar Rights.
|
||||
|
||||
|
||||
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
|
||||
|
||||
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
|
||||
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
|
||||
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
|
||||
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
|
||||
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
|
||||
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
|
||||
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
|
||||
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
|
||||
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
|
||||
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
|
||||
|
||||
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
|
||||
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
|
||||
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
|
||||
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
|
||||
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
|
||||
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
|
||||
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
|
||||
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
|
||||
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided
|
||||
above shall be interpreted in a manner that, to the extent
|
||||
possible, most closely approximates an absolute disclaimer and
|
||||
waiver of all liability.
|
||||
|
||||
|
||||
Section 6 -- Term and Termination.
|
||||
|
||||
a. This Public License applies for the term of the Copyright and
|
||||
Similar Rights licensed here. However, if You fail to comply with
|
||||
this Public License, then Your rights under this Public License
|
||||
terminate automatically.
|
||||
|
||||
b. Where Your right to use the Licensed Material has terminated under
|
||||
Section 6(a), it reinstates:
|
||||
|
||||
1. automatically as of the date the violation is cured, provided
|
||||
it is cured within 30 days of Your discovery of the
|
||||
violation; or
|
||||
|
||||
2. upon express reinstatement by the Licensor.
|
||||
|
||||
For the avoidance of doubt, this Section 6(b) does not affect any
|
||||
right the Licensor may have to seek remedies for Your violations
|
||||
of this Public License.
|
||||
|
||||
c. For the avoidance of doubt, the Licensor may also offer the
|
||||
Licensed Material under separate terms or conditions or stop
|
||||
distributing the Licensed Material at any time; however, doing so
|
||||
will not terminate this Public License.
|
||||
|
||||
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
|
||||
License.
|
||||
|
||||
|
||||
Section 7 -- Other Terms and Conditions.
|
||||
|
||||
a. The Licensor shall not be bound by any additional or different
|
||||
terms or conditions communicated by You unless expressly agreed.
|
||||
|
||||
b. Any arrangements, understandings, or agreements regarding the
|
||||
Licensed Material not stated herein are separate from and
|
||||
independent of the terms and conditions of this Public License.
|
||||
|
||||
|
||||
Section 8 -- Interpretation.
|
||||
|
||||
a. For the avoidance of doubt, this Public License does not, and
|
||||
shall not be interpreted to, reduce, limit, restrict, or impose
|
||||
conditions on any use of the Licensed Material that could lawfully
|
||||
be made without permission under this Public License.
|
||||
|
||||
b. To the extent possible, if any provision of this Public License is
|
||||
deemed unenforceable, it shall be automatically reformed to the
|
||||
minimum extent necessary to make it enforceable. If the provision
|
||||
cannot be reformed, it shall be severed from this Public License
|
||||
without affecting the enforceability of the remaining terms and
|
||||
conditions.
|
||||
|
||||
c. No term or condition of this Public License will be waived and no
|
||||
failure to comply consented to unless expressly agreed to by the
|
||||
Licensor.
|
||||
|
||||
d. Nothing in this Public License constitutes or may be interpreted
|
||||
as a limitation upon, or waiver of, any privileges and immunities
|
||||
that apply to the Licensor or You, including from the legal
|
||||
processes of any jurisdiction or authority.
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons is not a party to its public
|
||||
licenses. Notwithstanding, Creative Commons may elect to apply one of
|
||||
its public licenses to material it publishes and in those instances
|
||||
will be considered the “Licensor.” The text of the Creative Commons
|
||||
public licenses is dedicated to the public domain under the CC0 Public
|
||||
Domain Dedication. Except for the limited purpose of indicating that
|
||||
material is shared under a Creative Commons public license or as
|
||||
otherwise permitted by the Creative Commons policies published at
|
||||
creativecommons.org/policies, Creative Commons does not authorize the
|
||||
use of the trademark "Creative Commons" or any other trademark or logo
|
||||
of Creative Commons without its prior written consent including,
|
||||
without limitation, in connection with any unauthorized modifications
|
||||
to any of its public licenses or any other arrangements,
|
||||
understandings, or agreements concerning use of licensed material. For
|
||||
the avoidance of doubt, this paragraph does not form part of the
|
||||
public licenses.
|
||||
|
||||
Creative Commons may be contacted at creativecommons.org.
|
||||
@@ -1,24 +1,39 @@
|
||||
# Description
|
||||
|
||||
This repository is the source for https://handbook.status.im/.
|
||||
This repository is the source for https://contributors.free.technology/.
|
||||
|
||||
It is built using [mdBook](https://rust-lang.github.io/mdBook/).
|
||||
|
||||
# Development
|
||||
|
||||
### GitHub
|
||||
|
||||
The simplest way to make changes is by [editing files on GitHub](https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files) and [creating Pull Requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
|
||||
|
||||
A simple alternative to using the GitHub Web UI is using their [Desktop Application](https://desktop.github.com/).
|
||||
|
||||
### Local Build
|
||||
|
||||
Clone repository locally using [Git](https://git-scm.com/):
|
||||
```
|
||||
git clone https://github.com/status-im/contributors.free.technology.git
|
||||
```
|
||||
You will need to [install mdBook](https://github.com/rust-lang/mdBook#installation).
|
||||
|
||||
To start a server that also builds the page use:
|
||||
```
|
||||
cd contributors.free.technology
|
||||
mdbook serve
|
||||
```
|
||||
Will expose the built page under http://localhost:3000/.
|
||||
|
||||
# Continuous Integration
|
||||
|
||||
Two branches are built by [our Jenkins instance](https://ci.status.im/):
|
||||
|
||||
* `master` is deployed to https://handbook.status.im/ by [CI](https://ci.status.im/job/website/job/handbook.status.im/)
|
||||
* `develop` is deployed to https://dev-handbook.status.im/ by [CI](https://ci.status.im/job/website/job/dev-handbook.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.free.technology/) `master` and pushes to `deploy-master` branch, which is hosted at <https://contributors.free.technology/>.
|
||||
- [CI builds](https://ci.infra.status.im/job/website/job/dev-contributors.free.technology/) `develop` and pushes to `deploy-develop` branch, which is hosted at <https://dev-contributors.free.technology/>.
|
||||
|
||||
The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
|
||||
|
||||
Information about deployed build can be also found in `/build.json` available on the website.
|
||||
|
||||
@@ -3,12 +3,14 @@ authors = ["Jakub Sokołowski"]
|
||||
language = "en"
|
||||
multilingual = false
|
||||
src = "src"
|
||||
title = "Status Contributors Guide"
|
||||
title = "IFT Contributors Guide"
|
||||
|
||||
[preprocessor.emojicodes]
|
||||
|
||||
[output.html]
|
||||
cname = "handbook.status.im"
|
||||
cname = "contributors.free.technology"
|
||||
default-theme = "light"
|
||||
path = "book/"
|
||||
additional-css = ["custom.css"]
|
||||
git-repository-url = "https://github.com/status-im/handbook.status.im"
|
||||
git-repository-url = "https://github.com/status-im/contributors.free.technology"
|
||||
git-branch = "master"
|
||||
|
||||
@@ -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;
|
||||
}
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
{
|
||||
source ? builtins.fetchTarball {
|
||||
url = "https://github.com/NixOS/nixpkgs/archive/614b4613980a522ba49f0d194531beddbb7220d3.tar.gz";
|
||||
sha256 = "sha256:1kipdjdjcd1brm5a9lzlhffrgyid0byaqwfnpzlmw3q825z7nj6w";
|
||||
},
|
||||
pkgs ? import (source) {}
|
||||
}:
|
||||
|
||||
pkgs.mkShell {
|
||||
name = "contributors-docs-shell";
|
||||
|
||||
buildInputs = with pkgs; [
|
||||
mdbook mdbook-emojicodes
|
||||
];
|
||||
}
|
||||
@@ -0,0 +1,5 @@
|
||||
# Hiring
|
||||
|
||||
For all your hiring needs. This is the section that you will need.
|
||||
|
||||
If you feel that we've missed anything or that something is unclear, please reach out to People Ops.
|
||||
@@ -0,0 +1,173 @@
|
||||
# Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
|
||||
|
||||
Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
|
||||
|
||||
**Using Creative Commons Public Licenses**
|
||||
|
||||
Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
|
||||
|
||||
* __Considerations for licensors:__ Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. [More considerations for licensors](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensors).
|
||||
|
||||
* __Considerations for the public:__ By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. [More considerations for the public](http://wiki.creativecommons.org/Considerations_for_licensors_and_licensees#Considerations_for_licensees).
|
||||
|
||||
## Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
|
||||
|
||||
### Section 1 – Definitions.
|
||||
|
||||
a. __Adapted Material__ means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
|
||||
|
||||
b. __Adapter's License__ means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. __BY-NC-SA Compatible License__ means a license listed at [creativecommons.org/compatiblelicenses](http://creativecommons.org/compatiblelicenses), approved by Creative Commons as essentially the equivalent of this Public License.
|
||||
|
||||
d. __Copyright and Similar Rights__ means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
|
||||
|
||||
e. __Effective Technological Measures__ means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
|
||||
|
||||
f. __Exceptions and Limitations__ means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
|
||||
|
||||
g. __License Elements__ means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution, NonCommercial, and ShareAlike.
|
||||
|
||||
h. __Licensed Material__ means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
|
||||
|
||||
i. __Licensed Rights__ means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
j. __Licensor__ means the individual(s) or entity(ies) granting rights under this Public License.
|
||||
|
||||
k. __NonCommercial__ means not primarily intended for or directed towards commercial advantage or monetary compensation. For purposes of this Public License, the exchange of the Licensed Material for other material subject to Copyright and Similar Rights by digital file-sharing or similar means is NonCommercial provided there is no payment of monetary compensation in connection with the exchange.
|
||||
|
||||
l. __Share__ means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
|
||||
|
||||
m. __Sui Generis Database Rights__ means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
|
||||
|
||||
n. __You__ means the individual or entity exercising the Licensed Rights under this Public License. __Your__ has a corresponding meaning.
|
||||
|
||||
### Section 2 – Scope.
|
||||
|
||||
a. ___License grant.___
|
||||
|
||||
1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
|
||||
|
||||
A. reproduce and Share the Licensed Material, in whole or in part, for NonCommercial purposes only; and
|
||||
|
||||
B. produce, reproduce, and Share Adapted Material for NonCommercial purposes only.
|
||||
|
||||
2. __Exceptions and Limitations.__ For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
|
||||
|
||||
3. __Term.__ The term of this Public License is specified in Section 6(a).
|
||||
|
||||
4. __Media and formats; technical modifications allowed.__ The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
|
||||
|
||||
5. __Downstream recipients.__
|
||||
|
||||
A. __Offer from the Licensor – Licensed Material.__ Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
|
||||
|
||||
B. __Additional offer from the Licensor – Adapted Material.__ Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
|
||||
|
||||
C. __No downstream restrictions.__ You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
|
||||
|
||||
6. __No endorsement.__ Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
|
||||
|
||||
b. ___Other rights.___
|
||||
|
||||
1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
|
||||
|
||||
2. Patent and trademark rights are not licensed under this Public License.
|
||||
|
||||
3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties, including when the Licensed Material is used other than for NonCommercial purposes.
|
||||
|
||||
### Section 3 – License Conditions.
|
||||
|
||||
Your exercise of the Licensed Rights is expressly made subject to the following conditions.
|
||||
|
||||
a. ___Attribution.___
|
||||
|
||||
1. If You Share the Licensed Material (including in modified form), You must:
|
||||
|
||||
A. retain the following if it is supplied by the Licensor with the Licensed Material:
|
||||
|
||||
i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
|
||||
|
||||
ii. a copyright notice;
|
||||
|
||||
iii. a notice that refers to this Public License;
|
||||
|
||||
iv. a notice that refers to the disclaimer of warranties;
|
||||
|
||||
v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
|
||||
|
||||
B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
|
||||
|
||||
C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
|
||||
|
||||
2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
|
||||
|
||||
3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
|
||||
|
||||
b. ___ShareAlike.___
|
||||
|
||||
In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
|
||||
|
||||
1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-NC-SA Compatible License.
|
||||
|
||||
2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
|
||||
|
||||
3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
|
||||
|
||||
### Section 4 – Sui Generis Database Rights.
|
||||
|
||||
Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
|
||||
|
||||
a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database for NonCommercial purposes only;
|
||||
|
||||
b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
|
||||
|
||||
c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
|
||||
|
||||
For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
|
||||
|
||||
### Section 5 – Disclaimer of Warranties and Limitation of Liability.
|
||||
|
||||
a. __Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.__
|
||||
|
||||
b. __To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.__
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
|
||||
|
||||
### Section 6 – Term and Termination.
|
||||
|
||||
a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
|
||||
|
||||
b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
|
||||
|
||||
1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
|
||||
|
||||
2. upon express reinstatement by the Licensor.
|
||||
|
||||
For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
|
||||
|
||||
c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
|
||||
|
||||
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
|
||||
|
||||
### Section 7 – Other Terms and Conditions.
|
||||
|
||||
a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
|
||||
|
||||
b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
|
||||
|
||||
### Section 8 – Interpretation.
|
||||
|
||||
a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
|
||||
|
||||
b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
|
||||
|
||||
c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
|
||||
|
||||
d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
|
||||
|
||||
> Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at [creativecommons.org/policies](http://creativecommons.org/policies), Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
|
||||
>
|
||||
> Creative Commons may be contacted at creativecommons.org
|
||||
@@ -0,0 +1,38 @@
|
||||
# How to request goods or services for the organization
|
||||
|
||||
IFT is a rapidly growing organization with multiple moving parts. As a result, core contributors may need to utilize new tools, technologies, or seek support from consultants and other service providers to support our expansion journey.
|
||||
|
||||
To ensure that these needs align with the organizational strategy, priorities, and established policies, it is crucial that each core contributor follows the standard process for requesting goods/services.
|
||||
|
||||
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.
|
||||
@@ -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)
|
||||
@@ -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
|
||||
@@ -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.
|
||||
@@ -1,34 +1,52 @@
|
||||
# Summary
|
||||
|
||||
- [Introduction](./index.md)
|
||||
- [Welcome to Status](./welcome-to-status.md)
|
||||
- [Introduction](./introduction.md)
|
||||
- [Welcome to IFT](./welcome-to-IFT.md)
|
||||
- [Our principles](./our-principles.md)
|
||||
- [Directory of Core Contributors](./catalog.md)
|
||||
- [IFT Core Contributors](./catalog.md)
|
||||
- [Settling in](./settling-in/index.md)
|
||||
- [Your autonomy](./settling-in/your-autonomy/index.md)
|
||||
- [Self-time management](./settling-in/your-autonomy/self-time-management.md)
|
||||
- [Downtime FAQs](./settling-in/your-autonomy/downtime-faqs.md)
|
||||
- [Location independence](./settling-in/your-autonomy/location-independence.md)
|
||||
- [Your autonomy](./settling-in/your-autonomy.md)
|
||||
- [Self-time management](./settling-in/self-time-management.md)
|
||||
- [AFK FAQs](./settling-in/afk-faqs.md)
|
||||
- [The trial period](./settling-in/the-trial-period.md)
|
||||
- [Evaluation Guide](./settling-in/Self-Evaluation-Guide.md)
|
||||
- [Your first day, week, month…](./settling-in/your-first-day-week-month.md)
|
||||
- [Onboarding buddy](./settling-in/onboarding-buddy.md)
|
||||
- [People Operations](./settling-in/people-operations.md)
|
||||
- [Download Status Desktop](./settling-in/download-status-desktop.md)
|
||||
- [Contributing to IFT](./contributing-to-ift/index.md)
|
||||
- [Journey to your first contribution](./contributing-to-ift/journey-to-your-first-contribution.md)
|
||||
- [Value-creating Behaviours](./contributing-to-ift/value-creating-behaviours.md)
|
||||
- [Laptops and devices](./contributing-to-ift/laptops-and-devices.md)
|
||||
- [Collaboration](./contributing-to-ift/collaboration.md)
|
||||
- [Movement Guidelines](./contributing-to-ift/movement-guidlines.md)
|
||||
- [Coworking allowance](./contributing-to-ift/coworking-allowance.md)
|
||||
- [AI allowance](./contributing-to-ift/ai-allowance.md)
|
||||
- [Location independence](./contributing-to-ift/location-independence.md)
|
||||
- [Events and meetups](./contributing-to-ift/events-and-meetups.md)
|
||||
- [Travelling for IFT](./contributing-to-ift/travelling-for-IFT.md)
|
||||
- [Health resources for your working space](./contributing-to-ift/health-resources-for-your-working-space.md)
|
||||
- [Referrals](./contributing-to-ift/referrals.md)
|
||||
- [Headspace](./contributing-to-ift/headspace.md)
|
||||
- [Fundamentals](./fundamentals/index.md)
|
||||
- [Security guidelines](./fundamentals/security-guidelines.md)
|
||||
- [Recommended reading](./fundamentals/essential-reading.md)
|
||||
- [Contributor Code of Conduct](./fundamentals/contributor-code-of-conduct.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)
|
||||
- [Finance](./finance/index.md)
|
||||
- [Getting paid](./finance/getting-paid.md)
|
||||
- [Third-party invoices format](./finance/third-party-invoices-format.md)
|
||||
- [Expense reimbursements](./finance/expense-reimbursements.md)
|
||||
- [Perks](./perks/index.md)
|
||||
- [Computers and devices](./perks/computers-and-devices.md)
|
||||
- [Events and meetups](./perks/events-and-meetups.md)
|
||||
- [Health resources for your home office](./perks/health-resources-for-your-home-office.md)
|
||||
- [Contributing to Status](./working-here/index.md)
|
||||
- [Traveling for Status](./working-here/traveling-for-status.md)
|
||||
- [How to use TravelPerk](./working-here/how-to-use-travelperk.md)
|
||||
- [Your most important role](./hiring/index.md)
|
||||
- [Offboarding](./offboarding/index.md)
|
||||
- [Device Logistics](./offboarding/device-logistics.md)
|
||||
- [Team Lead Manual]()
|
||||
- [Candidate Tasks](./Team-lead-manual/Candidate-Tasks.md)
|
||||
|
||||
*****
|
||||
|
||||
- [Contributing to the Contributors Guide](./contributing-to-this-page.md)
|
||||
- [Contributing to the Contributors Guide](./contributing-to-this-guide.md)
|
||||
- [License](./LICENSE.md)
|
||||
<!-- # This is hidden using custom.css file. -->
|
||||
- [2023 Lead evaluation guide](./Playbooks/2023-Lead-Evaluation-Guide.md)
|
||||
|
||||
@@ -0,0 +1,48 @@
|
||||
## ✨ Lead Evaluation Guide
|
||||
|
||||
_This document is intended to be a supporting document to help Core Contributors complete the 2023 Lightweight Evaluation Process._
|
||||
|
||||
This guide has been created to assist you in providing constructive and meaningful feedback to Core Contributors regarding their impact on Status. The evaluation will be structured in two parts. The first section will have specific questions about the Core Contributor’s contribution, collaboration and autonomy. Following that, there will be a short answer section that will give you an opportunity to provide more detailed feedback about the Core Contributors in the team you lead.
|
||||
|
||||
**Writing Meaningful Feedback**
|
||||
|
||||
There are two questions in the evaluation process designed to be more freeform qualitative questions to give you the opportunity to provide specific feedback to the core contributors in your team - these are:
|
||||
|
||||
1. What is (at least) one thing the contributor does well?
|
||||
2. What is (at least) the one thing the contributor could improve on?
|
||||
|
||||
With these questions, we suggest.
|
||||
|
||||
1. Provide clear and specific examples to support your feedback.
|
||||
2. Focus on addressing behaviors, not personality traits, for objective and action-oriented feedback
|
||||
3. Maintain a respectful and empathetic tone to ensure your contributors feel supported
|
||||
|
||||
There are a variety of frameworks and guides that are useful in helping write and deliver feedback. For more on giving feedback, please see [here](https://www.forbes.com/sites/forbeshumanresourcescouncil/2021/12/02/how-to-give-feedback-to-freelancers-contractors-and-remote-workers/?sh=d753b074d5b4).
|
||||
|
||||
Additionally, here are examples of effective and ineffective feedback for the Core Contributors in your team:
|
||||
|
||||
> 😃 _Effective:_
|
||||
“Over the past year, the contributor has shown exceptional collaboration skills within our team. One particular instance to highlight was their collaboration skills during our recent project with Team X and Team Y. In this project, the contributor took the initiative to organize and lead discussions among the teams and consistently encouraged participation from others. The contributor helped to facilitate open conversations and create safe spaces for such collaboration which made a really positive impact on the project’s success. We were able to make better and more informed decisions as a result of this (for example, as a result, we decided to prioritise feature z) - the contributor played a significant role in making this happen.”
|
||||
|
||||
> 😔 _Ineffective:_
|
||||
“Excellent collaboration skills”.
|
||||
|
||||
**Quantitative Assessment**
|
||||
|
||||
It’s important to approach the quantitative section of this process with fairness and objectivity. The expectation is that not all of your Core Contributors in your team will receive an “Outstanding” rating. Instead, the aim is to offer honest and well-balanced feedback that reflects each Core Contributor’s actual performance. Keep in mind that most Core Contributors will likely receive a “Meets Expectations” rating. This will ensure that our evaluations are realistic and meaningful.
|
||||
|
||||
**Rating Guide**
|
||||
|
||||
The evaluation process requires you to provide a rating of the Core Contributors in your team - please use the guidance below:
|
||||
|
||||
* **Does Not Meet Expectations:** Core Contributor consistently fails to meet role expectations.
|
||||
* **Partially Meets Expectations:** Core Contributor sometimes meets role expectations but has room for improvement
|
||||
* **Meets Expectations:** Core Contributor consistently meets expectations for their role - likely the majority of Core Contributors will fall into this category (it’s a good rating that demonstrates they are meeting our high expectations).
|
||||
* **Exceeds Expectations:** Core Contributor consistently goes above and beyond what is expected in their role
|
||||
* **Outstanding:** Core Contributor consistently has exceptional performance and contributions. Would expect this to be awarded to only a very small group of Core Contributors.
|
||||
|
||||
**Distribution of ratings**
|
||||
|
||||
Whilst there’s no forced distribution of ratings, it’s natural to expect (with 200+ core contributors) we’ll use the full scale of ratings. It is likely that most CCs will fall into the “meets expectations” category, but that we will also have some (a smaller amount) that are distributed in the higher, and lower, categories.
|
||||
|
||||
Please reach out to your People Ops Partner if you have any questions.
|
||||
@@ -0,0 +1,101 @@
|
||||
# Candidate Tasks in Recruitment
|
||||
|
||||

|
||||
|
||||
## 1. What is a task:
|
||||
It is a practical assessment to evaluate candidate skills.
|
||||
|
||||
## 2. Why do we use tasks in the hiring process?
|
||||
We use them to:
|
||||
- Get a better assessment beyond CVs, portfolios, github repos and interviews.
|
||||
- Gain a deeper understanding of someone's abilities (technical & non-technical) for the role at hand.
|
||||
- Give candidates a chance to showcase their working style & communication, it’s common to set up a Discord chat so the candidate & task reviewers can chat, ask/answer questions and also provide updates.
|
||||
|
||||
## 3. How to design a task
|
||||
Step 1: Understand the role's requirements.
|
||||
|
||||
Step 2: Design a task that aligns with the expected output of the role.
|
||||
|
||||
Step 3: Clearly communicate task instructions, expectations, and deadline.
|
||||
|
||||
What does a good task look like:
|
||||
- Has clear instructions & expectations
|
||||
- Has a deadline that’s realistic (usually 1 week is enough)
|
||||
- Has a recommended timeframe in which to complete the task i.e 2-4hrs (this keeps all candidates 'fair' in terms of time dedicated to the task)
|
||||
- Is aligned with the day-to-day responsibilities of the role
|
||||
- It is tackling a real problem the team face, some teams use a bounties approach
|
||||
|
||||
Examples:
|
||||
- UX/UI Designer: Create a mobile app prototype/feature based on the target audience.
|
||||
- Sales: Create a presentation on selling a complex product to a potential client.
|
||||
- Engineer: Assess problem-solving skills by tasking them with debugging code.
|
||||
- Customer Support: A simulated chat interaction to assess their communication skills.
|
||||
- Financial Analyst: Analyze an investment portfolio to gauge forecasting abilities.
|
||||
- Content Writer: Create a blog post on a specified topic.
|
||||
|
||||
## 4. Time restrictions & compensation:
|
||||
We want to see a glimpse of what they can do within the allocated time, this shouldn’t be seen as their full potential since they are not integrated into the working styles of the team or the full context of the team.
|
||||
|
||||
A simple and effective approach is:
|
||||
- A flat rate for completion of the task; ie. $200
|
||||
- A set time allowing completing the task; ie. 2-4hrs (some teams have longer, rule of thumb is allow enough time for the task to be completed)
|
||||
… The longer the task, the more time you/your team have to spend reviewing it
|
||||
|
||||
## 5. Materials for Candidates:
|
||||
Ensure candidates have all the reference materials needed to perform and succeed on the task.
|
||||
|
||||
Examples:
|
||||
- A digital marketer may need access to Google Analytics data.
|
||||
- A data scientist may need to be provided a dataset and access to statistical software.
|
||||
- A content creator may need a brand style guide and existing content for reference.
|
||||
- A Mobile UI Engineer will need access to Figma
|
||||
|
||||
## 6. Evaluating Tasks:
|
||||
Setting clear evaluation standards is important so everyone is assessed fairly and we don’t let personal biases get in the way of hiring people who perform well during tasks. We should determine the criteria for task evaluation prior to seeing the first task submitted by a candidate.
|
||||
|
||||
Examples:
|
||||
- Evaluate a coding task based on criteria like code quality, efficiency, and adherence to project requirements.
|
||||
- Assess customer service interactions based on responsiveness, problem-solving, and professionalism.
|
||||
- Evaluate a design task considering creativity, usability, and alignment with brand guidelines.
|
||||
|
||||
|
||||
## 7. Effective Communication:
|
||||
Maintain transparent and professional candidate communication.
|
||||
|
||||
- Clearly inform candidates of the evaluation timeline and when they can expect feedback.
|
||||
- Use the Discord chat to interact with the candidate throughout their task
|
||||
|
||||
## 8. Feedback and Improvement:
|
||||
Use candidate feedback to refine task instructions and evaluation criteria.
|
||||
|
||||
## 9. Sample Tasks:
|
||||
|
||||
- Engineering: [Vac Pair Programming Task](https://notes.status.im/Jvd03lPKSMiDI_eo9Dq9xw)
|
||||
- Communications: [Activist Event Manager](https://drive.google.com/file/d/1TsIbMduelr_TjbwfEcT-AnXnVco1GejC/view?usp=sharing)
|
||||
- Recruitment: [Sourcing Task](https://docs.google.com/document/d/1ICiYpsvT6sh6akyM6RxQX1tu_D3tq3bVgLWEIpj1aOM/edit?usp=sharing)
|
||||
- Pops: [People Ops Partner](https://docs.google.com/document/d/1nLFu6sQvfqCqfdlWP8kVTBzBDLTIZknNRc8FMCw9vrA/edit?usp=sharing)
|
||||
|
||||
## FAQs
|
||||
|
||||
Q: How long should candidates typically spend on the task?
|
||||
A: We recommend 2-4 hours to avoid impacting the candidate's current job and any family commitments.
|
||||
|
||||
Q: How long should the task take to complete?
|
||||
A: 1-week max (unless the candidate has let us know they have something that won’t allow them to complete the task, ie. health conditions, family, personal, ect.)
|
||||
|
||||
Q: What happens if a candidate encounters issues during the task?
|
||||
A: You can communicate with them via the discord chat created by the recruiter.
|
||||
|
||||
Q: Is there room for negotiation on compensation for exceptionally well-performed tasks?
|
||||
A: No.
|
||||
|
||||
Q: What if I can’t think of any tasks?
|
||||
A: Then check out the tasks templates above as inspiration or/and think of a daily task someone in your team does that you would expect this candidate to be competent with, for example, in recruitment we would expect someone to show their competency & creativity sourcing candidates, so that is what the task is based around.
|
||||
|
||||
Q: My team doesn't have time to review every task, what do we do?
|
||||
|
||||
A: The number of tasks to review should be minimal as you don’t need to send a task to every candidate, only the good ones that stand out as potential hires.
|
||||
|
||||
|
||||
_If that is still too much, revert to a technical discussion, so long as you’re confident you can accurately assess a candidate's suitability this way._
|
||||
|
||||
@@ -1,4 +1,6 @@
|
||||
# ℹ️ Directory of Core Contributors
|
||||
# ℹ️ IFT Core Contributors
|
||||
|
||||
Directory of Core Contributors
|
||||
|
||||
<style>
|
||||
div#content>main {
|
||||
@@ -14,4 +16,4 @@ div#content>main>iframe.contacts {
|
||||
border: none;
|
||||
}
|
||||
</style>
|
||||
<iframe src="https://contacts.status.im/" class="contacts"></iframe>
|
||||
<iframe src="https://contacts.free.technology/" class="contacts"></iframe>
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
# 🤖 AI Allowance
|
||||
|
||||
To support core contributors in integrating AI tools into their workflow while maintaining flexibility and cost control, we are introducing a monthly expensable allowance for AI services.
|
||||
|
||||
### Benefits
|
||||
|
||||
We are equipping core contributors with a crucial skill set for the future. As AI becomes more integrated into workflows, those who effectively leverage these tools will have a competitive advantage. Key benefits include:
|
||||
|
||||
* Enhancing core contributor productivity by effectively integrating AI into daily work
|
||||
* Improving documentation and knowledge sharing within the organization
|
||||
* Ensuring AI is used responsibly and effectively in alignment with organizational needs
|
||||
|
||||
### Allowance Details
|
||||
|
||||
You can expense up to USD 60 per month for AI-related services. This allows core contributors to choose the tools that best fit their needs without incurring unnecessary costs for those who do not use them.
|
||||
|
||||
### Expense Guidelines
|
||||
|
||||
You can expense:
|
||||
|
||||
* AI service subscriptions, API credits, or tools directly aiding work productivity
|
||||
* AI-powered coding assistants, research tools, and documentation aids
|
||||
|
||||
You cannot expense:
|
||||
|
||||
* Non-work-related AI services
|
||||
* Premium AI features not directly contributing to IFT work
|
||||
* Hardware or devices for AI-related activities
|
||||
|
||||
Please keep receipts and submit your expenses through Expensify under the Software & subscriptions category following expense reimbursement guidelines.
|
||||
|
||||
If your total expense exceeds the allowance, only claim up to the approved amount.
|
||||
|
||||
If you're unsure whether an expense qualifies, reach out to People Ops for clarification.
|
||||
@@ -0,0 +1,19 @@
|
||||
# Collaboration
|
||||
|
||||
We use multiple tools for knowledge management and collaboration across the organisation. The basic platforms you need access to from Day 1 are: Google Suite, ProtonMail and Notion. On top of this, each individual teams may use other platforms such as Miro, CodiMD etc. As you start working with various teams, you will be provided access to these platforms.
|
||||
|
||||
|
||||
## Google Suite
|
||||
|
||||
Google suite is used for emails, various types of document collaboration and video calls. You will be provided with a @status.im email address which will give you access to the whole Gsuite.
|
||||
|
||||
|
||||
## ProtonMail
|
||||
|
||||
Google does not align with our values as an organisation and so there is currently a project to move away from Google and start using ProtonMail as our email provider. You will be getting a secondary email address on-top of your existing @status.im address.
|
||||
|
||||
You can read about this change, [when to use Gmail vs. ProtonMail](https://www.notion.so/Phase-1-Replace-Google-Mail-w-Proton-Mail-34d999eacb27446dacdbb426075fe6da) along with the more details about the project and timelines.
|
||||
|
||||
|
||||
## Notion
|
||||
Notion is a collaborative Wiki, just like Confluence (if you have ever used it). Most teams collaborate on this platform and this is part of knowledge management across the organisation.
|
||||
@@ -0,0 +1,31 @@
|
||||
# 🏓 Coworking Allowance
|
||||
|
||||
The coworking allowance offers core contributors some flexibility to find a workspace different from your home office if needed. It's non-transferrable for other expenses in case you don't make use of it.
|
||||
|
||||
You can expense up to USD 270 / EUR 250 (or local currency equivalent) per month for coworking costs (any coworking space rental/hotdesk/access pass).
|
||||
|
||||
You can also include the coffee you consume at the coworking space.
|
||||
|
||||
You can't use the allowance for:
|
||||
|
||||
* Your internet/broadband costs.
|
||||
* Covering additional bills arising from you working from home.
|
||||
* Meals or drinks outside working hours or for take-away drinks.
|
||||
* Meals or drinks for people accompanying you that don't contribute to IFT.
|
||||
* Gratuities.
|
||||
|
||||
>😃 An example of a claimable expense:
|
||||
USD 200 for coworking space + USD 50 on drinks consumed at the coworking space;
|
||||
or
|
||||
USD 50 consumed on drinks at a space **used for working** outside your home office.
|
||||
|
||||
>😡 An example of a non-claimable expense: USD 0-270 consumed on drinks at a space when you are not contributing to a IFT project.
|
||||
|
||||
Please keep the invoices/receipts and submit your costs through Expensify as per the [expense reimbursement guidelines](../finance/expense-reimbursements.md), specifying coworking as the category detailing the expense in the comments field of your expense line item.
|
||||
|
||||
If your coworking cost is above budget, please only expense up to that amount in your expense claim.
|
||||
|
||||
Please also consider that (for smaller/less frequent coworking expenses), our minimum threshold for submitting an expense report is USD 70 / EUR 50. As such, we'd ask you to group coffee receipts into one batch of at least USD 70 / EUR 50 before submitting them for processing.
|
||||
|
||||
> ℹ️ If you're unsure whether or not this applies to you, ping People Ops.
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
# 🎤 Events and meetups
|
||||
|
||||
As a IFT core contributor, you may have the opportunity to speak at or attend external online or in-person events.
|
||||
|
||||
The community is an essential part of the Web3 ecosystem. Ecosystem, domain-specific, and internal events and meetups are networking and growth opportunities. And we strongly encourage you to be part of them!
|
||||
|
||||
Here you'll find helpful information to make the most out of organising, speaking, or attending events.
|
||||
|
||||
## What events does IFT sponsor
|
||||
|
||||
IFT will consider sponsoring and covering the costs for any online or in-person event with a clear purpose. That means it must align with IFT's strategy and goals. This includes, but is not limited to:
|
||||
|
||||
* Ecosystem events such as DevCon, ETH[city], ETHCC, Hackathons, blockchain weeks, etc.
|
||||
* Domain-specific events for your role for career purposes.
|
||||
* Events and meetups to promote IFT or our projects to potential new core contributors.
|
||||
* Internal events and meetups to prepare a product/project launch or work together.
|
||||
* Moderating or speaking opportunities related to IFT.
|
||||
|
||||
> ✨ Remember that when you're at an event, you're an ambassador for IFT’ projects and everyone who shares our values. Don't forget that and spread the word! You never know who's listening and might contribute to IFT thanks to you 🙂
|
||||
|
||||
> Always speak to your team lead and discuss the impact going to an event will have on yourself or IFT.
|
||||
|
||||
> 💡Before attending an event, ask your Talent Partner to generate a QR code for our job pages that you can share with anyone interested.
|
||||
|
||||
## Related articles
|
||||
|
||||
👉 Check out [Travelling for IFT](../contributing-to-ift/travelling-for-IFT.md) for commute and accommodation guidelines if you need to travel for the event.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
### 🔆 Headspace: manage stress and unwind
|
||||
|
||||
Headspace is one of the leading apps that focuses on mindfulness, meditation and has a range of tailored workouts for the mind. There's [research](https://www.headspace.com/science/meditation-research) that the app can positively impact stress, focus, mood, and work.
|
||||
|
||||
If you contribute to IFT, you can enjoy a premium subscription (free of charge). To use one of the subscriptions, signup with your @status.im email [here](https://work.headspace.com/ift/member-enroll). If there are no available seats, please reach out to your People Partner and they will purchase a new seat for you.
|
||||
|
||||
[Here](https://drive.google.com/drive/folders/122aJjQRK-CCnC0f_y8vWRAhiLQR_f9H9) you can find some helpful resources to help you on your journey.
|
||||
|
||||
While meditation and mindfulness might not be for everyone, we hope that some of you will find Headspace useful.
|
||||
@@ -0,0 +1,43 @@
|
||||
# ⚡️ Health resources for your working space
|
||||
|
||||
We spend almost as many hours working as sleeping. Having great working habits is as essential as getting a good night's sleep, and more often than not, they go hand in hand.
|
||||
|
||||
Here you'll find some resources to manage stress and best practices to make your working routine lighter from complaints from your future self.
|
||||
|
||||
|
||||
### 🏃♂️ Move
|
||||
|
||||
The number one rule is move! Everyone's body needs some stretching, standing up, and moving around every now and then. And it's easy to forget about moving when we're too focused on something.
|
||||
|
||||
Think about it as a system where when certain parts become more passive (your body), others overload to compensate (more mental effort to do things). Taking moving breaks helps sustain balance.
|
||||
|
||||
Some people organise their days so that training, lunchtime, or picking up kids from school happen between focus work blocks. If you don't have a smartwatch, here are some desktop tools that can remind you to have frequent, short breaks:
|
||||
|
||||
* [Stretchly](https://hovancik.net/stretchly/)
|
||||
* [Workrave](https://workrave.org/)
|
||||
|
||||
Think about what this means to you and what tools and habits you'd like to incorporate into your routine.
|
||||
|
||||
|
||||
### 🐒 Workspace ergonomics
|
||||
|
||||
The second most relevant rule is your working ergonomics. That is the set of improvements on posture and setup that help prevent muscle, joint, and bone injuries and improve performance and productivity.
|
||||
|
||||
It's actually a pretty simple theory, and it's a matter of bringing consciousness to this area. With practice, it will eventually become intuitive and effortless to do.
|
||||
|
||||

|
||||
|
||||
Experts recommend a posture where the neck, shoulder, and lower back are aligned with your monitor at eye level. Ideally, you'd switch from sitting to a standing desk, so you strike rules one and two all at once.
|
||||
|
||||
Most injuries are reversible, so if you experience pain or discomfort, seek advice.
|
||||
|
||||
### 🌀 Blue light
|
||||
|
||||
Constant exposure to blue light over time can mess with your sleep and may cause harm to your eyes. Your eyes are precious so treat them kindly with some time and attention to your blue light exposure.
|
||||
|
||||
Some ideas for minimising the strain on your eyes:
|
||||
Enable Night Shift or a similar blue light reduction app on your mobile device. Night Shift pro tip - move the colour temperature slider to warm because the default still allows some blue light.
|
||||
Install f.lux on your computer to gradually fade out blue light as your working day turns to night.
|
||||
Buying a good monitor. Two things you can check: a) that there is no extra blue light in the LED, and b) that there is no PWM (Pulse Width Modulation), which is used as a cheap way to reduce brightness.
|
||||
|
||||
Got any other tips and tricks for filtering blue light? Create a PR!
|
||||
@@ -0,0 +1,20 @@
|
||||
# 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 IFT and the core contributor to ensure the overarching product and strategy goals are met.
|
||||
|
||||
Our aim is to normalise (self-)evaluations and talk about what’s good and what requires improvement on a continuous basis. Lattice is our performance management platform across Status. It is widely used for 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 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 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 IFT.
|
||||
* In order to help with what behaviours create value, here you can see a IFT-specific list of [value-creating behaviours](../contributing-to-ift/value-creating-behaviours.md) and some examples in which they could manifest.
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
# 🌟 Journey to your first contribution...
|
||||
|
||||
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
|
||||
|
||||
Read your project last quarter's retro and learnings, and focus on this quarter's priorities and goals.
|
||||
|
||||
## Ask other core contributors in your project:
|
||||
- What went well
|
||||
- What could have been improved
|
||||
- What were the key learnings for your project
|
||||
- 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 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!
|
||||
|
||||
| 💡 | Remember.... There is always someone available to help you on your journey! |
|
||||
|---------------|:-----------------------------------------------------------------------------|
|
||||
|
||||
@@ -0,0 +1,60 @@
|
||||
# 🖥 Laptops and devices
|
||||
|
||||
Having the proper setup is fundamental to ensure you can work comfortably to successfully deliver services to IFT and our projects. We hold our principles dear and support you as a core contributor with some of the tools you might need to succeed in providing services using secure, decentralised devices.
|
||||
|
||||
Here you'll find some helpful information to get yourself set up with the right equipment you may need.
|
||||
|
||||
## ☑️ Available equipment
|
||||
|
||||
Core contributors have the potential option of leasing devices from IFT to ensure that they can provide their services. We have a list of pre-approved equipment considered within their project budgets to the extent that you need certain devices to deliver your services.
|
||||
|
||||
While IFT provides you the flexibility to purchase the appropriate devices in line with the capped amounts stated in this section, IFT ultimately owns such devices. Following your purchase, we will subsequently lease you back the device which you have purchased.
|
||||
|
||||
For the purposes of purchasing devices, reach out to your Project Lead and PeopleOps partner for approval.
|
||||
|
||||
The standard setup for everyone includes a laptop, a Keycard, a Yubikey, and a Ledger.
|
||||
|
||||
For each item we have defined a budget. Your spend will stay below the defined budget, in most cases. When this happens, it is not an option to use the difference towards the cost of other items.
|
||||
|
||||
* Laptop: up to USD 3,000
|
||||
* Mic and headphones: up to USD 120
|
||||
* Keycard: ping the #keycard channel to get a code
|
||||
* Yubikey: you can reimburse one (approx USD 75)
|
||||
* Ledger: you can reimburse one (approx USD 80)
|
||||
|
||||
> Most core contributors should be able to effectively perform their work using standard equipment, but if you're struggling to participate or you need other equipment to perform your role successfully (for example, you need a better quality webcam to record videos or a higher quality mic to record demos for IFT), then please speak to your Project Lead or PeopleOps partner to discuss your needs on a case by case basis. For those that are approved to receive higher quality equipment, we recommend the **Logitech Brio 4K Webcam** and the **Rode NT-USB USB Condenser Microphone**.
|
||||
|
||||
Following the cessation or termination of your services to IFT, you have the option of purchasing from IFT any equipment you purchased in accordance with this section.
|
||||
|
||||
## 🏪 How to get your devices
|
||||
|
||||
1. Choose official or trusted vendors to buy your devices
|
||||
2. Seek approval from your Project Lead or your PeopleOps partner
|
||||
3. Upon getting okays from your Project Lead and PeopleOps partner, proceed with the purchase.
|
||||
4. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
5. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
|
||||
6. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
7. Enter into a leasing agreement with IFT in respect of the device you have purchased.
|
||||
|
||||
## ℹ️ FAQ
|
||||
|
||||
* __Who owns the devices which I’ve purchased__
|
||||
|
||||
IFT is the owner of the devices which you have purchased. IFT will lease back these devices to you in order for you to deliver your services. We have found that this is a flexible and convenient arrangement to ensure that you can obtain the appropriate devices in a timely manner to deliver your services.
|
||||
|
||||
* __What if I don't have enough funds to buy the device before reimbursement?__
|
||||
|
||||
If cash flow is an issue, please ping your People Partner and we'll help come up with a solution!
|
||||
|
||||
* __What if my devices becomes outdated?__
|
||||
|
||||
At the 3 year mark, if your device needs an upgrade, speak to your PeopleOps partner about purchasing a new one.
|
||||
|
||||
* __What happens if I accidentally damage a device?__
|
||||
|
||||
You should treat the devices as if they were yours. If the damage was due to factors beyond your control, please obtain a quote for a repair and let your People Partner know. If the cost is reasonable (i.e., less than ~75% of the trade-in value of the asset), we would ask you to go ahead and get the device repaired. Then, submit the repair expense cost for reimbursement.
|
||||
|
||||
* __What happens if my services agreement with IFT finishes?__
|
||||
|
||||
Please check out [this guide](../offboarding/device-logistics.md) for your options on recycling or buying back devices.
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
# 🌏 Location independence
|
||||
|
||||
IFT is a fully remote, location-agnostic organisation – meaning that we don’t mandate the location where you should provide your services.
|
||||
|
||||
Being location independent means you could decide to move away from where you were first delivering your services, and that's okay. IFT can provide you with confirmation of a service engagement letter if you need it in the process of migrating abroad.
|
||||
|
||||
However, we will not cover the visa/work permit processing or relocation costs as we're location agnostic for work.
|
||||
|
||||
## What happens if I'm thinking about relocating
|
||||
|
||||
Get in touch with your People Partner to start the discussion about your relocation plans. They will help with the preparation of all the necessary paperwork regarding your service agreement address amendment.
|
||||
|
||||
## If you need supporting documents
|
||||
|
||||
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 IFT as your employer if the DE/CH entity formally employs you. Otherwise, you should indicate that you are self-employed or providing services as a freelance contractor, as appropriate.
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
|
||||
# Movement Guidelines
|
||||
|
||||
Movement to a different role within IFT offers many benefits. It is an important process that helps us keep valuable expertise within the organisation, allows core contributors to develop additional skills and enhances the strength and adaptability of our teams.
|
||||
|
||||
|
||||
To ensure fair, transparent, and efficient movement to the new role, we have established the following guidelines for core contributors to follow:
|
||||
|
||||
|
||||
### Open Roles
|
||||
|
||||
All open roles can be found on our websites ([IFT](https://free.technology/jobs), [Logos](https://boards.greenhouse.io/logos), [Status](https://status.app/jobs)) or by checking out the hiring channels in the Logos Discord and Status App.
|
||||
|
||||
For more information regarding the requirements of any roles, we suggest contacting the Talent team directly rather than the hiring lead.
|
||||
|
||||
We believe in transparency and open communication between core contributors, team leads, and People Ops. Before applying for a different role, core contributors should discuss their interests with their current team lead and/or People Partner to evaluate their fit and motivations.
|
||||
|
||||
### Eligibility Criteria
|
||||
|
||||
We expect a core contributor to meet at least the minimum required skills/attributes, which will be clearly described in the role’s description before applying.
|
||||
|
||||
Whilst we don’t have strict rules, as a general guideline, we’d expect someone to have contributed to their current project for 12 months before moving to a different team.
|
||||
|
||||
### Application and Screening Process
|
||||
|
||||
All applications are carefully reviewed based on skills, experience and alignment with the role requirements.
|
||||
|
||||
The screening process varies depending on the role. Some roles may involve a few interviews and possibly a task. The process may be more extensive for other roles, typically including interviews with program leads and Co-Founders.
|
||||
|
||||
The hiring team will likely consult with a core contributor's current team lead to gain insights into their skillset, motivations, and team fit.
|
||||
|
||||
### What happens if a core contributor successfully moves to a new team/project?
|
||||
|
||||
Congratulations! If the decision is favourable, together with the team leads and People Partners, a transition plan will be formed to move the core contributor to the new role. It is important to respect the current team by providing an extensive handover and allowing time for a backfill to be embedded. Overall, the goal is to ensure that the transition into the new internal role is as smooth and successful as possible, setting the core contributor up for success.
|
||||
|
||||
### Is there a trial period for moves?
|
||||
|
||||
Whilst there is no official trial period, we consider the first 12 weeks within the new role as the trial. During this period, the team leads are encouraged to provide ongoing feedback, check in’s and support as necessary.
|
||||
|
||||
|
||||
@@ -0,0 +1,89 @@
|
||||
# 👑 Referrals
|
||||
|
||||
There are many ways you can help IFT grow: engaging with the community, interviewing, helping out with events, etc., but referring outstanding people to IFT is one of the most direct ways you can make an impact.
|
||||
|
||||
As an organisation, we're reliant on many groups to help us reach our goals: freelancers, community members, testers, researchers, users and more. We need these groups and individuals who make hugely valuable contributions, alongside core contributors who contribute to Status on a full-time basis.
|
||||
|
||||
Engaging with potential core contributors that align with IFT' values and excel in their field is essential to us; and we'd love your help! Below, you'll find helpful information to connect the extraordinary people you know, with IFT.
|
||||
|
||||
## Referral bonus
|
||||
|
||||
If you've worked with someone amazing and think they would be a great fit at IFT, not only would we like to know, but we'll also reward you once they've successfully completed their trial period.
|
||||
|
||||
IFT will reward you a referral payment of USD 5,000 worth of SNT after a successful trial period. At times, we might offer higher rewards for specific critical roles, so stay tuned for updates in the #people-ops channel!
|
||||
|
||||
### Eligibility criteria
|
||||
|
||||
* You can only refer potential core contributors who have not applied to us independently within the last 60 days.
|
||||
* Referrals are for individuals; we are not responsible for any fees related to resumes received from recruitment agencies.
|
||||
* The initial contact between IFT and your referral must be facilitated by you.
|
||||
* The referral payment only applies to engaging core contributors. It does not apply to engaging freelancers.
|
||||
* For someone you refer, you would be removed from any interview process involving them (this ensures we are fair and unbiased in our acquisition. process).
|
||||
* Team Leads should recuse themselves from decision-making if they stand to gain financially. i.e. they can refer someone, and get the bonnus. But the decision to hire should be made by someone impartial, or a team committee.
|
||||
|
||||
Sorry for the many conditions! We want to be fair and apply some common-sense guidelines, but let us know if you have any better ideas! 🙂
|
||||
|
||||
## How to make a referral
|
||||
|
||||
Here are the basics of referring incredible people to join IFT. There are a few ways:
|
||||
|
||||
* Send the CV, GitHub or LinkedIn URL along with a note detailing why you recommend them, how well you know this person etc to [referrals@status.im](mailto:referrals@status.im) (Talent will upload to Greenhouse adding you as referrer; alongside the notes you provide).
|
||||
* If you are a Greenhouse user, you can also make use of it to make a referral - you’ll find the detailed steps [here](https://docs.google.com/presentation/d/16sg-pgJr7MGndemyBdulaz7sbgFYMp5DKpz30H_g1Xw/edit#slide=id.g131b733a5f9_1_522). Make sure to add their contact information, CV, and where and why you think they'd be great for IFT. The project leads your comments when reviewing referrals, so this can help them stand out among other potential core contributors.
|
||||
* Ask the Talent team to give you access to Greenhouse if the URL isn't working for you.
|
||||
* While you should share people whose work you can speak to and are impressed by (i.e., the top 25% of people you've worked with), don't feel pressured to refer everyone who asks. If you feel uncomfortable saying no (we get it; it can be awkward), you can mention it in the notes in the referral form.
|
||||
|
||||
## What happens after you’ve referred someone?
|
||||
|
||||
The Talent team will take good care of them and keep you posted on their progress through the selection process. Still, you can be a critical layer of support to them by:
|
||||
* Help them prepare for interviews or activities, just enough for them to be prepared. But not too much. Why? We’ve had instances in the past where referrals were prepared too well, meaning they did great during the interview process but then struggled once they were onboarded.
|
||||
* Answering questions about working at IFT and your experiences as a core contributor.
|
||||
* If they get an offer, help us convince them to accept it!
|
||||
|
||||
> ✨ Diverse perspectives, backgrounds, and experiences lead to better products. When you refer talent from underrepresented groups, particularly into technical positions, you're doing your part to build a diverse workforce across all functions and levels.
|
||||
|
||||
## Referral and engagement of a Personal Relation
|
||||
|
||||
To ensure that we are being fair and transparent, we have some guidelines around referring and engaging what we call a “Personal Relation”:
|
||||
|
||||
We consider a “Personal Relation” to be a core contributor’s spouse or partner, family members or close friends, including any legal entity that any of these listed individuals have a direct or indirect interest in, or any other related party as Status may determine in its sole discretion.
|
||||
|
||||
As such, we have set out the following rules for core contributors and their Personal Relations when both are engaged by Status:
|
||||
|
||||
* The core contributor should not work directly for or lead a Personal Relation.
|
||||
* The core contributor should not participate in or influence the decision-making process of a Personal Relation (including interviewing, engagement offers or fee negotiations).
|
||||
* The core contributor should not participate in or influence the performance management process of a Personal Relation including trial periods and ongoing performance management or any performance-related issues.
|
||||
* The contributor does not have access to sensitive personal information including payroll, compensation, personnel reviews/files, job performance of the Personal Relation.
|
||||
|
||||
To ensure maximum flexibility, fairness, and transparency, please disclose any (potentially) conflicting relationships or relationships that may give rise to favouritism, to your project lead and People Partner at the beginning of the engagement process and we can assess each case individually.
|
||||
|
||||
## Interviewing Personal Relations
|
||||
|
||||
We want to ensure that our engagement process is fair and transparent. As such, best practice for these situations is:
|
||||
|
||||
* No interviewer may interview Personal Relations or referrals
|
||||
* If you, as an interviewer, become aware of any potential conflict of interest, please alert the relevant member of the Talent team immediately.
|
||||
|
||||
We understand that Personal Relations and referrals may be highly qualified for open positions and we want to ensure that all applicants receive the same level of consideration and respect. We will make sure that any Personal Relation or referral is given the same opportunity as any other applicant by assigning the interview to another interviewer. This applies to all interviewers across IFT.
|
||||
|
||||
## Success, your referral is onboard! What's next?
|
||||
|
||||
If the referral is successful and passes their trial period, you are eligible for a bonus of USD 5,000 worth of SNT. The recruiter in charge will contact you to give you the green light to submit the SNT bonus on an invoice.
|
||||
|
||||
* Submit a separate invoice for the referral bonus payment to finance (billing@status.im).
|
||||
* The deadline to submit your invoice is 3 months.
|
||||
* Once submitted, the bonus will be paid with the next monthly payment.
|
||||
|
||||
_Note: Please, make sure that you attach your correct wallet address to the invoice AND have it updated in BambooHR!_
|
||||
|
||||
**Important: In case you are not legally allowed to receive crypto in your country, please reach put to #people-ops team or the recruiter in charge.**
|
||||
|
||||
## It doesn't always work out...why hasn’t my referral been engaged?
|
||||
|
||||
While referrals generally have a much higher success rate than those engaged via the full recruitment process, there may be a chance that your referral doesn't end up being a core contributor engaged by IFT (the performance of the core contributor won’t be held against you, after all, it’s on the project to interview and come to a decision on whether they deem the referred individual a fit for the role/project). This might happen due to:
|
||||
|
||||
* Timing: their qualifications don't match the roles currently available.
|
||||
* Suitability: they don't meet all of the minimum requirements listed for the role.
|
||||
* Competition: there was someone else who was more qualified.
|
||||
* Demand: the role was reduced or closed.
|
||||
|
||||
Thank you for your support in bringing great people into IFT!
|
||||
@@ -0,0 +1,98 @@
|
||||
# 🌍 Travelling for IFT
|
||||
|
||||
Connecting with people in person is such an essential part of the remote working experience at IFT. Magic happens when people get together.
|
||||
|
||||
Here you'll find helpful information to make your travel abroad experience more efficient while being compliant and accountable to project resources. These guidelines apply to anyone travelling for or sponsored by IFT away from their usual working location.
|
||||
|
||||
Some of these points might not apply to offsites as they're usually centrally organised with their particular budget.
|
||||
|
||||
Your travel budget comes from your project's budget. Speak to your team lead and check out [Events and meetups](../contributing-to-ift/events-and-meetups.md) before booking your trip. Your team lead will need to approve the budget before you book!
|
||||
|
||||
## Before travelling abroad:
|
||||
|
||||
> * Head to the official government pages to understand the risks in a country and the latest restrictions applicable to you, including re-entry requirements.
|
||||
> * Keep in mind that government guidelines may change frequently and that they can impact your travel plans severely.
|
||||
> * Be aware of and account for any extraordinary events which may impact your travel, such as natural disasters, political unrest, wars, riots, epidemics, pandemics and any other extraordinary events.
|
||||
> * Consider booking timeframes and select cancellation and insurance policies accordingly.
|
||||
|
||||
|
||||
## 💸 Expenses while travelling
|
||||
|
||||
It's hard to cover every case within a guide. We trust you to use your best judgement when travelling for company purposes and proactively report back anything you consider relevant.
|
||||
|
||||
Don't go overboard with spending on bookings, food, and drinks. Keep accountability and transparency in mind. Always ask for receipts and keep them organised. IFT will reimburse for all reasonable expenses while travelling in accordance with this section.
|
||||
|
||||
|
||||
### What are reasonable expenses
|
||||
|
||||
* 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 USD $85/day/person for meals. However, this will depend on the destination. If you're dining together with other core contributors, you can submit one bill - just make sure to add their names in the comments section when you file the expense.
|
||||
* Laundry charges for trips longer than five days.
|
||||
* When required and justified for the trip, expedited service fees, travel visas, and inoculation fees necessary for the destination are reimbursable.
|
||||
* Reasonable mobile, roaming, or hotspot connection fees to allow you to work while travelling would be covered. However, we suggest purchasing a local SIM card or eSIM providers, such as [Airalo](https://www.airalo.com/).
|
||||
|
||||
* Non-reimbursable expenses examples:
|
||||
|
||||
* Travel programs, airline upgrades, fast tracks, or premium services.
|
||||
* Airline/accommodation no-show, cancellation, or rebooking fees.
|
||||
* Convenience products, alcohol, cigarettes and fees for the use of the gym, spa, and other facilities.
|
||||
* Travelling companions' hotel, flights and meals.
|
||||
* Room service (except for meals within the daily limit) or in-room movies/entertainment.
|
||||
* Mobile, roaming, or hotspot connection fees for personal use.
|
||||
* In-flight entertainment
|
||||
* Any personal expenses and fines, custom charges, etc.
|
||||
|
||||
If there are any issues or you believe that you should get reimbursed for any of the expenses above, please speak to your People Partner, who can review your request on a case by case basis. Ultimately, it will be in IFT’ sole discretion to determine whether an expense is a “reasonable expense” and whether it will be reimbursed.
|
||||
|
||||
Whether using a card or requesting reimbursements, you're responsible for submitting your expenses correctly as a traveller. We currently process expenses together with payroll or invoices. When you're back from your trip, follow the instructions on [How to file expenses or get reimbursed](../finance/expense-reimbursements.md) for uploading your receipts in a compliant and timely manner to keep our finances healthy.
|
||||
|
||||
## 🛩 Getting there
|
||||
|
||||
Usually, the earlier you plan your trip, the cheaper and better it's going to be. We suggest preparing 4 to 6 weeks ahead to have enough time to communicate your plans and stay within budget. We understand that sometimes last-minute bookings are unavoidable, however, please be mindful of flights and accommodation costs and always look to book the most reasonable option.
|
||||
|
||||
|
||||
### 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 IFT or the event.
|
||||
* For flights that are 12+ hours, premium economy is permitted, but please ensure that the overall cost is still reasonable (if the price is more than 2x the economy price, please do consider alternate options).
|
||||
* For moving around, choose the most affordable ground transportation option. In some places, traffic is unpredictable, and public transport is more reliable. In others, car rental, and ride-sharing, such as Uber or local equivalents, are better to move from/to the airport and share the ride with others travelling with you.
|
||||
|
||||
> 💡 Pro-tip: in-flight entertainment might be limited. You might want to bring a book or download media, music, or documents offline beforehand. For some people, commutes are a great way to disconnect or do some reading or focus work.
|
||||
|
||||
|
||||
## 💻 Where to stay and work from
|
||||
|
||||
You can book your stay at a 3-4 star hotel or an Airbnb. We generally recommend hotels for solo or two person trips and Airbnbs for groups or project travel.
|
||||
|
||||
An Airbnb can be more practical for spending quality time together and setting up a coworking space in the dining or living room, than a hotel. It's also more convenient to coordinate meals and share rides to/from the event or airport when we're staying together.
|
||||
|
||||
If you are organising a project off-site, reach out to your People Partner who can help with logistics and bookings of an AirBnb.
|
||||
|
||||
|
||||
> 💡 Pro-tip: it's useful to check the wifi speed of your accommodation before confirming a booking.
|
||||
|
||||
|
||||
## 🚨 Emergencies
|
||||
|
||||
In case of an emergency, we'll use the emergency information provided in BambooHR.
|
||||
|
||||
|
||||
## 📌 Useful resources
|
||||
|
||||
Some insurers specialising in global travel insurance:
|
||||
|
||||
* [World Nomads](https://worldnomads.com)
|
||||
* [True Traveller (EU-focused)](https://www.truetraveller.com)
|
||||
* [IMG (US-based)](https://www.imglobal.com/travel-medical-insurance/patriot-travel-medical-insurance)
|
||||
* [Safety Wings](https://safetywing.com/)
|
||||
|
||||
International prepaid SIM cards:
|
||||
|
||||
* [TravelSIM](https://travelsim.com)
|
||||
* [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.
|
||||
@@ -0,0 +1,90 @@
|
||||
# 🌟 Value-creating behaviours
|
||||
|
||||
## 🧘 Focus
|
||||
### Great ✅
|
||||
* Prioritising and deprioritising efforts correctly - most effort on the most important thing for IFT’ continuance
|
||||
* Translate theory into pragmatic decisions
|
||||
* Find ways to increase revenue
|
||||
|
||||
### Not great ❌
|
||||
* Spending huge amounts of time on lower priority work
|
||||
* Getting sidetracked
|
||||
|
||||
## 🗣️ Good communication
|
||||
### Great ✅
|
||||
* Explaining clearly and calmly in text/Discord/ Status app
|
||||
* Asking questions and explanations
|
||||
* Good technical documentation
|
||||
* Answer timely/precisely/don’t let people hang (within async)
|
||||
* Giving feedback, timely
|
||||
* Asking for feedback, timely
|
||||
* Showing empathy
|
||||
|
||||
### 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 ✅
|
||||
* Supporting project rituals
|
||||
* Offering a hand/helping other core contributors
|
||||
* Helping new core contributors adjust to the project
|
||||
* Resolving tensions
|
||||
* Sharing knowledge
|
||||
* Improving internal processes
|
||||
* Flagging issues
|
||||
|
||||
### Not great ❌
|
||||
* Going invisible
|
||||
* Not documenting what you’re working on
|
||||
* Delaying others’ work
|
||||
* Being late to meetings/project rituals
|
||||
|
||||
## 🤝 Collaboration across other projects
|
||||
### Great ✅
|
||||
* Cross-functional projects or ideas that can improve IFT as a whole
|
||||
* Reading/being active on channels outside of the immediate area of work
|
||||
* Supporting with events/community
|
||||
* Helping communication flow/easing misunderstandings
|
||||
* Replying to questions from other core contributors outside your project
|
||||
|
||||
### 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 ✅
|
||||
* Picking up on things that need to happen, and jumping in to make them happen
|
||||
* Looking outside of what we’ve always done, taking inspiration from the wider world
|
||||
|
||||
### Not great ❌
|
||||
* Waiting for instructions at all times
|
||||
* Raising issues without follow up action
|
||||
|
||||
## 💪 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
|
||||
* Not + lines of code (mostly, the less lines of code needed to achieve the objective the better)
|
||||
* Overall contribution to project’s output (proportional to skill)
|
||||
|
||||
### Not great
|
||||
* 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 ✅
|
||||
* Speaking at events
|
||||
* Being an ambassador
|
||||
* Contributing to discussions on EIP and other ecosystem developments (Github, Discourse, Twitter, etc)
|
||||
|
||||
## 🛠️ Master own skill/speciality
|
||||
### Great ✅
|
||||
* Delivering your project or providing your services at the best of your ability
|
||||
* Always be learning
|
||||
* Striving for quality
|
||||
@@ -0,0 +1,29 @@
|
||||
# 🚀 Contributing to this guide
|
||||
|
||||
The Contributors Guide is an open living repo built for you. The truth is, the organisation evolves faster than it can keep the documentation updated. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit.
|
||||
|
||||
Here you'll find helpful guidelines on how to contribute to this guide and make it yours!
|
||||
|
||||
_Note: You can start contributing only once access to the organisation is provided to you by people-ops. Prior to that, the github link will not be working._
|
||||
|
||||
## 👾 Contributing with pull requests
|
||||
|
||||
Whether you'd like to fix typos, update information, add sections, or build new content, you can create a pull request to contribute to the guide.
|
||||
|
||||
Our current workflow has two main branches: `master` that deploys to `[contributors.free.technology](https://contributors.free.technology)` and `develop` that deploys to `[dev-contributors.free.technology](https://dev-contributors.free.technology)`.
|
||||
|
||||
Before creating a pull request, create a new branch from `develop` and commit your changes to one or multiple PRs. Once finished, assign someone from the People Ops team to review or comment on it. Once merged, we'll delete the branch, and you'll see your contributions on this handbook!
|
||||
|
||||
## 📌 Leaving feedback with issues
|
||||
|
||||
Issues open a world of possibilities: from proposing changes to simply dropping an idea or leaving comments or tasks.
|
||||
|
||||
There are a few ways to create an issue:
|
||||
|
||||
* Go to the `issues` tab in the Contributor guide repo and create one.
|
||||
* From the source code of a file, click the `+` sign at the beginning of a line.
|
||||
* From a comment from a pull request, click `reference in new issue`.
|
||||
|
||||
Just like a PR, assign the issue to someone from the People Ops team, and we'll tag/re-assign it accordingly to address it.
|
||||
|
||||
The People Ops team is responsible for the maintenance of this guide, but it's really a collective effort. So please help us make it better for you and future readers!
|
||||
@@ -1,27 +0,0 @@
|
||||
# 🚀 Contributing to this guide
|
||||
|
||||
Status Contributors Guide is an open living repo built for you. The truth is Status evolves faster than it does the documentation. Read it carefully, and feel free to add sections, suggest changes, or make proposals for others to edit.
|
||||
|
||||
Here are you'll find helpful guidelines on how to contribute to this guide and make it yours!
|
||||
|
||||
## 👾 Contributing with pull requests
|
||||
|
||||
Whether you'd like to fix typos, update information, add sections, or build new content, you can create a pull request to contribute to the handbook.
|
||||
|
||||
Our current workflow has two main branches: `mater` that deploys to `[contributors.status.im](https://contributors.status.im)` and `develop` that deploys to `[dev-contributors.status.im](https://dev-contributors.status.im)`.
|
||||
|
||||
Before creating a pull request, create a new branch from `develop` and commit your changes to one or multiple PRs. Once finished, assign someone from the People Ops team to review or comment on it. Once merged, we'll delete the branch, and you'll see your contributions on this guide!
|
||||
|
||||
## 📌 Leaving feedback with issues
|
||||
|
||||
Issues open a world of possibilities: from proposing changes to simply dropping an idea or leaving comments or tasks.
|
||||
|
||||
There are a few ways to create an issue:
|
||||
|
||||
* Go to the `issues` tab in the Status Contributors Guide repo and create one.
|
||||
* From the source code of a file, click the `+` sign at the beginning of a line.
|
||||
* From a comment from a pull request, click `reference in new issue`.
|
||||
|
||||
Just like a PR, assign the issue to someone from the People Ops team, and we'll tag/re-assign it accordingly to address it.
|
||||
|
||||
The People Ops team keeps this guide's maintenance, but it's really a collective effort. So please help us make it better for you and future readers!
|
||||
@@ -2,91 +2,134 @@
|
||||
|
||||
## How to get reimbursed for expenses?
|
||||
|
||||
You can request a reimbursement for expenses incurred on behalf of Status during the project's development. You can read about some of these expenses at:
|
||||
* [Workspace, computers and devices](src/perks/workspace-computers-and-devices.md)
|
||||
* [Events and meetups](src/perks/events-and-meetups.md)
|
||||
* [Traveling for Status](src/remote-at-status/traveling-for-status.md)
|
||||
* [Essential reading](src/welcome-to-status/essential-reading.md)
|
||||
You can request a reimbursement for reasonable expenses incurred on behalf of IFT during the project's development. You can read about some of these expenses at:
|
||||
* [Computers and devices](../contributing-to-ift/laptops-and-devices.md)
|
||||
* [Events and meetups](../contributing-to-ift/events-and-meetups.md)
|
||||
* [Travelling for IFT](../contributing-to-ift/travelling-for-IFT.md)
|
||||
* [Essential reading](../fundamentals/essential-reading.md)
|
||||
|
||||
It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly. The standard expense reimbursement process uses:
|
||||
* [Expensify](https://www.expensify.com/) to report and store the expense receipts, AND
|
||||
* Adding expenses to your monthly invoice sent to `billing@statusm.im` to send the reimbursement.
|
||||
It's essential that you carefully read the following instructions to get reimbursed so we can file expenses correctly.
|
||||
To get your expenses reimbursed correctly and on time:
|
||||
- Ensure that you get your purchase or travel request approved by your budget owner via Discord, email, or other means of communication.
|
||||
- After the purchase or travel, submit the expense receipts to [Expensify](https://www.expensify.com/)
|
||||
- Add these expenses to your monthly invoice sent to `billing@status.im`
|
||||
|
||||
In addition to these notes, you can find a guide [here](https://docs.google.com/document/d/1UX9uizHnJDXZjghiXiBGUexrQxxaiyv3-KpyKfHYJKU/edit#) and you can also view our video walkthrough [here](https://youtu.be/04YB_Xz48E8).
|
||||
|
||||
## How to report expenses through Expensify
|
||||
|
||||
We use Expensify to store and report the expense details and receipts incurred on behalf of Status during the project's development.
|
||||
We use Expensify to store and report the expense details and receipts incurred on behalf of IFT during the project's development. Please note that this guide is based on the current version of Expensify and not the new Expensify experience.
|
||||
|
||||
### Account setup
|
||||
|
||||
You'll need to head to the [Expensify](https://www.expensify.com/) web or download the mobile app and sign in using your Status email to get started. Please input your full name as it appears in your Bamboo profile when setting up your Expensify account.
|
||||
You'll need to head to the [Expensify](https://www.expensify.com/) web or download the mobile app and sign in using your Status (@status.im) email to get started. Please input your full name as it appears in your BambooHR profile when setting up your Expensify account.
|
||||
|
||||

|
||||
If you don’t have access to your account, please reach out to the Finance team to create or update your account.
|
||||
|
||||
### Uploading expenses
|
||||
|
||||
We kindly ask you to upload expenses as they incur or by the end of a trip to avoid complications like old or lost receipts.
|
||||
### 1. Log into Expensify.com
|
||||
|
||||
Go to the `Expense` tab on either the web or mobile apps to upload expenses manually or by scanning them:
|
||||

|
||||
|
||||

|
||||
If you don’t have access to your account, message us on our `#finance` channel to create or update your account.
|
||||
Once you have logged in please ensure that you are claiming your expenses under the correct policy. Your policy should match the correct project for example "IFT - Finance" or "Status-Mobile"
|
||||
|
||||
1. Make sure to fill or review all the fields as the scanning feature isn't always reliable. Pay special attention to amounts and currencies.
|
||||
2. You should claim expenses using the date they incurred. For example: if the purchase happened on Jan 10th and you're uploading or requesting the reimbursement on Jan 14th, the correct expense date would be Jan 10th.
|
||||
3. When paying for a group (i.e., a meal shared with other contributors from Status), please list all those in attendance in the `attendee's` field.
|
||||
4. Choose a category for your expense and add a detailed description of how's it business-related. Include information such as the trip it belongs to, who approved it, what budget it comes from, whether or not you've paid for other contributors (i.e., group meal), and any other data you consider relevant.
|
||||

|
||||
|
||||
* Team Event Expense
|
||||
* Category: Events
|
||||
* Description: "Devcon Conference, Berlin - Taxi from LHR airport to conference with 1 other team member, Joe"
|
||||
### 2. Go to Reports
|
||||
|
||||
* Another Team Event Expense
|
||||
* Category: Meals & Drinks
|
||||
* Description: "People Ops Meetup - Evening meal on May 26th with 3 others: John, Jane, Joseph"
|
||||
Please use the ‘Reports’ tab instead of the ‘Expenses’ tab as this will allow you to submit multiple claims together. This makes it easier for you and Finance to approve and track your expense claims.
|
||||
|
||||

|
||||

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

|
||||
Create a new report for your expenses. One report can include multiple expenses hence it is important for you to submit this as a report and not as an individual expense claim.
|
||||
|
||||
> ⚠️ You **always need to submit a receipt with each expense you log.** Make sure to take photos or keep digital receipts handy - missing receipts might result in your reimbursements not being approved. We understand that in some rare cases, this is not possible. When not possible, please provide as much info as possible and why no receipt is possible.
|
||||

|
||||
|
||||
### Submitting an expense report for approval
|
||||
|
||||
Uploading expenses and submitting an expense report are different actions within Expensify. Once you've uploaded all your receipts, it's fundamental that you submit the report for Finance's review and approval.
|
||||
### 4. Add Expenses
|
||||
Click ‘Add Expenses’ to start adding claims to your report.
|
||||
|
||||
You must submit the expense report by the 10th of the month before submitting the monthly invoice on the 15th. To do that, click the `Reports` tab and `Submit` your report.
|
||||

|
||||
|
||||

|
||||
|
||||
Please follow these links if you need help with [creating expenses](https://community.expensify.com/discussion/4560/how-to-create-expenses-manually) and [submitting reports](https://community.expensify.com/discussion/4561/how-to-submit-a-report/p1?new=1) on Expensify. If you need further help, reach out to the Finance team, and we'll be able to guide you through the process.
|
||||
### 5. New Expense
|
||||
Create a new expense. Do not use previously created expenses from the available list. It’s important to create a new expense even for recurring expenses as we need up-to-date information for each claim. Any outdated expense claims will be rejected.
|
||||
|
||||
### Adding the expenses to your monthly invoice
|
||||

|
||||
|
||||
The finished and approved report from Expensify will show the total for each expense category. For example, if you have several costs in one category, Expensify will show the following:
|
||||
|
||||

|
||||
### 6. Fill in the expense claim
|
||||
|
||||
Your invoice should only contain the total per category, not each expense item.
|
||||
<b> It is mandatory to complete all of these fields according to the requirements below! Please ensure that you complete a separate claim for each expense. Joint expenses will be rejected and will require 2nd submission. </b>
|
||||
|
||||
<i> Merchant (Field 1) </i> - The name of the company/brand/service provider used for the expense claim
|
||||
|
||||
<i> Date (Field 2) </i> - Date when the expense took place. This needs to match the date that is on the expense invoice/receipt which you will attach in ‘Field 8’
|
||||
|
||||
<i> Total (Field 3) </i> - Either the total amount spent or the maximum allowable amount per claim (e.g. for coworking or hardware expenses). If you are claiming the expense in full, please record the exact amount as seen on the invoice/receipt which you will attach in ‘Field 8’
|
||||
|
||||
<i> Currency (Field 4) </i> - Choose the same currency as on the receipt/invoice of your expense (shown in ‘Field 8’). Expensify will automatically calculate the correct exchange rate for your invoicing currency.
|
||||
|
||||
<i> Category (Field 5) </i> - Choose the category of your expenses (e.g Hardware, Travel…)
|
||||
|
||||
<i> Attendees (Field 6) </i> - If this is your own expense, then please leave it as it is; however, if you attend a team meal and you paid for everyone else’s meal as well, please tag them in the attendee's fees as this expense covers multiple contributors.
|
||||
|
||||
<i> Description (Field 7) </i> - Please specify the event you are attending and the reason/additional information for the expenses. This is an important field and will enable us to track event spending.
|
||||
|
||||
<i> Document (Field 8) </i> - attach an invoice/receipt that proves your expense claim and confirms the details shown in fields 1-7.
|
||||
|
||||
<i> Events (Field 9) </i> - for all travel expenses select the event you are attending. If the event you are going to is not available, please message us on our Discord #ask-finance channel.
|
||||
|
||||

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

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

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

|
||||
## When are you getting reimbursed
|
||||
|
||||

|
||||
|
||||
## When you're going to be 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 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 of February. This invoice was received after the payment cut-off date for February, so it will be paid in the following payment run.
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.
|
||||
Scenario 2: David submits an invoice on the 14th of February, and he includes an expense claim that shows as not approved in Expensify. The Finance team will reach out to David, to amend the invoice. If the invoice is not amended on time before the payment cut-off date, it will not be included in the payment run.
|
||||
|
||||
Scenario 3: David submits an invoice on the 15th of February, and he includes an expense claim that shows as approved in Expensify. The Finance team will include it in the payment run as usual.
|
||||
|
||||
If you have other questions related to this process, please feel free to ping the Finance team in the `#finance` channel or through an email to `billing@status.im`.
|
||||
|
||||
@@ -1,33 +1,34 @@
|
||||
# 💰 Getting paid
|
||||
|
||||
As a Contributor, you need to send your PDF invoice to the Billing inbox. Here you'll find helpful information about deadlines, formats and other requirements to get compensated correctly on time.
|
||||
As a core contributor and those with services agreements with IFT, you'll need to send your PDF invoice to the Billing inbox (billing@status.im). Here, you'll find helpful information about deadlines, formats and other requirements to ensure your invoices are processed correctly and you receive timely payment.
|
||||
|
||||
## Invoices due date
|
||||
|
||||
Send your invoice in PDF format to `billing@status.im`, latest on the 15th. Your invoicing period is the current calendar month (i.e., invoice by October 15 for your services in October).
|
||||
Send your invoice in a PDF format to (`billing@status.im`), **latest on the 15th of every month**. Your invoicing period is the current calendar month (i.e., invoice by October 15 for your services from 1 - 31 October).
|
||||
|
||||
## What to include
|
||||
|
||||
You need to include your total expenses per category in your invoice (and these should be submitted separately via Expensify). Check out [expense reimbursements](/src/finance/expense-reimbursements.md/) for more details on this topic.
|
||||
You need to include your total approved expenses per category in your invoice (and these should be submitted separately via Expensify). Check out [expense reimbursements](../finance/expense-reimbursements.md/) for more details on this topic.
|
||||
|
||||
Your invoice should include:
|
||||
* Your legal name and address as per your agreement.
|
||||
* A unique invoice number.
|
||||

|
||||
|
||||
Your invoice must include:
|
||||
|
||||
* Your legal name (or legal entity) and address as per your agreement.
|
||||
* A unique invoice number (this number should be sequential based on your invoice numbering, if you have any questions, please reach out to the Finance and Accounting team, or your accountant, if you have one).
|
||||
* The date the invoice is issued.
|
||||
* Payment due date.
|
||||
* Status legal entity with which you have the services agreement.
|
||||
* The payment due date.
|
||||
* The date range of the invoicing period according to your agreement (i.e., "March 1 to March 31").
|
||||
* Description of the service rendered or reference to your contract.
|
||||
* Total per category for expense reimbursements being claimed as per the [expense reimbursements guide](/src/finance/expense-reimbursements.md/).
|
||||
* Total approved expense reimbursements per category as per the [expense reimbursements guide](../finance/expense-reimbursements.md/).
|
||||
* According to your agreement, the full fee and the fiat currency (in CHF, USD, EUR, or other).
|
||||
* Your contributor number as per your Bamboo profile.
|
||||
* Your contributor number as per your BambooHR profile.
|
||||
|
||||
You can use [this template](https://docs.google.com/spreadsheets/d/1FbH0CxLqar0ZyjhiMEA5ceToL2ikv5C-Rv-qCwBNeRA/edit#gid=790763898), but please remember to download the finished invoice as a PDF before sending it and that the exported PDF is on a single page.
|
||||

|
||||
|
||||
Address the invoice to the Status legal entity with which you have your agreement. The primary Status Legal Entities are:
|
||||
* Status Research & Development GmbH, Baarerstrasse 10, 6302 Zug, Switzerland
|
||||
* Status Research & Development Deutschland GmbH, ℅ Cormoran GmbH, Am Zirkus 2, 10117 Berlin, Germany
|
||||
* Status Holdings Pte. Ltd., 160 Robinson Road, #24-09, Singapore 068914
|
||||
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 **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.
|
||||
|
||||
@@ -35,15 +36,15 @@ There are exceptional cases where another legal entity applies. Please use the c
|
||||
|
||||
### Bank and Wallet details
|
||||
|
||||
Please maintain your details on your Bamboo profile if you have one. For simplicity, we only allow the indication of one wallet and one bank account (if you have intermediary accounts, please use the appropriate fields of the Bank Information section). You can edit it directly if you want to change the % paid in ETH, DAI, or SNT. Once you save it, it will send an approval request to the Finance team —the reason is so that we get a notification that something's changed and can update our payment records timely.
|
||||
Please maintain your details on your BambooHR profile if you have one. For simplicity, we only allow the indication of one wallet and one bank account (if you have intermediary accounts, please use the appropriate fields of the Bank Information section). You can edit it directly if you want to change the % paid in ETH, DAI, or SNT. Once you save it, BambooHR will send an approval request to the Finance team. The reason for this approval step is so that the Finance team get a notification that something has changed and can ensure we're using the correct payment details in subsequent payment runs.
|
||||
|
||||
Only after we confirm the approval will your changes be reflected in your Bamboo profile, and you can then change your payment split preferences again.
|
||||
Only after we confirm the approval, will your changes be reflected in your BambooHR profile. If you need to change your bank details or payment preference, any pending changes will need to be approved first, in order for you to be able to make a new change.
|
||||
|
||||
If you need a specific reference to complete this payment, please state it explicitly on your invoice.
|
||||
|
||||
> ⚠️ To make sure that your changes are considered for the current month, change your info before the 15th. Remove accented or special characters. We can only correctly upload plain text to the system.
|
||||
> ⚠️ To make sure that your changes are considered for the current month, change your info before the 15th of each month. Remove accented or special characters. We can only correctly upload plain text to the system.
|
||||
|
||||
Please be sure that your employment contract or services agreement reflects your registered address for banking purposes, as our bank sometimes asks us to validate that banking details match contract details.
|
||||
Please be sure that your services agreement reflects your registered address for banking purposes, as our bank sometimes asks us to validate that banking details match contract details.
|
||||
|
||||
### Getting Paid in Crypto
|
||||
|
||||
@@ -51,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 colleagues in the #people-ops channel when you have questions about crypto payments and wallets. Not everyone starts with the same level of knowledge, and building it up is part of working with Status.
|
||||
Don't be shy to ask your more experienced core contributors in the `#finance` channel on logos discord or Status app when you have questions about crypto payments and wallets. Not everyone starts with the same level of knowledge, and building it up is part of working with IFT.
|
||||
|
||||
### Rate Calculation
|
||||
|
||||
@@ -60,53 +61,30 @@ For determining rates when paying in crypto, we establish the following two rate
|
||||
* The average closing rate across the last five days of the invoiced period, OR
|
||||
* The current rate when payments are being issued.
|
||||
|
||||
You can change your split % preference monthly. Just make sure you update your preferences on Bamboo before the 15th of the month.
|
||||
You can change your crypto split % preference monthly. Just make sure you update your preferences in BambooHR before the 15th of each month.
|
||||
|
||||
## Special situations
|
||||
|
||||
### December pay
|
||||
|
||||
As the holiday season affects the regular working days, we might bring forward the December payment run. Please be aware of date changes for the December payment run.
|
||||
Due to operational considerations in December, we might bring forward the December payment run. Please be aware of date changes for the December payment run.
|
||||
|
||||
### Hourly rate contributors
|
||||
|
||||
If you're paid on an hourly basis and need to estimate your hours in the remainder of the month and reconcile them in the next invoice (as you'll be invoicing by the 15th of each month), it's ok to do that, or you could carry forward actual hours to your next invoice.
|
||||
|
||||
If your fees have been agreed on an hourly rate basis, our monthly cap for hours billed is the lower of either the amount specified in your agreement with us or the number of business days in the month x 8.5 hours per day, i.e.:
|
||||
|
||||
A month with 23 workdays has an hourly billing cap of 23 * 8.5 hours = 195.5 hours.
|
||||
If your fees have been agreed on an hourly rate basis, the monthly cap for hours billed is the fee equivalent to a monthly amount (or the calculated monthly equivalent) specified in your agreement with IFT.
|
||||
|
||||
Please discuss with People Ops if you intend to bill over this amount.
|
||||
|
||||
### Pro-rating the first month
|
||||
### During your first month
|
||||
|
||||
For your first month (if being paid on an annual or monthly basis), please prorate the amount in your invoice to reflect the number of days from the beginning of your contract to the last day of the month.
|
||||
For your first month (if your Fee is stated as a (maximum) annual or monthly amount), please only state the amount in your invoice to reflect the period of time you actually contributed.
|
||||
|
||||
*Example: If March has 22 working days (counting Mon-Fri) and you started on a Monday, March 12, your monthly invoice amount will be {your monthly fee amount}/22 x 15.*
|
||||
*Example: If after you started providing your services, you contributed 10 (ten) days in March, your monthly invoice amount will be {your monthly fee amount}/30 x 10.*
|
||||
|
||||
Please bill the flat monthly or annual/12 figure for each subsequent month.
|
||||
|
||||
*Example: You joined Status on March 12. During April, you took 1 week of vacation. Your April invoice amount will be {your monthly stipend amount in full} or {your annual stipend amount}/12*
|
||||
|
||||
Please use the working days shown below for your calculations:
|
||||
|
||||
**Working days 2022**
|
||||
|
||||
| January - 21 | February - 20 | March - 23 |
|
||||
|:---:|:---:|:---:|
|
||||
| April - 21 | May - 22 | June - 22 |
|
||||
| July - 21 | August - 23 | September - 22 |
|
||||
| October - 21 | November - 22 | December - 22 |
|
||||
|
||||
### Expense Reimbursements
|
||||
|
||||
From time to time, you might need to pay reimbursable expenses for the development of the project. To read more on how to get reimbursed for these expenses, please follow [this link](/src/finance/expense-reimbursements.md).
|
||||
From time to time, you might need to pay reimbursable expenses for the development of the project. To read more on how to get reimbursed for these expenses, please follow [this link](../finance/expense-reimbursements.md).
|
||||
|
||||
### Swiss and German employees
|
||||
|
||||
You will be paid via monthly payroll as calculated by our outsourced payroll partners. There is no need to submit an invoice for your monthly salary. Please, maintain the percentages you wish to receive in crypto on your Bamboo profile, as we will prepare payments based on the split you indicate there.
|
||||
|
||||
|
||||
*****
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.
|
||||
|
||||
@@ -1 +1,5 @@
|
||||
# Finance
|
||||
|
||||
In this section you will find some information on finance processes.
|
||||
|
||||
If you have any questions, please reach out to the Finance team or your People Partner.
|
||||
|
||||
@@ -1,50 +1,56 @@
|
||||
# 🧾 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.
|
||||
|
||||
## Supplier Information
|
||||
* Supplier Name (*);
|
||||
* Supplier Address (*);
|
||||
## Invoice Header
|
||||
|
||||

|
||||
|
||||
### Document Information
|
||||
* The word INVOICE or CREDIT NOTE or DEBIT NOTE (mandatory);
|
||||
* Invoice/note number (must be unique) (mandatory);
|
||||
* Invoice/note date (dd/mm/yyyy) (mandatory);
|
||||
* Due date (dd/mm/yyyy) (mandatory);
|
||||
|
||||
### Supplier Information
|
||||
* Supplier Name (mandatory);
|
||||
* Supplier Address (mandatory);
|
||||
* Supplier’s tax registration number (if applicable);
|
||||
* Supplier’s telephone number, contact person and email address (optional);
|
||||
* Payment information (optional).
|
||||
|
||||
## Status Information
|
||||
* Status legal entity and invoicing address (*).
|
||||
### IFT Information
|
||||
* Invoicing address (mandatory).
|
||||
|
||||
| 🇨🇭 Status Switzerland | 🇸🇬 Status Singapore | 🇩🇪 Status Germany |
|
||||
|:---:|:---:|:---:|
|
||||
| Status Research & Development GmbH | Status Holdings Pte. Ltd. | Status Research & Development Deutschland GmbH |
|
||||
| Baarerstrasse 10, | 160 Robinson Road, #24-09, | Am Zirkus 2, |
|
||||
| 6302 Zug, | 068914, Singapore | 10117 Berlin, |
|
||||
| Switzerland | Singapore | Germany |
|
||||
| MWST-Nr: CHE-319.159.934 MWST | UEN: 201625575Z | USt-IdNr: DE317300297 |
|
||||
##### IFT Singapore
|
||||
IFT Studio Pte. Ltd.
|
||||
160 Robinson Road, #24-09,
|
||||
068914, Singapore
|
||||
UEN: 201625575Z
|
||||
|
||||
|
||||
## Invoice Content
|
||||
|
||||

|
||||
|
||||
### Product/Service Description
|
||||
* Currency (mandatory);
|
||||
* Specification of goods and/or services delivered (mandatory);
|
||||
* Total net amount (if no taxes are applicable) (mandatory).<br>
|
||||
|
||||
## Content Information
|
||||
* The word INVOICE or CREDIT NOTE or DEBIT NOTE (*);
|
||||
* Invoice/note number (must be unique) (*);
|
||||
* Invoice/note date (dd/mm/yyyy) (*);
|
||||
* Due date (dd/mm/yyyy) (*);
|
||||
* Payment terms (optional);
|
||||
* Currency (*);
|
||||
* Specification of goods and/or services delivered (*);
|
||||
* Total net amount (if no taxes are applicable) (*).
|
||||
**If taxes are applicable**
|
||||
* Tax amount (*);
|
||||
* If multiple taxes are applicable, the tax rate for every net amount should be specified (*);
|
||||
* Total payable amount (*).
|
||||
* Tax amount;
|
||||
* If multiple taxes are applicable, the tax rate for every net amount should be specified;
|
||||
* Total payable amount.
|
||||
|
||||
|
||||
You can download a copy of this checklist [here](https://docs.google.com/document/d/1Opy0n_BckSD7_BD6B5a7VTH2sZgqhzinQk-4QBWBeo8/).
|
||||
|
||||
*/* Mandatory fields.*
|
||||
|
||||
*****
|
||||
|
||||
Without this information, we run into issues with properly booking the expense for accounting purposes, which creates extra work hours to resolve on the backend. So thanks in advance for helping us out on this 🙌🏻
|
||||
|
||||
If you have any questions on whether your invoice has the format and information needed, feel free to reach out to the Finance team, and we'll look into it together!
|
||||
|
||||
|
||||
*****
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the Finance team to review it.
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
# In case of a dispute
|
||||
|
||||
## Background
|
||||
|
||||
* While we hope that you may never have to run into this issue, and for the most part it is relatively exceptional, IFT, like any other organisation, faces the risk of entering into disputes, whether they are arising from internal or external events, within or outside of IFT’ control and with different types of counterparties, from service provides to (former) core contributors (“Counterparty”).
|
||||
* Therefore we have developed this guidance for core contributors on how you can help prevent and mitigate potential disputes, protect IFT’ interests and how to best collaborate with Legal to resolve any disputes in the most peaceful and amicable manner possible.
|
||||
|
||||
## Guidance
|
||||
|
||||
#### When to involve Legal - the earlier, the better. However, please contact Legal immediately if:
|
||||
* It is more than likely that IFT will fail to fulfil its obligation(s) towards a Counterparty or if IFT has already failed on its obligation(s) towards a Counterparty (doesn’t matter if the Counterparty is aware about this or not). For example,
|
||||
* IFT failed to pay, or failed to pay on time any amounts due (e.g. an invoice has been unpaid past the stated due date);
|
||||
* Breached a term of a contract in any way, for example, by inappropriate use of services (e.g. a service is being used contrary to a service’s acceptable use policy); or
|
||||
* Breached confidentiality (e.g. a core contributor inadvertently shares confidential information with another third party that is not compliant with the contract).
|
||||
* If a Counterparty claims that IFT is not fulfilling its obligations (whether this is accurate or not) or threatens legal action against IFT in this respect; or
|
||||
* if a legal counsel or a law firm has taken over communications with IFT;
|
||||
|
||||
#### If any of the above takes place - the following should be observed:
|
||||
* Follow good practices: Preserve all communications with the Counterparty, such as discord chats, emails, any social media chats (e.g. Telegram), calls and meeting notes.
|
||||
|
||||
## After you contact Legal:
|
||||
|
||||
* Do not let the Counterparty know you are involving Legal, (for example, do not include Legal in -cc to an email with a Counterparty) unless Legal has advised you to do so. In our experience, if a Counterparty becomes aware that Legal is being involved, it may escalate an already sensitive situation or unnecessarily provoke hostility.
|
||||
* Communicate with the Counterparty only in consultation with Legal and other internal stakeholders as relevant, for example, your team lead.
|
||||
* Any communication with the Counterparty must be screened and approved by Legal.
|
||||
* Any strategy or potential proposals/compromises must also be discussed with Legal.
|
||||
|
||||
## After the dispute has been resolved:
|
||||
|
||||
* Rectify/Monitor - Legal and core contributors should continue to monitor for any potential signs that the dispute may resume or re-escalate and ensure that events or factors which led to the dispute have been adequately addressed (e.g. has IFT’ failure to perform an obligation now being rectified?)
|
||||
* Lessons learned - Legal, core contributors, relevant team lead, and any other relevant internal stakeholders should form a “lessons learned” group to review the events and factors, which led up to the dispute and determine whether any changes to procedure or practices should be made to prevent or mitigate the chance of such a dispute arising again. Notes and conclusions should be well documented for future reference
|
||||
@@ -1,20 +1,21 @@
|
||||
# ⚓️ Contributor Code of Conduct
|
||||
# ⚓️ Code of Conduct
|
||||
|
||||
The Code of Conduct serves to establish guidelines on how to conduct your behavior.
|
||||
The Code of Conduct serves to establish guidelines on how to conduct your behaviour.
|
||||
|
||||
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 honored by everyone who represents the project officially or informally, claims affiliation with the project, or participates directly.
|
||||
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.
|
||||
|
||||
@@ -24,13 +25,13 @@ Nothing is more important than to show appreciation for every and anyone's contr
|
||||
|
||||
## Be Considerate
|
||||
|
||||
Other people will use our work, and we, in turn, depend on the work of others. Any decision we take will affect users and fellow team members, and we should consider them when making decisions.
|
||||
Other people will use our work, and we, in turn, depend on the work of others. Any decision we take will affect users and core contributors, and we should consider them when making decisions.
|
||||
|
||||
When somebody leaves or disengages from the project, we ask that they do so in a way that minimizes disruption to the project. They should tell people they are leaving and take the proper steps to ensure others can pick up where they left off.
|
||||
When somebody leaves or disengages from the project, we ask that they do so in a way that minimises disruption to the project. They should tell people they are leaving and take the proper steps to ensure others can pick up where they left off.
|
||||
|
||||
## Respect the staff
|
||||
## Respect other core contributors
|
||||
|
||||
Core contributors have been chosen on a specific basis to have good judgment. The staff will always attempt to implement universally peaceful solutions but are tasked with establishing the most civil solution for the majority of the community.
|
||||
Core contributors have been chosen on a specific basis to have good judgement. Core contributors will always attempt to implement universally peaceful solutions but are tasked with establishing the most civil solution for the majority of the community.
|
||||
|
||||
Therefore, they cannot always please everyone with the decisions made. Please, help out to contribute to a healthy community.
|
||||
|
||||
@@ -42,14 +43,14 @@ The participants in the project should be able to accept and give constructive c
|
||||
|
||||
## Civility
|
||||
|
||||
Uncivil behavior will not be tolerated in our community. Sutton's "No Asshole Rule" has these concise pointers on the kind of behavior that is considered uncivil:
|
||||
Uncivil behaviour will not be tolerated in our community. Sutton's "No Asshole Rule" has these concise pointers on the kind of behaviour that is considered uncivil:
|
||||
|
||||
> Two tests are specified for recognition of the asshole.
|
||||
>
|
||||
> 1. After encountering the person, do people feel oppressed, humiliated, or otherwise worse about themselves?
|
||||
> 2. Does the person target people who are less powerful than them?
|
||||
>
|
||||
> Their unpleasant actions are cataloged as The Dirty Dozen:
|
||||
> Their unpleasant actions are catalogued as The Dirty Dozen:
|
||||
>
|
||||
> * Insults
|
||||
> * Violation of personal space
|
||||
@@ -73,9 +74,9 @@ Those who are asked or answer a general question should be responsive and helpfu
|
||||
|
||||
## Be Collaborative
|
||||
|
||||
What we work together to produce is a complex whole made of many parts and is the sum of many dreams. Collaboration between teams that each have their own goal and vision is essential. To be efficient and effective, and for the whole to be more than the sum of its parts, each team must make an effort to understand the system as a whole.
|
||||
What we work together to produce is a complex whole made of many parts and is the sum of many dreams. Collaboration between projects that each have their own goal and vision is essential. To be efficient and effective, and for the whole to be more than the sum of its parts, each team must make an effort to understand the system as a whole.
|
||||
|
||||
Wherever possible, we work closely with projects in the same space and others in the Ethereum community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible. Collaboration at all levels improves the quality of our work, and we value it both internally and externally.
|
||||
Wherever possible, we work closely with other projects in the same space and others in the Ethereum community to coordinate our efforts. We prefer to work transparently and involve interested parties as early as possible. Collaboration at all levels improves the quality of our work, and we value it both internally and externally.
|
||||
|
||||
## Discuss and Communicate
|
||||
|
||||
@@ -89,22 +90,22 @@ Some members may be more visible than others, but good ones use their visibility
|
||||
|
||||
## Open Source Community
|
||||
|
||||
We invite any and everybody to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required commitment, capacity, and competence.
|
||||
We invite any and everybody to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any core contributor who demonstrates the required commitment, capacity, and competence.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise, unacceptable behavior may be reported by contacting the Status People Ops team at `people-ops@status.im` or pinging the individual POPs folks for a confidential chat.
|
||||
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.
|
||||
|
||||
Allegations of misconduct typically require some behind-the-scenes fact-checking to verify what happened. If you're involved in an incident of misconduct, you'll be asked for your observations and recollections of the event. People Ops will follow up with you to let you know the next steps.
|
||||
|
||||
Depending on the severity of the misconduct, this may be a formal warning, through to immediate dismissal.
|
||||
Depending on the severity of the misconduct, this may be a formal warning, through to immediate termination of the relevant contract.
|
||||
|
||||
## License
|
||||
## licence
|
||||
|
||||
Status.im is a Free Software project, and the individuals and communities around it are its custodians. We choose not to exclude others from using, understanding, modifying, and distributing our work. In doing so, we trust one another to act in the best interests of the broader human community that Status.im is designed to serve. This license holds the developers to account in the knowledge that the software is a common trust and that it is a privilege and a responsibility to continue to develop it.
|
||||
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.*
|
||||
@@ -1,72 +1,172 @@
|
||||
# 🔑 Contributor Privacy Policy
|
||||
# 🔑 Core Contributor Privacy Policy
|
||||
|
||||
As you can see from our [principles](https://our.status.im/our-principles/), we take privacy and transparency seriously. We strive to only request necessary and required data and not to hold that data longer than necessary.
|
||||
This Privacy Notice is effective as of February 2022.
|
||||
|
||||
Here is a quick explanation of what data we obtain, how we use that information, and how to update/control that information.
|
||||
This Privacy Notice refers to our commitment to treat all Personal Data (as defined below) of the relevant individuals, including contractors, and Provider’s Workers providing services to the Beneficiary (“Data Subjects”), with the utmost care and confidentiality.
|
||||
|
||||
## Policy brief & purpose
|
||||
With this Privacy Notice, we ensure that we gather, store, protect and handle Personal Data fairly, transparently and with respect towards individual rights, even after the termination of the contractual relationship with the Beneficiary, where applicable.
|
||||
|
||||
This Core Contributor Privacy Policy refers to our commitment to treat the information of employees, contractors, and contributors with the utmost care and confidentiality.
|
||||
We process Personal Data lawfully, fairly, securely and in a transparent manner. We only collect and process Personal Data that is adequate, relevant and limited to what is necessary for specified, explicit and legitimate purposes and we do not further process such Personal Data in a manner that is incompatible with those purposes. We keep Personal Data accurate and up to date and keep it in a form which permits identification of Data Subjects for no longer than is necessary.
|
||||
|
||||
With this policy, we ensure that we gather, store and handle data fairly, transparently and with respect towards individual rights.
|
||||
|
||||
## About
|
||||
|
||||
As part of our operations, we need to obtain and process information.
|
||||
|
||||
This information includes any offline or online data that makes a person identifiable such as names, addresses, usernames and passwords, digital footprints, photographs, social security numbers, financial data, etc.
|
||||
|
||||
Status collects this information in a transparent way and only with the full cooperation and knowledge of interested parties. Once this information is available to us, the following rules apply.
|
||||
|
||||
Our data will be:
|
||||
|
||||
* Accurate and kept up-to-date.
|
||||
* Collected fairly and for lawful purposes only.
|
||||
* Processed by Status within its legal and moral boundaries.
|
||||
* Protected against any unauthorized or illegal access by internal or external parties.
|
||||
|
||||
Our data will not be:
|
||||
|
||||
* Communicated informally.
|
||||
* Stored for more than a specified amount of time.
|
||||
* Transferred to organizations that do not have adequate data protection policies.
|
||||
* Distributed to any party other than the ones agreed upon by the data's owner (exempting legitimate requests from law enforcement authorities).
|
||||
|
||||
In addition to ways of handling the data, Status has direct obligations towards people to whom the data belongs. Specifically, we will:
|
||||
|
||||
* Let people know which of their data is collected.
|
||||
* Inform people about how we'll process their data.
|
||||
* Inform people about who has access to their information.
|
||||
* Allow people to request that we modify, erase, reduce, or correct data contained in our databases.
|
||||
|
||||
## Data
|
||||
|
||||
* **You provide:** as part of the recruitment/onboarding process, we may ask you to provide relevant data such as name, contact details, bank account, or wallet address. We may also request social security, identification, passport, or national insurance details where required by law. Depending on your contract with us, you may also provide us details of hours/days worked so that we can compensate you appropriately or verify that we have fulfilled our compliance obligations as your employer.
|
||||
* **We obtain:** assessments of your performance during the trial period and on an ongoing basis (based on peer feedback and evidence of work), details of periods of leave taken by you, including holiday, sickness absence, family leave, and the reasons for the leave, and notes of our discussions with you. We endeavor to maintain accurate information.
|
||||
* **We store:** pay records, including payslips and invoices; copies of contracts and formal notices/letters relating to your employment/contracting relationship with us.
|
||||
|
||||
You can request to see a copy of the data we hold on you. To do so, please get in touch with People Ops to make an access request.
|
||||
|
||||
## Use
|
||||
|
||||
* We store most of your data in our HR System (BambooHR). We keep some data (documents, payslips) in a secure Google Drive Folder. We tightly control access to the data to only members of the organization that have a valid reason to access your information (generally - People Ops & Finance).
|
||||
* We share the minimum necessary amounts of your data with the following third-party accounting, payroll, benefits, and compliance partners as applicable for statutory filings, benefits, and reporting:
|
||||
* HMT Partners (Switzerland)
|
||||
* The Friendly Accountants (UK)
|
||||
* Fidura (Switzerland)
|
||||
* Buchhalter Berlin / Lohnstar (Germany)
|
||||
* Pikohana (Singapore)
|
||||
* Atelier Consulting AG (Switzerland)
|
||||
* SwissLife (Switzerland)
|
||||
* Ebner-Stolz (Germany)
|
||||
* 3E Accounting (Singapore)
|
||||
* Yourpension (Switzerland)
|
||||
* Cleverkin S.R.O.
|
||||
* We will request your permission before releasing your data to any other third-party.
|
||||
|
||||
We hold your data while you are a contributor. If you're an employee, upon leaving Status, our policy is to store your data for a minimum of six years to comply with international statutory HR information retention legislation. We will delete your data after six years. If you have a question about the data we hold or how we use it, don't hesitate to contact `people-ops@status.im`.
|
||||
This Privacy Notice is issued by the Beneficiary, to explain how we process Personal Data before, during and after any contractual relationship with us and in connection with affiliation with us. We process Personal Data, in accordance with the applicable data protection laws, including the EU General Data Protection Regulation 2016/679 (the “GDPR”) where applicable. The Beneficiary is the entity that is considered the controller with respect to Personal Data processed by us.
|
||||
|
||||
|
||||
*****
|
||||
In this Privacy Notice where we refer to "we" or "us", we mean the Beneficiary.
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the Legal team to review it.
|
||||
## What data do we collect?
|
||||
The Beneficiary will process certain Personal Data related to Data Subjects. "Personal Data" means any
|
||||
information relating to an individual and processed by us, including any information through
|
||||
which an individual can be identified or identifiable, directly or indirectly, which may include:
|
||||
|
||||
* Contact and general information, such as name, surname, postal and/or email address,
|
||||
phone number, date of birth, gender, marital status, and photo (if such is provided to us).
|
||||
* A resume and any other information required to apply for the role with the Beneficiary.
|
||||
* Professional information, such as education credentials and professional experience and
|
||||
qualifications, professional networks, training employment history, board memberships
|
||||
and employment status.
|
||||
* Other information, if applicable, such as government issued identification number, social
|
||||
security number, identification document, passport, or national insurance details where
|
||||
required by law, tax status, bank account details, wallet address, travel and expenses,
|
||||
performance management, emergency contact details, compensation, holidays and
|
||||
benefits related information.
|
||||
* In case of contractors, details of the deliverables and/or services provided to compensate
|
||||
appropriately.
|
||||
* Assessments of a performance during the trial period and on an ongoing basis (based on
|
||||
peer feedback and evidence of performance provided, as relevant) and where relevant,
|
||||
details of periods of leave taken, and notes of relevant discussions as applicable. We
|
||||
endeavour to maintain accurate information.
|
||||
|
||||
## How do we collect Personal Data?
|
||||
Sometimes individuals directly provide us with most of their Personal Data we process. We collect and process Personal Data when someone registers online or applies for a position through any online site where the Beneficiary posts a new role and when they enter into a contractual relationship with us. Sometimes we will obtain Personal Data from alternative sources, including but not limited to: other affiliates and service providers (such as recruitment agents and background checking services to the extent permitted by applicable law) and government bodies where required by law (such as tax authorities). If the requested information is not provided, we may be unable to conduct certain business operations or comply with the applicable legislation. We may also receive Personal Data indirectly from sources such as Greenhouse, or others.
|
||||
|
||||
Exceptionally, we might process sensitive information and only for limited and strictly defined purposes, such as equal opportunities monitoring and diversity monitoring and initiatives may involve us using race or ethnicity data such as information contained in the passport or other citizenship document.
|
||||
|
||||
|
||||
## How will we use Personal Data?
|
||||
We will process Personal Data for the following purposes:
|
||||
|
||||
* For entering into and the performance of a contract with an individual and to manage our
|
||||
contractual relationship, including business communication, maintaining relevant records,
|
||||
payment of compensation, evaluations, and legally required procedures.
|
||||
* For the purposes of the legitimate interests pursued by us and in our role as the controller
|
||||
of Personal Data.
|
||||
* To comply with applicable laws and regulations.
|
||||
|
||||
Where relevant, we will only process Personal Data with an express prior consent of the Data
|
||||
Subjects.
|
||||
|
||||
We store most of Personal Data in our internal systems. We keep some data in a secure Google Drive folder. Between affiliates of the Beneficiary we only grant access to Personal Data on a need-to-know basis, necessary for the purposes for which such access is granted. In some cases, the Beneficiary uses third parties located in various countries to collect, use, analyse, and otherwise process Personal Data on its behalf. We tightly control access to the data to only members of the organisation that have a valid reason to access the information (generally - Legal, People Ops and Finance).
|
||||
|
||||
We maintain records of processing of Personal Data in accordance with the applicable laws,
|
||||
including obligations established by the GDPR.
|
||||
|
||||
## How do we share Personal Data?
|
||||
We may share Personal Data with our group entities and third-parties in accordance with the
|
||||
applicable laws. When we share Personal Data with a data processor, we will put the appropriate
|
||||
legal framework in place in order to cover data transfer and processing.
|
||||
|
||||
## Outsourcing
|
||||
We may outsource all or part of Personal Data processing to outsourcee. When executing an
|
||||
outsourcing agreement, the eligibility of the counterparty as an outsourcee is sufficiently
|
||||
investigated. Safety management measures, confidentiality, conditions for the outsourcee to
|
||||
outsource to another party, and other matters regarding the appropriate processing of the data are
|
||||
prescribed in the outsourcing agreement, and our outsourcees are appropriately supervised by
|
||||
implementing periodic monitoring, etc. of the outsourcing conditions.
|
||||
|
||||
## Corporate affiliates and corporate reorganisations
|
||||
We may share Personal Data with all our corporate affiliates. In the event of a merger, corporate
|
||||
reorganisation, acquisition, joint venture, assignment, transfer, sale or disposition of all or any
|
||||
portion of our business (including in connection with any bankruptcy or similar proceedings), we
|
||||
may transfer any and all Personal Data to the relevant third party.
|
||||
|
||||
## Legal compliance and security
|
||||
It may be necessary, by law, legal process, litigation, and/or requests from public and relevant
|
||||
governmental authorities that we disclose Personal Data. We may also disclose Personal Data if
|
||||
we determine that, for purposes of national security, law enforcement, or other issues of public
|
||||
importance, disclosure is necessary or appropriate.
|
||||
|
||||
We may also disclose Personal Data if we determine in good faith that disclosure is reasonably
|
||||
necessary to protect our rights and pursue available remedies, enforce our internal regulations,
|
||||
investigate fraud, or protect our operations or users.
|
||||
|
||||
## Transferring data
|
||||
Disclosures or sharing of Personal Data as described above may involve transferring Personal
|
||||
Data out of the EEA. For each of these transfers we make sure that we provide an adequate level
|
||||
of protection to the data transferred.
|
||||
|
||||
## Sharing
|
||||
We may share the minimum necessary amounts of Personal Data with the following third-party
|
||||
partners as required and applicable for statutory filings, benefits, and reporting, these include:
|
||||
|
||||
1. Greenhouse
|
||||
2. Juro Online Limited
|
||||
3. Google LLC
|
||||
4. Bamboo HR LLC
|
||||
|
||||
|
||||
There might be other third-party providers we will use in the future. If necessary, we will request
|
||||
the relevant Data Subjects’ permission before releasing Personal Data to any other third-party.
|
||||
|
||||
## How do we secure Personal Data?
|
||||
The Beneficiary takes the protection of Personal Data seriously and we intend to protect Personal Data and to maintain its accuracy. We process Personal Data in a manner that ensures such data undergoes appropriate security (including protection against unauthorised or unlawful processing and against accidental loss, destruction damage, unauthorised access, use and disclosure etc.) using appropriate technical or organisational measures to achieve this. We also require that our suppliers and providers protect such information from unauthorised access, use and disclosure.
|
||||
|
||||
## How long will we store Personal Data?
|
||||
We will not retain Personal Data longer than necessary to fulfil the purposes for which it is
|
||||
processed, including the security of our processing, complying with legal and regulatory
|
||||
obligations (e.g. audit, accounting and statutory retention terms), handling disputes, and for the
|
||||
establishment, exercise or defence of legal claims in the countries where we do business.
|
||||
|
||||
Therefore, we will hold Personal Data for a maximum of six years if an individual is a contractor
|
||||
and for a maximum of 18 months, if an individual is a candidate, to comply with applicable laws.
|
||||
|
||||
## What are applicable data protection rights?
|
||||
We would like to make sure that we inform Data Subjects of all data protection rights, such as:
|
||||
|
||||
The right to access - The right to obtain from us confirmation as to whether or not Personal Data
|
||||
concerning the individual is being processed and request access to and copies of such Personal
|
||||
Data.
|
||||
|
||||
The right to rectification - The right to obtain from us without undue delay the rectification of
|
||||
inaccurate Personal Data concerning the individual. The right to request us to complete Personal
|
||||
Data that is incomplete.
|
||||
|
||||
The right to erasure - The right to request that we erase Personal Data without undue delay,
|
||||
under certain conditions.
|
||||
|
||||
The right to restrict processing - The right to request that we restrict the processing of Personal
|
||||
Data, under certain conditions.
|
||||
|
||||
The right to object to processing - The right to object to processing of Personal Data by us, under
|
||||
certain conditions.
|
||||
|
||||
The right to data portability - The right to receive Personal Data we process, in a structured,
|
||||
commonly used and machine-readable format and the right to transmit those data to another
|
||||
controller, under certain conditions.
|
||||
|
||||
The right not to be subject to profiling and automated decision making - The right not to be
|
||||
subject to a decision based solely on automated processing, including profiling, which produces
|
||||
legal effects concerning individuals or similarly significantly affecting them.
|
||||
|
||||
The additional rights pursuant to local laws applicable to the processing of Personal Data.
|
||||
|
||||
For more information on how to exercise any of these rights, please contact us at email legal@free.technology.
|
||||
After receiving a request, we have one month to respond.
|
||||
|
||||
## How to lodge a complaint?
|
||||
In the event anyone considers our processing of their Personal Data not to be compliant with the applicable data protection laws, a complaint can be lodged directly with the Beneficiary by contacting us via legal@free.technology or with the competent data protection authority. The name and contact details of the Data Protection Authorities in the European Union can be found at:
|
||||
|
||||
http://ec.europa.eu/justice/data-protection/article-29/structure/data-protection-authorities/index_en.htm.
|
||||
|
||||
In case of breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise processed, we have the mechanisms and policies in place in order to identify it and assess the details of the breach promptly. Depending on the outcome of our assessment, we will make the necessary notifications to the supervisory authorities and communications to the affected Data Subjects.
|
||||
|
||||
|
||||
## Changes to Privacy Notice
|
||||
We may occasionally make changes to this Privacy Notice, as well as any other specific privacy
|
||||
statement. When making changes to this Privacy Notice we will add a new date at the top of this
|
||||
Privacy Notice. Any changes to this Privacy Notice will become effective upon posting of the
|
||||
revised Privacy Notice in the relevant section of our website. If we make changes which we
|
||||
believe are significant, we will inform the relevant Data Subjects and seek the Data Subjects’
|
||||
consent where applicable.
|
||||
|
||||
## How to contact us?
|
||||
In case of any questions related to this Privacy Notice, don't hesitate to contact us via email at legal@free.technology
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
# ☢️ In case of emergency
|
||||
Although we don't usually encounter emergencies (and that's why they're exceptional situations), when they happen, it's good if we all know how to react to them.
|
||||
|
||||
Here you'll find helpful information about what to do and expect from each other in case of emergency.
|
||||
|
||||
## Keep your contact information up to date
|
||||
|
||||
We'll use your emergency contact info in [Bamboo](https://statusim.bamboohr.com/) if we ever need an emergency contact for you. Please keep it up to date! Navigate to `My info` > `Emergency Contact` to maintain it.
|
||||
|
||||
It's also helpful to review your contact phone number and email address from time to time if we need to reach you directly.
|
||||
|
||||
## IFT emergency contacts
|
||||
|
||||
In all emergencies and only after you are safe and out of harm’s way and/or in a secure location contact people-ops@status.im or ping your People Partner directly via DM (or phone for urgent matters) for immediate attention. Your People Partner will use their reasonable efforts to coordinate with others (i.e., legal or security) on your behalf to the extent required.
|
||||
|
||||
## Reporting a potential legal claim or dispute
|
||||
|
||||
As a responsible organisation, we take all potential legal claims or disputes against 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.
|
||||
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
# 🎓 Recommended reading
|
||||
|
||||
We encourage using some time to learn about things related to your tasks and our collective mission. Make your peers aware of you being on/offline and that the team's progress doesn't get hindered. Feel free to discuss it openly and agree on timing with everyone involved.
|
||||
We 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 170 USD for each core contributor. You can use this budget towards things like books, conferences, or online courses. Speak with your team lead to request additional funding if needed.
|
||||
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.
|
||||
|
||||
> ℹ️ Team leads: if there's room in your budget, you can approve learning requests directly. Otherwise, create a [funding request](./finance/requesting-funding.md).
|
||||
For the purpose of purchasing learning & development items (learning platforms, courses, online conferences), you need to get approval from your Project Lead and/or PeopleOps partner.
|
||||
|
||||
If you need a reference, a regular contributor could spend their first 1-4 weeks spending 50% of their billed hours to learn and ~2-5 hours p/w after that on an ongoing basis. This is just an example, and we encourage you to figure out a learning cadence that best helps you succeed in contributing to Status.
|
||||
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.
|
||||
|
||||
We've added PDFs whenever possible, but you can also order them and [file a reimbursement](/src/finance/expense-reimbursements.md) for books or other applicable learning expenses. Read them at your own pace! We highly recommend you read the first group; the second one is nice to go through but less critical.
|
||||
We've added PDFs whenever possible, but you can also order them and [file a reimbursement](../finance/expense-reimbursements.md) for books or other applicable learning expenses. Read them at your own pace! We highly recommend you read the first group; the second one is nice to go through but less critical.
|
||||
|
||||
## Essential reading
|
||||
|
||||
@@ -33,6 +33,3 @@ We've added PDFs whenever possible, but you can also order them and [file a reim
|
||||
* [Pirate Organization: Lessons from the Fringes of Capitalism](https://www.goodreads.com/book/show/13586923-the-pirate-organization)
|
||||
|
||||
|
||||
*****
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.
|
||||
|
||||
@@ -1 +1,6 @@
|
||||
# Fundamentals
|
||||
|
||||
In this section you will find some information on the fundamentals of IFT such as our legal and security frameworks.
|
||||
|
||||
If you have any questions, please reach out to People Ops who can help navigate your questions or concerns.
|
||||
|
||||
|
||||
@@ -1,23 +1,22 @@
|
||||
# 🔐 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 organization from attackers.
|
||||
Here you'll find helpful links to resources to protect yourself and the organisation from attackers.
|
||||
|
||||
> In much the same way we've decentralized the organization and applications, we've done the same for security.
|
||||
> In much the same way we've decentralised the organisation and applications, we've done the same for security.
|
||||
>
|
||||
> It means the vast majority of the attack surface is you, the people that contribute. Furthermore, the controls and information a security specialist has in terms of making decisions and monitoring how things are run is constrained. It also means education takes a forward step in importance across the organization, and personal responsibility of quality security practices become paramount. It is up the people to understand potential threats, take preventative measures, and report any issues they come across to the security team to protect the organization as a whole.
|
||||
> It means the vast majority of the attack surface is you, the people that contribute. Furthermore, the controls and information a security specialist has in terms of making decisions and monitoring how things are run is constrained. It also means education takes a forward step in importance across the organisation, and personal responsibility of quality security practices become paramount. It is up to the people to understand potential threats, take preventative measures, and report any issues they come across to the security team to protect the organisation as a whole.
|
||||
> – @petty
|
||||
|
||||
## Ask for help
|
||||
|
||||
Above all else, never be afraid to ask for help, ask questions, or report security concerns. Until we have an official infrastructure for support tickets, drop by:
|
||||
|
||||
* #security for more broad, public questions.
|
||||
* #security-internal for anything that is more private.
|
||||
* Drop an email to `security@status.im` if none of the above channels fit.
|
||||
* [#security](https://discord.com/channels/973324189794697286/1078729684168233090) for more broad, public questions, or
|
||||
* Drop an email to `security@status.im`.
|
||||
|
||||
All contributors with an onboarding process will have a security touchpoing with the security team during the first month of their onboarding.
|
||||
All contributors with an onboarding process will have a security touchpoint with the security team during the first month of their onboarding.
|
||||
|
||||
## Best practices checklists
|
||||
|
||||
@@ -29,25 +28,31 @@ Phishing attacks are the most common: discord bots, telegram messages, and email
|
||||
|
||||
## Hardware
|
||||
|
||||
Check out this [list](https://notes.status.im/zkr20eWFTwGD92xixGX2CA) of essential hardware. Core contributors can expense hardware security keys (yubikeys) and should be used for Github, Gsuite, and Bitwarden.
|
||||
Here's a list of recommended hardware for protecting accounts, crypto assets, and data:
|
||||
|
||||
* Security Keys (e.g., YubiKey, Google Titan, OnlyKey) – Provides phishing-resistant 2FA login, useful against remote attacks and credential leaks.
|
||||
* Hardware Crypto Wallets (e.g., Ledger, Trezor, Coldcard) – Stores private keys offline.
|
||||
* Encrypted External Storage (e.g., IronKey) – Secures private key backups and sensitive data with hardware encryption for added protection.
|
||||
* Privacy-Focused Phone (e.g., GrapheneOS Pixel) – Enhances privacy and security with encrypted communication and minimal data tracking.
|
||||
* Faraday Bag (e.g., Mission Darkness) – Shields devices from remote hacking and tracking by blocking all wireless signals.
|
||||
|
||||
Core contributors can expense hardware security keys (yubikeys) and should be used for Github, Gsuite, and Bitwarden.
|
||||
|
||||
Here's Corey's Status Learn-Up session about [hardware wallets and best practices](https://www.youtube.com/watch?v=9nzqntuFR44&ab_channel=HashingItOut).
|
||||
|
||||
## Password manager
|
||||
|
||||
Our password manager is [Bitwarden](https://bitwarden.com/). All organizational passwords should be kept and shared here. So if you plan to store a Status related password, or get access to platforms that require username/passwords/2fa, then it should all be shared using Bitwarden.
|
||||
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 organization, you get the premium features and sign up with any email you like. That way, if you ever leave Status, you can take your password manager secrets with you, and you only lose access to Status related items.
|
||||
You can request an invite in #people-ops. By signing up with the organisation, you get the premium features and sign up with any email you like. That way, if you ever leave the IFT, you can take your password manager secrets with you, and you only lose access to IFT related items.
|
||||
|
||||
## Security team
|
||||
|
||||
Learn more about Security @ Status at:
|
||||
Learn more about Security @ IFT at:
|
||||
|
||||
* [Status Security](https://status.im/security/)
|
||||
* [Notion Security homepage](https://www.notion.so/bee2c4d28567424fae21c3c97e733e46?v=fdc44ecba717474fae7ae65f3097b315)
|
||||
* [status-im/status-security](https://github.com/status-im/status-security)
|
||||
* [status-im/security-internal](https://github.com/status-im/security-internal)
|
||||
|
||||
|
||||
*****
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
# Hirign
|
||||
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 175 KiB |
|
After Width: | Height: | Size: 461 KiB |
|
After Width: | Height: | Size: 188 KiB |
|
After Width: | Height: | Size: 396 KiB |
|
After Width: | Height: | Size: 187 KiB |
|
After Width: | Height: | Size: 54 KiB |
|
After Width: | Height: | Size: 65 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 33 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 40 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 140 KiB |
|
After Width: | Height: | Size: 119 KiB |
|
After Width: | Height: | Size: 112 KiB |
|
After Width: | Height: | Size: 114 KiB |
|
After Width: | Height: | Size: 101 KiB |
|
After Width: | Height: | Size: 98 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 82 KiB |
|
After Width: | Height: | Size: 78 KiB |
|
After Width: | Height: | Size: 129 KiB |
|
After Width: | Height: | Size: 135 KiB |
|
After Width: | Height: | Size: 120 KiB |
|
After Width: | Height: | Size: 138 KiB |
|
After Width: | Height: | Size: 41 KiB |
|
After Width: | Height: | Size: 66 KiB |
|
After Width: | Height: | Size: 183 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 124 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 46 KiB |
|
After Width: | Height: | Size: 135 KiB |
|
After Width: | Height: | Size: 566 KiB |
|
After Width: | Height: | Size: 569 KiB |
|
After Width: | Height: | Size: 685 KiB |
|
After Width: | Height: | Size: 308 KiB |
@@ -1,11 +0,0 @@
|
||||
# Introduction
|
||||
|
||||
The Status Network is an open set of projects building peer-to-peer technologies for people to transact securely and communicate freely. We build decentralized technologies ranging from protocol-level infrastructure to consumer applications — forming an open-source peer-to-peer technology stack.
|
||||
|
||||
The [Status](https://status.im/get/) app is a secure communication tool that upholds human rights. Designed to enable the free flow of information, protect the right to private, secure conversations, and promote the sovereignty of individuals. [Discover more projects →](https://statusnetwork.com/)
|
||||
|
||||
### Contributing
|
||||
|
||||
Status is an open community, you don’t need to ask permission to join or become a member. If you see something you think should be improved, you can [make a PR](https://github.com/status-im/), join our [Discord](https://discord.gg/2HyyjgFHVK) or create a [a proposal](https://discuss.status.im/) and make it happen.
|
||||
|
||||
You can also contribute to specific Status Network projects such as [Waku Connect](https://wakuconnect.dev/) or [Nimbus](https://nimbus.team/). As an open-source project, we are location-agnostic and operate fully remote. You can find what profiles each project is looking for [on this page](https://jobs.status.im/).
|
||||
@@ -0,0 +1,11 @@
|
||||

|
||||
|
||||
# 🚀 Introduction
|
||||
|
||||
### Institute of Free Technology
|
||||
|
||||
#### Fostering innovation, defending digital liberties
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
@@ -0,0 +1,23 @@
|
||||
# 💻 Laptop and device logistics
|
||||
|
||||
First make sure that all devices (laptops and mobile phones) details are reflected in the Asset tab of BambooHR for record-keeping purposes, and that factory settings have been restored. To erase your laptop hard drive follow [these](https://support.apple.com/en-gb/HT201065) instructions if you have Mac OS.
|
||||
|
||||
Once you have made a decision whether you are buying or returning your device, speak to your People Partner who can help facilitate the right paperwork for your offboarding.
|
||||
|
||||
## Buying back your devices
|
||||
|
||||
The buyback value should be included on your last invoice to IFT, and can be deduced from your last service fee. We're using a 36-month useful life formula for laptops and mobiles to calculate the buy back value:
|
||||
|
||||
Purchase value - purchase value * contract duration / 36 months.
|
||||
|
||||
| ❗Example |
|
||||
|:----------------------------------------|
|
||||
| Laptop cost EUR 2,000 23 months ago|
|
||||
| The buyback value is EUR 722 |
|
||||
| 2000 - (2000*23/36)|
|
||||
|
||||
|
||||
## Returning your devices back to IFT
|
||||
|
||||
Your devices could still be used by someone else at IFT so please check with your People Partner on how best to return your device prior to your last day.
|
||||
|
||||
@@ -0,0 +1,93 @@
|
||||
# 💠 Offboarding
|
||||
|
||||
We’re sorry that you’re leaving the IFT and wish you the best of luck in your next endeavours ☘️ - thanks for everything you brought to IFT during the time we had together! 🙌
|
||||
|
||||
Your People Partner will help facilitate this process with various other stakeholders such as your project lead, Legal and Finance.
|
||||
|
||||
There's a lot to do before you leave so please follow the steps assigned to you in BambooHR and outlined below:
|
||||
|
||||
## ⏬ Logistics
|
||||
|
||||
* ### Final working day
|
||||
|
||||
Your People Partner will agree on a final date with you which you’ll be providing your services. Generally, this will align with the notice period mentioned in your (services) agreement. If you have any concerns about being able to wrap up your work in progress during the notice period available, please let your People Partner know, who’ll be happy to help you.
|
||||
|
||||
* ### Bamboohr offboarding checklist
|
||||
|
||||
The offboarding process will be initiated in BambooHR. Please go through the checklist and complete all tasks assigned to you.
|
||||
|
||||
* ### Letter of Termination
|
||||
|
||||
Your People Partner will share a confirmation of termination with you, confirming your last day of service with IFT.
|
||||
|
||||
* ### Offboarding Agreement
|
||||
|
||||
This document will be sent to you via Juro once your last day and asset buyback / return is confirmed. Please kindly sign this document and keep a copy for your records.
|
||||
|
||||
* ### Returning or buying back 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 buybacks and expenses.
|
||||
|
||||
* ### Verify your payment details in BambooHR are accurate
|
||||
|
||||
This will be how your final invoice and expenses are settled so make sure it's correct!
|
||||
|
||||
* ### Handover & transferring responsibilities
|
||||
|
||||
Share any ongoing work/files/deliverables with your project. You should transfer ownership of any critical documents so that these don’t get deleted when your accounts are closed. Transfer your routine tasks and responsibilities within your project and draft a handover document to share with your project lead.
|
||||
|
||||
* ### Announcing your departure
|
||||
|
||||
We’d like to be transparent with all core contributors when someone leaves the project. Please post a goodbye message, or let People Ops know if you’d prefer that they post a general departure message on your behalf (this won’t share any personal details, but will confirm that you are not going to be around, along with your expected last day). You may also want to ping fellow core contributors within other projects directly to let them know about your departure.
|
||||
|
||||
* ### Forthcoming IFT travel
|
||||
|
||||
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 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
|
||||
|
||||
Access will be revoked by 5pm UTC on your final day. If you need longer to wrap up, please let your People Partner know. Tools including BambooHR, Google, Notion, Github, Bitwarden etc.
|
||||
|
||||
* ### Passwords
|
||||
|
||||
Please clear your password vault of any passwords relating to tools/software licences belonging to IFT.
|
||||
|
||||
* ### Tools
|
||||
|
||||
If you have access to any tools/software specific to your role, please liaise with your project to close out your access.
|
||||
|
||||
* ### Contact details
|
||||
|
||||
Please check your BambooHR profile to verify that we have the correct email and postal address for you (in case we need to contact you in future about something related to your time with us).
|
||||
|
||||
* ### Letter of reference
|
||||
|
||||
We’ll be happy to provide a specific (i.e addresses to a specific person or organisation) letter of reference confirming your contributions to IFT. Should you ever need a reference letter, please email people-ops@status.im at any time, and we’ll get a letter to you within 5 - 10 working days.
|
||||
|
||||
## "Offboarding" chats
|
||||
|
||||
We're not a traditional organisation, but we try to hold 'offboarding' chats with every departing core contributor. This chat is a chance for you to reflect on your time with us, and share your feedback on your experience. The feedback we collect from these interviews will be used to improve the way we work with contributors moving forward.
|
||||
|
||||
We’ll share your feedback with relevant project members we think may benefit from hearing your reflections. If you’d prefer the conversation to be 100% private, that’s totally ok - just let us know what you’re comfortable with being shared further.
|
||||
|
||||
Feel free to prepare notes in advance, or send us your feedback async if you’d prefer. We're happy to converse via voice/video/text.
|
||||
|
||||
## Coming back?
|
||||
|
||||
We’re open to working with former core contributors again, and we’d consider each situation on an individual basis.
|
||||
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 the #finance channel.
|
||||
|
||||
@@ -1,33 +1,34 @@
|
||||
# 🗿 Our Principles
|
||||
These principles act as tools. Tools for thinking, for communication, and for decentralized decision making. They keep us honest about where we are failing short of our vision.
|
||||
|
||||
These principles act as tools. Tools for thinking, for communication, and for decentralised decision-making. They keep us honest about where we are failing short of our vision.
|
||||
|
||||
|
||||
### I. Liberty
|
||||
We believe in the sovereignty of individuals. As a platform that stands for the cause of personal liberty, we aim to maximize social, political, and economic freedoms. This includes being coercion-resistant.
|
||||
We believe in the sovereignty of individuals. As a platform that stands for the cause of personal liberty, we aim to maximise social, political, and economic freedoms. This includes being coercion-resistant.
|
||||
|
||||
### II. Censorship Resistance
|
||||
We enable free flow of information. No content is under surveillance. We abide by the cryptoeconomic design principle of censorship resistance. Even stronger, Status is an agnostic platform for information.
|
||||
We enable free flow of information. No content is under surveillance. We abide by the crypto economic design principle of censorship resistance. Even stronger, the Status app is an agnostic platform for information.
|
||||
|
||||
### III. Security
|
||||
We don't compromise on security when building features. We use state-of-the-art technologies, and research new security methods and technologies to make strong security guarantees.
|
||||
|
||||
### IV. Privacy
|
||||
Privacy is the power to selectively reveal oneself to the world. For us, it's essential to protect privacy in both communications and transactions, as well as being a pseudo-anonymous platform. Additionally, we strive to provide the right of total anonymity.
|
||||
Privacy is the power to selectively reveal oneself to the world. For us, it's essential to protect privacy in both communications and transactions, as well as being pseudo-anonymous through the Status app . Additionally, we strive to provide the right of total anonymity.
|
||||
|
||||
### V. Transparency
|
||||
We strive for complete openness and symmetry of information within the organization, and have no border between our core contributors and our community. We are frank about our shortcomings, especially when making short-term tradeoffs in service of our long-term goals.
|
||||
We strive for complete openness and symmetry of information within the organisation, and have no border between our core contributors and our community. We are frank about our shortcomings, especially when making short-term tradeoffs in service of our long-term goals.
|
||||
|
||||
### VI. Openness
|
||||
The software we create is a public good. It is made available via a free and open source license, for anyone to share, modify and benefit from. We believe in permission-less participation.
|
||||
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. Decentralization
|
||||
We minimize centralization across both the software and the organization itself. In other words, we maximize the number of physical computers composing the network, and maximize the number of individuals who have control over the system(s) we are building.
|
||||
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
|
||||
We believe in fair and widespread access to our software, with an emphasis on ease-of-use. This also extends to social inclusivity, permissionless participation, interoperability, and investing in educational efforts.
|
||||
|
||||
### IX. Continuance
|
||||
We create software incentivized to continue to exist and improve, without the stewardship of a single entity or any of the current team members.
|
||||
We create software incentivized to continue to exist and improve, without the stewardship of a single entity or any of the current project members.
|
||||
|
||||
### X. Resourcefulness
|
||||
We are relentlessly resourceful. As we grow and have ready access to capital, it is our obligation to token holders to fight bureaucracy and inefficiencies within the organization. This means solving problems in the most effective way possible at lower economic costs (in terms of capital, time and resources).
|
||||
We are relentlessly resourceful. As we grow and have ready access to capital, it is our obligation to token holders to fight bureaucracy and inefficiencies within the organisation. This means solving problems in the most effective way possible at lower economic costs (in terms of capital, time and resources).
|
||||
|
||||
@@ -1,67 +0,0 @@
|
||||
# 🖥 Computers and devices
|
||||
|
||||
Having the proper setup is fundamental to ensuring you can work comfortably. Since we're all working remotely, you can choose what suits you best within a budget. If you're a core contributor at Status, we'll provide you with the tools required to succeed in your role during your onboarding.
|
||||
|
||||
Here you'll find helpful information to set yourself up with the computers and devices you need.
|
||||
|
||||
## ☑️ Pre-approved equipment
|
||||
|
||||
All core contributors have a list of pre-approved equipment budgets previously considered within their team budgets. That means you do not need prior approval from Finance to expense up to the pre-approved amount. Let your team lead know about your equipment purchasing plans. Follow the instructions below to get your computer and other devices.
|
||||
|
||||
The standard setup for everyone includes a laptop, headphones, a Keycard, a Yubikey, and a Ledger.
|
||||
|
||||
We defined the amounts to cover a range of options, so you will stay below that budget in most cases. When that happens, note that pre-approved amounts aren't "balances," and you can't spend the difference for other stuff.
|
||||
|
||||
* Laptop: up to 2000 USD
|
||||
* Mic and headphones: up to 100 USD
|
||||
* Keycard: ping the #keycard channel to get a code
|
||||
* Yubikey: you can reimburse one
|
||||
* Ledger: you can reimburse one
|
||||
|
||||
For additional funds per item or other equipment, you need to obtain a previous approval from your team lead and add the approval details to your reimbursement. If your equipment needs fall outside your team's budget, you can [request funds](/src/finance/request-funds.md) for approval. Some examples of other equipment:
|
||||
|
||||
* Testing phones for engineering roles
|
||||
* A printer for an ops role
|
||||
* A digital sketchpad for a design role
|
||||
|
||||
> ℹ️ If you're unsure whether or not this applies to you, ping People Ops. We occasionally have loan assets available to all contributors.
|
||||
|
||||
## 🎁 How to get your computers and devices
|
||||
|
||||
1. Let your team lead know prior to purchasing the devices.
|
||||
2. Choose official or trusted vendors to buy your equipment.
|
||||
3. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
4. Once registered, request a refund by adding the expense to Expensify and your next invoice.
|
||||
5. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
|
||||
## ℹ️ FAQ
|
||||
|
||||
* **What if I'm a German or Swiss employee?**
|
||||
|
||||
If you're a German or Swiss employee, please be sure to buy your devices via an invoice addressed to the [German or Swiss entity](./finance/third-party-invoices-format.md). The invoice should be submitted to billing@status.im.
|
||||
|
||||
* **What if I don't have enough funds to buy the device before reimbursement?**
|
||||
|
||||
If cash flow is an issue and you'd prefer not to outlay the cash upfront for your new device, please ping People Ops. We'll help you with the purchase.
|
||||
|
||||
* **What if my devices become outdated?**
|
||||
|
||||
After 36 months usage or if your device needs an upgrade, ping People Ops.
|
||||
|
||||
* **What happens if I accidentally damage a device?**
|
||||
|
||||
You should treat the devices as if they were yours. If the damage was due to factors beyond your control, please obtain a quote for a repair and let People Ops know. If the cost is reasonable (i.e., less than ~75% of the trade-in value of the asset), we would ask you to go ahead and get the device repaired. Then, submit the repair expense cost for reimbursement.
|
||||
|
||||
* **What if I leave Status?**
|
||||
|
||||
Please check out [this offboarding guide](/src/settling-in/offboarding.md) for your options on recycling or buying back your laptop.
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
* [How to get reimbursed](/src/finance/expense-reimbursements.md)
|
||||
|
||||
|
||||
*****
|
||||
|
||||
✍️ **Contribute to this page!** Create a PR and assign someone from the People Ops team to review it.
|
||||