Requests to become project owner, maintainer, or co-maintainer

Requirements for people who want to be maintainer/co-maintainer or project owner

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 maintainer/co-maintainer or project owner. However, shared accounts can be project owners, even for a project covered by Drupal's security advisory policy.

Project moderators will not add as owner, maintainer, or co-maintainer a person who cannot opt projects into security advisory coverage, when a project is covered by Drupal's security advisory policy. In that case, the request needs to be accepted by project maintainers. Project moderators will make maintainer a co-maintainer who cannot projects into security advisory coverage since, in that case, no new people is added to the group of maintainers/co-maintainers.

See Apply for permission to opt into security advisory coverage for details on how to obtain that permission.

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

Issues created to become project owner, maintainer, co-maintainer, or take over a project namespace, need to be created in the project issue queue and stay there at least 14 days. If none of the project maintainers posts a comment in the created issue to decline or accept the request, the issue can be moved in the Drupal.org project maintainership queue.

The person who moves the request from the project issue queue to the Drupal.org project maintainership issue queue is expected to be the person who created the request, not another person, even if that person is a co-worker. When the person who created the request moves the issue to the Drupal.org project maintainership issue queue, that person is implicitly saying to still be interested in being maintainer/co-maintainer or project owner. Without that confirmation, the request will not be handled.

Project moderators will only handle a single request per issue. Please do not use an issue created by another person, even if the original request was created by a co-worker, or that issue has not been completed for any reason. Instead, open your own issue.

Becoming owner, maintainer, or co-maintainer of a project

If you are a developer who have been working in the issue queue of a Drupal-contributed project, and you find that your work is being ignored by the maintainers/co-maintainers, the patches you've carefully reviewed do not get committed, or there is no progress, you may be interested in becoming co-maintainer/maintainer or the new project owner. You could also use this procedure if you are a co-maintainer and you think it is more appropriate for you to become maintainer or project owner.

=== Project owner

• File an issue in the project's queue, 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 maintain <project_name>. (Replace <project_name> with the project name shown on the project page, not its machine name.)
• 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. This step is not mandatory, but it can speed up the process to become the new project owner.
• 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. 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 two weeks (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. 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 that they are no longer active in the Drupal community, giving to the contacted project maintainers two weeks (14 days) to reply to the message that they have sent via the Contact tab.
• Leave a comment 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/co-maintainer

• File an issue in the project's queue, stating your interest in becoming maintainer or co-maintainer. 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 maintain <project_name> or Offering to co-maintain <project_name>. (Replace <project_name> with the project name shown on the project page, not its machine name.)
• 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. This step is not mandatory, but it can speed up the process to become maintainer or co-maintainer.
• 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 or co-maintainer, the issue is fixed.
• If the project maintainers agree to make you maintainer/co-maintainer, but do not make any change, create a new issue in the Drupal.org project maintainership issue queue. Please include a link to the project page. If the project maintainers privately agree to make you maintainer/co-maintainer, ask them to post a comment on the issue you created.
• If the project maintainers do not reply in two weeks (14 days) since the request appeared in the project issue queue, move the issue to the Drupal.org project maintainership issue 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 two weeks (14 days) to reply to the message that they have sent via the Contact tab.
• Leave a comment 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.

=== Co-maintainer to be maintainer or project owner

In some cases, the project maintainers may have added additional co-maintainers without granting them permissions like Administer maintainers or Administer releases. This is an acceptable decision, at the discretion of the project maintainers.

However, in those cases, if the project maintainers are no longer present or have not committed code in the project, and these co-maintainers are willing to take over the project, or simply become maintainers, they could create an issue in the project issue queue, following the procedure described in the previous sections. Project moderators will still contact the project maintainers (including the project owner), when at least one of them logged in on drupal.org.