From: MeganerdNL <MeganerdNL@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fail2ban: change maintainer
Date: Fri, 07 Jul 2023 15:38:20 +0200 [thread overview]
Message-ID: <20230707133820.CZBewIrW_7ccxE37QZV9UCtCH5nhsZ5QVH2IIdar6Qo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44894@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
New comment by MeganerdNL on void-packages repository
https://github.com/void-linux/void-packages/pull/44894#issuecomment-1625430365
Comment:
> We generally don't want to change maintainer ship for packages to people who are really new, there has a been a history of one-of maintainers adopting packages and then not contributing anymore.
I really do understand that!
You will have to take my word for it, but that's hard on the internet :).
I have Void installed on several machines now (1 in production but I will add 3 more in the near future). I'm coming from Debian and I recently searched for a rolling release without systemd and with a greater userbase than Artix (which I use for my laptop) and that let me to Void and I'm really enthusiastic about it since. Great documentation too. Fail2ban is a must-have on servers imho, but there was an old version here, so I PR'd for a new one a few days ago (merged) and that went well and it learned me how the flow is in void-packages as a bonus.
So a little introduction that can help you decide. I'm also happy to update fail2ban without being the official maintainer for now and than you can decide later. The former maintainer didn't update it in a long time (so he said himself), so that is the alternative. Cheers.
next prev parent reply other threads:[~2023-07-07 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 6:26 [PR PATCH] " MeganerdNL
2023-07-07 6:49 ` necrophcodr
2023-07-07 13:00 ` Duncaen
2023-07-07 13:38 ` MeganerdNL [this message]
2023-07-07 16:14 ` necrophcodr
2023-07-07 16:32 ` Duncaen
2023-07-07 19:44 ` necrophcodr
2023-07-07 19:45 ` necrophcodr
2023-07-09 7:48 ` classabbyamp
2023-07-09 8:06 ` [PR PATCH] [Closed]: " MeganerdNL
2023-07-09 8:06 ` [PR PATCH] [Updated] " MeganerdNL
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=20230707133820.CZBewIrW_7ccxE37QZV9UCtCH5nhsZ5QVH2IIdar6Qo@z \
--to=meganerdnl@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).