So, we've got http://drupal.org/project/uc_coupon and http://www.ubercart.org/contrib/1991
Both have issues, some duplicate even, and both work sporadically (some report success, others have problems).
1) In this specific case, can we get the two merged back together? Both versions have been through changes and through the whole period of "I need this for a client so I built it/fork it" and then "my client is gone so I'm not giving it as much attention as it deserves." So, let's get them together, eh? I think that's happening...and I've got cvs commit access to the Drupal.org project to be able to help there.
2) In general, I think this shows how forking a module is painful for a community. But it also shows (at least me) that the comment threads on contribution pages just won't cut it for keeping track of problems and fixes. I'd like to propose that, for any non-trivial module, the Ubercart project uses Drupal.org module pages and issue trackers. Much like forking code can cause problems, forking the community can cause problems, so we need to be coordinated about this. I propose that in the future if a module outgrows the Ubercart contrib pages that a final comment is made pointing to the relevant Drupal.org pages the contrib page has it's comment settings changed to "read only".
Thoughts on either topic?



Responding to your points:
(I think there may even be a third place to download it if he's got it up on his personal page.)




Joined: 12/12/2007