This project hasn't had any activity in over 6 months. There appears no be no progress on a Drupal 7+ port of this project and the functionality seems to be duplicated in https://drupal.org/project/uc_varprice .

Would it make sense to change the status of this project to reflect the current state and/or encourage current users and developers to move over to varprice and support that project instead?

Comments

Anonymous’s picture

Project: Ubercart Donation Products » Drupal.org site moderators
Version: 6.x-2.x-dev »
Component: Miscellaneous » Broken link

I posted this request on http://drupal.org/project/uc_donation back on 19 March and haven't had a response to it (and none of the other queued issues have responses). I think this project has been abandoned and its functionality is largely implemented in http://drupal.org/project/uc_varprice . Therefore, it may be best to return this project back to the aether.

Anonymous’s picture

Component: Broken link » Project ownership

not sure why it didn't take this setting the first time. I'll reset it.

dddave’s picture

The reasons you name for "abandoning" uc_donation can be used in exactly the same way for uc_varprice. That module hasn't seen a commit in almost two years and the issue queue seems sleepy as well. Given that uc_donation is reporting 800+ installs and there is no functional reason to shock those users with changing the the status so drastically I am tempted to "won't fix" this request.

Anonymous’s picture

Fair enough. However, I would add that uc_varprice has a working D7 version whereas the D7 porting discussion on uc_donation, #1097020: Port to Drupal 7, seems to have settled on 'just switch to uc_varprice' after a few porting attempts.

Aesthetically, I think uc_varprice uses a better hook into the existing uc_product system by adding it as a feature, whereas uc_donation creates a new content type altogether. I've read a discussion that uc_donation was designed this way due to limitations in D5 and, again, it seems that a D7+ version of uc_donation would likely adopt a design paradigm closer to uc_varprice.

Even if you disagree on those points, I still think it's clear that the project's status should be updated to reflect that it needs a new maintainer and development has stalled if not stopped altogether.

dddave’s picture

Status: Active » Needs work

This module will phase out with D6 and I think that's the way it should be. We are discussing how to best approach these maintenance status issues currently. Marking needs work because in this case it clearly is a false statement that the module is actively maintained.

dddave’s picture

Status: Needs work » Fixed

I have changed the status of uc_donation to reflect the current situation.

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

Status: Fixed » Closed (fixed)

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