Noratrieb/slides
1
0
Fork 0
mirror of https://github.com/Noratrieb/slides.git synced 2026-01-14 16:35:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

more

Browse source
This commit is contained in:
nora 2024-01-03 17:26:22 +01:00
parent 6ba4f4eacd
commit fa1556cab3
3 changed files with 15 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
speaker_notes.md
View file

@ -37,4 +37,13 @@ Triaging issues is great because it's easy to get started and you can put in ver
You can triage one issue in two minutes, or you can spend 2 hours on an issue. It always depends on the
issue and how much time you want to put in, even the small work is nice.
For issues
Some of the things that are involved when triaging issues are labelling, minimization, bisection and adding tests.
Labelling is the task here that takes the least time. We have an example issue here, that requests that the standard
library documents the memory ordering guarantees for the thread spawn function.
Let's think about what this is: This is a *feature request* for *documentation* about *threads* and *atomics*.
The feature request is to the *library API team*, as it's about a guarantee.
So we add those labels. Remove needs-triage, as we're doing triage, add the docs, thread and atomics area, the category
feature request and the team libs api. If you're not part of a team that has write access to the repository, you can leave
a comment with rustbot as shown here. If you're interested and want to know more, see the link below.