Skip to content

Commit 8e10f82

Browse files
authored
Update 2019-11-12-goverance-wg-cfp.md
1 parent f9381a1 commit 8e10f82

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

posts/inside-rust/2019-11-12-goverance-wg-cfp.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ the result as a RFC and then if merged provide a version on
2424
schedule people involved in Rust and other governance structures to come and
2525
talk about their experiences.
2626

27-
For deciding what topics, we're going to rotate
28-
who takes the lead for each meeting. It's that person's responsibility to
29-
decide the topic and to prepare a blog post similar to this informing people of
30-
the topic and how they might best prepare.
27+
For deciding what topics, we're going to rotate who takes the lead for each
28+
meeting. It's that person's responsibility to decide the topic and to
29+
prepare a call for participation similar to this post informing people of
30+
the topic and how they might best prepare if they wish to join.
3131

3232
We also hope that having a focused topic will reduce any barrier of expected
3333
knowledge in order to participate and contribute. With that said let's talk
@@ -37,25 +37,25 @@ about the topic for next meeting.
3737

3838
Our first topic for new meeting is going to be to read [RFC 1068], the
3939
original Rust Governance RFC, review how accurate it is to today's structure,
40-
and see any if there are questions that we have that it doesn't answer. There's
41-
also some other RFCs that are also good to read that are listed below.
40+
and see any if there are questions that we have that it doesn't answer. Here
41+
are some other relevant RFCs for additional context:
4242

4343
- ["North Star" RFC] lays out the Rust roadmap process.
4444
- [Compiler contributors RFC] details the process of contributing to the
4545
compiler and progression towards joining the compiler team.
4646
- [Compiler bug fix procedure] defines the best practices for making a bug fix
4747
to the compiler.
4848

49-
Our next meeting is going to be at **22:00 on Tuesday, November 19th** and we'd
50-
like to encourage anyone who's interested, regardless of their previous
51-
experience to read those RFCs and come to the `#wg-governance` channel on
52-
discord to attend the meeting. (Our meetings are done over a video call with
53-
Zoom, but we use the discord channel to organise ourselves).
49+
Our next meeting is going to be at **22:00 UTC on Tuesday, November 19th**
50+
and we'd like to encourage anyone who's interested, regardless of their
51+
previous experience to read those RFCs and come to the `#wg-governance`
52+
channel on discord to attend the meeting. (Our meetings are done over a video
53+
call with Zoom, but we use the discord channel to organise ourselves).
5454

5555
If some reason you know you won't be able to attend these meetings but would
56-
still like to participate. We're encouraging for people to post any questions
57-
they have about Rust's governance they have as [issues on our
58-
GitHub repository][gh-issues].
56+
still like to participate. Please feel free to post any questions about Rust's
57+
governance as [issues on our GitHub repository][gh-issues], even if you are
58+
not available to attend the working group's meetings.
5959

6060
[rfc 1068]: https://rust-lang.github.io/rfcs/1068-rust-governance.html
6161
["north star" rfc]: https://github.com/rust-lang/rfcs/blob/26197104b7bb9a5a35db243d639aee6e46d35d75/text/1728-north-star.md

0 commit comments

Comments
 (0)