Token Filter has nearly 10k sites currently reporting using it. It's time for a 7.x-1.2 release of this module.

The project page may be out of date, but looking at activity in contrib on d.o it occurred to me that we don't really have a good process for bringing on co-maintainers. Not that there isn't a process to make it happen, but it is all very mechanical.

Ultimately there are always going to be many more users than developers in any successful project. That being said, for a popular module like this, a module maintainer should be able to choose. I've tried to outline #2185511: Highlight User Contributions & What They Can Do Next in Issue Queue how to encourage people to start participating in projects. A project like this one that is actively Seeking co-maintainer(s), should have some way to more actively remind folks in the issue queue that help is being requested.

Now it could be just dealing with the issue queue or building up enough knowledge about the module that they can effectively test a number of outstanding patches. Maybe it's working on the D8 version. Maybe something like documentation or tests. In an actively used module there is always going to be something.

Having a goal can also help. I've proposed #2186377: Highlight projects that follow Best Practices but I'm really not sure what can arbitrarily be evaluated.

I started off by looking incentives for getting people involved in the issue queue and thought both of these might help - #2138397: Highlight Flattr, Paypal or Whatever Opportunities on Issue Pages & #2177459: Highlight Supporting Organizations in the Issue Queue

Having new ways to alert people in the Drupal community how they might engage is useful. http://www.comaintainer.com was set up to try to gather together information about modules like this one that were looking for support maintaining the code base.

I'm starting this issue in the hopes of having a discussion with this community about what would help more people step up and take on the responsibility of helping to maintain this module.

Comments

Dave Reid’s picture

Only one commit since the last release and one RTBC issue in the queue, I don't think there's really much needed here frankly. Just having more people reviewing patches in the issue queue might be nice, but on the long list of "modules that need help" I think this is pretty far down.

mgifford’s picture

Agreed. It's not on the top of the pile. But it's interesting to see those that have used the Maintenance status to clearly call for a co-maintainer. This is folks clearly saying they don't have time to properly manage this module and inviting others to take a role.

Having more folks reviewing patches would be good. @johnbarclay had a good idea here #2200855-1: Time for a Stable Release & More Co-Maintainer - maybe there's a way to encourage folks to review other patches in a more active way after they have posted one....

It's also an issue of critical mass. If 10k sites donated a $1 a year to have a stable D7 release of this module, I think it would probably be much easier to have it maintained.

I'd like to have a definition of what a well maintained module is. I think it would be an interesting guide to strive for.

When in doubt, this is just a stub to talk about the next release. Maybe we can inspire folks to take on reviewing these issues so it's worth rolling up a new one:

Dave Reid’s picture

I also think that the co-maintainers wanted was from before I joined with the D7 branch. We might just remove that from the project page.

mgifford’s picture

Makes sense. Thanks Dave!

darvanen’s picture

Status: Active » Closed (outdated)