Greg Knaddison - GVS wrote:
If you believe someone needs to manage a module differently then consider contacting the maintainer and saying to them:
"Thank you for this module. I find it very useful. I would like to see a 'stable 1.0 release' of this module. Is there some way that I can help you to confirm that it is stable enough that it's ready for that 1.0 release? Are there some issues that need testing?"
I think in most cases that the module developer will be so overjoyed at getting positive feedback and an offer of help (you have to follow up on the offer, of course) that they will use your help and quickly get the module to a 1.0 state. Testing is something that everyone can help with and will make the developer's life much easier which will make them more likely to release the 1.0. If they don't respond, maybe they have lost interest in the project. Then you could take it over and create the all important 1.0 release.
Enormous, blinking, flaming, marquee +1 to this. An even bigger and more flashy -1 to all the other proposals about introducing more process or rules here. I've never once been refused by any developer when I've used this approach, and a couple times I've either ended up educating someone on how the release system works (which then resulted in more official releases), or I've ended up with co-maintainer rights, and able to make the changes to the module that I needed for a client. -Angie