Contributor's Guide: Create "Using Github Issues" #1178
Conversation
The previous, more procedural, way of determing docs root sections did not take into consideration possible docs sections outside of `/learn/*`. I would've done a better procedural way, but the lack of while loops in Tera threw a wrench in that plan, so for now this is the best I can do without further blocking progress on the contributing guide.
There was a problem hiding this comment.
Good content! I think this page is in a bit of a weird place: it's talking to two different audiences. The first is "I'm a random user who wants to file an issue" and the second is "I want to do or understand triage". The intro and "When to File an Issue" feel like they should be lumped into a "Filing Issues" doc, while the rest belongs in a "Bevy's Triage Process" doc.
In the second doc, we should also make it very clear that we hand out triage rights like candy, and to just ask if you have any interest.
|
I've split up the document into a page on Github Issues and a page on triage. Tell me what you think! Does "Using Github Issues" now need more content, or does it serve its purpose? |
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
|
Edit: Done! |
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Co-authored-by: ramirezmike
BD103
added
S-Ready-For-Final-Review
Part of #1146. This covers both a guide on when to create issues, as well as a more general-purpose triage reference.