| KR-1.1 |
50% Increase in user engagement with Joystream ecosystem tools. |
Implement statistic collection tools in order to measure key results. Developing/purchasing a Blockchain Explorer. Validator payout bot developed. Conduct a Hackathon to attract developers in building ecosystem tools. |
🔴 |
🟡 |
Council: Let’s exclude Hakathon activity from KR-1.1 OKR. Looks like we are not gonna do it. |
| BWG: What’s status on the Blockchain Explorer development from KR-1.1 OKR? |
|
|
|
|
|
| Council: Clarify what does it mean - “50% Increase in user engagement with Joystream ecosystem tools. ” May be we can simply state that Blockchain Explorer is 50% and payout bot is the rest 50% of criteria achievement? |
|
|
|
|
|
| KR-1.2 |
50% Reduction on reported security and technical issues in discord. |
|
🟡 |
🟡 |
BWG: Does BWG compile any data on reported security and technical issues? Is it possible to discern which of these issues were submitted via Discord? As of KR-1.2, BWG should start collecting the stats if they haven’t done it yet. |
| KR-1.3 |
Average response time on pioneer is reduced by 50% |
Developing Email notifications to track all activity on Pioneer.Pioneer works on mobile. Develop a mobile application. |
🟡 |
🟡 |
BWG: Is anyone working on the email notifications for the Pioneer? What is the status of the mobile Pioneer version? Are we on track to complete this work in the Q2 OKR? |
| Council: (1) ****Let's remove the Pioneer mobile app development from the Q2 OKR initiatives, as it is not feasible to implement the feature within the deadline. (2) Let’s adjust KR-1.3 and consider only response time for pre-proposal discussions. Should we count only 1st response in the topic - TBD |
|
|
|
|
|
| FWG: Can we track the average response time for pre-proposals on Pioneer and incorporate this into the FWG report? The full stats should be collected as a separate page in the FWG space on Notion |
|
|
|
|
|
| KR-1.4 |
60% reduction in reported bugs and errors in Pioneer. |
Implementing necessary Pioneer upgrades. |
🟡 |
🟡 |
BWG: Does BWG track any statistics regarding the number of reported issues that are specific to Pioneers? If no, it should start doing that for KR-1.4 |
| KR-2.1 |
At least 1 gateway provider was hired to the App working group |
Hire APP working group lead.Research and identify potential video applications that align with Joystream's vision and mission.Create Atlas SDK.Create new necessary documentation for developers to build on top of the platform.Create video tutorials on how to start Gateway. |
🟢 |
🟢 |
|
| KR-3.1 |
100% growth in user count on Joystream discord server. |
Execute a range of marketing campaigns in order to promote community growth. |
🟢 |
🟢 |
Stats are here ‣ |
| KR-3.2 |
100% growth in followers on JSG and Joystream DAO Twitter accounts |
Conduct Twitter spaces AMA sessions. |
🟢 |
🟢 |
Stats are here ‣ Specifically, stats on https://twitter.com/JoystreamDAO and https://twitter.com/joystream_mwg |
| KR-3.3 |
100% growth on Joystream telegram chat users |
Promote community activity on Telegram, and assign HR working group workers with moderation rights. |
🟢 |
🟢 |
Stats are here ‣ Specifically, stats on https://t.me/JoyStreamOfficial |
| KR-3.4 |
JOY listed on 1 tier2 CEX |
Establish communication with reputable CEX, discuss terms, and finalize the listing agreement.Boost Joystream social metrics and community engagement in order to meet CEX requirements. |
🟢 |
🟢 |
|
| KR-3.5 |
On-chain memberships reach 7000 |
Provide necessary help to the community in making on-chain memberships.FWG reorganizes threads and category structure for easier engagement and better communication according to needs.Implement a bounty program in Pioneer in order to attract new community members to contribute and earn JOY. |
🟢 |
🟢 |
|
| KR-3.6 |
Average 10% weekly growth in channels count that have more than 1 video uploaded. |
Kickstart creator adoption by incentivizing content creators for quality content. |
🟡 |
🟡 |
CWG: Let's introduce an indicator for the “channels count that have more than 1 video uploaded” counter. We should record this data in a separate database, updating the statistics every two weeks and including a link to this report in the CWG report. |
| KR-3.7 |
30% growth of Joystream.org backlinks. |
Create high-quality content and distribute it across multiple websites, incorporating links to joystream.org. |
🟡 |
🟡 |
Council: clarify what doest that mean? |
| KR-4.1 |
Achieve an average video loading time of 1.2 seconds or less, as measured by tests conducted from major populated regions, by the end of Q2. |
Collect analytics, and perform the necessary testing to identify errors.Perform necessary infrastructure upgrades to reduce playback speed.Increase the global diversity of DWG servers. |
🔴 |
🔴 |
DWG: I don't think that the proposed time of 1.2 is achievable for KR 4.1. Let’s come up with method on how we can perform the suggested test and what can be criteria of “success” |
| Council: Consider adjusting KR 4.1. and “1.2s” according DWG feedback. |
|
|
|
|
|
| KR-4.2 |
Each Council member and lead participate in no less than 50% of new weekly open mandatory kickoff meetings |
Introduce an incentives system to encourage Council to participate.Developing a lead scoring system.Reminding CMs and leads about the meetings/introducing email notifications. |
🟡 |
🟡 |
HRWG (or Council Secretary): Collect data on weekly meeting (”Each Council member and lead participate in no less than 50% of new weekly open mandatory kickoff meetings”) for KR-4.2. You should record this data in a separate database, updating the statistics after every meeting |
| Council: adjust the OKR so deputy can present at the meetings instead of Leads with no slashing |
|
|
|
|
|
| KR-4.3 |
Validators count not less than 45 by the end of Q2. |
|
🟢 |
🟢 |
|
| KR-4.4 |
Average Block time is less than 6.3s. |
|
🟢 |
🟡 |
|
| KR-4.5 |
All non yt-synch channels are reviewed for respecting content policy by curators in no more than 48 hours after the first video is published. |
Improve existing tools for curation, and introduce notifications. |
🟢 |
🟡 |
|
| KR-4.6 |
All councils have a lower implied total annual issuance rate (including validation) than 20% |
Analyze the spending in order to identify if the platform infrastructure and workforce are cost-effective |
🟢 |
🟢 |
|