|
|
|
Reminder that we also have the code of conduct: https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt#n80
|
|
|
|
|
|
|
|
ALL HANDS MEETINGS AGREEMENT 2.0 - edits by al based on notes stored in https://nc.torproject.net/s/39KjwieoFeMqMxW
|
|
|
|
|
|
|
|
|
|
|
|
Before the meeting
|
|
|
|
* (Organizers) Write an agenda.
|
|
|
|
* Write next meeting agenda in advance: either at the previous meeting or at least one day prior.
|
|
|
|
* Ensure agendas include a clear goal for the meeting.
|
|
|
|
* Set a meeting schedule to prevent rushing through the last topic(s) of the agenda.
|
|
|
|
* (Attendees) Review the agenda.
|
|
|
|
* Understand that some agenda items are not directly of your interest, but may be useful for the group.
|
|
|
|
* After reviewing the agenda, don't be afraid to not attend a meeting if it isn't useful to you, though consider if being there is useful to others. Ask this question.
|
|
|
|
|
|
|
|
At the beginning of the meeting
|
|
|
|
* Be respectful: be on time, start on time.
|
|
|
|
|
|
|
|
During the meeting
|
|
|
|
* Assume best intentions!
|
|
|
|
* Record Outcomes
|
|
|
|
* Not every body will make every meeting. Record outcomes (take notes).
|
|
|
|
* Rotate notetakers. Take initiative to take notes.
|
|
|
|
* Don't make the juniormost person always take the notes.
|
|
|
|
* Speaking
|
|
|
|
* Introduce yourself. We have a lot of new people, many have not met in person. Help foster community!
|
|
|
|
* Explain jargon and acronyms.
|
|
|
|
* Do not monopolize the speaking time. For example, When there are N people, try to do no more than 1/N of the talking. For those who are naturally quiet, consider talking 1/N of the time.
|
|
|
|
* Speak with a goal in mind; don't speak for the sake of speaking. Processing outloud is OK, but keep the point above in mind.
|
|
|
|
* Listening
|
|
|
|
* Mute when not talking.
|
|
|
|
* If you do not understand something please ask in main chat or in private. It can be intimidating for new people to ask lots of questions, especially in a group call, so make room for following up in private.
|
|
|
|
* Discussions
|
|
|
|
* Don't moderate a discussion that you're the main proponent of.
|
|
|
|
* Facilitate more tech-focused breakout sessions across teams.
|
|
|
|
* Break into smaller groups when possible.
|
|
|
|
* Rephrase what you think somebody meant, to see if you have them right.
|
|
|
|
* If you see a problem with someone's idea, try to help find a solution or alternative (rather than just listing problems).
|
|
|
|
* Avoid endless listing of things; focus on most important aspects as best you can.
|
|
|
|
|
|
|
|
At the end of the meeting
|
|
|
|
* End the meeting on time. Defer or delegate if necessary.
|
|
|
|
* Don't be afraid to end a meeting early.
|
|
|
|
* Don't be afraid to leave a meeting if it isn't useful to you, though consider if your being there is useful to others. Send message saying on why you are leaving the meeting.
|
|
|
|
|
|
|
|
After the meeting
|
|
|
|
* Send recorded outcomes of the meeting to constituents in a timely fashion. |
|
|
|
\ No newline at end of file |