Such FRS Extension is present, works with GForge and Joomla!. Just should be ported to here... and depend on the Linux, I'm using Gentoo with modified Portage to use GIT.
There should be only trusted files, eg.
Stable Repository (Final)
Unstable Repository (Alpha, Beta, RC, PR stages)
User Submitted Files, eg. new module developers, new module maintainers.
Otherwise if everything is allowed for everyone, Gentoo Stable will be worst distribution ever if every new packages without testing is added there freely. It's simple on every administrator's login to get ping to that repository and to check if there is new core update and full fetch list of the stable repository (or unstable for advanced users).
Quote:
The idea is that with your default install you will have the xoops org thread and if you want to add a thread from chronoslab then you can do so or there may be links available to turn on if you so desire.
This is not applicable, till there is not naming policy set. Not any rules for maintaining and forking modules.
Quote:
Any modules will be listed in the associated thread. So you could actually have a module shown in more than one area if the author has their own thread setup and there is one in xoops.
Sounds complicated even as idea....
In case current SF.NET FRS is used things can be simplified.
'repository' => 'stable',
'module' => 'module-name',
'version'=> 'module-version',
'provisions'=> 'plugin1, plugin2 etc.', (some modules provides plugins for additional modules, such as waiting, rss, whatsnew)
'deps' => 'dep1, dep2',
'guid' => 'b5942b655ba2d8592604c79af6b73dd8',
'native_key' => 1, (some modules are fully functional with 2.5.5, but they're using Legacy interface; so 1 for native, 0 for legacy)
'conflicts' => 'conflict1, 2, 3 etc.',
Everything in one XML for Stable and another for unstable. If this is done, Modules Repository on xoops.org can be done only for prestige :)