Skip to content

Commit a0a582a

Browse files
committed
steering meeting minutes from 2019.04.12
1 parent 9d8c387 commit a0a582a

File tree

1 file changed

+104
-0
lines changed

1 file changed

+104
-0
lines changed
Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
# 2019.04.12
2+
3+
[Zulip topic.](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850)
4+
5+
## Announcements
6+
7+
- [nikomatsakis](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163192566)
8+
has opened a [PR with a draft
9+
RFC](https://github.com/rust-lang/compiler-team/pull/52) on the
10+
compiler-team repository. This RFC describes adding a new level
11+
("compiler team contributors") to recognize people who have been
12+
contributing regularly. It also tries to document a few things about
13+
members etc. Please give it a read!
14+
- [eddyb](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193094)
15+
is nearing completion on their work on the symbol naming revamp. It
16+
[might even offer some performance
17+
improvements](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193354).
18+
- [nikomatsakis](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193402)
19+
mentioned that in the [wg-traits meeting on
20+
Monday](https://calendar.google.com/event?action=TEMPLATE&tmeid=NnViNzZxN252dGZ2ZHRvNTdnN2dpbGo2NjRfMjAxOTA0MTVUMTgwMDAwWiA2dTVycnRjZTZscnR2MDdwZmkzZGFtZ2p1c0Bn&tmsrc=6u5rrtce6lrtv07pfi3damgjus%40group.calendar.google.com&scp=ALL)
21+
we plan to discuss how the Chalk crates are setup and the work to
22+
refactor them to make them more friendly for the RLS etc.
23+
24+
## Main topic
25+
26+
Our [main
27+
topic](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193454)
28+
of the day was a **proposal to add a regular design meeting**:
29+
30+
> So this was our plan for the main topic today:
31+
> ```quote
32+
> - After that we'll talk about my [proposal for a regular design meeting](https://gist.github.com/nikomatsakis/3afbec52758741727e4535d973bb0667) and perhaps also a bit about working groups and how we feel they are working, what's could be improved, etc.
33+
> ```
34+
35+
The goal of the proposal was to have a central place where the team
36+
can review designs and have design discussions. These discussions could
37+
have a few forms:
38+
39+
- In some cases, people might bring a thorny problem, looking for help in
40+
finding a design. ([Example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193679))
41+
- In other cases, people might be bringing an existing idea for
42+
evaluation and broader discussion, looking to reach a
43+
conclusion. ([Example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193734))
44+
45+
In each case, there will be a proposal describing the question at hand
46+
and the goals of the meeting. [The expectations for this proposal
47+
would vary depending on the kind of
48+
discussion.](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194111)
49+
For "early stage" discussions, the proposal might be fairly sparse.
50+
([Perhaps like this
51+
example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194566).)
52+
For meetings that aim to reach firm decisions, [the proposals would be
53+
expected to contain more
54+
details](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194229);
55+
it would be useful to list [things the author expects are hard to
56+
do](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194768)
57+
and also points where there are [design decisions to be
58+
made](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194846).
59+
60+
The expectation is that these meetings will help us propagate
61+
knowledge of what is going on through the project; they will help
62+
people get feedback on designs (right now, it can be hard to get
63+
people to make time to really talk out a design). Finally, [they can
64+
help newcomers to get more familiar with
65+
things](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194881),
66+
since people can lurk in the meetings and soak up details ([not to
67+
mention the paper
68+
trail](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194320)).
69+
70+
While the basic idea of the proposal was popular, we wound up changing
71+
some of the details for how it would run. We settled ultimately on
72+
**reusing the slot for the existing steering meeting** (Friday
73+
mornings, Boston time) but making it **weekly**.
74+
75+
Every Nth meeting (likely 3 or 6) would be a designated **steering
76+
meeting**. The role of these steering meetings it so select the next
77+
N-1 topics that will be discussed (from a list of proposals). In
78+
between meetings, people can add meeting proposals to the list for the
79+
next round.
80+
81+
When we make these decisions, we would be trying to take a ["global
82+
view"](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195057).
83+
In particular, [we don't want to be doing designs unless there are
84+
people who will put them into
85+
practice](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163198133). This
86+
probably means that we will prioritize design questions arising from
87+
existing working groups, but we might also take up design questions
88+
that might become the basis for a new working group, as long as there
89+
are people who would want to take part.
90+
91+
We also spent some time discussing the idea of a [mentoring or
92+
'internship'
93+
program](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195743)
94+
for helping "frequent contributors" make the jump to "compiler team
95+
member". The designs that we discuss in this meeting would hopefully
96+
wind up detailed enough that [frequent contributors can pick them up
97+
and implement
98+
them](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195172),
99+
even if the people *making* the design are busy with other things.
100+
Similarly, [design documents can become the basis for rustc-guide
101+
chapters](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195352).
102+
103+
[We plan to flesh out some more details and put this idea into action
104+
starting May 3rd (the next steering meeting).](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163198505)

0 commit comments

Comments
 (0)