User Tools
voting_system_overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| voting_system_overview [12/03/2021 00:56] – gfactor | voting_system_overview [12/03/2021 00:58] – gfactor | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| Voting will also be used for the community to help approve new developers as an admin of the DevTeam. What this means is that we have two types of DevTeam members: 1) anyone can join the team and help develop the codebase who DO NOT have the ability to vote on the 60% approval to push updates to the chain, and 2) DevTeam admins who DO have the ability to vote on the 60% approval to push updates to the chain. The DevTeam would notify the community of the vetted developers being entered into a community vote, then the community will vote to approve the DevTeam admins to push the update with their 60% approval. This update will then assign the admin permission to the vetted dev(s) and it's official. It is extremely important to have this layer of security with these two types of DevTeam members as the DevTeam admins will be the only ones who can vote for a 60% approval to push updates. This creates a way for the community to have a say in who becomes a DevTeam admin, and the DevTeam admins keep the rest of the DevTeam in check as DevTeam admins are the only devs who can push the 60% approval updates to the chain. | Voting will also be used for the community to help approve new developers as an admin of the DevTeam. What this means is that we have two types of DevTeam members: 1) anyone can join the team and help develop the codebase who DO NOT have the ability to vote on the 60% approval to push updates to the chain, and 2) DevTeam admins who DO have the ability to vote on the 60% approval to push updates to the chain. The DevTeam would notify the community of the vetted developers being entered into a community vote, then the community will vote to approve the DevTeam admins to push the update with their 60% approval. This update will then assign the admin permission to the vetted dev(s) and it's official. It is extremely important to have this layer of security with these two types of DevTeam members as the DevTeam admins will be the only ones who can vote for a 60% approval to push updates. This creates a way for the community to have a say in who becomes a DevTeam admin, and the DevTeam admins keep the rest of the DevTeam in check as DevTeam admins are the only devs who can push the 60% approval updates to the chain. | ||
| - | The community will NOT be voting to directly approve code updates. There' | + | The community will NOT be voting to directly approve code updates. There' |
| The community will always be able to submit proposals and vote on them. This can be done by anyone. If they are approved by the community vote, they will get passed on to the DevTeam for review and to determine what is actually possible. The DevTeam will make changes to the concept if necessary, then submit a final approval for the community to vote on. Thereafter, the DevTeam will move forward with development of the concept. | The community will always be able to submit proposals and vote on them. This can be done by anyone. If they are approved by the community vote, they will get passed on to the DevTeam for review and to determine what is actually possible. The DevTeam will make changes to the concept if necessary, then submit a final approval for the community to vote on. Thereafter, the DevTeam will move forward with development of the concept. | ||
voting_system_overview.txt · Last modified: 04/29/2023 18:35 by gfactor