duckzland [duckzland]

Remember to change status, when you upload new code.

Why didn't you open a feature report for the other module?

As the module adds a block to Drupal showing the content obtained from Ubercart, I think the module doesn't make sense as stand alone project.

I am not saying that it should not be added to Drupal.org CVS. We tend to give more space to cooperation, and IMO a module that adds a functionality to an existing project should be first proposed as feature request.

I didn't get offended; I simply explained better what I reported in my previous comment.

May you point out to any comments where it is stated ubercart doesn't accept any feature request?

That doesn't mean that feature requests are not accepted.
If you sent an email to the current maintainer, then the absence of reply could just mean that you have chosen the wrong media to ask for them (you should open a feature request in the project queue; that is the reason I asked for a link to a comment where it's clearly stated feature requests are not accepted).

1) Lack of response isn't a no, especially in the Ubercart queue where even important patches can languish for months.

2) However, based on my detailed knowledge of Ubercart acquired as a major contributor to the project for more than 2 years, I can tell you that there's absolutely no way this will be included in core. In fact, similar features were taken *out* of core and put into the uc_marketing contribution over a year ago.

3) That does not mean I think the module should be approved. In fact, the stated functionality in #1 duplicates that provided by other Ubercart contributed modules, specifically uc_marketing and uc_best_seller, and perhaps one or two others (ubercart.org has been down, so I can't research this completely). While there may be some minor differences (I'm not sure uc_best_seller provides a block, for instance), these seem to be more on the level of feature enhancements to existing contributions, and *not* appropriate as a stand-alone module.

As far as I can tell, you're just querying the {uc_best_sellers} table for your information anyway - you don't define your own tables or do your own determination of what is "popular". It really seems like all you've done is add some features to the existing uc_best_sellers module, in which case you should submit patches/feature requests to that module's issue queue.

Thus, I'm against hosting this module on drupal.org.