I see that the current branch last release was 2022, offering to come in and help get this module ready for D11.

My approach on other modules has been a new branch for just D10 + D11 so things for php8.1 can be used. And I see a number of issues in review so would probably include in a new 2.0.x branch so that 8.x-1.x stays roughly the same.

I typically close all tickets around README or PHPCS. Will rely on the gitlab findings, which I would also address under the D11 bot ticket.

Currently maintain about 25+ modules and a sub-maintainer on core

Comments

smustgrave created an issue. See original summary.

smustgrave’s picture

smustgrave commented

Got ahead of myself and started triaging a few issues

Most just need test coverage which I have contribution time next month so I could tackle .

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Hi @smustgrave, I'd be super happy to see you as Co-maintainer! +100% ;)
Sadly I can't administer maintainers and the other maintainers seem a bit inactive currently: https://www.drupal.org/project/extlink/maintainers.json

For that reason I'd even suggest making you maintainer (not co-maintainer) and I'd offer the same to be able to manage maintainers.
See https://www.drupal.org/project/extlink/maintainers.json

smustgrave’s picture

smustgrave commented

Thanks @Anybody I've sent emails to the other 3 maintainers as well.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Offering to co-maintain External Links » Offering to maintain External Links
Category: Plan » Support request
avpaderno’s picture

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

I contacted the maintainers as project moderator. This is the message I sent to quicksketch.

Hello Nate,

I am contacting you because Stephen (https://www.drupal.org/u/smustgrave) offered to become maintainer for External Links (https://www.drupal.org/project/extlink), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/extlink/issues/3456760 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
In the case you accept the offer, you can also add Stephen as maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
Without a comment posted on that issue in the next 14 days, Stephen will be probably made maintainer.

Neither project moderators nor site moderators will 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.

A last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the 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.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

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

The status has been changed because we are waiting for a reply.

elachlan’s picture

elachlan commented

Done.

smustgrave’s picture

smustgrave commented
Status: Postponed » Fixed

Much appreciated!

quicksketch’s picture

quicksketch
he/him
commented

Hi folks, the more the merrier in my opinion! Thanks @smustgrave for volunteering and @elachlan for accelerating the process. I'm no longer involved in the current versions of extlink or most other contrib projects so I'm happy to see this work distributed to more developers. I'll ask that you please try to continue as much backwards-compatibility as possible. Even major refactorings are okay, as long continuous upgrade hooks are in place. Thanks and welcome!

smustgrave’s picture

smustgrave commented

Absolutely! I started #3457153: Stable 2.0.0 release to help track fixes going in. Anything major fully plan to backport till we can do a stable release of 2.0.0 and for that more want time to pass and more people to try it out.

We just updated it and have not noticed any issue yet.

Status: Fixed » Closed (fixed)

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