Is posting similar patches for multiple projects allowed?

It doesn't seem the user is posting automated patches. Even if PHP_CodeSniffer were used, the user would still need to clone the project locally and run the command to see what changes are suggested.

While the user seems to focus on the content of .info.yml files, the reports are tailored for really existing issues. Even if it could seem a minimal contribution, it still contributing.

When the patch was provided, the project was not showing as unsupported and obsolete.

As side note, if you don't want to get notification from that project issues, or be associated to it (for example, when somebody wants to take over it, or re-use the project namespace for a new project), the project can be moved to the Unsupported Projects user.

I agree with kiamlaluno (in particular comment #4). This is not spam, but an attempt made in good faith to fix a coding standard issue. Also, it does not look automated to me.

We actually encourage people to contribute here, so we should very careful when using the word "spam" when somebody tries to contribute.

I think this issue should be closed, as there has been no activity for three months (before I chipped in), but I leave it to kiamlaluno or mikl to make the call.

mikl wrote:

It improves nothing, it just waste [of] maintainer time having to deal with the issues.

The community happens to have some guidelines about the stuff that goes into the the repo, and one those guidelines are:

Capitalize the name of the module, because module names are proper nouns.

(See for intstance: https://www.drupal.org/docs/develop/documenting-your-project/help-text-s....)

You may even disagree with this particular guideline, and choose to ignore in the projects you maintain – and that's also OK. However, to use the word "spamming" to characterize the contribution of another community member who wants to help out with getting those guidelines followed is IMHO not treating others with the respect they deserve.

You have a lot of options here, but most appropriate is already mentioned in comment #4: Hand any project you no longer maintain over to the 'Unsupported Projects' user. That saves others from wasting time trying to contribute to the project, and you from wasting time reviewing patches.

(And you've probably wasted more time complaining about this than you did eyeballing the proposed patch in the first place.)

I would also not say it's a waste of time for the project maintainer, as the user has opened just two issues per project.

What can be done is correcting the user when she is posting a wrong patch, or she misunderstood what the guidelines say.

I am closing this issue, since two webmasters answered. I am also changing the title to better describe what the support request was asking.

What described here is not spamming; therefore, I changed the title to better describe what the issue discussed here is, given that the title is thought to give an idea of what the issue is, not describing it exactly. You are free to change it, as long as spamming (or a similar word) doesn't compare in the title.

No, they aren't useless patches, by drupal.org standards. If you consider them useless, you are free to ignore them, but that is not a webmasters issue.

It's a support request. There isn't anything that needs to be fixed, as you just asked a question, which has been answered.

No, that is not spamming by Drupal.org terminology, and by Drupal.org webmasters terminology. Since this issue is in the webmasters queue, the title must make clear what the webmasters need to do.

Since this is the webmasters issue queue, your terminology is irrelevant.