Problem/Motivation

I would like to become a co-maintainer of the Flags module. I have been actively contributing to the module and want to help ensure it continues to receive maintenance and support for current and future Drupal versions.

My contributions to Flags:

I also maintain the Country module, which integrates well with Flags.

Proposed resolution

I am requesting co-maintainer permissions for the Flags module, including the ability to:

  • Merge code to the repository
  • Manage issues in the issue queue
  • Create releases

My primary goal is to create a stable release that is covered by Drupal's security advisory policy, as requested in https://www.drupal.org/project/flags/issues/3263294.

I am committed to:

  • Reviewing and testing patches
  • Maintaining code quality and following Drupal coding standards
  • Ensuring comprehensive test coverage
  • Responding to community needs and security concerns
  • Coordinating with the current maintainer(s)

Remaining tasks

  • Current maintainer(s) to review my contribution history
  • Community review period
  • Grant maintainer permissions if approved

Comments

batigolix created an issue. See original summary.

batigolix’s picture

Project: Flags » Drupal.org project ownership
Version: 2.0.0-alpha1 »
Component: Miscellaneous » Maintaining offer

I received an email of one of the maintainers. He says he hasnt been on drupal.org for years and does not know how to add maintainers.

avpaderno’s picture

Category: Support request » Task
avpaderno’s picture

I am contacting the only maintainer with the Administer maintainers permission, matsbla, who is the project owner.

avpaderno’s picture

This is the message I sent.

Hello matsbla,

I am contacting you because Boris (https://www.drupal.org/u/batigolix) offered to become maintainer for Flags (https://www.drupal.org/project/flags), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3567794 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Boris will be probably made maintainer.

I am contacting all the project maintainers, and the project co-maintainers with the "Administer maintainers" permission, who logged in at least once in the past 12 months. In this case, that is just you.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on the offer issue. We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Active » Postponed

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder that a project moderator's action is required.

batigolix’s picture

Status: Postponed » Needs work

I did not receive any news on this. Can we proceed ?

Thanks for your efforts.

avpaderno’s picture

Status: Needs work » Fixed

I added batigolix as maintainer.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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