|
| 1 | +# Learning Working Group |
| 2 | +![working group status: active][status] |
| 3 | + |
| 4 | +This working group aims to make the compiler easier to learn by ensuring that rustc-guide and api docs are "complete". |
| 5 | + |
| 6 | +- **Leads:** [@nikomatsakis][nikomatsakis] and [@spastorino][spastorino] |
| 7 | +- **[Ideas][ideas]** |
| 8 | +- **Meeting Notes:** [All](NOTES.md) |
| 9 | + |
| 10 | +[status]: https://img.shields.io/badge/status-active-brightgreen.svg?style=for-the-badge |
| 11 | +[nikomatsakis]: https://github.com/nikomatsakis |
| 12 | +[spastorino]: https://github.com/spastorino |
| 13 | +[ideas]: https://paper.dropbox.com/doc/Learning-Working-Group-Ideas--Ab18Mvvg7fYl8b~WL_klryqnAg-2R49k1GWZFojHIQ5x1fuB |
| 14 | + |
| 15 | +## What is the goal of this working group? |
| 16 | +This working group aims to accomplish the following: |
| 17 | + |
| 18 | +- Ensure that major components of rustc are covered in rustc-guide |
| 19 | +- Ensure that API doc coverage is at least 90% |
| 20 | + |
| 21 | +# How can I get involved? |
| 22 | +If you are interested in getting involved in this working group, come and say hi in the Zulip |
| 23 | +stream. You can be added to the Zulip group for the working group if you are interested in being |
| 24 | +pinged when there are available tasks. |
| 25 | + |
| 26 | +## Meetings |
| 27 | +We follow a "sprint-like" structure where on each "sprint" cycle we start with a planning and then |
| 28 | +work towards the goals defined on that plan. |
| 29 | + |
| 30 | +- **Desired experience level:** Any |
| 31 | +- **Relevant repositories:** [`rust-lang/rust`][rust-repo] and [rust-lang/rustc-guide][rustc-guide-repo] |
| 32 | +- **Zulip stream:** [`#t-compiler/wg-learning`][zulip] on Zulip |
| 33 | + |
| 34 | +[rust-repo]: https://github.com/rust-lang/rust |
| 35 | +[rustc-guide-repo]: https://github.com/rust-lang/rustc-guide |
| 36 | +[zulip]: https://rust-lang.zulipchat.com/#narrow/stream/196385-t-compiler.2Fwg-learning |
0 commit comments