However, if you use the name of your company, product or brand as username, and you require Git vetted access, you need to make it clear that the account is for an individual. To make this clear, you should edit your user profile to show your real name. After clicking on "Edit", click on the vertical tab "Personal Information" and fill in the following two fields: "First or given name", "Last name or surname".
Please change the account name to make it clear that this is an individual account.
I addition this project has opted into being covered by the security advisory policy. It can only be owned by users that has permission to opt into this policy. The hCaptcha user does not have this permission.
The owner of a project can be a shared account, but that account cannot be used to commit code. That is described in Drupal.org Terms of Service - Accounts.
If you are sharing your user account with multiple people (e.g. as your “official” organization account), you are not allowed to do the following using this account:
commit code to Git repositories on the Website
create any nodes except for organization, case study or project nodes
comment on nodes
If you are sharing your user account with multiple people you ARE allowed to:
create project nodes
create organization nodes
create case study nodes
submit translations to localize.drupal.org
It's allowed to transfer a project to a shared account, but must be clear that account cannot be used to commit code in Drupal.org repositories.
Also, since the project opted into security coverage, it cannot be maintained from users who don't have the vetted role. Even supposing that the hcaptcha account weren't a shared account, it could not be used to maintain (committing code into) that project, because that account doesn't have the vetted role and has not consented to the Git agreement.
You will still be able to commit code, since you have the Write to VCS permission on that project. New co-maintainers will need to get the permission, in order to commit code.
Comments
Comment #2
newsec commentedComment #3
gisleProjects can only be owned by individual accounts, please see: Guidelines for username for a Git vetted account:
Please change the account name to make it clear that this is an individual account.
I addition this project has opted into being covered by the security advisory policy. It can only be owned by users that has permission to opt into this policy. The hCaptcha user does not have this permission.
Comment #4
avpadernoThe owner of a project can be a shared account, but that account cannot be used to commit code. That is described in Drupal.org Terms of Service - Accounts.
It's allowed to transfer a project to a shared account, but must be clear that account cannot be used to commit code in Drupal.org repositories.
Comment #5
avpadernoAlso, since the project opted into security coverage, it cannot be maintained from users who don't have the vetted role. Even supposing that the hcaptcha account weren't a shared account, it could not be used to maintain (committing code into) that project, because that account doesn't have the vetted role and has not consented to the Git agreement.
Comment #6
newsec commentedIt is ok if other co-maintainers will be able to commit the code.
Comment #7
avpadernoYou will still be able to commit code, since you have the Write to VCS permission on that project. New co-maintainers will need to get the permission, in order to commit code.
Comment #8
avpadernoI changed ownership as requested.
Comment #9
newsec commentedThanks kiamlaluno.