Disturbing behavior by Specbee employee

Created on 13 July 2023, over 1 year ago
Updated 7 September 2023, over 1 year ago

I've noticed a rather disturbing behavior by one of our users, working for Specbee , with the job title "QA Test Engineer" (of all things!)

In the last few weeks, this individudal has posted in a large number of issues. His MO is to quickly move some patch posted in the issue queue to RTBC, apparently without even attempting to review what the patch does. Example: Comment #4 in this issue: 📌 Replace README.txt with README.md Closed: outdated

He also often uploads upload screenshots of his terminal showing that the patch applies, and the resulting directory listing. Neither provides any benefit to the project's maintainers. He also just repeats whatever automatic output warnings git produces (if any). Also, if there exists a valid merge request that supersedes an outdated patch, he ignores it.

Sometimes his strategy pays off. Here's the issues where he has received issue credit.

I don't think Specbee is well served by having a highly visible employee with such a perspective on QA testing and engineering. If somebody knows a point of contact, please make Specbee management aware of his behavior.

🌱 Plan
Status

Active

Component

User account

Created by

🇳🇴Norway gisle Norway

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @gisle
  • 🇩🇰Denmark ressa Copenhagen

    @gisle: Here's another instance of identical behavior by Specbee employee https://www.drupal.org/u/nupur-badola in 📌 Replace README.txt with README.md file Fixed .

    Page after page of checking if the patch applies, posting a screenshot and changing status to RTBC: https://www.drupal.org/user/3715602/track

    I guess all these RTBC's should be reverted?

  • 🇧🇪Belgium Frederikvho Belgium

    Dear @Gisle,

    I would like to add to ressa's #2 comment and to point out I just had a similar interaction with this other Specbee employee.

    https://www.drupal.org/project/webform_all_download/issues/3321717#comme... 📌 Replace README.txt with README.md Fixed

    I also e-mailed you about this. Sorry, only noticed just now that this drupal issue already covers both employees.

    Kind regards.

  • 🇮🇳India imalabya Bangalore

    Hi @gisle, I am Malabya, Drupal Practice Head at Specbee
    On behalf of Specbee, I would apologize for such behavior from one of our team members. However, she is not working with us any longer.

    Thanks, @ressa @Frederikvho for highlighting the issue. We have reached out to Nupur about this and explained what was she doing wrong. We are also conducting internal training to make people aware of the Code of Conduct while working on issues to mitigate such instances in the future.

    This is something we don't promote or sponsor at Specbee. We have been active contributors to the community since we started using Drupal and always encourage our team members to do their bit to drive the project forward. Although we do conduct regular Code of Conduct sessions, these mentioned instances clearly imply that we need more such sessions conducted internally. Again, I'd like to thank you for bringing this to our notice.

    Please reach out to me, on Slack or contact mail, if you notice any such cases in the future.

    Regards.

  • 🇳🇴Norway gisle Norway

    Malabya,
    it looks like you need to step up your internal training. One of your people (Sakthi Shanmuga Sundaram M is at it again. Please see: 🌱 Comment Permissions for Drupal 10 Active .

Production build 0.71.5 2024