Hi Seth,
On Sat, Sep 2, 2023 at 4:13 AM Seth Forshee <[email protected]> wrote:
>
> A new release of wireless-regdb (master-2023-09-01) is available at:
>
> https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2023.09.01.tar.xz
>
> The short log of changes since the master-2022-05-03 release is below.
>
> As previously announced, I am stepping down as the maintainer of
> wireless-regdb effective today. This is the last release I plan to do,
> and currently there is no new maintainer for the project.
I'd like to take up maintainership.
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.
Thanks
ChenYu
> Thanks,
> Seth
>
> ---
>
> Adam Nielsen (1):
> wireless-regdb: Update regulatory rules for Australia (AU) for June 2023
>
> Seth Forshee (3):
> wireless-regdb: Update regulatory rules for Egypt (EG) from March 2022 guidelines
> wireless-regdb: Update regulatory info for Türkiye (TR)
> wireless-regdb: update regulatory database based on preceding changes
>
> kleo (1):
> wireless-regdb: Update regulatory rules for Philippines (PH)
>
>
> _______________________________________________
> wireless-regdb mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/wireless-regdb
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
On Tue, Oct 31, 2023 at 4:39 AM Seth Forshee <[email protected]> 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 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.
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
On Tue, Oct 31, 2023 at 05:32:15PM +0800, Chen-Yu Tsai wrote:
> 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?
Releases tarballs are produced using kup [1]. It's not quite automatic,
but with some simple scripting it's pretty close.
[1] https://korg.docs.kernel.org/kup.html
On Tue, Oct 31, 2023 at 05:32:15PM +0800, Chen-Yu Tsai wrote:
> > 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.
Johannes, we haven't heard from you. Let us know if you have any
objections, otherwise I'm going to start moving forward on this.
Thanks,
Seth
On Sun, 2023-11-19 at 16:59 -0600, Seth Forshee wrote:
> On Tue, Oct 31, 2023 at 05:32:15PM +0800, Chen-Yu Tsai wrote:
> > > 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.
>
> Johannes, we haven't heard from you. Let us know if you have any
> objections, otherwise I'm going to start moving forward on this.
>
Sorry! I fell way behind on email :( Yeah I'm happy with this.
johannes