linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab+huawei@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>
Subject: [PATCHv6 0/3] docs: media: multicommitters model documentation
Date: Mon, 27 Oct 2025 14:28:30 +0100	[thread overview]
Message-ID: <cover.1761571713.git.hverkuil+cisco@kernel.org> (raw)

I finally had time to continue Mauro's work on documenting the
multicommitter model.

It is a fairly big overhaul of v5. The most significant change is
that I extended the maintainer profile substantially. A lot of
the committer requirements from the v5 of media-committer.rst were
actually maintainer requirements, so I moved those over to the
maintainer profile.

Patch 1/3 updates maintainer-entry-profile.rst: it introduces the
three Media maintainer levels (Media Maintainer, Media Core Maintainer
and Media Subsystem Maintainer) and what the responsibilities are.

Patch 2/3 adds media-committer.rst: that focusses on the additional
commit rights that can be granted to a Media Maintainer.

Patch 3/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.

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

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        | 407 +++++++++++++++---
 .../driver-api/media/media-committer.rst      | 196 +++++++++
 3 files changed, 548 insertions(+), 56 deletions(-)
 create mode 100644 Documentation/driver-api/media/media-committer.rst

-- 
2.51.0


             reply	other threads:[~2025-10-27 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 13:28 Hans Verkuil [this message]
2025-10-27 13:28 ` [PATCHv6 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2025-10-27 22:06   ` Sean Young
2025-10-28  8:25     ` Hans Verkuil
2025-10-28  9:10       ` Sean Young
2025-10-27 13:28 ` [PATCHv6 2/3] docs: media: document media multi-committers rules and process Hans Verkuil
2025-10-27 13:28 ` [PATCHv6 3/3] docs: media: document Media Maintainers Hans Verkuil

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=cover.1761571713.git.hverkuil+cisco@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).