All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sean Young <sean@mess.org>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [PATCHv7 0/3] docs: media: multicommitters model documentation
Date: Wed, 4 Feb 2026 15:36:36 +0100	[thread overview]
Message-ID: <20260204153636.53d6ed47@localhost> (raw)
In-Reply-To: <cover.1769511207.git.hverkuil+cisco@kernel.org>

Hi Hans,

On Tue, 27 Jan 2026 11:53:24 +0100
Hans Verkuil <hverkuil+cisco@kernel.org> wrote:

> Here is v7, based on yesterday's meeting.
> 
> The main change is what a "Media Maintainer" is. In v6 I considered a
> Media Maintainer to be someone who has patchwork access and has
> responsibility for an area of the media subsystem, deciding when a
> patch is ready to be merged and making PRs.
> 
> That was confusing since that name was too generic.
> 
> In v7 a "Media Driver Maintainer" is anyone who is listed in MAINTAINERS
> for a media driver. "Media Driver/Core/Subsystem Maintainers" are collectively
> called "Media Maintainers".
> 
> I also added the distinction of being granted patchwork access: only Media
> Maintainers with patchwork access can decide when a patch is ready to be
> merged and make PRs. If you are trusted enough to be able to do that, then
> patchwork access is granted since you need that to be able to delegate patches
> and update the patch status.
> 
> I'm still not entirely satisfied with this, as I would prefer to have a
> specific name for such maintainers. Saying "Media Maintainers with patchwork
> access" is a mouthful. I can't think of a good name, though.
> 
> So the hierarchy is as follows:
> 
> - Media Contributor: posts patches
> - Media Driver Maintainer: as above, but also reviews patches and is
>   listed in MAINTAINERS
> - Media Driver Maintainer with patchwork access: decides when patches are
>   ready for mainline, posts PRs, keeps patchwork up to date. Optionally
>   has commit rights.
> - Media Core Maintainer: same as above, but is also responsible for one
>   or more media core frameworks.
> - Media Subsystem Maintainer: as above, but is also responsible for the
>   whole subsystem, processes PRs and has commit rights.
> 
> 
> 
> Patch 1/3 updates maintainer-entry-profile.rst: it introduces the
> three Media maintainer levels (Media Driver Maintainer, Media Core Maintainer
> and Media Subsystem Maintainer) and what the responsibilities are.
> 
> Patch 2/3 adds back and updates the list of Media Maintainers that
> disappeared in patch 1/3. Please verify this whether the email
> addresses are the correct ones, and verify that the areas of responsibility
> are correct and that nothing is missing.
> 
> Patch 3/3 adds media-committer.rst: that focusses on the additional
> commit rights that can be granted to a Media Maintainer.
> 
> It feels much more consistent to me, I'm looking forward to the
> review comments.
> 
> I have uploaded the documentation with these patches here:
> 
> https://hverkuil.home.xs4all.nl/spec/driver-api/maintainer-entry-profile.html
> https://hverkuil.home.xs4all.nl/spec/driver-api/media-committer.html
> 
> Regards,
> 
> 	Hans

This new version is much better than v6. There are a couple of
minor changes to be changes, but afterwards, I guess we're ready
to go. I'll submit such changes as two patches at the end of this
series.


-- 
Thanks,
Mauro

  parent reply	other threads:[~2026-02-04 14:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 10:53 [PATCHv7 0/3] docs: media: multicommitters model documentation Hans Verkuil
2026-01-27 10:53 ` [PATCHv7 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2026-02-05 11:37   ` Bryan O'Donoghue
2026-02-05 18:03   ` kernel test robot
2026-01-27 10:53 ` [PATCHv7 2/3] docs: media: document Media Maintainers Hans Verkuil
2026-02-05 11:38   ` Bryan O'Donoghue
2026-02-05 14:24   ` Nicolas Dufresne
2026-02-05 16:59     ` Laurent Pinchart
2026-02-06  8:30       ` Jacopo Mondi
2026-01-27 10:53 ` [PATCHv7 3/3] docs: media: document media multi-committers rules and process Hans Verkuil
2026-02-04 14:36 ` Mauro Carvalho Chehab [this message]
2026-02-04 14:37 ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Mauro Carvalho Chehab
2026-02-04 14:37   ` [PATCH 2/2] docs: media: media-committer: do some editorial changes Mauro Carvalho Chehab
2026-02-04 15:07     ` Mauro Carvalho Chehab
2026-02-05 11:52     ` Hans Verkuil
2026-02-05 13:51       ` Mauro Carvalho Chehab
2026-02-05 13:58         ` Hans Verkuil
2026-02-05 11:25   ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Hans Verkuil
2026-02-05 13:53     ` Mauro Carvalho Chehab

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=20260204153636.53d6ed47@localhost \
    --to=mchehab+huawei@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.