Problem/Motivation

https://www.drupal.org/project/token_custom is a super helpful project, which we use in many projects since Drupal 7. Sadly there are several RTBC'd issues and issues in progress, which didn't get maintainers attention recently.

To help pushing things forward at Custom Tokens I'd like to offer my help as maintainer.

See my profile for references and other maintained projects.

Thanks a lot in advance.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Anybody created an issue. See original summary.

quietone’s picture

@Anybody, Hi, are you still interested in pursuing this? I ask because I am working to make sure that documentation is moved from the old system and the docs for this module are still on the old system. It would help greatly to have an active maintainer here.

anybody’s picture

Hi @quietone, yes! We're actively using this in many projects and my offer still stands :)

It's quite a lot of modules our three persons company maintains, so don't expect too much activity, but surely I'll have a look at the issues and do the housekeeping! Agree that this definitely needs active maintainers. We should then also add @Grevil.

anybody’s picture

Project: Custom Tokens » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer

Moving this over accordingly.

anybody’s picture

Status: Active » Needs review

@quietone and the others: Any plans here? No reply yet... We'd like to take this to Drupal 11!

anybody’s picture

grevil’s picture

Project: Drupal.org project ownership » Custom Tokens
Version: » 8.x-1.x-dev
Component: Maintaining offer » Code
grevil’s picture

Project: Custom Tokens » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Code » Maintaining offer
grevil’s picture

Hey @avpaderno, we already moved this request to the project ownership back on 8th November 2024, without any reply.

It seems like you don't want to get contacted via drupal.org, so I moved the request once again for visibility’s sake.

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Needs review » Postponed

hanoii, the only person who can add maintainers/co-maintainers, logged in on drupal.org at least once in the past seven days. I am going to contact him in the next four hours.

anybody’s picture

Thanks @avpaderno! :) I also wrote him but got no reply at all.

avpaderno’s picture

In some cases, they reply to messages sent from site moderators / project moderators. If he does not reply, we will be back in 14 days. 😉

avpaderno’s picture

This is the message I sent.

Hello Ariel,

I am contacting you because Julian (https://www.drupal.org/u/anybody) offered to become maintainer for Custom Tokens (https://www.drupal.org/project/token_custom), 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/3406253 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, Julian will be probably made maintainer.

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 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.
If there is any reason for not giving Julian all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3406253.

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.
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 an action is required for this offer.

anybody’s picture

Thank you @avpaderno much appreciated.

hanoii’s picture

Hi All, I got all emails, sorry for not getting back, keep wanting to. Today's activity of @anybody reminded me of that. Will add set him up and close this issue.

anybody’s picture

Thank you so much @hanoii! Could you maybe also add my team-mate @Grevil as Co-Maintainer? That would be super helpful.

Furthermore, it would be great to have elevated permissions for GitHub to for example being able to edit the default branch: https://git.drupalcode.org/project/token_custom/-/project_members

Currently that's only possible for full Maintainers.

Thank you!

hanoii’s picture

Status: Postponed » Fixed

@anybody has been added as co-maintainer. I might probably clean up some of the other maintainers as I don't think they have been active in the module.

hanoii’s picture

I'll add Grevil. Full maintainers means just giving you the administer maintainer option? no prob

hanoii’s picture

Did that and added @grevil. I will look into removing other maintainers sometime over the week. If you wish to do that yourself based on their d.org activity and/or the module, please do.

Thanks for taking interest on this module. I am personally not currently using it so it got behind in my support priority, but I know it has progressed on its own. I will take a look on the shape of it and maybe give it another chance.

anybody’s picture

Thank you very very much @hanoii! Custom Tokens is great and we love it since Drupal 7!
We'll care for all the 8.x issues in the next weeks, asap! :)

And yes, cleaning up inactive maintainers would make sense, also for security reasons. Thank you!

avpaderno’s picture

hanoii’s picture

FWIW, I removed all previous mantainers, latest commit from anyone was circa 2020, if they ever express the will to be added again, we can revisit.

If at all possible I'd recommend releasing a new stable 2.0.0 as soon as you see best. Also, would you be open to help maintaining the D7 version of it? No need honestly, but just wondering if you are open to it.

I saw lrwebks which I assume you added.

Thanks for pushing the module forward.

anybody’s picture

Thanks @hanoii, right. I added lrwebks to support us, I'll manage his Co-maintainership.

We're also using the D7 version, so generally yes, BUT ( :P ) Drupal 7 will be EOL in January 2025 so I think it won't make sense to invest much time anymore? We might just have a look at major bugs?

And yes, we'll tag a new 2.0.0 release once we have tested all the latest final changes again and have some tests in place, I'd say?

Status: Fixed » Closed (fixed)

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