From: Seth Forshee <sforshee@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2023-09-01
Date: Mon, 30 Oct 2023 15:39:06 -0500 [thread overview]
Message-ID: <ZUAUahZakEvOXpip@do-x1extreme> (raw)
In-Reply-To: <CAGb2v657baNMPKU3QADijx7hZa=GUcSv2LEDdn6N=QQaFX8r-g@mail.gmail.com>
On Tue, Oct 24, 2023 at 02:23:26PM +0800, Chen-Yu Tsai wrote:
> I'd like to take up maintainership.
Thanks for volunteering! Sorry I didn't get respond sooner, this thread
was buried kinda deep in my inbox so I didn't notice your message right
away.
> As far as I know, I would need to:
>
> 1. Make a clone of the repository on git.kernel.org under my own namespace.
> 2. Generate a key pair and certificate
> 3. Put the certificate into the kernel tree
> 4. Update the docs to point to the new repository and certificate
> 5. Review incoming patches and apply them
> 6. Tag releases timely
>
> I'm not sure if I missed anything.
That's the bulk of it. Most of the time is spend validating proposed
changes against the government documents. There's also maintaining the
tools to build the database and moderating the mailing list, but neither
of those are much effort.
Johannes will be the one who needs to accept your key into the kernel,
so we should wait for a +1 from him at least before we really get the
ball rolling.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2023-10-30 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 20:13 [wireless-regdb] [ANN] wireless-regdb: master-2023-09-01 Seth Forshee
2023-10-24 6:23 ` Chen-Yu Tsai
2023-10-30 20:39 ` Seth Forshee [this message]
2023-10-31 9:32 ` Chen-Yu Tsai
2023-10-31 20:44 ` Seth Forshee
2023-11-19 22:59 ` Seth Forshee
2023-12-01 8:17 ` Johannes Berg
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=ZUAUahZakEvOXpip@do-x1extreme \
--to=sforshee@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@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