workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	workflows@vger.kernel.org, Hans Verkuil <hverkuil@xs4ll.nl>
Subject: Re: [PATCH] docs: media: document media multi-committers rules and process
Date: Wed, 27 Nov 2024 12:54:15 +0100	[thread overview]
Message-ID: <20241127124629.704809f1@foz.lan> (raw)
In-Reply-To: <20241127103948.501b5a05@foz.lan>

Em Wed, 27 Nov 2024 10:39:48 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:

> > This workflow doesn't apply to patch submitters who are not allowed to
> > send pull requests and who don't have direct commit access. I thought
> > these submitters are the main audience of this document. In that case, I
> > think moving the next section that explains the e-mail workflow before
> > the "Media development workflow" section (which should likely be renamed
> > to make it clear that it is about merging patches, not developing them)
> > would be best. The "Review Cadence" section could also be folded in
> > there, to give a full view of what a submitter can expect.
> > 
> > This would also have the advantage of introducing the linuvtv.org
> > patchwork instance, which you reference above. Documents are more
> > readable when they introduce concepts first before using them.  
> 
> Will try to do such change at v2.

Actually, both workflows (a) and (b) apply to the ones that can't
send pull requests or push at media-committers.git:

---

a. Normal workflow: patches are handled by subsystem maintainers::

     +------+   +---------+   +-------+   +-----------------------+   +---------+
     |e-mail|-->|patchwork|-->|pull   |-->|maintainers merge      |-->|media.git|
     +------+   +---------+   |request|   |in media-committers.git|   +---------+
                              +-------+   +-----------------------+

   For this workflow, pull requests can be generated by a committer,
   a previous committer, subsystem maintainers or by a couple of trusted
   long-time contributors. If you are not in such group, please don't submit
   pull requests, as they will likely be ignored.

b. Committers' workflow: patches are handled by media committers::

     +------+   +---------+   +--------------------+   +-----------+   +---------+
     |e-mail|-->|patchwork|-->|committers merge at |-->|maintainers|-->|media.git|
     +------+   +---------+   |media-committers.git|   |approval   |   +---------+
                              +--------------------+   +-----------+

---

No matter who sent an e-mail, this will be picked by patchwork and either
be part of a PR or a MR, depending on who picked it.

Thanks,
Mauro

  parent reply	other threads:[~2024-11-27 11:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 13:28 Mauro Carvalho Chehab
2024-11-26 15:19 ` Laurent Pinchart
2024-11-27  9:39   ` Mauro Carvalho Chehab
2024-11-27 11:19     ` Laurent Pinchart
2024-11-27 14:48       ` Simona Vetter
2024-11-28 11:24         ` Jani Nikula
2024-11-28 18:47           ` Mauro Carvalho Chehab
2024-11-28 21:27             ` Jani Nikula
2024-11-28 21:52               ` Simona Vetter
2024-11-29  2:21                 ` Mauro Carvalho Chehab
2024-11-29  1:57               ` Mauro Carvalho Chehab
2024-11-28 18:28         ` Mauro Carvalho Chehab
2024-11-28 19:08           ` Laurent Pinchart
2024-11-27 11:54     ` Mauro Carvalho Chehab [this message]
2024-11-27 13:39       ` Laurent Pinchart
2024-11-27 15:09         ` Mauro Carvalho Chehab
2024-11-27 17:59           ` Laurent Pinchart
2024-11-27 11:59   ` Hans Verkuil
2024-11-27 13:25     ` Laurent Pinchart
2024-11-28 18:15       ` Mauro Carvalho Chehab
2024-11-28 19:07         ` Laurent Pinchart
2024-11-29 10:29           ` Mauro Carvalho Chehab
2024-12-02 10:24             ` Laurent Pinchart
2024-11-28  8:19     ` Mauro Carvalho Chehab
2024-11-28  9:31       ` Laurent Pinchart
2024-11-28 17:44     ` 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=20241127124629.704809f1@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hverkuil@xs4ll.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=workflows@vger.kernel.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