Please add an e-mail prefix for linux-media profile

[mchehab]

After some discussions with media maintainers, we'd like to add at:

sashiko/sashiko.dev/email_policy.toml

Line 176 in 9edb115

[subsystems.linux-media]

a prefix message to be added at the e-mails sent from sashiko related to the media subsystem. e.g. something like:

[subsystems.linux-media]
lists = ["linux-media@vger.kernel.org"]
reply_to_author = true
cc = ["linux-media@vger.kernel.org"]
prefix = ["This review was done by AI. When in doubt about some of the findings, please consult an experienced developer first." ]

[pinchartl]

The consensus from discussions in the recent Linux media summit was that sashiko reviews should not be sent to the linux-media mailing list nor to the author for the time being. Please drop it for now. If you want to change the policy, please initiate a discussion with the community.

[rgushchin]

@pinchartl any links to the discussion or any details? I'm happy to drop the current configuration, just want to make sure it's indeed a consensus.

[pinchartl]

Hans Verkuil is working on the meeting minutes and will publish them to the linux-media mailing list (probably after a round of proof-reading). He confirmed my understanding on IRC (I think Mauro can also confirm this).

[rgushchin]

Sure, thanks!

[mchehab]

The consensus from discussions in the recent Linux media summit was that sashiko reviews should not be sent to the linux-media mailing list nor to the author for the time being. Please drop it for now. If you want to change the policy, please initiate a discussion with the community.

For now, keep sending it to linux-media, until we setup a different way for sashiko to update our patchwork instance.

[pinchartl]

Mauro, bypassing the consensus reached by the community during the recent Linux media summit is not acceptable.

[mchehab]

@pinchartl any links to the discussion or any details? I'm happy to drop the current configuration, just want to make sure it's indeed a consensus.

This was not the consensus during media summit. Basically we want sashiko's review.

Also, on a discussion we had today among media maintainers (https://linuxtv.org/irc/oftc/irclogger_log/media-maint?date=2026-06-08,Mon), we agreed that, for now, Sashiko would keep sending e-mails to linux-media. All we want is to add a small text on the top of the e-mails to avoid new developers to blindly try to consider its review as something mandatory.
So, Hans proposed to add:

This review was done by AI. When in doubt about some of the findings, 
please consult an experienced developer first.

which I agreed.

We want to avoid too much traffic at linux-media, so we're aiming to either use a separate list for Sashiko, or if Sashiko gains support to directly update patchwork, and if my patchwork's PR is accepted (getpatchwork/patchwork#656), instead of sending e-mails it could directly update our patchwork's instance. Otherwise, I'll setup a different process on our side, and Sashiko would be sending e-mails to a different ML.

[pinchartl]

Quoting the same discussion,

10:29 < hverkuil> Laurent is correct: we didn't want it on the mailinglist to avoid inexperienced devs to take it as gospel. Polluting the ML is definitely another reason for not posting to linux-media.
10:29 < hverkuil> (I'm working on the minutes of our meeting today)

I take note that you don't agree with Hans' and my (among others) understanding of the consensus reached during the media summit. The way to resolve this is to wait for the minutes to be published and discuss it there, on the mailing list, with the whole community. There is no urgency to get sashiko e-mails to the list, I don't see why you want to bypass the community discussion and rush this. Acting unilaterally is damaging to our community.

[mchehab]

Mauro, bypassing the consensus reached by the community during the recent Linux media summit is not acceptable.

Check the etherpad with the notes taken during the Media Summit:

laurent: crictial about Sashiko usage, on point with Erik's Opinion (https://kusma.xyz/blog/2026/03/26/open-source-and-ai/), Hans and Mauro are OK with Sashiko and think we should request to add linux-media to Sashiko bot.

nicolas: if sashiko notices a security flaw, we don't want to ignore it

laurent: we have to be careful to not get dependent on Sashiko (although being free at the moment)

There was no such consensus of not receiving Sashiko bot feedback.

[rgushchin]

It sounds like there is no consensus yet and I generally prefer to be conservative here, so I’m disabling emails for now. But also it would be great to receive the feedback - it’s the only way how sashiko can get better.
Also, it sounds like the media mailing list is being used by many maintainers. I’m thinking if per-MAINTAINERS-entry policy makes more sense? Would it help in such cases?
Re sashiko being free for now/creating a dependency - the code will remain free in any case, it’s Apache 2.0 and belongs to the Linux Foundation, so it’s not going anywhere. So it’s more like an open-source harness which can be used with various LLM providers. I totally understand and acknowledge the concern here, but at the same time ignoring all benefits which ai can bring already is also strange, IMO. But it’s just 2c for me, I leave maintainers to decide for each specific mailing list/subsystem.

[jailuthra]

Hans and Mauro are OK with Sashiko and think we should request to add linux-media to Sashiko bot.

@mchehab I always interpreted that as adding linux-media@ as an input to Sashiko, and not sending Sashiko outputs to linux-media@ given a lot of people in the discussion were vocal about not polluting the ML.