Team

Meta for projects management and general information in the wiki.

Applications Team

About us

Welcome to the Applications Team wiki page. The Applications Team is a group of Tor people who are working on different user facing products like Tor Browser.

People

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. This team also has the participation of user support and localization team members and members of other teams that give support to the Application team efforts.

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).

Communication

Just go to #tor-dev, and somebody from the team might either be around or appear later and get back to you. You can use the tbb-team alias for getting the attention of someone on the team (many of us have added this specific keyword so it highlights us).

We use IRC for our meetings, we meet on the OFTC network. We use a meeting pad to take notes each meeting.

Team meeting	UTC	CET
Primary team meeting	Monday 15:00	Monday 16:00

The Applications team's asynchronous medium of communication are the tbb-dev@ mailing list and tor-dev@ mailing list, depending on which is more applicable. These lists are 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.

Roadmapping goals

We keep the board for the team up to date but you can look at our broad goals next.

The following were our goals for 2020

Migrate Tor Browser for Android onto Fenix and away from Fennec.
Improve Tor Browser experience for human rights defenders under censorship.

The following are our "reach" goals for 2021

~~Multi-locale packages~~
Go/Rust/Java dependency resolution
~~Convert torbutton into tor-browser patches~~
~~F-Droid presence for Tor Browser for Android~~
~~General webcompat improvements~~
~~Improve fingerprinting defenses~~
~~Improve sandboxing~~
V2 Deprecation UI/UX
About:torconnect
Desktop ESR Transition - starts in July
Enable HTTPS-Only Mode
Integrate libhttps-everywhere-core (replacing https-everywhere webextension) - tor-browser#40458
Go/Rust/Java dependency resolution: how to resolve dependencies ahead of time.
Improve bridge selection in tor browser

Roadmap (June 2021 - September 2021)

suggest bridges based on location (Sponsor 30)
TB bootstrap flow (Sponsor 30)
Firefox 91esr transition for Tor Browser'
experiment with active resistance (Sponsor 103)

Roadmap (November 2020 - June 2021)

Sponsor 58
Move nightly builds into TPO infrastructure
Stabilize Android Rapid Release processes
Sponsor 30
Move Linux onto Rapid Release
Stabilize/Bug-fix Android Tor Browser features
Watershed update
RAPPOR
Seeding HSTS cache
Sponsor 103

Roadmap (June 2021 - October 2021)

V2 Deprecation UI/UX.
About:torconnect
Desktop ESR Transition.
Enable HTTPS-Only Mode.
Integrate libhttps-everywhere-core (replacing https-everywhere webextension) - tor-browser#40458
Go/Rust/Java dependency resolution: how to resolve dependencies ahead of time.
Improve bridge selection in tor browser.

Active Sponsor Projects

Sponsor 103 - Collaborative Resistance to Web Surveillance
Sponsor 30 - Empowering Communities in the Global South to Bypass Censorship

Triaging Tickets

We are triaging tickets once a week .

The criteria to include tickets in a specific milestone are:

bugs that must be fixed (include security, regression or crash bugs)
tickets that have been road-mapped before because they are part of a sponsored project
tickets that are very fast to fix (around 1 hour)

The process we are using for triaging tickets is:

filter out all tickets not in the milestone sorted by creation date
for each new ticket:

add related labels (for example add an UX label to tickets that needs UX/UI help and the same for other teams)
if it fits the criteria written above then add it to the right milestone

Becoming a volunteer

The best way to get involved is to visit our weekly IRC meeting (see above). Tell us your background and interests and we will find a project for your to get started.

GitLab