README.md 3.3 KB
Acropolis OKR Archive
Objective: Launch Acropolis Network
- Active from: 09.05.19
- KR Measurement Deadline: 7-9 days after Acropolis launch (first weekday)
- Tracked: Every Monday
- Tracking Manager: Martin
- Key Results:
Get 75 posts on forum (limits, not Jsg) (ewd)- Bedeho: 2/3
- Alex: 1/3
Forum (runtime), storage (runtime and P2P) fully specd (n)- Bedeho (as manager): 1/2
- Bedeho (as writer): 1/6
- Jens: 2/6
- Mokhtar from 10.06.19
Have 4x replication for all 2 tranches on storage node (ewd)- Jens: 2/3
- Mokhtar from 10.06.19
- Mokhtar: 1/3
- Jens: 2/3
95% uptime Storage Providers (ewd)- Jens: 1/4
- 0 from 10.06.19
- Mokhtar: 1/4
- 1/2 from 10.06.19
- Martin: 1/4
- Alex: 1/4
- Jens: 1/4
No PRs merged to master (excluding bugfixes and "pioneer") after "Sub-system Test" (conf)- Martin: 1/2
- Jens: 1/8
- 0 from 10.06.19
- Mokhtar: 1/8
- 1/6 from 10.06.19
- Bedeho: 1/8
- 1/6 from 10.06.19
- Alex: 1/8
- 1/6 from 10.06.19
- Final Score
| Date | KR #1 | KR #2 | KR #3 | KR #4 | KR #5 | Total |
|---|---|---|---|---|---|---|
| 03.07.19 | 0.55 | 0.67 | 0.5 | 0.75 | 0.5 | 0.594 |
- Notes
Although we only got 7 posts that counts, the forum was shipped successfully. We decided to grade it as two separate results.The forum and storage runtime was fully spec'd, whereas the P2P aspect of the storage was considered too incomplete to publish.We achieved more than 4x replication, but tranches had to be abandoned.We split this up in two parts, where the end user uptime, and provider uptime was weighted at 0.5 each.The storage node had non-bug fixes (improvements) merged to master after "Full test", whereas the forum side had none.Tracking:
| Date | KR #1 | KR #2 | KR #3 | KR #4 | KR #5 | Comments |
|---|---|---|---|---|---|---|
| 13.05.19 | (0.55,0.65) 0.58 | (0.4,1,0.1) 0.4 | (0,0) 0 | (0,0,0,0) 0 | (0.5,1,0.5,0.95,0.95) 0.68 | KR3 tracking N/A as SoW must be finalized |
| 20.05.19 | (0.6,0.8) 0.7 | (0.4,1,0.1) 0.4 | (0,0.1) 0.03 | (0,0,0,0) 0 | (0.5,1,0.25,0.95,0.95) 0.64 | n denotes Jens' tracking (absent) |
| 27.05.19 | (0.7,0.85) 0.78 | (0.4,1,0.9) 0.67 | (0,0.1) 0.03 | (0,0,0,0) 0 | (0.7,1,0.6,1,0.95) 0.79 | - |
| 03.06.19 | (0.9,0.85) 0.88 | (0.4,1,0.95) 0.67 | (0.45,0.2) 0.37 | (0,0.2,0,0) 0.05 | (0.6,1,0.8,1,0.95) 0.77 | - |
| 10.06.19 | (1.0,0.9) 0.95 | (0.4,1,0.95) 0.67 | (0.4) 0.4 | (0.85,0,0) 0.43 | * |
* Due to changes in circumstances, we chose abstain from tracking KR5 |
| 17.06.19 | (0.99,0.97) 0.98 | (0.8,1.0,1.0) 0.9 | (0.49) 0.49 | (0.99,0.5,1.0) 0.85 | (0.65,0.95,0.3,0.7) 0.65 | - |
| 24.06.19 | (1.0,1.0) 1.0 | (0.67,1.0,1.0) 0.83 | (0.5) 0.5 | (0.9,0.8,1.0) 0.9 | (0,0.8,1.0,1.0) 0.47 | |
| 03.07.19 | (1+7/75)x0.5 0.55 | (2/3) 0.67 | (1+0)x0.5 0.5 | (1+0.5)x0.5 0.75 | 0.5 | Actual score |
- Notes
- During the first tracking, it was decided to track KR5 by how confident (conf) each assigned individual is that the KR will be achieved.