From: Lorenz Schori <lo@znerol.ch>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] Prometheus PVE exporter is looking for a co-maintainer
Date: Fri, 3 Sep 2021 11:47:16 +0200 [thread overview]
Message-ID: <20210903114702.23c561c3@bonemachine> (raw)
Hi,
Prometheus PVE Exporter has developed into a project used by people and
organizations around the globe. It is a honor for me to contribute a
small piece of software which makes the lives easier for fellow
sysadmins and devops engineers.
At this point I can easily keep up with resolving issues and reviewing
/ merging PRs. In the long run it will for sure be beneficial for the
project if more than one person is capable of maintaining the code base
and rolling releases.
Thus, I am looking for some reliable creature who is willing to assume
responsibility for the maintenance of this project and for keeping its
users happy. If you are actively using Prometheus PVE Exporter, if you
did contribute to this project in the past and if you like to step up
as a maintainer, then please ping me.
https://github.com/prometheus-pve/prometheus-pve-exporter/issues/84
Cheers,
Lorenz
reply other threads:[~2021-09-03 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210903114702.23c561c3@bonemachine \
--to=lo@znerol.ch \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox