Requests to become project owner, or maintainer

Requirements for people who want to be project owner or maintainer

• Shared (corporate) accounts are not allowed to commit code to the Drupal.org repository and cannot gain permission to opt into security advisory coverage. This means that shared accounts cannot be used to request to be project owner or maintainer. However, shared accounts can be project owners, even for a project covered by Drupal's security advisory policy, although they cannot be used to make commits.
• Project moderators will not add as owner or maintainer a person who cannot opt projects into security advisory coverage, when a project is covered by Drupal's security advisory policy. Project moderators will give more permissions to a maintainer who cannot opt projects into security advisory coverage since, in that case, no new people is added to the group of maintainers.

Requirements for the issues created to become project owner, take over a project namespace, or become maintainer

• For requests to take over a project namespace because a trademark in the project name, the issue created in the project issue queue and in the Drupal.org project maintainership queue can be created at the same time.
• Requests to take over a project namespace (except the ones created because a trademark in the project name), or become project owner or maintainer, need to be created in the project issue queue and stay there at least fourteen (14) days.

Becoming owner or maintainer

If you have been working in the issue queue of a Drupal-contributed project, and you find that your work is being ignored by the maintainers, the patches you've carefully reviewed do not get committed, or there is no progress, you may be interested in becoming maintainer. You could also use this procedure if you are a maintainer, and you need more permissions to make any project progress.

Project owner

• File an issue in the project's queue, explicitly stating your interest in becoming the new project owner. Adding links to issues for the relevant project in which you have added merge requests or patches or where you have reviewed merge requests or patches from other users will help demonstrate that you are actively involved in the project. Describe the motivation behind your request. (For example, you are already using the project, and you want it to be well-maintained.) For the title, use Offering to be project owner for <project_name>. (Replace <project_name> with the project name shown on the project page, not its machine name.)
• (Highly preferred) If enabled, use the Contact tab on the project maintainers' profile page. Request that a comment is posted on the issue you have created. We need a comment on the issue you opened to see what the decision has been.
• If you contacted the project maintainers, report in the issue summary which project maintainers have been contacted regarding the request and how you contacted them.
• If the project maintainers agree to make you the new owner, create a new issue in the Drupal.org project maintainership issue queue with the same title used for the issue in the project queue. Please include a link to the project page and a link to the issue you created in the project queue. If the project maintainers privately agree to transfer ownership, ask them to post a comment on the new issue.
• If the project maintainers do not reply in fourteen (14) days since the request appeared in the project issue queue, create a new issue in the Drupal.org project maintainership issue queue with the same title used for the issue in the project queue. Please include a link to the project page and a link to the issue you created in the project queue. Project moderators will normally try to contact the project maintainers as an extra safeguard, unless it is evident they are no longer active in the Drupal community, giving to the contacted project maintainers fourteen (14) days to reply to the message that they have sent via the Contact tab.
• Leave a comment fourteen (14) days after the project maintainers have been contacted by project moderators, if none of the project maintainers rejected the request. The comment will show you are still interested in the request, and it will allow project moderators to notice they need to take action on the issue. Without that comment, no change will be done to project maintainers.

Maintainer

• File an issue in the project's queue, explicitly stating your interest in becoming maintainer and which project permissions you need between: Write to VCS, Edit project, Administer maintainers, Maintain issues, and Administer releases. Having both the Write to VCS and Administer maintainers permissions is necessary to be able to change the default branch for the project.
• Add links to issues for the relevant project in which you have added merge requests or patches or where you have reviewed merge requests or patches from other users will help demonstrate that you are actively involved in the project. Describe the motivation behind your request. (For example, you are already using the project, and you want it to be well-maintained.) For the title, use Offering to maintain <project_name>. (Replace <project_name> with the project name shown on the project page, not its machine name.)
• (Highly preferred) If enabled, use the Contact tab on the project maintainers' profile page to contact them. Request that a comment is posted on the issue you have created. We need a comment on the issue you opened to see what the decision has been.
• If you contacted the project maintainers, report in the issue summary which project maintainers have been contacted regarding the request and how you contacted them.
• If the project maintainers reply and set you up as maintainer, the issue is fixed.
• If the project maintainers agree to make you maintainer, but do not make any change, create a new issue in the Drupal.org project maintainership issue queue with the same title used for the issue in the project queue. Please include a link to the project page. If the project maintainers privately agree to make you maintainer, ask them to post a comment on the issue you created.
• If the project maintainers do not reply in fourteen (14) days since the request appeared in the project issue queue, create a new issue in the Drupal.org project maintainership issue queue with the same title used for the issue in the project queue. Please include a link to the project page. Project moderators will normally try to contact the project maintainers as an extra safeguard unless it is evident that they are no longer active in the Drupal community, giving to the contacted project maintainers fourteen (14) days to reply to the message that they have sent via the Contact tab.
• Leave a comment fourteen (14) days after the project maintainers have been contacted by project moderators, if none of the project maintainers rejected the request. The comment will show you are still interested in the request, and it will allow project moderators to notice they need to take action on the issue. Without that comment, no change will be done to project maintainers.