Module Support

[gmoore]

With regards to module support or lack there of. Would people want us to put in our partner/module writer policy:

If there is a lack of support for a module for X days/months:
1) Remove the module from the market place.
2) Grey out the module but still list it making it unavailable for download.
3) Keep the module up but note the lack of support
4) Take over the module and provide support
5) Ignore the lack of support.

And, what would you define as lack of support? A rating system perhaps?

We can do either of these scenarios. Just want your opinions.

Thank you,
Greg

[KyleMassacre]

I myself would do scenario #3. If it works, it works but maybe add a feature for people to say that the module doesnt work and then you can handle it from there

[gmoore]

I struggle with what is 'lack of support' so probably I will let the community define that with their comments.

Greg

[KyleMassacre]

Well I wouldn't consider "lack of support" not pushing updates but not pushing updates to fix the module if it is broken. *which reminds me I need to fix my promo code module* but the past few weeks have been crazy in my family

[Dominion]

I'd recommend a mixture of 3 & 4. If the module is free anyway offer an option to open it, and support it through the community. Offer security updates yourself if you feel a reported problem is serious enough, and the module is popular enough to be worth looking at.

If it's an old module no one has downloaded for a long time make a note before anyone downloads it, and only pick up basic support through the forums. People can always ask for help.