Recently some juniors have started posting patches for very trivial, non-essential, of zero importance clearly to gain more credit on drupal.org and look like professionals.

Example: fixing a single typo perhaps in the module's readme file! an space after comma is missing?

Another example: https://www.drupal.org/project/calendar_systems/issues/3067955
Look at the profile for both users. The user posting the patch and the user reviewing it, both working at the same company. And the company is gathering credit by being mentioned in these one-little-typo-being-fixed patches.

There are many more. It's clearly abusing the system.

Comments

hkoosha created an issue. See original summary.

hkoosha’s picture

Priority: Major » Normal
gisle’s picture

Component: Spam » Other
Category: Bug report » Support request
Status: Active » Closed (duplicate)
Parent issue: » #3050888: Is posting similar patches for multiple projects allowed?

There already an open issue about this - please see #3050888: Is posting similar patches for multiple projects allowed?. Please post your opinion there to weigh in on this.

Closing as a duplicate.

hkoosha’s picture

Status: Closed (duplicate) » Active

I can not post anything to that issue queue. It's closed. Sounds like kiamlaluno got angry and shut the user up?

avpaderno’s picture

Title: Site functionality problem » Users are posting trivial patches
Status: Active » Closed (duplicate)
Parent issue: #3050888: Is posting similar patches for multiple projects allowed? »
Related issues: +#3050888: Is posting similar patches for multiple projects allowed?

The other issue has comments closed to avoid unnecessary, irrelevant for the webmasters, changes.

This issue is still a duplicate of that issue because what said there still applies here. What described in both the issues isn't something that concerns the webmasters, as webmasters cannot limit the number of patches a user posts, nor the number of issue a user posts.

If you think a user is doing something wrong, you can contact the Community Working Group as described in Incident Report. (I would suggest to first read Conflict Resolution Policy and Process.)

hkoosha’s picture

I will follow the matter there.
Thanks.