Skip to content

Commit 715397a

Browse files
authored
Merge pull request #267 from nikomatsakis/lang-team-triage-meeting
document lang-team triage meeting procedure
2 parents e34d2d5 + a4d0725 commit 715397a

File tree

1 file changed

+61
-0
lines changed

1 file changed

+61
-0
lines changed

src/lang/triage-meeting-procedure.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# Triage meeting procedure
2+
3+
This page documents how to run a lang team triage meeting,
4+
should you have the misfortune of being forced to do so.
5+
6+
## Attending a meeting
7+
8+
If you would just like to **attend** a lang-team triage meeting, all
9+
you have to do is join the zoom call (the URL is attached to the
10+
calendar invite below).
11+
12+
## Scheduling
13+
14+
Note that the scheduling for all meetings is recorded in the [team
15+
calendar], links to which can be found on the [rust-lang/lang-team]
16+
repository.
17+
18+
[team calendar]: https://github.com/rust-lang/lang-team/#meeting-calendar
19+
[rust-lang/lang-team]: https://github.com/rust-lang/lang-team/
20+
21+
## Pre-triage
22+
23+
To start, we have a pre-triage meeting which occurs before the main
24+
meeting. This is not recorded. It is boring.
25+
26+
To execute this meeting you:
27+
28+
* Open the [Current Meeting] dropbox paper document
29+
* Skim down the action items and look to see if there are any you know have been handled
30+
* they can be checked off and removed
31+
* Skip down to the Triage section
32+
* For each Triage section, click on the link and populate it with what you find
33+
* typically it is best to copy-and-paste the title of the issue, so that links remain intact
34+
* For each item, click in and try to add a few notes as to the main topic
35+
* look for things where there isn't much discussion needed, or just reminders
36+
* these can be handled quickly in the meeting, or perhaps not at all
37+
* items that require more discussion will need time alotted for them
38+
39+
[Current Meeting]: https://paper.dropbox.com/doc/T-Lang-Meeting-Current-meeting--AmyXFNnryXTNzBsSWjbdJcVSAg-nRfrSxCbfeo9q7fEYogZQ
40+
41+
## Main meeting
42+
43+
* Ping the team on discord `@lang-team`
44+
* Begin the recording on Zoom, if you have acccess
45+
* If nobody has access to the recording, oh well, we don't do it every week
46+
* Discuss item by item and take some notes on what was said
47+
* Add specific actions to the action items section above
48+
* If a consensus arises, make sure to create an action item to document it!
49+
* The goal should be that we leave some comment on every issue
50+
51+
## After meeting
52+
53+
* Export the meeting file to markdown
54+
* you will need to cleanup "check boxes" -- Niko usually searches and replaces
55+
`^(\s*)[ ]` with `\1* [ ]` or something like that to insert a
56+
`*` before them, which makes them valid markdown
57+
* Upload video to youtube if applicable and get the URL
58+
* Add the file to the [minutes] directory of [rust-lang/lang-team] repository
59+
with a file name like `YYYY-MM-DD.md`
60+
61+
[minutes]: https://github.com/rust-lang/lang-team/tree/master/minutes

0 commit comments

Comments
 (0)