Closed (fixed)
Project:
Drupal.org project ownership
Component:
Ownership transfer
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
4 May 2022 at 17:44 UTC
Updated:
19 May 2022 at 16:22 UTC
Jump to comment: Most recent
We'd like to request that ownership of the following modules which are currently owned by lreynaga be transferred to a new organizational account representing the University of Texas at Austin: https://www.drupal.org/u/utexas, to reflect our commitment to organizational stewardship of these modules.
- https://www.drupal.org/project/breadcrumbs_visibility
- https://www.drupal.org/project/page_title_visibility
Please let me know if we need to provide any additional information.
Comments
Comment #2
lreynaga commentedI am the current owner of the two modules listed above, and I approve this transfer of ownership to the
utexasuser.Comment #3
cmlaraThe 2 above projects appear to be covered by the security advisory policy.
It is my understanding that webmasters are prohibited from transferring security advisory policy covered modules to owners who are not vetted.
The utexas account does not appear to be vetted and appears from its profile to be a shared account which can not be vetted.
Setting as needs review for a webmaster to provide a more authoritative response..
Comment #4
avpadernoI changed ownership as requested.
Comment #5
avpadernoComment #6
gislecmlara, just to clarify the policy:
An organization account (such as "Information Technology Services University of Texas at Austin") are not allowed to commit code to the repo here. All commits must be done by natural persons. Hence, an organization account will never get the vetted role through project application peer review (there may be some organization accounts that was grandfathered into the role).
However, it is OK for an organization account to own projects. This is typical the case when a an IT organization with a staff maintains a project on Drupal.org. Staff leave and new staff join. By having the project owned by the organization, the organization management can administer maintainers, while the natural persons that are the staff commit code. Usually, at least one of the project's maintainers have the vetted role – in this case: https://www.drupal.org/u/mark_fullmer
So the site moderators will not transfer the ownership of a module covered by the security advisory policy to a natural person who is not vetted, but they may do so when the new owner is an organization that employs natural persons who are vetted.
Comment #7
cmlaraThank you for the clarification @gisle