Commit Graph

8 Commits (e674791fe08033faafbea550b8b83fe85c0ba871)

Author SHA1 Message Date
codedust 765af8d00f
Proposal template: explicitly mention RFC 3552 in security section (#4378)
* Template: explicitly mention RFC 3552 in security section

Signed-off-by: codedust <codedust@users.noreply.github.com>

* Apply suggestions from code review

---------

Signed-off-by: codedust <codedust@users.noreply.github.com>
Co-authored-by: Travis Ralston <travpc@gmail.com>
3 weeks ago
Kegan Dougal 27bc9a50e9
Mandate a 'Security Considerations' section on MSCs (#4199)
And link to lists of possible problems to think about.
This is part of an effort to improve the overall security
of Matrix during the design process.
1 year ago
Matthew Hodgson 8d9a67d9f6
add an explicit dependencies block. 4 years ago
Richard van der Hoff 4aa778cdee
Put the MSC number in the proposal template (#2622)
this seems to be our convention.
6 years ago
Hubert Chathi b7234c7fd3 add unstable prefix section to proposal template 6 years ago
Richard van der Hoff 5d6113db1e
Update the MSC template (#2296)
Tradeoffs->Alternatives, and kill the Conclusions section
6 years ago
Hubert Chathi 58091fa3fe make heading level for "Security considerations" match the other headings
as much as I like that "Security considerations" gets to be bigger than the
other headers, we should probably make it consistent
7 years ago
Andrew Morgan 748a81523c Rename proposal template to MSC #0000 7 years ago