Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-11 08:33:42 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

add TODO for clarifying features v. extensions

Browse source
This commit is contained in:
Matthew Hodgson 2019-01-07 02:47:37 +00:00
parent 303e1081f8
commit e6fb403dd0
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -121,6 +121,10 @@ 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