Skip to content

team

About us

Mission

Our mission is to empower people worldwide by giving out an operating system that protects against surveillance and censorship.

If you want to help, see https://tails.net/contribute/ :)

Team members

name role email Matrix/IRC
intrigeri Tails Team Lead intrigeri at torproject dot org intrigeri
anonym Tails Developer anonym at torproject dot org anonym
boyska Tails Developer boyska at torproject dot org boyska

Contact

If you already know which individual team member is the best placed to have the conversation you need, contact them directly. In doubt, contact the Team Lead.

Email

If you need to get in touch with the entire Tails Team at once, you can:

  • write to the foundations@tails.net Schleuder mailing list
  • mention @tails-team on GitLab: GitLab will send an email notification about it to every member of the Tails Team, and add it to their To-Do list.

Text-based chat

See https://tails.net/contribute/chat/.

How our team & work connect to the rest of Tor

The Tails product is built on top of other Tor products (among other things), so we collaborate regularly with the teams that build these products:

We constantly work with the UX Team, that helps us understand the needs of our users and make the Tails user experience a better fit for their needs.

Like all other teams at Tor, we also interface with internal structures and support teams, in particular TPA given our strong dependency on systems infrastructure.

We interact less frequently with other teams but we do appreciate their work!

Process

Priorities

Priorities for 2025

MUST

  • Remediate vulnerabilities identified by security audit and pick low-hanging fruits to avoid repeating past mistakes
  • Converge workflows and tooling towards Tor's — MUST bundle
    • Hand over ticket gardening role to intrigeri (tails#20510)
    • Revisit Tails Team Lead / Project Manager arrangements for FY 2025-2026 (tails#20700 (closed))
  • KTLO, including:
    • Release Tails 7.0 based on Debian 13 (Trixie)
    • Upgrade Tor Browser to new ESR
    • Upgrade Thunderbird to new ESR
    • Prototype and collaborate on using Arti
  • Fix long-lasting usability issues (P165 C.1)
    • We'll determine which ones when we prioritize UX Debt issues.
  • Act on feedback received by email and in-app tool, still with a focus on identifying high-impact work (P165 C.2)
    • We'll determine in Q1 if this work should have a particular focus in 2025 (in 2024 it was Persistent Storage & partitioning robustness).
  • Improve test suite robustness, focusing on time sinks (P165 D.1)
  • Research alternatives to Etcher for Windows; then, if there's a good enough candidate, switch to it
    • Goal: Improve the privacy of the Tails installation process
  • Improve website navigation

SHOULD

MAY

  • Finish the initial exploration and prototyping of the automatic verification of Tails downloads
  • Define 5-years strategy for the Tails product & team in the Tor organization
  • Converge workflows and tooling towards Tor's - MAY bundle
    • Migrate from Schleuder to Mailman
    • Migrate from XMPP to IRC (unless we build confidence that TPI will migrate away from IRC by the end of 2026)

Priorities for 2026

TBD: tails/tails#20795+

Past priorities

Roadmap

This is the big picture. For details about what's happening on the short term, see the board and filter with the current milestone.

Projects

Project 165

2025 Q4

Boards:

Other resources