Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-26 10:58:38 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

fix 'which features should go in the spec?' TODO and reword intro

Browse source
This commit is contained in:
Matthew Hodgson 2019-01-12 23:14:36 +00:00
parent c053996a77
commit edaf3596f4
1 changed files with 6 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
proposals/1779-open-governance.md
View file

@ -1,11 +1,11 @@
# Proposal for Open Governance of Matrix.org
This whole document is a **work in progress** draft of a constitution proposal
for open governance for Matrix.org, and forms the basis of the first full
Articles of Association (AoA) for [The Matrix.org Foundation
C.I.C.](https://beta.companieshouse.gov.uk/company/11648710) - a non-profit legal
entity incorporated to act as the neutral guardian of the Matrix decentralised
communication standard on behalf of the whole Matrix community.
This whole document is the proposed constitution proposal for Matrix.org, and
will form the basis of the first full Articles of Association (AoA) for [The
Matrix.org Foundation
C.I.C.](https://beta.companieshouse.gov.uk/company/11648710) - a non-profit
legal entity incorporated to act as the neutral guardian of the Matrix
decentralised communication standard on behalf of the whole Matrix community.
See https://matrix.org/blog/2018/10/29/introducing-the-matrix-org-foundation-part-1-of-2/
for more context.
@ -121,10 +121,6 @@ rather than closed deployments. For example, if WhatsApp adopted Matrix it
wouldn’t be a complete win unless they openly federated with the rest of the
Matrix network.
TODO: spell out when features should land in the spec, versus via
integration/widget or other non-core extension. e.g. should video conferencing
be in the spec itself, or done via Jitsi?
### Values
As Matrix evolves, it's critical that the Spec Core Team and Guardians are