Version 7 (modified by mikeperry, 7 months ago) (diff)



Tor has all-hands meetings roughly twice a year. These meetings are typically broken into three parts: team meetings (staff and invited volunteers only), community meetings (staff and invited community members), and public days (open to everyone).

This page serves to provide meeting templates primarily for the team meetings, with some overlap for community meetings. It is intended to describe the types of meetings all teams should have, as well as additional meetings that individual teams tend to have.

Every meeting has three components: Goals, Outputs, and Stakeholders. Meetings can also have additional explicit non-goals, and may also list critical bottlenecks -- people who need to be there, but tend to be in high demand for other concurrent meetings.

Meeting Templates

Meeting Name Description
Duration 20 minutes, 60 minutes, 90 minutes
Description What is this meeting about? How does it usually run?
Goal Describe the meeting's goal
Non-Goals Describe ways this meeting type can get derailed or distracted by off-topic material (optional)
Outputs What notes/diagrams/documents/tickets should the meeting produce?
Stakeholders Who should attend for the meeting to reach a conclusion?
Critical Bottlenecks Who do we need to attend for a decision to be made, but is at risk of having a conflict? (optional)

Meetings that every team has every 6 months

Team roadmap Plan and document what the team wants to accomplish in the next 6 months
Duration 60 minutes
Description For development-oriented teams, this is the creation of milestones and a schedule. For non-development teams (and Agile teams), this is a story or narrative (or set of narratives) of what Tor should look like in 6 months as a result of your work.
Goal Produce some kind of plan for the next 6 months, with specific people committing to roles and/or specific action items.
Outputs For development teams, this is usually a schedule of post-it notes that gets transferred to the wiki and trac tags, usually with difficulty estimates and people+sponsor tags. For non-development or agile teams, this can be a written narrative of a plan, with specific action items and/or roles needed to achieve that plan.
Stakeholders Team members
Critical Bottlenecks Isabela

Team retrospective Review the roadmap from the last 6 months, with an eye towards process improvements
Duration 60 minutes
Description For development-oriented teams, review your roadmap and development activities from last time. What did you achieve? What didn't you achieve? Why? Are there any processes, estimating, or scheduling improvements that you can make to improve your ability to execute? For non-development teams (and Agile teams), how does your narrative match reality today. Is there anything that you should try to do differently this time around? See this list of retrospective meeting formats for ideas.
Goal Evaluate and improve workflow and planning processes.
Outputs For development teams, this is usually changes to development process, meetings, trac usage, etc. For non-development or agile teams, the outputs will depend on your workflow, etc.
Stakeholders Team members
Critical Bottlenecks Isabela?

Tor Network Team Meetings

Tor Browser Team Meetings