[tor-project] minutes from the sysadmin meeting

Time for your monthly dose of sysadmin minutes!

# Roll call: who's there and emergencies

all team present, no emergencies

## Normal per-user check-in

we went through our normal check-in

* Issue Boards · Development Board · Boards · The Tor Project · GitLab
* Issue Boards · Development Board · Boards · The Tor Project · GitLab
* Issue Boards · Development Board · Boards · The Tor Project · GitLab
* Issue Boards · Development Board · Boards · The Tor Project · GitLab
* Issue Boards · Development Board · Boards · The Tor Project · GitLab

## General dashboards

We noticed a lot of untriaged issues in the web boards, and @lelutin
is a little overloaded, so we picked issues off his board.

* Issue Boards · Development · Boards · The Tor Project / TPA / TPA team · GitLab
* Issue Boards · Iterations YEC · Boards · Web · GitLab
* Issue Boards · Development · Boards · TPA · GitLab

# Roadmap review

anarcat mentioned that we need to review Q3 and plan Q4 in the next
monthly meeting.

keep in mind that what we don't do from the 2025 roadmap in q4 will
get postponed to 2026, and that has an influence on the tails merge
roadmap!

we would really like to finish the puppet merge this year, at least.

we hope to start brainstorming a proper 2026 roadmap in october.

# Other discussions

## state of the onion

do we do it? what do we want to present?

we haven't presented for the last two years, didn't seem to cause an
issue for the grand public, no one asked us for it...

maybe we could do a talk to TPI/TPO directly instead of at the SOTO?

But then again, not talking contributes to an invisibilisation of our
work... It's important for the world to know that developers need help
to do their work and sysadmins are important: this organization
wouldn't *immediately* collapse if we would go away, but it would
certainly collapse *soon*. It's also important for funders to
understand (and therefore fund) our work!

Ideas of things to talk about:

- roadmap review? we've done a lot of work this year, lots of things
  we could talk about
- asncounter?
- interactions with upstreams (debian, puppet, gitlab, etc)
- people like anecdotes: wrong gitlab shrink? mailman3 memory issues
  and fix

anarcat will try to answer the form and talk with pavel for some help
on next steps.

# Next meeting

as usual, first monday of october.

# Metrics of the month

* host count: 99
* number of Apache servers monitored: 33, hits per second: 696
* number of self-hosted nameservers: 6, mail servers: 99
* pending upgrades: 0, reboots: 99
* average load: 1.62, memory available: 4.6 TB/7.2 TB, running processes: 240
* disk free/total: 88.7 TB/204.3 TB
* bytes sent: 514.4 MB/s, received: 334.0 MB/s
* [GitLab tickets]: 244 tickets including...
   * open: 0
   * ~Roadmap::Icebox: 130
   * ~Roadmap::Future: 44
   * ~Needs Information: 3
   * ~Roadmap::Backlog: 38
   * ~Roadmap::Next: 12
   * ~Roadmap::Doing: 15
   * ~Needs Review: 3
   * (closed: 4198)
   * [~Technical Debt]: 12

[Gitlab tickets]: Issue Boards · Development · Boards · The Tor Project / TPA / TPA team · GitLab
[~Technical Debt]: Issues · TPA · GitLab

Upgrade prediction graph lives at trixie · Wiki · The Tor Project / TPA / TPA team · GitLab

We've past our estimated finish date for the trixie upgrades
(2025-08-06), which means we've slowed down quite a bit in our upgrade
batches. But we're close to completion! We're still hoping to finish
in 2025, but it's possible this drags into 2026.

···

--
Antoine Beaupré
torproject.org system administration
_______________________________________________
tor-project mailing list -- tor-project@lists.torproject.org
To unsubscribe send an email to tor-project-leave@lists.torproject.org