DRAFT: [PROPOSAL-002] Guru Network Token Distribution Between Core Contributors #3
Conversation
| |-------------------|--------| | ||
| | Tasks Completed | 0.3 | | ||
| | Time Efficiency | 0.2 | | ||
| | Task Complexity | 0.2 | |
There was a problem hiding this comment.
Main point: Our tasks often sound like, "It's all done, just a few small changes, and then let's cache everything." But they often turn into a rabbit hole instead
|
|
||
| Each member's contribution will be evaluated based on the following metrics: | ||
|
|
||
| - **Tasks Completed:** Number of tasks completed during the period. |
There was a problem hiding this comment.
Perhaps we should measure not just tasks, but also the features and system components designed, ensuring they correspond with our main mission (guru_framework and guru_network)?
|
|
||
| | Metric | Weight | | ||
| |-------------------|--------| | ||
| | Tasks Completed | 0.3 | |
There was a problem hiding this comment.
We also have a significant legacy to support, which generates tasks and impacts new releases as it becomes components of apps built over the framework. Therefore, should we prioritize the legacy or the framework?
|
Maybe we should practice live demo of system parts designed. Present benefits. Metrcs, uptime of apps, etc. And then evaluate? |
DRAFT
It can't be the final version. Please, leave your comments and suggestions.
This proposal outlines an algorithm for distributing tokens among DAO members based on their contributions and the importance of their roles. The goal is to ensure a fair and transparent method for rewarding members based on their efforts and impact.
Special thanks <3: GPT-4