Each week choose a scribe at random. Everyone should take a turn, and there are enough people that you won't have to do this too often. If you've never scribed a meeting before, don't worry. The basic principle is to just write down what everybody says, and attribute it to the right person - this can be verbatim if you type fast, or a summary or paraphrased if that's easier for you (or a combination).
We have a script that parses the Zulip logs into human-readable static minutes for the website. Here are some tips to make sure your scribing comes out right:
..as a continuation.
**@Their Name**so the script can parse this as a speaker anyway.
TOPIC: topiccreates a subhead for "topic" in the minutes. Please use this! Topics are typically on the agenda beforehand, so you can prepare what to expect by glancing over that.
PROPOSED: proposaladds the proposal to the list of proposals.
RESOLVED: resolutionadds the resolution to the list of resolutions.
scribe: namerecords the name of the scribe (optional)
present+adds whoever says it to the list of attendees (scribe doesn't need this)
As the scribe, you can interrupt a speaker any time to:
If you need to speak, please ask someone else to scribe you! (It's very hard to speak and scribe at the same time.)
Don't worry about fixing typos and grammar during the meeting. You can go back and edit your messages afterwards to clean up things like this (please do!).
If you forgot to add topics, or mistyped someones name, or spelled 'says' wrong somewhere, please go fix these up too, ideally as soon as the meeting is over.
Keep a look out for people correcting your scribing inline, and if necessary go back and edit your messages to take their corrections into account after the meeting.