Skip to content
T

team

Other resources

Process

Contact

To get in touch with the entire Tails Team, 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.

You can encrypt your email with our OpenPGP key (details).

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)

Past priorities

Roadmap

This is the big picture. For details about what's happening on the short term, see the board for the upcoming milestone.

Projects

Project 165

2025 Q2

  • Frontdesk (@intrigeri)
  • Upgrade to Debian 13 and release 7.0: do the bulk of the porting work (P165) (@intrigeri, @anonym)
  • Help get grant proposals for 2026 ready (tails/tails#20767) (driven by @intrigeri, may need help from others)
  • Converge workflows and tooling towards Tor's (@intrigeri)
  • Improve website navigation (tails#20766) (@sajolida)
    • 1. General navigation
    • 2. Accessibility issues
  • Document why we are using /home as the homepage of Tor Browser in Tails (tails#20822) as a starting point to figure out how to integrate Tor's calls for donations in Tails (@sajolida)
  • Public report about security audit (tails/summit#186) (@sajolida)
  • Start integrating our doc for contributors with Tor's, identifying other problems in this section along the way (tails#20768) (@sajolida)
  • Recurring P165 (OTF FOSS Sustainability Fund) work
    • A.2 Prototype and collaborate on using Arti (@boyska)
      • Redesign and draft our run-in-netns for Arti (tails#20811)
      • Monitor the work on Arti's RPC and make sure our needs are met (tails#20508)
    • B.1 Release management and smaller OS migrations
    • C.1 Fix long-lasting usability issues
    • C.2 Act on feedback received by email and in-app tool (candidates: tails#20785 (closed))
    • D.1 Make the Tails development process more efficient (test suite) (@anonym):
      • Fix most frequent sources of failures:
        • tails#20297 "The proxy server is refusing connections" after Tor has bootstrapped
        • tails#20890 Test suite: step "available upgrades have been checked" fails a lot
      • tails#18215 Upgrade Chutney (2025 edition)
      • Other potential candidates:
        • tails#20851 Test suite: make the remote shell server handle aborted client commands
        • tails#20570 Test suite: improve Chutney network bootstrap with launch phases
  • Metrics (tails#19476): inform the Tor-wide policy discussions about metrics with our own needs & draft design (@boyska)

Boards:

2025 Q3

  • Frontdesk (@intrigeri)
  • Upgrade to Debian 13 and release 7.0 (P165):
    • Coordination (@boyska)
    • Get it ready (including beta/RC)
    • Process feedback
    • Fix blockers for 7.0 stable
    • Doc upgrades (@sajolida)
  • KTLO
  • Converge workflows and tooling towards Tor's
  • Talk with sysadmins about the future of Jenkins (tails#20774) (@intrigeri)
  • Recurring P165 (OTF FOSS Sustainability Fund) work

2025 Q4

  • Frontdesk
  • Upgrade to Debian 13 and release 7.0 (P165):
    • Coordination (@boyska)
    • Release
    • Post-release feedback & fixes
  • KTLO
  • Converge workflows and tooling towards Tor's
  • Improve website onboarding (tails#20777) (@sajolida)
  • Recurring P165 (OTF FOSS Sustainability Fund) work — until the end of November
    • A.2 Prototype and collaborate on using Arti
    • B.1 Release management and smaller OS migrations
    • C.1 Fix long-lasting usability issues
    • C.2 Act on feedback received by email and in-app tool (candidates: tails#20785 (closed))
    • D.1 Make the Tails development process more efficient (test suite) (@anonym)