kodadot / kodadot/subwork

Define success of SubWork

Open
#146 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
9
Forks
5
PR merge metrics
No merged PRs in 30d

Description

This was something I have been thinking about a lot in recent days. So let's try to define some goals.

Briefly, numbers would be to reach meaningful metrics which predict the success of this experiment.
To make it easy to explore, I'll make it into the table, comparing current, optimistic, pessimistic, and realistic would be somewhere between.
Metrics are the goal for EOY 2023.


Service
Current
Pesimistic
Optimistic

Google Maps
52
70
110

LinkedIn
108
150
300

Telegram
169
300
400

Meetup group
110
150
200

Twitter
287
350
500

A significant impact on these numbers could move when hackathons, hacker houses, and campaigns happen, partnership and acquisition of strategic channels, remote/local

Strategic moves
---
- #141
- #133
- #13
- #111
- #127
- #3

Contributor guide

No contributing guide indexed for this repository

Research direction

No implementation files, tests, or entry points are named. Review the metrics table and the referenced strategic issues (#141, #133, #13, #111, #127, and #3); the work is done when the success metrics, targets, timing, and relevant strategic dependencies are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.