---
tags: rustc, learning
---

# Learning WG - Rolling Agenda

## Discussion priority queue (pop from top)

> Meetings start with some progress reporting...

- What is each of us working on and what's the progress we are having?

> ... then work through as many as we can of these topics. Feel free to add stuff or reorder if you think something should have higher priority.

- Sprint planning. Possible tasks:
- Technical debt (lots of potential cleanup, followup work, lots of open issues)
- mark-i-m: I particularly want to go through open issues and triage them systematically and fix low-hanging fruit. I know this is tedious work, but I feel like we need to do it at some point...
- Mermaid -- add diagrams throughout the guide
- Errors/Diagnostics chapter
- Reorganizing Part 1 in general
- where to put the contributing stuff
- where to put procedures about various things, like stabilizing features?
- Profiling the compiler
- Debugging the compiler
- Work more on the structure of the guide?
- Walkthrough sections?

## Discussed 2020/04/14

- The overview chapter
- decided that we want to just go ahead and merge with minimal changes
- created followup issue for additional improvements

## Discussed 2020/03/03

We defined the next sprint as:

- Write an Overview chapter, include a walkthrough section about what the compiler does to your code
- Do a cookbook-style appendix for PRs that help understanding some parts of the compiler
- [ ] [@mark-i-am] Schedule a lecture about codegen mir -> llvm IR with @nagisa
- [ ] [@spastorino] Schedule a lecture about Parallel with @nikomatsakis, @simulacrum or @Alex Crichton
- [ ] [@spastorino] Schedule a lecture about LLVM with @Alex Crichton
- [ ] [@spastorino] Schedule a lecture about monomorphization/type memory layout with @oli
- [x] [@spastorino] Change the name of the guide to rustc-dev-guide

## Discussed 2020/02/18

- Recap of directions from [planning meeting](https://rust-lang.zulipchat.com/#narrow/stream/196385-t-compiler.2Fwg-learning/topic/planning.20meeting)
- Came up with this [master doc](https://hackmd.io/iamkyR_QTdSIdGjYQX_XjQ) prioritizing things to do
- Started [this overview doc](https://hackmd.io/j8EsXGI1RiOnjZSiSRf3ng) to collect questions/knowledge
- Walkthrough section with explanations of a PR, see https://github.com/rust-lang/rustc-guide/issues/584
- Schedule discussion about LLVM/Codegen?
- Schedule other discussions about other topics?
- codegen mir -> llvm IR (@nagisa, maybe?)
- LLVM (@Alex Crichton, maybe?)
- monomorphization/type memory layout (@oli, maybe?)
- parallel (@nikomatsakis, @simulacrum, @Alex Crichton)
- Restart a sprint-like process?
- Discuss about the structure of the guide
- Does it worth to have a lot of procedures instead of the actual meat of Rustc? won't be better to move those somewhere else or at least to appendices?
- Should we do another blog post?

## Discussed 2019/11/26

- Define Roadmap
- Define the most important missing content that we want to add to rustc-guide. See `rustc-guide missing chapters` on tasks on the [master document](https://hackmd.io/nr5Ww319TnWM2HL_cg5I-w).
- Prioritize that content.. what needs to be done first and what things can wait a bit more.
- Define working process
- Define the strategy we want to follow to accomplish progress over the different chapters.
- Define a good process that allows us to improve and quickly change things that are not working.
- Decide if it's worth having meetings, given the low attendance and activity.
- Sprint like process
- Will be trying it
- Asynchronously watch videos, then hold meetings to ask/answer questions
- Have some sort of timeline for things, every 2 months

## Completed 2019/09/17
- Procedure for debugging and fixing toolstate

## Completed 2019/07/23

- create a rustc-guide strike force (mark-i-m)
- lots of issues marked "easy" or "medium"
- Need to triage each issue and do all low-hanging fruit

## Completed 2019/07/09

- organize lectures on codegen and macros
- more generally, discussed organizing lectures

## Completed 2019/06/25

- Helping out with mdBook
- Blog post announcing documentation efforts and tasks, location and contents
- A way to track the lectures we want to do, the one's we've scheduled, the ones we've transcribed, etc
- Discuss what to add from https://forge.rust-lang.org/bibliography.html to the guide.

## Completed 2019/06/11

- How to triage the rustc-guide repo (cont'd)
- triagebot or github assignment or what?
- How/where to link to the forge and the rustc-guide
- current doc.rlo doesn't link to either
- perhaps a rlo/contribute page?
- add people to rustc toolstate when available

## Completed 2019/05/28

- Define what forge should be and how that affects rustc-guide

## Completed 2019/05/14

- Define what's the walkthrough section we want to add
- Triage missing `rustc-guide` chapters
- How do we want to keep track of who is doing what? does github `Projects` works nice for this?