Roll call: who's there and emergencies

all folks on the team present

Normal check-in

Went through the normal per person check-in.

Roadmap review (Q4)

postponed to next week

Other discussions

incident response proposal

feedback:

• good to have procedure, nice that we can keep it simple and the complexity is optional
• do we want to document when we need to start the procedure? some incidents are not documented right now... yes.
• unclear exactly what happens, when roles get delegated... current phrasing implies the original worker is the only one who can delegate
• people can bump in and join the team, e.g. "seems like you need someone on comms, i'll start doing that, ok?"
• add examples of past or theoretical incidents to the proposal to clarify the process
• residual command position, once all roles have been delegated, should default to team lead? it's typically the team lead's role to step in those situation, and rotate into that role
• no pager escalation
• define severity
• discomfort at introducing military naming, we can call it incident lead

anarcat will work on improvements to the proposal following the discussion.

Next meeting

Next week, we'll try to work again on the roadmap review.

Metrics of the month

• host count: 99
• number of Apache servers monitored: 33, hits per second: 659
• number of self-hosted nameservers: 6, mail servers: 99
• pending upgrades: 0, reboots: 0
• average load: 3.40, memory available: 4.1 TB/7.2 TB, running processes: 276
• disk free/total: 106.2 TB/231.7 TB
• bytes sent: 564.3 MB/s, received: 382.2 MB/s
• GitLab tickets: 248 tickets including...
• open: 1
• ~Roadmap::Icebox: 126
• ~Roadmap::Future: 43
• ~Needs Information: 3
• ~Roadmap::Backlog: 38
• ~Roadmap::Next: 16
• ~Roadmap::Doing: 15
• ~Needs Review: 6
• (closed: 4227)
• ~Technical Debt: 12 open, 38 closed