I have a D6 site on which I may want to use this and have plans for a D7 site that will definitely need this. I'd like to become a co-maintainer of this module and will make my first priority rolling a D7 version.

Comments

ezra-g’s picture

ezra-g commented

Thanks for offering to help. As a first step, it would be great if you could file/review some patches :).

vegantriathlete’s picture

vegantriathlete
he/him/his
Primary language English
Location Lakewood, CO
commented

My plan is that my first patch will be the port to D7. I know this is a huge first step. But, I'm willing to take it on. This way you will be able to have a really good sample to review. I wasn't expecting you to grant co-maintainership blind. I was just giving you a "heads up." I am assuming that I can just submit that as a patch that (once it's been reviewed and approved) you will then commit to a new branch.

Please respond to the issue filed for a D7 version to let me know what you want me to use as my "code base."

siliconmeadow’s picture

siliconmeadow commented

vegantriathlete and I spent over an hour this week in a call going through various issues, both issues here in the queue and more generally about the project. I have a vested interest in seeing this module is maintained, and would be happy to co-maintain it as well. My company will back my time and effort, and can also provide funding for others too, if necessary.

In the discussion that we had, our biggest concern was: where and what do we start on? We have tried deduce from the artifacts which branches ezra-g was most interested in and why certain decisions seem to have been made. The most confounding thing is, although the description of the project explains the 6.x-2.x rewrite by danniboy, which provides multiple subqueues per user, this branch is unsupported and therefore not available from the front page. My primary usage of the module is due to this feature and therefore the 6.x-2.x branch is the only version that I have interest in. I would require the ability to have multiple subqueues per user in the Drupal 7 version.

This begs the question: Why was the 6.x-2.x branch demoted to an 'unsupported' branch?

Looking at the usage statistics:

  • the D5 version has 0 users, yet it is the only version labelled as a 'recommended' version;
  • 25% of the sites are using the 6.x.2.x branch - the 'unsupported' one.

From the discussions we had, vegantriathlete is most interested in the 'multiple subqueue per user' features seen in the 6.x.2.x branch and would be endeavouring to make those features available in his 7.x branch.

I would prefer (and respectfully request) that vegantriathlete use the 6.x-2.x as his code base and that you evaluate his suitability as a co-maintainer based on the effort he spends working on the 6.x-2.x branch. Admittedly, he can't leave behind the other 6.x branches (the other 75% of sites are using them), but I'm the only one who's made any effort to provide further feedback on the subject so far. Plus, I have a pending patch for the 6.x-2.x version which is needed to make the 6.x-2.x branch work with the latest version of nodequeue ;-)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Request for co-maintainership » Offering to co-mainain Smartqueue Per User
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this issue, as there haven't been follow-up actions as per Taking over unsupported (abandoned) projects (which isn't just about unsupported or abandoned projects).