credit farming of rajan-kumar2026

I had a quick look at todays actions. The user continues to post random screenshots and core_version_requirement merge requests without reading the issue. It's not "only" gaming the system. This is harmful spam and a lot of noise in a huge amount of projects.

I also thought again about the very low quality contributions (CSS and PHP) I saw yesterday. It always does something, but never the right thing. My guess: This person is not employed for programming and it smells hard like chatbot usage.

Between those issues, there are also bug reports about themes that are not installable, for which a screenshot show the theme's dependencies are missing.
I cannot say those are open to farm credits, but they show rajan does not have clear how Drupal core is supported to work.

I also noticed that, in one issue, Rajan has hidden an issue fork, after he created a duplicate issue and somebody gave the link to the existing issue.
It seems Rajan does not understand how to contribute on drupal.org.

Upon reviewing Rajan's contributions on Drupal.org, it's evident that he's eager to contribute but lacks a comprehensive understanding of the Drupal platform. He appears to navigate through various project issues, attempting to address them based on his limited understanding.

While skimming some more issues I also found a few, that looked valid or where Rajan actually reacted to feedback. When I opened this issue, I was sick and in a bad mood, so I didn't even see good intentions as an option. Now I share @adaperno's and @vishalkadam's conclusion.

I still think, that Rajan's contributions do more harm than good, but I also don't have a better idea for handling such cases other than teaching.

I want to avoid public shaming and it doesn't look like abusive behavior anymore. So... How to move on? Should I change the issue title and summary?

And because it's not fair to talk in public about people without their knowledge, I informed Rajan about this thread in #3445444-10: Unit/Kernel tests are incompatible with Drupal 11 → .

Yes, I'm new to the Drupal community. I'm learning Drupal and striving to give my best. When it comes to my contributions, there may be instances where my analysis was not entirely accurate. However, I will endeavour to improve myself and dedicate more time to understanding requirements.

Thank you for your valuable input.

@raffaelj @apaderno @vishal.kadam

https://www.drupal.org/project/rabbitmq/issues/3471515#comment-15753038 ✨ Add Drupal 11.0 Support Needs review Appears to be an example of on-going issues.

The feedback is a repeat of what automated testing already provide to maintainers. There is no indication the user tested the internals of the module. This is the same behavior as previously reported in this issue.

Briefly reviewing post history on https://www.drupal.org/user/3813580/track → it appears many issues are the same.

It does not appear the user has learned from previous resources provided on this thread and further action may be required.

Note: it appears the user is no longer listed as an employee under Virasat and new issues do not hold the Virasat as a beneficiary for credit.