Re: Finding the answer
Posted: Mon Nov 16, 2009 1:03 pm
aln_cms offered to help in another thread and in that same thread I offered time as well and I see replytomk3 is working his tail off verifying what's in there now.
Other than maybe coordinating some initial steps and direction (so we don't have people doing 3 or 4 different things) I see no reason why the dev team needs to be distracted from core development.
As a starting point...what about picking out stuff we like by looking at some examples from www.xoops.org/modules/repository/ or extensions.joomla.org and starting with that. The "download now" link can still point to the current forge..but at least we can have some more control over what shows up and how it gets displayed and have a strict set of definitions for what is considered a production module.
The forge does work well for holding the actual code and revision history for the modules, it is just not a user friendly display and that is what everybody is truly griping about.
Other than maybe coordinating some initial steps and direction (so we don't have people doing 3 or 4 different things) I see no reason why the dev team needs to be distracted from core development.
As a starting point...what about picking out stuff we like by looking at some examples from www.xoops.org/modules/repository/ or extensions.joomla.org and starting with that. The "download now" link can still point to the current forge..but at least we can have some more control over what shows up and how it gets displayed and have a strict set of definitions for what is considered a production module.
The forge does work well for holding the actual code and revision history for the modules, it is just not a user friendly display and that is what everybody is truly griping about.