Don't suggest reusing old issues for spec proposals

In practice this was confusing for people, so instead we should encourage people to create new issues and reference the existing ones.

Signed-off-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
Travis Ralston 2018-06-18 12:03:14 -06:00 committed by GitHub
parent 8fe88d2590
commit fc402c296b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -30,9 +30,9 @@ The process for submitting a Matrix Spec Change (MSC) Proposal is as follows:
<https://docs.google.com/document/d/1CoLCPTcRFvD4PqjvbUl3ZIWgGLpmRNbqxsT2Tu7lCzI/>`_ <https://docs.google.com/document/d/1CoLCPTcRFvD4PqjvbUl3ZIWgGLpmRNbqxsT2Tu7lCzI/>`_
is available. is available.
- Make a new issue at https://github.com/matrix-org/matrix-doc/issues (or - Make a new issue at https://github.com/matrix-org/matrix-doc/issues, whose
modify an existing one), whose description should list the metadata as per description should list the metadata as per below. If an existing issue
below. relates to your proposal, link to it in your new issue.
- Gather feedback as widely as possible from the community and core team on - Gather feedback as widely as possible from the community and core team on
the proposal. the proposal.