Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34;
MIME-Version: 1.0
References: <ZPJF1/2YA4dP+ggY@ubuntu-x1> <CAGb2v657baNMPKU3QADijx7hZa=GUcSv2LEDdn6N=QQaFX8r-g@mail.gmail.com>
 <ZUAUahZakEvOXpip@do-x1extreme>
In-Reply-To: <ZUAUahZakEvOXpip@do-x1extreme>
Reply-To: wens@kernel.org
From:   Chen-Yu Tsai <wens@kernel.org>
Date:   Tue, 31 Oct 2023 17:32:15 +0800
Message-ID: <CAGb2v66cVj2O89G9qhKCqca+jyBK9ic3866giL=LZX4mQo-eDg@mail.gmail.com>
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2023-09-01
To:     Seth Forshee <sforshee@kernel.org>,
        Johannes Berg <johannes@sipsolutions.net>
Cc:     wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Oct 31, 2023 at 4:39=E2=80=AFAM Seth Forshee <sforshee@kernel.org> =
wrote:
>
> 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 namesp=
ace.
> > 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.

I managed to get some support internally for the validation part. I
should be able to lean on our WiFi team or external partners if docs
provided are insufficient.

One thing I forgot to ask. After a release is tagged, is there some
magic bot that produces a tarball and uploads it to kernel.org? Or
is that a manual process?

> 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.

+Johannes for his opinion.

Thanks!
ChenYu

> Thanks,
> Seth