Version 63 (modified by nickm, 3 years ago) (diff)


Network Team


Welcome to the Network Team page. The Network Team is a group of Tor people who are working on the backend: the program called Tor, the pluggable transports, the bridge distribution, the network simulators, the scripts that supports directory authorities, hidden services etc.

There are currently three other teams in Tor: the Metrics Team a group of Tor people who care about measuring and analyzing things in the public Tor network, the Applications Team produces usable applications for end users, and the Community Team focuses on the non-technical aspects of growing a healthy Tor community.


The people who are part of this team is anyone working on the projects described above. We're not listing names here to keep the team open to everyone. You're on the team if you're participating in discussions and development, and you're not part of the team anymore if you decide you want to move on (which we hope won't happen).


Our synchronous medium of communication is IRC meetings that happen every other Mondays and Wednesdays in #tor-dev on OFTC. For the latest times for these meetings, see:

If you want to reach someone from the team between these meetings to ask a development-related question, just go to #tor-dev, and somebody from the team might either be around or appear later and get back to you.

Our asynchronous medium of communication is the tor-dev@ mailing list. This list is public in the sense that anyone can subscribe, send emails and read archives. Feel free to subscribe and just listen if you want, and feel free to post if you have a question that you think is on topic.


Information on how we file ticket: org/process/TorOnTrac

We use the keyword TorCoreTeamYYYYMM to mark the tickets we plan to work for the month.

Developer Git Repository

Often time in tickets, you'll see something like: See branch ticket20568_030_01.

That branch will usually be in the developer personal git repository. Here is a list of the common ones from the team ordered by their trac nickname:


Network team is responsible for Core Tor releases, we aim to have a new release every 6 months.

Please check our Release Guidelines for more detailed information on the process.


Past releases

Release Maintainer(s) Merge Window Start Declared Freeze Real Freeze Stable Ready End Of Life
0.2.4 nickm ... ... ... Dec 11, 2013 eol?
0.2.5 nickm ... ... ... Dec 24, 2014 eol?
0.2.6 nickm ... ... ... Mar 24, 2015 eol?
0.2.7 nickm ... ... ... Nov 20, 2015 eol?
0.2.8 nickm ... ... ... Aug 2, 2016 eol?

Experimental dates. May change over time.

Release Maintainer(s) Merge Window Start Feature Freeze Stable Ready
0.2.9 nickm ... Oct 17th, 2016 Nov 17th, 2016
0.3.0 nickm Oct 24th, 2016 Jan 24th, 2017 Apr 24th, 2017
0.3.1 nickm Jan 31st, 2017 May 1st, 2017 Aug 1st, 2017

Team rotation calendars

Weekly bug triage rotation


Calendar - October:

Week who:
10/03/16 - 10/07/16 NULL
10/10/16 - 10/14/16 asn
10/17/16 - 10/21/16 dgoulet
10/24/16 - 10/28/16 asn

Calendar - November:

Week Who
10/31/16 - 11/04/16
11/07/16 - 11/11/16 dgoulet
11/14/16 - 11/18/16 isis
11/21/16 - 11/25/16 dgoulet
11/28/16 - 12/02/16 asn

Calendar - December:

Week Who
12/05/16 - 12/09/16 dgoulet
12/12/16 - 12/16/16 nickm
12/19/16 - 12/23/16 nickm
(last week of December is holiday)

Current Team Discussions



Team Roadmap
Core Tor
Onion Services

Useful ticket queries

Here are the all of the tickets we're planning to fix by version grouped by sponsor. If you're looking for something to take on in the upcoming month, this is a good query to use.

Here are the open tickets for this month, grouped by owner. If you're looking for something to hack today, here's what you've said you'd do. If you're looking for something unclaimed, look for the ones with no owner.

Here are needs_(review|revision) tickets for this month, grouped by reviewer. If you're looking for something to review, here's what you said you'd review. If you're looking for something unclaimed, look for the ones with no reviewer.

Here are the 029-proposed tickets that somebody has marked as "possibly suitable for 0.2.9". Let's triage these in or out.

These tickets were in (or close to) needs_review. Nick will not review any other (non-critical) tickets until all of these have had reviews.:

November 2016

Ticket Summary Component Status Owner Reviewer Priority Severity Milestone Modified
No tickets found

Attachments (2)