Quality Assurance - Modules

[sjg]

I agree with a lot that's been said here.

As has been mentioned, Ted's working on a new Forge -- it'll be simpler, have less cruft, and make the job of maintenance easier. But the information will still need to be managed.

Clearly, the information in the Forge (old or new) is in need of cleanup.

Somehow, we're going to need to find a volunteer or group of volunteers who will take that job. The job is not an easy one. It will involve:

• Checking modules and giving them a frank assessment as to stability
• Organizing modules by CMS version
• Culling obsolete / dead modules
• Finding developers to adopt orphaned modules

All of this would be easy if we could pay someone to do it. But seeing as it's hard to get funding to even maintain widely used modules, that's probably not an option. Unless someone here has a wealthy benefactor, looking for a tax write off?

[cyberman]

Culling obsolete / dead modules

So is the question - when is a module dead?

On my support I see many people they are working with older version like 0.12 or 0.10.

For them module is not dead  .

[kazkas]

Culling obsolete / dead modules

So is the question - when is a module dead?

On my support I see many people they are working with older version like 0.12 or 0.10.

For them module is not dead  .

Maybe it's better to do like a dropdown list, where you choose a core version, and it provides you a module/tag versions for that core version. In this case you would save time downloading and trying install modules or tags that are no longer supported :/

[cyberman]

Maybe it's better to do like a dropdown list, where you choose a core version, and it provides you a module/tag versions for that core version.

Nice idea - i like it.

Would you do it for us ? We have not enought man power to check every CMSms version with every module / tag.