| Name | Slack | GitHub | Company | |
|---|---|---|---|---|
| Bartłomiej Płotka | [email protected] | @bwplotka |
@bwplotka | Red Hat |
| Frederic Branczyk | [email protected] | @brancz |
@brancz | Polar Signals |
| Giedrius Statkevičius | [email protected] | @Giedrius Statkevičius |
@GiedriusS | AdForm |
| Kemal Akkoyun | [email protected] | @kakkoyun |
@kakkoyun | Red Hat |
| Lucas Servén Marín | [email protected] | @squat |
@squat | Red Hat |
| Prem Saraswat | [email protected] | @Prem Saraswat |
@prmsrswt | Atlan |
| Marco Pracucci | [email protected] | @pracucci |
@pracucci | Grafana Labs |
| Matthias Loibl | [email protected] | @metalmatze |
@metalmatze | Polar Signals |
| Ben Ye | [email protected] | @yeya24 |
@yeya24 | Red Hat |
We are bunch of people from different companies with various interests and skills. We are from different parts of the world: Germany, Italy, Lithuania, Poland, UK, India and China. We have something in common though: We all share the love for OpenSource, Go, Prometheus, ☕ and Observability topics.
As either Software Developers or SRE (or both!) we've chosen to maintain (mostly in our free time) Thanos, the de facto way to scale awesome Prometheus project.
Feel free to contact us (preferably on Slack) anytime for feedback, questions or 🍻/☕/🍵.
Especially feedback, please share if you have ideas what we can do better!
You can reach us under [email protected] email.
We also have some nice souls that help triaging issues and PRs. See here for details about the role's permission.
Full list of triage persons is displayed below:
| Name | Slack | GitHub |
|---|---|---|
| Adrien Fillon | @Adrien F |
@adrien-f |
| Martin Chodur | @FUSAKLA |
@fusakla |
| Michael Dai | @jojohappy |
@jojohappy |
| Xiang Dai | @daixiang0 |
@daixiang0 |
Please reach any of the maintainer on slack or email if you want to help as well.
To improve navigating through issues and PRs we introduce various labels. Part of triaging process for Triage and Maintainers
is to adjust those labels if needed manual. The Prow system can automate a portion of this in future.
The main labels are:
component: * and website/docs labels indicate an area related to the change or issue.
difficulty: easy|medium|hard labels indicate the approximate difficulty for the change (in terms of reviewing) or the issue (in terms of addressing).
This helps to also estimate how long it can potentially take to review the PR or address the issue with this label.
help wanted label should be present if the issue is not really assigned (or the PR has to be reviewed) and we are looking for the volunteers (:
good first issue is similar as help wanted but present only on the issues when it's newcomer friendly. This means:
- issue has a clear acceptance criteria
- issue has limited scope
- issue is well described
priority: P0 should be assigned for the changes or the issues that are critical and should be addressed in first order.
Github shows some basic states, but sometimes PR is stale due to requested changes, but it's not clear from first glance.
That's why state: changes-requested is helpful on those.
Self explanatory ones:
questionlabel indicates an issue with question.proposallabel indicates an issue / PR with official proposal.duplicatefeature request / improvementbugandbugfix
Maintainers of bucket storage clients are available here
Any contributor that shows effort and willingness in maintaining Thanos repository can join maintainer team.
Open Source is all about the trust, which is the key factor in decision to add write permissions.
In time we plan to set up maintainers team that will be organization independent. Reach us if you have any questions or want to join maintainer team.
Fabian Reinartz @fabxc and Bartłomiej Płotka @bwplotka
Dominic Green Povilas Versockas