A year has passed since the D7 release, with strangely absent maintainers.
Several bugs has either seemingly been fixed but not committed, or insufficiently fixed without any attention or feedback from the current maintainers.
Numerous requests for maintainer feedback has been posted throughout 2011 with either zero or close to that response from those with commit privileges.

Several bug fixes are important, for example the one that breaks Views 3.x integration simply because the referenced table is called comment and not commentS in D7... Even such a simple "fix" has not even been committed to the -dev release.

Given the nature and importance of this very module ("voting API"...), which so many community features rely upon, means that it is holding back many web sites and projects on D7.

IMO, this is far below what can be expected for such an important module in an open source community like ours. Below our own standards, so to speak.

What does this mean?
More (or new?) maintainers needed?
The status of maintenance and development are both currently "Unknown" on the module page.

The current maintainers are possibly too busy elsewhere, and certainly deserves all the credit for bringing this module up to this point, but we have to get out of this deadlock asap.

Comments

rogical’s picture

rogical commented

maybe can start Dealing with abandoned projects

eaton’s picture

eaton commented

IMO, this is far below what can be expected for such an important module in an open source community like ours. Below our own standards, so to speak.

In a nutshell, none of the projects I've worked on for the past year or two have involved VotingAPI A number of co-maintainers have been added over the past couple of years but none appear to have gotten traction on working on the module. More recently, fuhby has taken up the mantle of a complete re-write in the form of the "Vote" project, but it appears to be stalled currently.

If there's any interest in a co-maintainer position, I'd be happy to add another developer.

eaton’s picture

eaton commented

FYI, FatGuyLaughing has been added as a new maintainer -- he's working on projects that need/use VotingAPI, which means that he'll be closer to it than I am at the moment, and I have high hopes. ;-)

Steven Brown’s picture

Steven Brown commented

After I dive into the guts of Voting API to make sure I understand how everything is working together. I will then create a flowchart/diagram that I probably will link to in case anyone else is interested. I will also start answering more issues after fully knowing the module.

Taxoman’s picture

Taxoman commented

great :)

torotil’s picture

torotil commented

I've just started a "fork" on github to maintain some of the bugfixes needed for my deployment. You can find the git-repository at https://github.com/torotil/votingapi .

Taxoman’s picture

Taxoman commented

For future reference, discussion at: #1105768: Discussing Vote and VotingAPI, and a closed one at #1073998: Vote (VotingAPI on steroids)

rogical’s picture

rogical commented

Is there any updates? Actually, I have much time and willing to maintain this module if possible.

Found that there's no new commits for a long time.

Steven Brown’s picture

Steven Brown commented

Sorry about the progress. I've been on a project for work that has taken roughly 80 hours of my weeks. So I haven't had much time for anything else. I'm going to have to step down on this one. However, I will do my best to help in the issue queue.

rogical’s picture

rogical commented

Why not add more maintainers, Toxoman? tortilla? Nothing new happen.

torotil’s picture

torotil commented

I'd happily help out to move this module along a bit. Anyone care to make me a co-maintainer?

rogical’s picture

rogical commented

Maybe send mail to the sponsor eaton, any updates?

torotil’s picture

torotil commented

Nothing new on this front. I think I've contacted eaton a while ago … but nothing happened.

eaton’s picture

eaton commented

The current maintainers are possibly too busy elsewhere, and certainly deserves all the credit for bringing this module up to this point, but we have to get out of this deadlock asap.

The responsibility is definitely mine -- apologies for the delay on this front. You're correct about the cause; none of the projects I've worked on for more than a year or two have used VotingAPI, and a while other maintainers who've been brought on board over the past year to help give it some additional attention, they've turned out to be too busy as well. Arrrr!

As per his request, I've added torotil as a maintainer; to start out, I do want to ask that you stick to bug fixes and non-breaking patches for the time being until we have a chance to touch base -- a number of people have come on board with dreams of totally rewriting the entire API, and then faltered when they realized some of the complexity of the contrib-space modules that use the API...

rogical’s picture

rogical commented

Yes, Never easily change the API of an API module, Like other modules, API change should go to newer branch.

torotil’s picture

torotil commented

Thanks, for making me co-maintainer. Surely I have ideas for a future votingapi, but I'm also running two projects right now that use the current stable versions that would benefit a lot from getting those bugs fixed … Let's see what I can do about it.

rogical’s picture

rogical commented
Status: Active » Fixed

Glad we have new active maintainer!

BTW, pls apply patch with --author="xxx"

torotil’s picture

torotil commented
Assigned: Unassigned » eaton
Status: Fixed » Needs work

not yet: It seems that I don't have the permission to edit the project (description, release management, …).

torotil’s picture

torotil commented
Status: Needs work » Closed (fixed)

I finally have all the permissions I need.