The last commit for Fivestar was 18 months ago, yet there are over 30 patches (including one of mine Conflict with the preview for comments) in "Reviewed & tested by the community" or "Needs review" status. The module has over 28,000 users, of which about 18,000 use the D7 version. Sadly the usage peaked at 38,000 last August, but is now trending down quite rapidly. Fivestar is also taught in several Drupal books, indicating that it's liked by the Drupal community.

I appreciate all of the hard work done on this module from inception to its current state, and would like to build on that work. Why? I discovered Drupal about three months ago, and love it. I think the best way for me to get deep into Drupal coding is to maintain/co-maintain a module with a substantial issues list. Qualifications? Developer for over 30 years, and in my day job manage a development department of over 100 people and have responsibility for the architecture of a complex real-time system.

I'd be happy to take over "ownership", or to be a co-maintainer. If the former, I'd also be happy to have co-maintainers.

My approach would be to create a new 7.x-2.0-alpha3 branch from the current 7.x-2.x-dev branch plus all outstanding patches which are valued/in use by the community. Next, review all issues for 7.x, close out duplicates (of which there are many), and fix "Critical" and "Major" bugs (help from the community welcome!). From this, create the first "official"/stable release for D7, 7.x-2.0. After that, work on other bugs and feature requests for the D7 version, and prepare to migrate to D8. I wouldn't be able to work on the D6 version, but would be happy to code review any patches in "Reviewed & tested by the community" and commit them into the 6.x-2.x-dev branch on behalf of the authors.

Let me know what you think of my approach, and if this is a useful thing to do.

Comments

david_garcia’s picture

david_garcia commented

Have you tried to get in touch directly with any of the maintainers? That usually works.

Voting API, that is base for Fivestar, is also lagging behind.

I wish Drupal integrated crowd funding mechanisms to get the modules going....

whiteph’s picture

whiteph commented

Yes. I mailed @ericduran offering help on 14th December, no reply as yet. I'm now following the process defined in Dealing with unsupported (abandoned) projects.

The crowdsourcing idea is good, you should take it up with the Drupal powers that be.

whiteph’s picture

whiteph commented
Project: Fivestar » Drupal.org site moderators
Version: 7.x-2.x-dev »
Component: Code » Project ownership

Fivestar module

I mailed @ericduran offering help on 14th December, with no reply. I entered this support request two weeks ago, and mailed him again - still no reply. Given that there have been no commits or 18 months and only dev releases, it's clear that this module has been abandoned. This is a shame, as it has tens of thousands of users.

Can you please make me the owner of the project? My plan for the module is in the issue summary.

Thanks,
Philip.

ericduran’s picture

ericduran commented

Sorry, I think I have a filter on my d.o emails which is why emails is probably the worse way to get to me. Twitter is really good. Not in front of my computer right now but I'll fix this when I get to my laptop.

Sorry for the delay. Thanks @david_garcia_garcia for just sending me a tweet.

dddave’s picture

dddave commented

Hey! ;)

Please set this to fixed when everything is done. Thanks for the quick reaction.

ericduran’s picture

ericduran commented

Fixed.

ericduran’s picture

ericduran commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer