https://www.drupal.org/project/address_autocomplete

I am a user of this module. It frequently goes without compatibility and maintenance work for long stretches of time.

I am offering to become co-maintainer, to ensure the module remains up to date and compatible with new versions of Drupal and addressing bugs reported by other users.

I also want to finish the remaining tasks needed to make a stable release of the module and have it under security coverage.
#3527350: Remaining tasks for stable release
#3527159: Implement validation tests

Some issues in this module I was involved in
#3226560: Commas in an address breaks autocomplete
#3260954: Administrative area is not handled
#3341452: Add Google places autocomplete provider
#3260958: Filter autocomplete suggestions by selected country

I will consult with other maintainers whenever I encounter something I do not have sufficient experience with or when making decisions that affect the feature set / design of the module.

I maintain several other modules and have an extensive contribution history to contrib modules.

Comments

rhovland created an issue. See original summary.

rhovland’s picture

rhovland
he/him
Primary language English
Location Oregon
commented
Project: Address Autocomplete » Drupal.org project ownership
Version: 1.0.x-dev »
Component: Miscellaneous » Maintaining offer
Issue summary: View changes

I contacted vaish and criz via the contact form around 25 Feb 2026. The other two have contact disabled.

vaish responded via email saying they didn't have permission to add maintainers and couldn't help further. Suggested contacting criz but I received no reply from them.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: Unassigned » avpaderno
Category: Support request » Task

The only person with the Administer maintainers permissions is criz. He logged in at least once in the past 30 days, so he will be contacted.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: Maintaining offer » Co-maintaining offer
Status: Active » Postponed
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

This is the message I sent.

Hello Christian,

I am contacting you because rhovland (https://www.drupal.org/u/rhovland) offered to become co-maintainer for Address Autocomplete (https://www.drupal.org/project/address_autocomplete), 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/3575804 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, rhovland will be probably made co-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 co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
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

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.

rhovland’s picture

rhovland
he/him
Primary language English
Location Oregon
commented

Still interested in maintaining this module.

vaish’s picture

vaish commented

I'm one of the current maintainers of the module but I don't have "Administer maintainers" permission. I'm in support of @rhovland being added as a co-maintainer.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Fixed

I added rhovland as co-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.

vaish’s picture

vaish commented

Thank you, avpaderno.

cmlara’s picture

cmlara
he/him
commented

@hestenet may have upgraded rhoveland to Maintainer, see Slack thread https://drupal.slack.com/archives/CGKLP028K/p1778786095171489 where @rhoevland requested higher level permission to make branch changes.

rhovland’s picture

rhovland
he/him
Primary language English
Location Oregon
commented

To be clear I asked what I should do about not having access to manage branch settings when the only person with permmission to do that has not been responding to attempts to contact them and my permissions were changed. If I need to submit a new request to be a maintainer I will do it. I did not know co-maintain meant developer I thought it meant become a cooperative maintainer as a group of people who have maintainer access.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

@rhovland Since you have been made maintainer from hestenet, there is no need to create a new issue.
The fact that to be able to change the default branch requires to be maintainer on the drupal.org side is caused by a mismatch with the GitLab roles and permissions. When the default branch was set on drupal.org, it was sufficient to have the Edit project permission, which project moderators assigned to co-maintainers.

Status: Fixed » Closed (fixed)

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