| From: |
| Hans Verkuil <hverkuil+cisco-AT-kernel.org> |
| To: |
| linux-media-AT-vger.kernel.org |
| Subject: |
| [PATCHv7 0/3] docs: media: multicommitters model documentation |
| Date: |
| Tue, 27 Jan 2026 11:53:24 +0100 |
| Message-ID: |
| <cover.1769511207.git.hverkuil+cisco@kernel.org> |
| Cc: |
| Mauro Carvalho Chehab <mchehab+huawei-AT-kernel.org>, Sakari Ailus <sakari.ailus-AT-linux.intel.com>, Laurent Pinchart <laurent.pinchart-AT-ideasonboard.com>, Sean Young <sean-AT-mess.org>, Nicolas Dufresne <nicolas.dufresne-AT-collabora.com>, Bryan O'Donoghue <bryan.odonoghue-AT-linaro.org>, Ricardo Ribalda <ribalda-AT-chromium.org> |
| Archive-link: |
| Article |
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/maintaine...
https://hverkuil.home.xs4all.nl/spec/driver-api/media-com...
Regards,
Hans
Hans Verkuil (1):
docs: media: document Media Maintainers
Mauro Carvalho Chehab (2):
docs: media: update maintainer-entry-profile for multi-committers
docs: media: document media multi-committers rules and process
Documentation/driver-api/media/index.rst | 1 +
.../media/maintainer-entry-profile.rst | 436 +++++++++++++++---
.../driver-api/media/media-committer.rst | 197 ++++++++
3 files changed, 577 insertions(+), 57 deletions(-)
create mode 100644 Documentation/driver-api/media/media-committer.rst
--
2.51.0