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

matthew/msc1779
Matthew Hodgson 6 years ago
parent c053996a77
commit edaf3596f4

@ -1,11 +1,11 @@
# Proposal for Open Governance of Matrix.org # Proposal for Open Governance of Matrix.org
This whole document is a **work in progress** draft of a constitution proposal This whole document is the proposed constitution proposal for Matrix.org, and
for open governance for Matrix.org, and forms the basis of the first full will form the basis of the first full Articles of Association (AoA) for [The
Articles of Association (AoA) for [The Matrix.org Foundation Matrix.org Foundation
C.I.C.](https://beta.companieshouse.gov.uk/company/11648710) - a non-profit legal C.I.C.](https://beta.companieshouse.gov.uk/company/11648710) - a non-profit
entity incorporated to act as the neutral guardian of the Matrix decentralised legal entity incorporated to act as the neutral guardian of the Matrix
communication standard on behalf of the whole Matrix community. 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/ See https://matrix.org/blog/2018/10/29/introducing-the-matrix-org-foundation-part-1-of-2/
for more context. for more context.
@ -121,10 +121,6 @@ rather than closed deployments. For example, if WhatsApp adopted Matrix it
wouldnt be a complete win unless they openly federated with the rest of the wouldnt be a complete win unless they openly federated with the rest of the
Matrix network. 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 ### Values
As Matrix evolves, it's critical that the Spec Core Team and Guardians are As Matrix evolves, it's critical that the Spec Core Team and Guardians are

Loading…
Cancel
Save