lfajardo
/
thegridprotocol
mirror of https://gitlab.com/thegridprotocol/home
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Be explicit that two independent impls requirement comes from BCP 9

master
Max Dor 2019-07-18 23:59:41 +02:00
parent 58702c4b3e
commit 992718ba5c
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/doc-principles.md
View File

@ -206,4 +206,4 @@ The Protocol Specification will be one of the final products and the most import
As a special authoritative document, its main Proof of Work will be "delayed" and mostly contained in its ability of As a special authoritative document, its main Proof of Work will be "delayed" and mostly contained in its ability of
[Peer convincing](#peer-convincing) and being backed by two independent [Implementation](#implementation), adding to a [Peer convincing](#peer-convincing) and being backed by two independent [Implementation](#implementation), adding to a
total of three independent *Documentations* (one is the specification, two are the implementations). total of three independent *Documentations* (one is the specification, two are the implementations). This is in line with the requirements of [BCP 9](https://datatracker.ietf.org/doc/rfc6410/?include_text=1).

2
docs/governing-body.md
View File

@ -38,7 +38,7 @@ The Governing Body will provide:
- What is reasonably necessary for its boards to fulfill their responsibilities - What is reasonably necessary for its boards to fulfill their responsibilities
- What is reasonably expected from the community about such entity with a similar mission - What is reasonably expected from the community about such entity with a similar mission
- End-users software, tools and services to showcase the protocol usage and goals - End-users software, tools and services to showcase the protocol usage and goals
- Development software, tools, documentation and services to ensure independent implementations are possible and straightforward - Development software, tools, documentation and services to ensure independent implementations are possible and straightforward, following [BCP 9](https://datatracker.ietf.org/doc/rfc6410/?include_text=1).
- Means and services to discuss, exchange, and learn about the protocol - Means and services to discuss, exchange, and learn about the protocol
- Guidelines and processes for protocol changes and community contributions, ensuring these are always welcoming, - Guidelines and processes for protocol changes and community contributions, ensuring these are always welcoming,
as easy as possible, and as rewarding as possible. as easy as possible, and as rewarding as possible.

4
docs/overview.md
View File

@ -119,7 +119,7 @@ If you believe in the same values and ideas as we do, we’ll be happy to have y
The high level steps are: The high level steps are:
- Creation of a non-profit to kick-start, grow, foster and maintain The Grid protocol. - Creation of a non-profit to kick-start, grow, foster and maintain The Grid protocol.
- Document all the concepts and network exchanges. - Document all the concepts and network exchanges.
- Ensuring that at least two independent implementations validate the documentation. - Ensuring that at least two independent implementations validate the documentation, following [BCP 9](https://datatracker.ietf.org/doc/rfc6410/?include_text=1).
### Governing body ### Governing body
To ensure the protocol is free of control from a single entity and that the users are empowered to control it, a non-profit To ensure the protocol is free of control from a single entity and that the users are empowered to control it, a non-profit
@ -173,5 +173,5 @@ in an invisible manner for the end user.
## Links and Sources ## Links and Sources
[1]: https://matrix.org/blog/home/ - “Support Matrix Today” section [1]: https://matrix.org/blog/home/ - “Support Matrix Today” section
[2]: https://matrix.org/blog/2018/05/01/security-update-synapse-0-28-1/ [2]: https://matrix.org/blog/2018/05/01/security-update-synapse-0-28-1/
[3]: https://matrix.org/blog/2018/06/14/security-update-synapse-0-31-2/ [3]: https://matrix.org/blog/2018/06/14/security-update-synapse-0-31-2/