Ubercart.org Contrib Clean-up

3 replies [Last post]
Joined: 01/25/2008
Juice: 752

I am looking for suggestions to clean-up the Ubercart Contrib page.

One thing I noticed was that CIF's are appearing under module and other. Maybe we should make another type called CIF?

It would also make sense to be able to filter by version compatibility.

Are there any other suggestions that would make adding, searching, or reporting issues for contribs any easier?

I know a future goal would be to get all contrib modules up in Drupal.org CVS, this will be the best thing for maintaining a 5.x and 6.x branch of each contrib.

Joined: 08/14/2007
Juice: 3867

I'm thinking that possibly the Abandoned category should be relegated to a checkbox or something. Normally I don't want to see any Contribs that aren't actively being developed. So some other way of filtering it, either a checkbox ("Show abandoned Contribs?") or making combination filters, a la the way Drupal.org's Issue Tracker works, would be great.

Some suggestions:

Work in Progress
Ready for testing
Complete and working
Abandoned
Broken
Deprecated
Bug Testing
Active (WIP, Testing, Complete)
Inactive (Abandoned, Broken, Deprecated)

Help directly fund development: Donate via PayPal!

TR
TR's picture
Bug FinderFAQ ModeratorGetting busy with the Ubercode.
Joined: 11/05/2007
Juice: 3225

One problem: people who abandon projects don't usually take the time to come back to the site and mark the project as "Abandoned". So there're actually a lot of projects which are abandoned or obsolete / superseded which continue to be marked as active, completed, working, etc. Like catalog grid display, for example, which has been in core since November - but people are still trying to use it.

I don't have a solution at this time, other than active management of the contribs.

<tr>.
Joined: 12/28/2007
Juice: 677

Good points here, but what about a different approach... in some CMS I've seen some modules "approved by core developers" (or having a "cigar" like in Typo3... also PHPBB has some kind of quality controlling & approve system for modules)

I'm not any developer or coder, but from quality point of view I believe this kind of approach would be more than fine for Ubercart. My respect for all developers, but I believe it's important to categorize modules more clearly from the shop owners & shop developer point of view.

I believe this kind of approach will more clearly help to separate development level modules from the production ready ones. There's of course some additional time needed from core developers if following this kind of approach, but maybe it is worth the trouble?

My 2 centimos from Sunny Spain...