[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-project] more minutes from the sysadmin meeting: 2025 roadmap



Hi!

So TPA had another meeting, and this time, we've made a roadmap! For
your convenience, a cleaned up copy is in:

https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2025

Otherwise here are our minutes:

# Roll call: who's there and emergencies

anarcat, groente, lelutin, zen

# Dashboard review

## Normal per-user check-in

* https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&assignee_username=anarcat
* https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&assignee_username=groente
* https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&assignee_username=lavamind
* https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&assignee_username=lelutin
* https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&assignee_username=zen

# Tails merge 2025 roadmap

In the previous meeting, we found consensus on a general plan. Now we
nailed down the things we actually do in 2025 in the [Tails merge
timeline][].

 [Tails merge timeline]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-73-tails-infra-merge-roadmap#timeline

We made those changes:

- move monitoring up to 2025: retire tails' icinga!
- start thinking about authentication in 2025, start brainstorming about next steps

Otherwise adopt the timeline as proposed for 2025.

# 2025 roadmap brainstorm

Throw ideas in the air and see what sticks about what we're going to do
in 2025. Following, of course, priorities established in the Tails
roadmap.

## Tails: What we promised OTF

For Tails:

- [B.2: Keep infrastructure up-to-date and secure][]

 [B.2: Keep infrastructure up-to-date and secure]: https://nc.torproject.net/s/eAa88JwNAxL5AZd?path=%2FGrants%2FOTF%2F2024%20-%20FOSS%20Sustainability%20Fund%20%5BTails%5D

> As in Year 1, this will involve the day-to-day work needed to keep the
> infrastructure we use to develop and distribute Tails up-to-date. This
> includes our public website, our development servers for automatic builds
> and tests, the translation platform used by volunteers to translate Tails,
> the repositories used for our custom Debian packages and reproducible
> builds, etc. Progressively over Year 2 of this contract with OTF, as Tails
> integrates within the Tor Project, our sysadmins will also start maintaining
> non-Tails-specific infrastructure and integrate internal services offered by
> Tails within Tor’s sysadmin workflow

TL;DR: maintenance work. Very few hours allocated for sysadmin work in
that project.

## TPA

We made a roadmap based on a brain dump from anarcat in
[tpo/tpa/team#41821][]:

 [tpo/tpa/team#41821]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41821

- Web things already scheduled this year, postponed to 2025
  - Improve websites for mobile
  - Create a plan for migrating the gitlab wikis to something else
  - Improve web review workflows, reuse the donate-review machinery
    for other websites (new)
- Make a plan for SVN, consider keeping it
- MinIO in production, moving GitLab artifacts, and collector to
  object storage, also for network-health team (contact @hiro) (Q1 2025)
- [Prometheus phase B][]: inhibitions, self-monitoring, merge the two
  servers, authentication fixes and (new) autonomous delivery
- Debian trixie upgrades during freeze
- Puppet CI (see also merge with Tails below)
- Possibly take over USAGM s145 from @rhatto if he gets funded elsewhere
- Development environment for anti-censorship team (contact @meskio), AKA
  "rdsys containers" ([tpo/tpa/team#41769][])
- Possibly more hardware resources for apps team (contact @morganava)
- Tails 2025 merge roadmap, from the [Tails merge timeline][]
  - Puppet repos and server:
    - [Upgrade Tor's Puppet Server to Puppet 7][]
    - Upgrade and converge Puppet modules
    - Implement commit signing
    - EYAML (keep)
    - Puppet server (merge)
  - Bitcoin (retire)
  - LimeSuvey (merge)
  - Website (merge)
  - Monitoring (migrate)
  - Come up with a plan for authentication

 [Upgrade Tor's Puppet Server to Puppet 7]: tpo/tpa/team#41819
 [tpo/tpa/team#41769]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41769
 [Prometheus phase B]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/14

Removed items:

- Evaluate replacement of lektor and create a clear plan for
  migration: performance issues are being resolved, and we're building
  a new lektor site (download.tpo!), so we propose to keep Lektor for
  the forseeable future
- [TPA-RFC-33-C][], high availability moved to later, we moved
  autononmous delivery to Phase B
  
 [TPA-RFC-33-C]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/15#tab-issues

-- 
Antoine Beaupré
torproject.org system administration

Attachment: signature.asc
Description: PGP signature

_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx