|
| 1 | +# Libs-impl Pre Meeting 2021-02-02/03 |
| 2 | + |
| 3 | +###### tags: `Libs-impl Meetings` |
| 4 | + |
| 5 | +**Attendees**: |
| 6 | + |
| 7 | +## Agenda |
| 8 | + |
| 9 | +- Current state of the Libs Impl Charter: |
| 10 | + - [Libs Impl](https://hackmd.io/AFIoTuatR5-RCJiHqGZk-A) |
| 11 | + - [Libs Reviewers](https://hackmd.io/FB_HLMRMR6Oxtm3t_oCNEQ) |
| 12 | +- Direction and organization of `std-dev-guide`. |
| 13 | +- What to do with the current `library-reviewers` team. |
| 14 | +- Process for recruiting/adding new people. |
| 15 | +- Next steps |
| 16 | + - Get some initial thoughts on charter from core (sometime in the next few weeks, possibly have a place to submit the charter in a week or so) |
| 17 | + - After that, create team on GitHub? |
| 18 | + |
| 19 | +## Notes |
| 20 | + |
| 21 | +- Libs Impl working with Libs: Link to the std dev guide |
| 22 | +- Library Reviewers |
| 23 | + - Leave as-is or possible expand |
| 24 | + - Charter the team later down the track |
| 25 | + - Consider reviewer sprints or work down the track |
| 26 | + - Spend a meeting exploring an area of the standard library |
| 27 | +- How do we grow these teams? |
| 28 | + - Space for bigger deisgn |
| 29 | + - Create project groups around areas |
| 30 | +- Don't split the repos for now |
| 31 | +- Documentation guidelines |
| 32 | + - Don't need to be fully prescriptive |
| 33 | + - Linking to `doc.rust-lang/org` things |
| 34 | +- Processes around issues and pull requests |
| 35 | + - Document labels |
| 36 | + - Re-assignment |
| 37 | + - Whether we look at specific labels |
| 38 | + - Assigning contributors to bugs |
| 39 | +- Using more of triagebot |
| 40 | +- Updates to rfcbot |
0 commit comments