https://www.drupal.org/u/jabastinameex has commited code he clearly did not write himself without proper attribution. See: https://www.drupal.org/node/2753897#comment-11359681
I have removed him as co-maintainer of the module in question and put the right author in charge. It might be worthwhile to take a look at jabastian.ameex's other code.

The user also tried to gain co-maintainer access in another case with giving false statements: https://www.drupal.org/node/2755245#comment-11359331 (I should've noticed this directly but I am not at the top of my game lately due to lack of good sleep.)

In https://www.drupal.org/node/2751777 he got co-maintainer access by approval of the project owner. Might be a good idea to check if this code also is stolen.
Same here: https://www.drupal.org/node/2745731
Do we ban him?

Comments

dddave created an issue. See original summary.

mlhess’s picture

We could remove the git role.

dddave’s picture

Issue summary: View changes
avpaderno’s picture

The Git access page every account has comes with a Disable Git access for this user checkmark. Selecting it also sends an email saying:

Your Git access on Drupal.org has been disabled because it is in violation of
the terms of service (http://drupal.org/node/1001544). To seek reinstatement,
post an explanation of what happened and the steps you will take to correct the
situation to the Drupal.org webmasters issue queue
(http://drupal.org/node/1042972).

On the linked page, I don't find anything that applies to this case, but maybe we can disable the git access for a while, sending a different email.

WorldFallz’s picture

imo this is a clear violation of the copyrights clause on http://drupal.org/node/1001544. Just remove access.

mlhess’s picture

Status: Active » Fixed

I have removed access. I have included a link to this issue in the email that gets sent out.

dddave’s picture

Thanks.
Just for posterity to the other webmasters: I've noticed slightly shady/reckless behavior by other DrupalGeeks coders (but to a much lesser degree than the case here) which I adressed ad hoc in the issues itself. Might be worth an extra look when you come across issues with their participation.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

avpaderno’s picture