I need to transfer ownership of ww_publish (https://www.drupal.org/project/ww_publish) to this user:
https://www.drupal.org/u/schluetersche
Thanks!

Comments

Antonín Slejška created an issue. See original summary.

gisle’s picture

Assigned: Unassigned » gisle
Status: Active » Postponed (maintainer needs more info)

Fine. Please make schluetersche comment here and confirm that he accepts the ownership.

avpaderno’s picture

Assigned: gisle » avpaderno
Status: Postponed (maintainer needs more info) » Fixed

Confirmation isn't required, when the ownership transfer comes from the project owner. (In this case, the project owner is also the user who created the project, but that doesn't make any difference.)

Since the project is not covered by Drupal’s security advisory policy, the new project owner doesn't need to have the vetted role. I changed ownership as requested.

gisle’s picture

Confirmation may not be required, but IMHO, it is desirable. Ownership usually means that the owner is supposed to monitor the issue queue and to some extent being committed (YMMV) to maintaining the project.

Therefore, I prefer that the new owner acknowledges the ownership transfer, just to make sure the new owner is actually aware of the transfer taking place.

antonín slejška’s picture

The confirmation will be done. Thanks!

schluetersche’s picture

We'll accept the Ownership of this project!

gisle’s picture

schluetersche,
thank you for confirming.

As a new community member, you may also want learn about Issue Etiquette.

antonín slejška’s picture

Thank you Gisle,

it is a profile of the company, where do I work: https://schluetersche.de/

The company develop and use the module...

Best regards
Antonin

gisle’s picture

Antonín Slejška,
thanks for the heads-up - I was under impression that this was an individual account.

It is OK for a company account to own a project, but please note that all commits to the project must be done by individuals:
https://www.drupal.org/docs/develop/git/setting-up-git-for-drupal/obtain...

avpaderno’s picture

No, delaying an action that may already be taken isn't desirable. The request comes from the user who has the right to ask for other users to become the project owner; acting on the request doesn't mean removing the user from the project maintainers.
Apart verifying the request can be acted upon, which means that a project covered from security advisory policy doesn't get as project owner a user without vetted role (from Drupal.org site moderators), there isn't any reason not to do as requested.

It's also not true that the project owner is requested to monitor the issue queue. This is not the case when the project owner is a shared account, which should not used to comment or post issues. (See Drupal.org Terms of Service / Accounts.)

gisle’s picture

I agree that when the requested owner is a corporate user, there is no reason to delay the transfer of ownership.

However, there was nothing in the request that suggested that "schluetersche" was a company user.

antonín slejška’s picture

@gisle: The schluetersche account will be used only to manage the maintainers. The developers have personal accounts.

Status: Fixed » Closed (fixed)

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