Employees of CMS Minds could use some training assistance

I don't think README MR's should be categorized as gaming the system by default. Feel free to participate in the discussion in #3367061: Categorize contributions that could be considered 'gaming the credit system' and propose solutions (policy, automation, etc).

I think it's important to discern between spammy, Drupal 7, no users, README MR's, and a clear improvement, for example by adding a README.md to a popular project without a README, in the first place.

I don't think README MR's should be categorized

@ressa but this issue is about the different question: a company which farms credit which also includes readme among all other tactics. This is not acceptable behavior.

Or more sophisticated negative contributions which wastes everyone's time like this #3460460: Improve AI API Explorer styling.

@smustgrave

We'll take care of it next time.

Thank you!!

Yes, you're probably right @mindaugasd ... I saw README mentioned in the Issue Summary which triggered me. I should have checked more thoroughly before posting.

I agree that negative contributions are wasting everyone's time, like the one you link to. They should be flagged and the offender called out, absolutely. Always.

The problem arises when great contributions are being flagged as credit gaming, merely for being a README MR. As an example, see #3343722: Clean up documentation. A great contribution, perfectly executed, and a clear improvement. But it was rejected, and on top of that, the creator called out as being a credit gamer:

@gajendra_sharma thank you but I don't accept tickets like these for projects I manage as this is viewed as a credit farming technique and doesn't bring value to the project. If you wish to get involved please work on actual issues.
Linking this because I know employees of the company have been warning before #3339883: Employees of Dotsquares are posting mass re-roll patches which are invalid and/or incomplete

The MR looks great, and reads better in my opinion:

• README original
• README markdown

Please also see the discussion I linked to. Anyways, sorry that I hi-jacked this issue.

On the one hand, companies who contributed to Drupal should be recognized in the listing, on the other hand, credit farmers sophistication grows, which means it may be better for Drupal to remove those advantages companies gain with credits and solve this problem.

Previous example I gave yesterday I was familiar with, but today I am wasting time trying to figure out what same people are changing here (1 line change) #3463243: Unable to install modules: module 'search_api_ai_simple_chatbot' is missing its dependency module jquery_once

They removing a dependency saying it causes error. But there would be no error, if they would install it with composer. Kinda inventing an error which does not exist. But maybe that dependency is really not used. It is fine line here requiring research, but what is their underlying goal - a credit or help and improve Drupal?

Similar to your example about documentation #3443827: Minor code documentation fixes - did it actually improved Drupal or wasted time?
I am sure there is 100 of places like this in my modules where few lines could be changed like this, but it is worthless to change them.

I have posted an official first warning per the Contribution Credit policy to all the users recently involved in the issues linked above, as well as the CMSWeb leadership as best as I could find their contact information.

I think this could use another poke: https://www.drupal.org/user/3641874/track

Not posting issues, but working actively on those kind of spammy issues and jumping on new ones within minutes of creation. Meaning they are actively watching or searching the issue queue for those kind of issues.

I have sent an updated nudge to org leadership.

Was hit by a phcps fixable issue under the appearance of PHP 8.4 depredations.

Not enough for a strike at this time, however it does go to #10's note that we still see this vendor working 'spammy' issues.

@cmlara
Our team was not aware that it would not receive D.O. issue credit under the Abuse of the Contribution Credit system. We had no intention of misusing the system.

Please feel free to close such issues, and we sincerely apologize for any inconvenience caused.

Next time, our team will take care to avoid working on the such issues .

Thank you for your understanding