Skip to content

Commit dfd7b34

Browse files
committed
planning/scribing: [How To Scribe] Basic instructions on how to scribe
1 parent 8293526 commit dfd7b34

File tree

1 file changed

+49
-3
lines changed

1 file changed

+49
-3
lines changed

planning/scribing.txt

Lines changed: 49 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,57 @@
22

33
Minutes must be taken for every CSS Working Group call. At the beginning of each call, the chair chooses a scribe.
44

5-
===== How To Scribe =====
5+
===== How To Scribe On IRC =====
66

7-
[todo: general details on what to write, link to how to get on W3C IRC server]
7+
<note tip>See the [[https://www.w3.org/wiki/IRC|IRC page on the W3C Wiki]] to find out how to join IRC. The CSSWG meet in the channel ''#css''.</note>
88

9-
See [[tools:scribing-conventions|Scribing Conventions]]
9+
Whether you're scribing or not, use this command first to declare you are present:
10+
11+
present+
12+
13+
Before you can scribe, you need to declare it. If you are the main scribe for the meeting, use this command:
14+
15+
ScribeNick: your_irc_nickname_here
16+
17+
If you are an additional scribe, use this command:
18+
19+
Scribe+ your_irc_nickname_here
20+
21+
Once the meeting starts, each discussion needs to go in a topic. When about to discuss a topic that is //not// on GitHub, use this command. You can get the topic name from the agenda.
22+
23+
Topic: Topic name here
24+
25+
Most topics will relate to a GitHub issue. When about to discuss a GitHub issue, use this command. You can copy the issue URL from the agenda.
26+
27+
github-bot, take up https://github.com/w3c/csswg-drafts/issues/123456
28+
29+
Starting a new topic also ends the previous topic. When you end a GitHub topic, the minutes automatically get posted by the GitHub bot to a comment in the issue.
30+
31+
Once you've set the topic, people can start discussing it. To record what people are saying, use their IRC nickname like so. You don't need to write every word; just a summary of what they are saying.
32+
33+
SomeonesName: i propose we change the initial value of box-sizing to border-box
34+
SomeonesName: it would make more sense than content-box
35+
SomeoneElse: no, that would break web compat
36+
37+
If it's easier for you, you can use ''...'' instead of repeating their IRC nickname.
38+
39+
SomeonesName: i propose we change the initial value of box-sizing to border-box
40+
... it would make more sense than content-box
41+
SomeoneElse: no, that would break web compat
42+
43+
<note important>It is everyone's responsibility to make sure the minutes get recorded. If you can't keep up with everyone who's talking, you should interrupt and ask people to: speak more slowly, repeat themselves or stop talking while you catch up. Don't feel embarrassed about interrupting; we expect you to do it!</note>
44+
45+
When everyone agrees a resolution on a topic, use this command to record it. The chair will normally say the resolution, so they will tell you how to phrase it. Make sure you record it accurately.
46+
47+
RESOLVED: The resolution here
48+
49+
<note tip>If the resolution sounds complicated, it's OK to ask someone else to write the it for you.</note>
50+
51+
Once you finish discussing the last topic and the meeting is ending, use this command:
52+
53+
github-bot, end topic
54+
55+
For more info, see [[tools:scribing-conventions|Scribing Conventions]] and the blog post [[https://www.bocoup.com/blog/how-to-scribe-at-tpac|How to scribe at TPAC]].
1056

1157

1258
===== Scribe Rota =====

0 commit comments

Comments
 (0)