linux-kernel - Re: [PATCH v3 0/3] Document the new media-committer's model

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b0843e80-c46c-4344-b9f1-1d3b57dd2bbe@xs4all.nl>
Date: Mon, 2 Dec 2024 16:03:45 +0100
From: Hans Verkuil <hverkuil@...all.nl>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
 linux-media@...r.kernel.org
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, workflows@...r.kernel.org
Subject: Re: [PATCH v3 0/3] Document the new media-committer's model

On 02/12/2024 10:26, Mauro Carvalho Chehab wrote:
> The media subsystem used to have a multi-commiter's model in the
> past, but things didn't go well on that time, and we had to move to
> a centralized model.
> 
> As the community has evolved, and as there are now new policies in
> place like CoC, let's experiment with a multi-committers again.
> 
> The model we're using was inspired by the DRM multi-committers
> model. Yet, media subsystem is different on several aspects, so the
> model is not exactly the same.
> 
> The implementation will be in phases. For this phase, the goal is that 
> all committers will be people listed at MAINTAINERS.
> 
> On this series,:
> 
> patch 1: updates the  media maintainer's entry profile and adds the
> workflow that will be used with the new model. While here, it also
> adds a missing "P:" tag at the MAINTAINERS file, pointing to it;
> 
> patch 2: adds a new document focused at the new maintainers
> process. Its target is for developers that will be granted with
> commit rights at the new media-maintainers.git tree. It also
> contains a reference tag addition to kernel.org PGP chain
> at process/maintainer-pgp-guide.rst.
> 
> patch 3: make documents cleared about maintainership duties.

At least from my perspective, v3 is close to being ready and I hope
that v4 will be good enough to be merged.

That said, what is missing in all this is that there is nothing here
that explains why you would want to become a media committer. It is all
very dry stuff, lots of 'shall's, and 'rights' and 'trust' and obligations,
but nothing about the satisfaction you get when you get the responsibility
of a part of the kernel and being able to guide the development of that
area.

It's good enough to get the multi-committer process off the ground, but
it definitely needs more work to make it more inviting to become a media
committer. Because right now it is as dry as dust.

Regards,

	Hans

> 
> ---
> 
> v3:
> - added patch 3;
> - addressed nits pointed by Ricardo during his review;
> - did minor editorial changes to improve Sphinx html output.
> 
> v2: I tried to address most of the suggestions where there was an agreement
> from Laurent's review and further comments. As there were several changes,
> on separate threads, I could have missed something.
> 
> 
> Mauro Carvalho Chehab (3):
>   docs: media: update maintainer-entry-profile for multi-committers
>   docs: media: document media multi-committers rules and process
>   docs: media: profile: make it clearer about maintainership duties
> 
>  Documentation/driver-api/media/index.rst      |   1 +
>  .../media/maintainer-entry-profile.rst        | 219 +++++++++++---
>  .../driver-api/media/media-committer.rst      | 278 ++++++++++++++++++
>  .../process/maintainer-pgp-guide.rst          |   2 +
>  MAINTAINERS                                   |   1 +
>  5 files changed, 456 insertions(+), 45 deletions(-)
>  create mode 100644 Documentation/driver-api/media/media-committer.rst
>