Closed (fixed)
Project:
Drupal.org site moderators
Component:
User account
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
10 Jun 2019 at 10:29 UTC
Updated:
29 Jul 2019 at 10:14 UTC
Jump to comment: Most recent
Hi,
We are currently trying to upload the latest version of the Global Payments plugin. The upgrade includes optimization for SCA.
Need to be able to upload as soon as possible.
Thanks,
Katie
Comments
Comment #2
alonaoneill commentedPlease visit https://www.drupal.org/node/1887616 user for information on how to become a 'confirmed' user.
After you will do some work on Drupal.org this issue will be revisited!
Thanks
Comment #3
developers@globalpay.com commentedHello,
We have updates we would like to push to 2 of our modules:
https://git.drupalcode.org/project/uc_realex
https://git.drupalcode.org/project/commerce_realex
These updates are so our clients can successfully use 3D Secure 2 with our solution.
However, we are currently unable to push the code because we are not maintainers
Our profile is: https://git.drupalcode.org/developersglobalpay.com
Is this something you can assist us with?
Comment #4
avpadernoWelcome to Drupal.org! Getting the confirmed role doesn't allow to commit code on projects created by other users. For that, you need to offer to the project owner to become co-maintainer.
Keep in mind that shared accounts aren't allowed to commit code on Drupal.org repositories.
Comment #5
gisleProject is:
https://www.drupal.org/project/commerce_realex
It is owned by an individual, so that bit has been sorted out. I've confirmed the account so they can go ahead and create an organization page.
Please keep in mind that future commits should be from individual accounts.
I see that the company account has made one commit. I've think the shared account should not be allowed to commit to repos. I don't have permission to adminster users, so I am handing that task to kiamlaluno. Setting status to "Needs work".
Comment #6
avpadernoGiven the user just wants to push code on projects created by other users, the account should not have been confirmed.
The owner of https://www.drupal.org/project/commerce_realex has been stella since its creation. Nothing has changed as for who is the owner of those projects, except that developers@globalpay.com has been added as co-maintainer in one of those projects. (The other project is https://www.drupal.org/project/commerce_realex.)
I am closing this issue, as there isn't anything more we need to do.
Comment #7
gisleI do not understand this.
Our criteria for users are that their contribution:
I carefully reviewed this:
https://git.drupalcode.org/project/commerce_realex/commit/6f5d00f
It clearly shows knowledge about Drupal.
So IMHO this user meets our criteria for getting the confirmed role.
What is your reasoning behind stating that "the account should not have been confirmed"?
(Bear with me, I am trying to learn how to do the right thing here.)
Comment #8
avpadernoTo be able to commit code in projects created by other users, it's not requested to have the confirmed role, but be added as co-maintainer from the project owner or one of the maintainers of the project. The user should not have opened a request for us, since we don't add new co-maintainers to projects.
Yes, committing code in drupal.org repositories is an activity we check when giving the confirmed role, but giving the confirmed role doesn't allow the users to commit code in any project they want.
Comment #9
gisleAre you trying to say that users have opened up a request here and giving an invalid reason for the request must not be given the 'Confirmed' role? Why?
FYI,
since I got the 'Community' user role (and that was a considerable time ago). I've been confirming users that I come across in forums, issue queues, and repos, provided they are not spammers and contribute stuff that has some merit to the Drupal community. Until now, I haven't even bothered to check if they've opened up a request for the role here. There is a big green button on their profile saying "Confirm", and I assume it was put there by the DA to be used.
And after becoming a webmaster (about a week ago), I've continued doing this. The main reason I do this is because our automatic spam-filter is un-publishing false positives right, left and center, creating a very hostile environment for good members of our community that happens to not have the 'Confirmed' role.
Frankly, I don't think that asking for being confirmed for the wrong reason should disqualify anyone from being confirmed, provided I am able to review the account and check the account otherwise meet the qualifications for the role.
This particular account belongs to an organization, so they should go ahead and create an organization page. To have permission to create an organization page, the account needs the 'Confirmed' role (as pointed out in comment #5).
Comment #10
avpadernoIf the request for the confirmed role is done for the wrong reason, for example one of the following ones, as moderators we say that getting the confirmed role doesn't allow the users to do what they want to achieve, and we don't give the role. This doesn't mean the user will never get the confirmed role, but it will not be given for the reason reported in the request.