<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Before one tries to solve a problem, it would be interesting to prove or provide evidence that it exists. As a module maintainer, I think REALLY HARD before considering creating a new module on CVS, because I know what maintaining a module entails, and I've already worked hard to try and get others involved in my own issue queue. I lean towards looking for duplicate modules cause I want to pair up with people to lessen my own workload. If I post a module, I've already tried to find another module that does something similar, and when possible have tried to float patches against that module to get it to do what I want it to do. Because I KNOW my time is limited. I don't think that I'm alone here. <div><br></div><div>Anecdotes don't count here. If we've got 5000+ modules, how many of these are duplicates posted by maintainers of other modules. My bet is the number is really low, and not worth investing a ton of time in. </div><div><br></div><div>Show me da numbers.... :)<br><div><br><div><div>On Nov 18, 2009, at 4:08 AM, Ashraf Amayreh wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I suddenly got this (perhaps silly) idea of only allowing a CVS owner to create one project and require approval by posting to the DEV list when wishing to create another project rather than making this open for all CVS owners. This would definitely help with the repetition problem and module boom.<br> <br>Posting to the DEV list should at least give other module developers and people interested the opportunity to object to, agree or suggest alternatives to the proposed module rather than suddenly finding a useless/repetitive module springing up here and there because the developer didn't know another one existed.<br> <br>Suggestions? Flames? Thoughts?<br><br>AA<br><br><div class="gmail_quote">On Sat, Oct 24, 2009 at 4:35 AM, Jeff Greenberg <span dir="ltr"><<a href="mailto:jeff@ayendesigns.com">jeff@ayendesigns.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Dave Reid wrote:<br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Again, how can one person know that one line is useful to the entire community if other people don't speak up about it? It requires the community to be involved in the process and not reacting to just when there are problems.<br> <br> </blockquote></div> Right, then if one person isn't qualified to know whether it would be useful to the community, let the community decide by downloading it or not.<br> </blockquote></div><br><br clear="all"><br>-- <br>Ashraf Amayreh<br><a href="http://aamayreh.org">http://aamayreh.org</a><br> </div></blockquote></div><br></div></div></body></html>