Maintainers

The Traefik codebase has 1,000+ unique committer emails over its lifetime. This page focuses on the people most likely to know a given subsystem today, derived from git log over the last 12 months on master plus the maintainers list at docs/content/contributing/maintainers.md.

Bot accounts (anything ending in [bot]) are filtered out — git history shows essentially zero bot-attributed commits in this repo, but the filter is applied in any case.

Subsystem ownership

Subsystem	Source path	Recent contributors (12 months)
Server core (lifecycle, watcher, router factory, entry points)	pkg/server	mmatur, Romain, Julien Salleyron
Providers	pkg/provider/*	LBF38, Romain, Michael
Middlewares	pkg/middlewares/*	mmatur, Gina A., Kevin Pollet
Observability (logs, metrics, tracing)	pkg/observability/*	mmatur, Michael, shreealt
API and dashboard backend	pkg/api	Romain, Michael, Kevin Pollet
TLS and ACME	pkg/tls, pkg/provider/acme	mmatur, Michael, Kevin Pollet
Reverse proxies	pkg/proxy	mmatur, Romain
Plugins	pkg/plugins	Romain, mmatur, Kevin Pollet
Web UI / dashboard	webui/	Gina A., mmatur, Kevin Pollet

The numbers behind these picks come from git log --since="1 year ago" --format="%an" -- <path> on the default branch — the standard heuristic for "who's been touching this code lately". Names match what appears in commit metadata; if a single contributor shows up under multiple spellings (e.g. Romain vs romain), they are treated as the same person.

How to find the right person

1. Run git log --since="6 months ago" -- <path> for the file you're touching and look at recent commits.
2. Cross-reference against docs/content/contributing/maintainers.md for the canonical maintainers list.
3. Tag the relevant area label (area/<topic>) on your PR — the labels are configured to auto-request reviews from the right people.

Becoming a maintainer

The process is documented in docs/content/contributing/maintainers-guidelines.md (and on the website). The short version: become a sustained contributor with PRs across multiple areas, build trust through reviews, and an existing maintainer will sponsor you.

The repository's README quotes the philosophy directly:

We are strongly promoting a philosophy of openness and sharing, and firmly standing against the elitist closed approach.

What's not on this page

• Per-person commit counts and rankings. Documentation should help you find the right reviewer, not rank contributors.
• Email addresses. The community forum and PR reviews are the recommended communication channels.