Meta for non-specific project tickets, projects management and general information in the wiki.
Welcome to the Network Team page. The Network Team is a group of Tor people who are working on Tor back-end: the program called tor, the network simulators, the scripts that supports directory authorities, onion services, etc. Basically, everything that sends and receives bytes from the network. It used to maintain the pluggable transports and the bridge distribution but now we have the anti-censorship team doing it.
One of the reasons we are not listing the names of the team members here is because we want 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).
Excited about joining the team? Here is more information on how to get started.
|Primary team meeting
|Monday 17:00||Monday 19:00||Monday 13:00||Monday 10:00|
|Tuesday 20:00||Tuesday 22:00||Tuesday 16:00||Tuesday 13:00|
strikethrough means that most people in that timezone are asleep.)
The boldfaced time for a meeting is canonical in its time zone; the other times are computed and might not be correct for a given location depending on factors like daylight saving time. The primary meeting will track US daylight saving time.
If you want to participate, try to show up to the team meeting or patch party.
Either one should be fine, though the primary meeting will be more attended.
Or just stop by the
#tor-dev IRC channel and see who is around!
Also note that these meeting times are not permanent. We sometimes need to reconfigure them from time to time as developers join, as people's schedules change, and as the global daylight savings slouches across the face of the earth. See the tor-dev mailing list for updates.
For other type of meetings, see:
How we work
Besides meeting every week on IRC for status update and team discussions, our team also uses the following mechanisms to organize our work:
- Core Tor Releases: Here is more information about tor release schedules, guidelines for release planning, and ideas of how we can improve this process.
- Filing a ticket for Core Tor.
- Ticket Triage.
How to find us
If you want to reach someone from the team between these meetings to ask a development-related question, just go to #tor-dev IRC channel, 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.
Becoming a volunteer
Thanks for volunteering with us! This part of our wiki is a collection of information we believe might be useful for you who wants to help us develop our tools.
You could start by submitting a patch! Patches can help you learn our code and how our team work.
Tips on finding a patch to work on
Have a look at the First Contribution in Team label on gitlab; it has things that we thought, at some point, would be a good place to begin.
Tips on finding your way around our code
For the past couple years we spent great amount of our time documenting our code to help people understand it. Here are some links for documentation that will help you get started with our code!
The HACKING/ folder has helpful information about what you need to know to hack on Tor!
- First, read GettingStarted.md to learn how to get a start in Tor development.
- If you've decided to write a patch, CodingStandards.txt will give you a bunch of information about how we structure our code.
- It's important to get code right! Reading WritingTests.md will tell you how to write and run tests in the Tor codebase.
- There are a bunch of other programs we use to help maintain and develop the codebase: HelpfulTools.md can tell you how to use them with Tor.
- If it's your job to put out Tor releases, see ReleasingTor.md so that you don't miss any steps!
- A very important part of our development is code review, if you would like to collaborate with this part or want to sharp your skills in this front, check HowToReview.md.
We use doxygen to generate documentation in html out of our comments on the code. We keep an up-to-date version of the generated documentation online at https://src-ref.docs.torproject.org.
This documentation should cover the overall code structure, data structures, and individual functions. It's a work in progress, but we hope it'll be useful to you.
More on Network Team
🛠 ⚠These links may be outdated.
—nickm, 14 August 2020.
- Team meeting at Tor Brussels Meeting 2019
- Team meeting at Tor Mexico Meeting 2018
- Team meeting at Tor Amsterdam Meeting 2017
- Team meeting at Tor Valencia Meeting 2016
- Team meeting at Tor Berlin Meeting 2015.
Processes and Policies
- Process for deciding what our team policies and processes are.
- Merge Policy.
- Committer Policy.
- Security issue policy
- Supported platforms
- (none right now)
Active Sponsors and Contracts
⚠ 🚧 🔨These lists are fairly outdated.
—nickm, 14 August 2020
The projects from sponsors/contracts that are making this work possible are:
- RACE (Resilient Anonymous Communication for Everyone)
- Empowering Communities in the Global South to Bypass Censorship
- Improving the Tor network’s IPv6 support
- Walking Onions Specification
- Bug Smash Fund Description -> Bug Smash Fund Tickets
- security fixes for medium/high severity bugs [No sponsor]
- Regular releases [no sponsor] - Nick with help from Team
- sbws - Alex [No sponsor for Network Team, but sponsored for Juga] (support from Georg/GeKo )
- IPv6 Support [S55] - Nick, David
- Walking Onions specs [S69] - Nick
- Supporting S30 and S28 (anticensorship) work - Alex
- HS DoS defenses [No sponsor, yet?] - George & David (with a little Nick?)
- Library size reduction [No sponsor] - Alex & David (with a little Nick?)
- Google Summer of Code & Outreachy - Nickm, Alex
Other priorities (everybody):
- community handling:
- relay operators
- answering email lists (tor-dev@, tor-relays@)
- do support on irc? (#tor-dev, #tor, etc.)
- fixing bugs for each release
- release blockers
- what else does other teams ask us for?
- liaison with network health team (usually 1-2 hours a week for dgoulet)
- Fixing bugs for android and iOS for the guardian project [see #33522 and #33837 for ios issues]
- ongoing tech-debt reduction
- Fixing windows bugs (ahf / ... others?):
- [UTF-8/16 names in filepaths makes Tor unable to start: #10416]
- Issues with mmap on some platform
- issues with mmap leading to relays spinning on consdiffcache [#24857 #24857]
- condition variable issue with 100% cpu [#30187 #30187]
- Windows DLL load order (possibly a Tor Browser packaging bug) reproducible in CI [#33702, #33643]
- Writing more grant proposals
- Miscelaneous onion service tasks that require our attention
- Onionbalance. Standardizing Onion-Location with the IETF. HTTPS-E
- Ricochet Refresh support
- Gitlab transition stuff for network-team related projects (ahf / gaba):
- Code base movements: chutney, tor.git, fallback-scripts.git on Github and git.torproject.org, torsocks, trunnel
- Code base movements (archive?): torflow, pytorctl, leekspin (+ dependencies), rpm-packaging
- DirAuth and sbws to network health, TorDNSEL to metrics