|
| 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 | +> > - 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. |
| 32 | +
|
| 33 | +The goal of the proposal was to have a central place where the team |
| 34 | +can review designs and have design discussions. These discussions could |
| 35 | +have a few forms: |
| 36 | + |
| 37 | +- In some cases, people might bring a thorny problem, looking for help in |
| 38 | + finding a design. ([Example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193679)) |
| 39 | +- In other cases, people might be bringing an existing idea for |
| 40 | + evaluation and broader discussion, looking to reach a |
| 41 | + conclusion. ([Example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163193734)) |
| 42 | + |
| 43 | +In each case, there will be a proposal describing the question at hand |
| 44 | +and the goals of the meeting. [The expectations for this proposal |
| 45 | +would vary depending on the kind of |
| 46 | +discussion.](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194111) |
| 47 | +For "early stage" discussions, the proposal might be fairly sparse. |
| 48 | +([Perhaps like this |
| 49 | +example](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194566).) |
| 50 | +For meetings that aim to reach firm decisions, [the proposals would be |
| 51 | +expected to contain more |
| 52 | +details](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194229); |
| 53 | +it would be useful to list [things the author expects are hard to |
| 54 | +do](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194768) |
| 55 | +and also points where there are [design decisions to be |
| 56 | +made](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194846). |
| 57 | + |
| 58 | +The expectation is that these meetings will help us propagate |
| 59 | +knowledge of what is going on through the project; they will help |
| 60 | +people get feedback on designs (right now, it can be hard to get |
| 61 | +people to make time to really talk out a design). Finally, [they can |
| 62 | +help newcomers to get more familiar with |
| 63 | +things](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194881), |
| 64 | +since people can lurk in the meetings and soak up details ([not to |
| 65 | +mention the paper |
| 66 | +trail](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163194320)). |
| 67 | + |
| 68 | +While the basic idea of the proposal was popular, we wound up changing |
| 69 | +some of the details for how it would run. We settled ultimately on |
| 70 | +**reusing the slot for the existing steering meeting** (Friday |
| 71 | +mornings, Boston time) but making it **weekly**. |
| 72 | + |
| 73 | +Every Nth meeting (likely 3 or 6) would be a designated **steering |
| 74 | +meeting**. The role of these steering meetings it so select the next |
| 75 | +N-1 topics that will be discussed (from a list of proposals). In |
| 76 | +between meetings, people can add meeting proposals to the list for the |
| 77 | +next round. |
| 78 | + |
| 79 | +When we make these decisions, we would be trying to take a ["global |
| 80 | +view"](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195057). |
| 81 | +In particular, [we don't want to be doing designs unless there are |
| 82 | +people who will put them into |
| 83 | +practice](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163198133). This |
| 84 | +probably means that we will prioritize design questions arising from |
| 85 | +existing working groups, but we might also take up design questions |
| 86 | +that might become the basis for a new working group, as long as there |
| 87 | +are people who would want to take part. |
| 88 | + |
| 89 | +We also spent some time discussing the idea of a [mentoring or |
| 90 | +'internship' |
| 91 | +program](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195743) |
| 92 | +for helping "frequent contributors" make the jump to "compiler team |
| 93 | +member". The designs that we discuss in this meeting would hopefully |
| 94 | +wind up detailed enough that [frequent contributors can pick them up |
| 95 | +and implement |
| 96 | +them](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195172), |
| 97 | +even if the people *making* the design are busy with other things. |
| 98 | +Similarly, [design documents can become the basis for rustc-guide |
| 99 | +chapters](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/steering.20meeting.202019.2E04.2E12.20.2358850/near/163195352). |
| 100 | + |
| 101 | +[We plan to flesh out some more details and put this idea into action |
| 102 | +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