After delivering the milesone 1 successfully, we had discussions with fellowship members, got feedbacks, made some fixes and improvements. We are proposing to implement milestone 2 to support collectives(fellowship, ambassadors) on polkadot.
From a techinical view, most ambassador businesses is similar with that of fellowship. Both of them includes members mangement, salary management, decision process via referenda. In this proposal we will implement most features for fellowship on referendum #631.
We have to refactor and reorganize most implemented features for fellowship to make them work with multiple instances of collective.
Collective members sumit evidences with expections to retain at their ranks or to be promoted to higher ranks. Failure to handle them may lead to members bumped to lower ranks accidently, or not to be promoted in time.
Members themselves may forget or fail to check their demotion/promotion status which will lead them fail to submit evidences.
We propose to implement some components warn:
We will be able to see a fellowship/ambassador member's basic info and life cycle on his/her profile page.
With this feature we can get to know:
Currently sub treasury is implemented for either fellowship and ambassador. These treasuries will be controlled by fellowship/ambassador members through their referenda mechanism. In this proposal we will implement:
| Work | Estimated hours | memo |
|---|---|---|
| Ambassador business support | 360 | 3 FTE * 15days |
| Profile info enhancement | 480 | 3 FTE * 20 days |
| Statistics | 240 | 3 FTE * 10 days |
| Sub treasury | 240 | 3 FTE * 10 days |
| Collective referenda enhancement | 600 | 3 FTE * 25 days |
| Testing | 40 | 1 FTE * 5 days |
| Total | 1960 |
Summary:
Features:
Budget:
After delivering the milesone 1 successfully, we had discussions with fellowship members, got feedbacks, made some fixes and improvements. We are proposing to implement milestone 2 to support collectives(fellowship, ambassadors) on polkadot.
From a techinical view, most ambassador businesses is similar with that of fellowship. Both of them includes members mangement, salary management, decision process via referenda. In this proposal we will implement most features for fellowship on referendum #631.
We have to refactor and reorganize most implemented features for fellowship to make them work with multiple instances of collective.
Collective members sumit evidences with expections to retain at their ranks or to be promoted to higher ranks. Failure to handle them may lead to members bumped to lower ranks accidently, or not to be promoted in time.
Members themselves may forget or fail to check their demotion/promotion status which will lead them fail to submit evidences.
We propose to implement some components warn:
We will be able to see a fellowship/ambassador member's basic info and life cycle on his/her profile page.
With this feature we can get to know:
Currently sub treasury is implemented for either fellowship and ambassador. These treasuries will be controlled by fellowship/ambassador members through their referenda mechanism. In this proposal we will implement:
| Work | Estimated hours | memo |
|---|---|---|
| Ambassador business support | 360 | 3 FTE * 15days |
| Profile info enhancement | 480 | 3 FTE * 20 days |
| Statistics | 240 | 3 FTE * 10 days |
| Sub treasury | 240 | 3 FTE * 10 days |
| Collective referenda enhancement | 600 | 3 FTE * 25 days |
| Testing | 40 | 1 FTE * 5 days |
| Total | 1960 |
Threshold
Threshold