From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
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>
Subject: Re: [PATCHv6 1/3] docs: media: update maintainer-entry-profile for multi-committers
Date: Fri, 23 Jan 2026 14:59:10 +0100 [thread overview]
Message-ID: <20260123145910.7b9fb258@localhost> (raw)
In-Reply-To: <f5e7f0fc-c259-4552-8513-a3862bee5c29@kernel.org>
On Fri, 23 Jan 2026 14:42:30 +0100
Hans Verkuil <hverkuil+cisco@kernel.org> wrote:
> On 03/12/2025 13:27, Ricardo Ribalda wrote:
> > Hi Hans
> >
> > Thanks for the new version
> >
> > On Mon, 27 Oct 2025 at 14:51, Hans Verkuil <hverkuil+cisco@kernel.org> wrote:
> >>
> >
> > I also prefer the original nomenclature for the roles:
> >
> > Contributor: Anyone that posts a patch to the ML
> > Committer: Contributors that can commit (List provided by you)
> > Core Committer: Laurent, Sakari, Sean and Sebastian (Names in the
> > original presentation, should be updated)
> > Subsystem Maintainer: Mauro and Hans
> >
> > In my head, a maintainer is someone that pushes to the upper tree,
> > rebases and merges. In the media-committer tree that is only you and
> > Mauro.
>
> No, a maintainer is someone who decides when patches are ready for
> mainline inclusion and posts PRs. A committer is a maintainer who
> can directly push patches to the git tree and can skip the PR step.
>
> Previous versions of this series mixed those concepts, which was very confusing.
The problem with this version is that it is also mixing/overriding
nomenclatures. Basically:
- a maintainer is anyone with his name at MAINTAINERS file;
- subsystem maintainer is also a clear concept.
We need to avoid more mess to the "maintainer" here. This was
clearer at the previous version, as "committer" and "core committer"
are clear concepts and won't conflict with existing nomenclature,
but now that we're splitting committer function as an orthogonal
attribute (nothing against that), we need better names for the
maintainers that are described on this profile. maybe:
- media core maintainer: for people responsible to maintain part of
the media framework;
- media driver maintainer: for everyone else that is listed
at MAINTAINERS with stuff under drivers/media and/or
drivers/staging/media(*) and it is not a media core maintainer.
(*) Should the ones with drivers only at staging be placed on
a different group like "staging media driver maintainer"?
Regards,
Mauro
next prev parent reply other threads:[~2026-01-23 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 13:28 [PATCHv6 0/3] docs: media: multicommitters model documentation Hans Verkuil
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-12-03 9:43 ` Mauro Carvalho Chehab
2025-12-03 10:00 ` Mauro Carvalho Chehab
2026-01-23 14:23 ` Hans Verkuil
2026-01-23 14:16 ` Hans Verkuil
2026-01-23 15:19 ` Mauro Carvalho Chehab
2025-12-03 12:27 ` Ricardo Ribalda
2026-01-23 13:42 ` Hans Verkuil
2026-01-23 13:59 ` Mauro Carvalho Chehab [this message]
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=20260123145910.7b9fb258@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox