User:Vilkris
Contact
matrix: @vilkris:hc1.chat
Maintainer guidelines
go-zenon
Protocol Changes
Protocol changes should reflect the goals of the community and have a supermajority of pillars supporting the changes. In addition to implementing protocol changes, the role of a developer should be to explain the technical details of a protocol change in a way that the wider community can understand, allowing for non-technical pillars and community members to form an opinion on the matter.
When evaluating a protocol change proposal, I am hoping to see the following:
- The proposed protocol changes are documented in a ZIP
- The changes are presented in such a way that non-technical pillars are able to form an opinion
- The proposed changes are discussed publicly
- A way for the community to test and verify an implementation