https://github.com/CityOfZion/governance

Rules of Zion
https://github.com/CityOfZion/governance

Last synced: 3 months ago
JSON representation

Rules of Zion

• Host: GitHub
• URL: https://github.com/CityOfZion/governance
• Owner: CityOfZion
• License: mit
• Created: 2017-07-07T00:26:01.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-10-05T03:49:44.000Z (about 7 years ago)
• Last Synced: 2024-04-15T04:31:03.912Z (7 months ago)
• Size: 3.12 MB
• Stars: 6
• Watchers: 12
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-neo - Community Governance - The home of the CoZ community rules and reports. (City of Zion / MainNet and TestNet (2.7.6+))

README

        
# Community Governance

This is the home of the [City of Zion](http://cityofzion.io/) (CoZ) community rules and reports.

Our formalization reflects a humble move from the NEO team to receive our contributions and provide support for quality work.

The community is free to choose its own targets and objectives. That said, our goal is to improve NEO, so we will align with the NEO team's needs and avoid retreading old ground as much as possible, unless it is possible to attain a substantially higher level of quality.

The initial structure is:

1. There will be a council always composed of 9 members. They are the Council team in our organization.

1. There will be a high council composed of 4 members of the council. They are the Maintainers of the Council team.

1. Any member of CoZ can create and collaborate on projects.

1. There will be a weekly report delivered to NEO by the high council via a PGP signed email and correspondent pull request on GitHub.

1. In case of any support from NEO as reward or bounty, the funds will initially be held by a trusted third party in wallet AXSoNQEKjmqPBNPg5cNrHyWivfjok3Vj9D for distribution.

1. After 1 September 2017, all CoZ funds will be held in a multi-sig wallet requiring a majority of the high council to unlock funding.

1. Rewards distribution will be voted on by project before being sent. There must be a majority agreement of all 9 council members.

1. All decisions not explicitly differentiated in this list will be voted upon as in item 7.

1. Item 7 voting polls of the council will run for 1 week on the #council Slack channel and after closing will be published in the #develop channel.

1. The high council will be voted upon each quarter, synchronizing with the quarters of the year. The first election will be on 1 October 2017. The newly elected high council can propose changes to these rules during the first week after the election. Changes will be voted upon as in item 7.

1. Any member of the council or high council is free to forfeit their position at any time. When this happens, an election will take place and a majority of council members must decide upon a replacement.

1. Any member of the council that does not vote on polls for more than 2 months will automatically forfeit their position.