Employees of https://www.drupal.org/opensense-labs → have been involved in several reports of credit farming or negative contribution.
https://drupal.slack.com/archives/C0451JV7HRD/p1714321728701869
In this slack thread can see that employees were posting responses that were generated from an AI bot. Providing no meaningful conversation to the issues at hand.
The user has sense gone back and removed all their responses and an employee from OSL did post to the thread
Hi, I am Anmol Goel, from OSL.
We have discussed this case internally and has taken action against this user and this will not be repeated. Please let me know if you find any case where people from OSL are not following the contribution guidelines.
Sorry for the inconvenience caused.
These slack threads can show the discussions around it
https://drupal.slack.com/archives/C0451JV7HRD/p1714331486445819
https://drupal.slack.com/archives/C0451JV7HRD/p1714420137551469
https://drupal.slack.com/archives/C0451JV7HRD/p1714519301621349
Essentially users from OPL were blindly applying suggestions without testing or verifying the changes. In some cases causing issues to break or requiring someone to revert what they did. In these scenarios the users never returned to the ticket to address what they broke so goes back to an old issue where users thought posting 1 solution counts as credit.
In several of the tickets around fixing the permissions in 📌 [Meta] Fix all tests that rely on UID1's super user behavior Active users from OSL were doing empty commits or just deleting the temporary code but not attempting to fix the actual issue of updating permissions. For this they did not receive credit.
In the third channel a core committer opened 📌 Branch 10.4.x Fixed which is just a core committer task but an OSL employee made a commit branch anyway. Will note in this thread the user did apologize and ask for some material for doing positive contribution.
Overall these have caused great community frustration in a very short time. As well as time to go back and undo these changes.
TBD - to be filled in by site moderator.
Active
Spam
Appreciate that this is framed as a training issue to start.
I will reach out with more resources, in addition to what we have provided in the Slack thread where some of these users responded already.
If the organization is unresponsive to the training material, we will move to warnings and apply the Credit Abuse Policy → as appropriate.