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

rst

Browse source
This commit is contained in:
Matthew Hodgson 2019-01-28 14:57:59 +00:00
parent 41c14c9e7d
commit a358e2d4d8
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
specification/proposals_intro.rst
View file

@ -111,6 +111,7 @@ engine behaviour be specified?
There is no universal answer to this, but the following guidelines should be There is no universal answer to this, but the following guidelines should be
applied: applied:
1. If the feature would benefit the whole Matrix ecosystem and is aligned with 1. If the feature would benefit the whole Matrix ecosystem and is aligned with
the guiding principles above, then it should be supported by the spec. the guiding principles above, then it should be supported by the spec.
2. If the spec already makes the feature possible without changing any of the 2. If the spec already makes the feature possible without changing any of the
@ -122,6 +123,7 @@ applied:
3rd party behaviour. 3rd party behaviour.
As a worked example: As a worked example:
1. Video conferencing is clearly a feature which would benefit 1. Video conferencing is clearly a feature which would benefit
the whole ecosystem, and so the spec should find a way to make it happen. the whole ecosystem, and so the spec should find a way to make it happen.
2. Video conferencing can be achieved by widgets without requiring any 2. Video conferencing can be achieved by widgets without requiring any