Re: [PATCH] docs: remove Assisted-by references

[Theodore Tso]

On Tue, Oct 20, 2026 at 01:44:48AM -0500, Laurent Pinchart wrote:
> > Recently 2 people sent 1,000 patches over 2 hours. Care to check each and
> > every patch for 'quality'? :) Only the beginning.
> 
> That's the kind of behaviour that should be easy to detect, and I have
> absolutely no issue with sending all those patches to /dev/null. This is
> script kiddies behaviour, not the work of someone with good intentions.
> Ignoring those patches is not "collateral damage".

Well, let's take the reverse.  Suppose there are 500 newcomers who
have each sent two patches each in the same time period.  This is
going to put the same stress on the reviewers and maintainers.  Of
those 500 newcomers, there will undoubtedly be few (single digit
percentage) that will eventually become valued reviewers, and somewhat
larger percentage that will become regular code contributors of
quality improvements.

These percentages were always there pre-AI, but there were much fewer
newcomers per unit time.  So this increase of new comers has its good
side --- it means we have the opportunity to significantly grow our
community.  But it also has its shadow side, which is when we only
have a newcomer every month or two or three, the overhead of trying to
engage with a newcomer isn't that great, even if the vast majority of
them disappear after the maintainer attempts to work with them.  And
if that happens, we just shrug and move on.

But if there is 10x or 100x the number of newcomers, it puts a huge
strain on the pre-existing community to engage with these newcomers.
And when we get newcomers who send patches like this:

> We could go a step further. There's also an increase in patches from
> newcomers who send a few patches only, with the usual signs of not
> understanding what they're doing: code changes that give an eerie
> feeling, very large comment to code ratios, and commit messages longer
> than the three volumes of Lord of the Rings combined.

.... the question is the probability that newcomers whose first few
patches look like this compare with the probability of newcomers who
first patches are 100% human generated?

I don't know the answer to this question, but clearly some people
believe that the probabilities are different, and so if they need to
make some lifeboat choices about which newcomers to engage with first,
it might influence their choices.

Even if doesn't, the reality is that with a huge influx of patches and
newcomers, maintainers' time is finite and expecting them to engage
with all newcomers, and review all patches promptly is a recipe for
burnout.  So "collateral damage" isn't just not just newcomers needing
to wait weeks before someone gets back to them (and some might never
get a reply if their patches get lost in someone's inbox), although
that can certainly be collateral damage.  It's also the potential of
maintainers getting burned out; that can also be collateral damage.

And having someone claim that it's the maintainers "fault" for not
building up the reviewing community is also not helpful.  We are where
we are, and as much as I would hate to lose a potential contributor
who gives up because they don't get attention right away, when only a
percentage of these newcomers become regular contributors a certain
amount of self-care and preserving the maintainers' sanity might have
to take higher priority.

Don't get me wrong.  Getting a large number of contributions, even if
not all of them are high priority fixes and/or high quality
contributions, and having a large number of newcomers is a ***good***
problem to have.  And I'm thankful that we have it.  But it still can
be a problem that we need to solve, one way or another.

							- Ted