A comment period would help with this.<br><br>One problem with all the approval strategies is that there are so many modules nobody has enough bandwidth to pay attention.<br><br>However, if there were enough bandwidth, I would propose not an approval scheme but just a comment period. If you had to describe your module and then wait 48 hours for comments, (and there were smart people listening) then the issues of duplication might be avoided.<br>
<br>Requiring a comment period, rather than requiring "approval" would keep the whole process completely open, but allow some possibility of correction of our current problems.<br><br>Finally, I think we should make it clear to people that if you contribute a module, you're expected to maintain it, or at least figure out how to get it maintained. I know there are a number of module contributors who have just dropped code into CVS and left it there for ever. Perhaps we should ask them to check a checkbox "I agree to maintain this module".<br>
<br>-Randy<br><br><div class="gmail_quote">On Wed, Nov 18, 2009 at 8:30 AM, Ashraf Amayreh <span dir="ltr"><<a href="mailto:mistknight@gmail.com">mistknight@gmail.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 dir="ltr">It seems you misunderstood my reasoning. I'm simply suggesting this to make it compulsory for any CVS owner to talk about a possible module on the dev list BEFORE being able to create the project node. If the module is new it will get a thumbs up and he would get the go, if it's repetitive, the CVS owner will need to give good reasoning and then could be allowed to post it, and if he can't persuade anyone it would get rejected. Other module developers could suggest teaming up or perhaps point him to modules with similar functionality that he was unaware of as long as he has to post to the dev list before being able to create a new project node (kind of reminds me of the node limit module).<br>
<br>I'm simply suggesting this to make sure modules don't spring up in the dark without anyone's knowledge rather than trying to oppose repetitive modules. Currently, CVS owners are free to add as many project nodes as they want when they get their CVS access. Which sounds wrong given that he got his access for creating one module.<br>
<br>Suggestions? Flames? Thoughts?<br><font color="#888888"><br>AA</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau <span dir="ltr"><<a href="mailto:pierre.rineau@makina-corpus.com" target="_blank">pierre.rineau@makina-corpus.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>On Wed, 2009-11-18 at 14:08 +0200, Ashraf Amayreh wrote:<br>
> I suddenly got this (perhaps silly) idea of only allowing a CVS owner<br>
> to create one project and require approval by posting to the DEV list<br>
> when wishing to create another project rather than making this open<br>
> for all CVS owners. This would definitely help with the repetition<br>
> problem and module boom.<br>
><br>
> Posting to the DEV list should at least give other module developers<br>
> and people interested the opportunity to object to, agree or suggest<br>
> alternatives to the proposed module rather than suddenly finding a<br>
> useless/repetitive module springing up here and there because the<br>
> developer didn't know another one existed.<br>
><br>
> Suggestions? Flames? Thoughts?<br>
<br>
</div>FLAAAAAAAAAAAAAAAAAAAAME! Repetitive modules are good, they always have<br>
subtile differences!<br>
<br>
Please, project owners, do describe why your module is unique on your<br>
project page!<br>
<font color="#888888"><br>
Pierre.<br>
<br>
</font></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br>Ashraf Amayreh<br><a href="http://aamayreh.org" target="_blank">http://aamayreh.org</a><br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Randy Fay<br>Drupal Development, troubleshooting, and debugging<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>