Skip to content

Commit c5408d6

Browse files
committed
modify procedure to talk about issues
1 parent 93d6c12 commit c5408d6

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

procedures/steering-meeting.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -74,13 +74,18 @@ meetings, rather than (e.g.) planning things at the last minute.
7474

7575
## Adding a proposal
7676

77-
Proposals can be added by opening a PR and adding a new file into the
78-
[proposals] directory. The file should use the [proposal
79-
template][template], but renamed to a suggestive title. **This format
80-
is meant to be lightweight:** Proposals are generally not expected to
81-
be a lot of work to produce.
82-
83-
[proposals]: /proposals
77+
Proposals can be added by opening an issue on the [compiler-team
78+
repository][ct]. There is an issue template for meeting proposals that
79+
gives directions. The basic idea is that you prepare your proposal in
80+
a gist/hackmd/document based on [this template][template] and then
81+
link to that in the issue, along with a few other details. **This
82+
format is meant to be lightweight:** Proposals are generally not
83+
expected to be a lot of work to produce. Accepted proposals will be
84+
added to the [proposals] directory (and linked to from the actual
85+
minutes).
86+
87+
[ct]: https://github.com/rust-lang/compiler-team
88+
[proposals]: /proposals/
8489
[template]: /proposals/_template.md
8590

8691
### Expectations for a technical proposal

0 commit comments

Comments
 (0)