From: Seth Forshee <sforshee@kernel.org>
To: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Stepping down as wireless-regdb maintainer
Date: Wed, 3 May 2023 14:34:37 -0500 [thread overview]
Message-ID: <ZFK3TQWDQMoH9obk@ubuntu-x1> (raw)
I started maintaining wireless-regdb over 8 years ago at a time when my
job responsibilities included investigating and working to fix reports
of wireless bugs in Linux. Not long after that my responsibilities
started shifting away from wireless work, and for the past several years
I've had no involvement in anything related to wireless beyond fairly
passive maintenance of wireless-regdb. Even in that role it's recently
been difficult to find time to validate proposed changes against the
source documents, which has frequently lead to slow response times.
As a result, I've decided that it is time for me to move on from
maintaining wireless-regdb. I won't step away immediately, but I plan to
stop applying patches and doing new releases around Sep 1 of this year.
If anyone is interested in taking over maintenance of this project,
please reach out and I'll be happy to discuss.
Thanks,
Seth
reply other threads:[~2023-05-03 19:34 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=ZFK3TQWDQMoH9obk@ubuntu-x1 \
--to=sforshee@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.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).