[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-project] intrigeri's report, February 2025
- To: tor-project@xxxxxxxxxxxxxxxxxxxx
- Subject: [tor-project] intrigeri's report, February 2025
- From: intrigeri via tor-project <tor-project@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 03 Mar 2025 15:04:04 +0100
- In-reply-to: <notmuch-sha1-556faef4fdf655a761799ab48436a9bf9f3a8e17>
- List-id: "Moderated discussion list for tor contributors." <tor-project.lists.torproject.org>
- References: <8734mgybn0.fsf@manticora> <87zfnmc3qd.fsf@manticora>
- Reply-to: intrigeri <intrigeri@xxxxxxxxxxxxxx>
Hi,
User-visible
============
- I've prepared the Tails 6.12 release.
- I've reviewed and supported the work of my team-mates on a number
of high priority user-visible improvements.
User-invisible
==============
Apart of the usual amount of KTLO work:
- I have upgraded AppArmor to 4.1 in Debian in time for the freeze
of Trixie.
- We've met with a number of stakeholders to figure out the strategy
for Tails comms this year, and how we're going to transition the
existing Tails comms tools & processes now that we're part of Tor.
- I've met with Freedom of the Press Foundation staff in order to
support their efforts to add Dangerzone to Debian, in a way that
will make it easier to use this tool in Tails.
- The Tails Team had a post-mortem of our last security audit and
identified a few low-hanging fruits that we can pick in order to
avoid introducing similar vulnerabilities again in the future.
Team lead
=========
- We've finalized our priorities for 2025:
https://gitlab.tails.boum.org/tails/team/-/wikis/home#priorities
- I have uplifted a few ideas from my team to the operations team.
Accounting & Fundraising
========================
- I have helped with the process of closing Tails' donation
infrastructure and merging it into Tor's.
Cheers,
--
intrigeri
_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx