<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Just speaking from personal experience. I don't think I would be as active with Drupal had I not been allowed to submit my modules to get feedback from the community. However, I do think some (alot, okay most) modules, including a couple of my own, are not worthy to be listed on Drupal.org. <br><br>Instead of taking away the ability to contribute, I do think there should be a minor approval process. I know this adds a layer of complexity but I think most solutions will. I think the following would be a good workflow:<br><br>1. Open CVS Repo for anyone to contribute. "Drupal Alpha Repository"<br><br>2. Once an Alpha module gains popularity and is approved as unique to existing modules it would then be ported to cvs.drupal.org repo<br><br>2a. alternatively, if the code is similar to or heading in the same direction as another module it could then be suggested that the new module developer assist with development on existing module.<br><br>This may have possibly been suggested before. I apologize if it has, I just re-enabled myself to this mailing list.<br><br>> From: development-request@drupal.org<br>> Subject: development Digest, Vol 83, Issue 34<br>> To: development@drupal.org<br>> Date: Wed, 18 Nov 2009 13:59:41 +0000<br>> <br>> Send development mailing list submissions to<br>> development@drupal.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.drupal.org/mailman/listinfo/development<br>> or, via email, send a message with subject or body 'help' to<br>> development-request@drupal.org<br>> <br>> You can reach the person managing the list at<br>> development-owner@drupal.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of development digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: CVS Approval Policy: was Re: new features in D6 core?<br>> (Ashraf Amayreh)<br>> 2. Re: CVS Approval Policy: was Re: new features in D6 core?<br>> (Pierre Rineau)<br>> 3. Re: CVS Approval Policy: was Re: new features in D6 core?<br>> (Randy Fay)<br>> 4. Re: CVS Approval Policy: was Re: new features in D6 core?<br>> (Daniel F. Kudwien)<br>> 5. Re: CVS Approval Policy: was Re: new features in D6 core?<br>> (Ashraf Amayreh)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Wed, 18 Nov 2009 15:30:15 +0200<br>> From: Ashraf Amayreh <mistknight@gmail.com><br>> Subject: Re: [development] CVS Approval Policy: was Re: new features<br>> in D6 core?<br>> To: development@drupal.org, pierre.rineau@makina-corpus.com<br>> Message-ID:<br>> <a53d1b3b0911180530k57fab7c3h8cfc34ca382f02fb@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> It seems you misunderstood my reasoning. I'm simply suggesting this to make<br>> it compulsory for any CVS owner to talk about a possible module on the dev<br>> list BEFORE being able to create the project node. If the module is new it<br>> will get a thumbs up and he would get the go, if it's repetitive, the CVS<br>> owner will need to give good reasoning and then could be allowed to post it,<br>> and if he can't persuade anyone it would get rejected. Other module<br>> developers could suggest teaming up or perhaps point him to modules with<br>> similar functionality that he was unaware of as long as he has to post to<br>> the dev list before being able to create a new project node (kind of reminds<br>> me of the node limit module).<br>> <br>> I'm simply suggesting this to make sure modules don't spring up in the dark<br>> without anyone's knowledge rather than trying to oppose repetitive modules.<br>> Currently, CVS owners are free to add as many project nodes as they want<br>> when they get their CVS access. Which sounds wrong given that he got his<br>> access for creating one module.<br>> <br>> Suggestions? Flames? Thoughts?<br>> <br>> AA<br>> <br>> On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau <<br>> pierre.rineau@makina-corpus.com> wrote:<br>> <br>> > 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>> > 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>> ><br>> > Pierre.<br>> ><br>> ><br>> <br>> <br>> -- <br>> Ashraf Amayreh<br>> http://aamayreh.org<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/18090e10/attachment-0001.html <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Wed, 18 Nov 2009 14:42:21 +0100<br>> From: Pierre Rineau <pierre.rineau@makina-corpus.com><br>> Subject: Re: [development] CVS Approval Policy: was Re: new features<br>> in D6 core?<br>> To: Ashraf Amayreh <mistknight@gmail.com><br>> Cc: development@drupal.org<br>> Message-ID: <1258551741.4350.16.camel@guinevere.makina-nantes.net><br>> Content-Type: text/plain<br>> <br>> On Wed, 2009-11-18 at 15:30 +0200, Ashraf Amayreh wrote:<br>> > It seems you misunderstood my reasoning. I'm simply suggesting this to<br>> > make it compulsory for any CVS owner to talk about a possible module<br>> > on the dev list BEFORE being able to create the project node. If the<br>> > module is new it will get a thumbs up and he would get the go, if it's<br>> > repetitive, the CVS owner will need to give good reasoning and then<br>> > could be allowed to post it, and if he can't persuade anyone it would<br>> > get rejected. Other module developers could suggest teaming up or<br>> > perhaps point him to modules with similar functionality that he was<br>> > unaware of as long as he has to post to the dev list before being able<br>> > to create a new project node (kind of reminds me of the node limit<br>> > module).<br>> <br>> It was some kind of joke, don't worry :)<br>> <br>> I agree with the fact a lot of modules shouldn't even exists. But this<br>> MY judgement, and because I'm a simple human, my judgement is not the<br>> only one which is right (and is probably wrong btw).<br>> <br>> It's difficult to define what is a good reasoning, because every man<br>> which will review appliances for a new project CVS will have a different<br>> opinion about this.<br>> <br>> My though is that on d.o, it should exist some kind of tag like "core<br>> team says YAY! to this module" and "core team totally disapprove this<br>> ugly module", which should help users to get stable, maintainable, and<br>> non abandoned modules.<br>> <br>> Pierre.<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Wed, 18 Nov 2009 08:49:31 -0500<br>> From: Randy Fay <randy@randyfay.com><br>> Subject: Re: [development] CVS Approval Policy: was Re: new features<br>> in D6 core?<br>> To: development@drupal.org<br>> Message-ID:<br>> <15c957090911180549t7e612de6sc25647db7a67e592@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> A comment period would help with this.<br>> <br>> One problem with all the approval strategies is that there are so many<br>> modules nobody has enough bandwidth to pay attention.<br>> <br>> However, if there were enough bandwidth, I would propose not an approval<br>> scheme but just a comment period. If you had to describe your module and<br>> then wait 48 hours for comments, (and there were smart people listening)<br>> then the issues of duplication might be avoided.<br>> <br>> Requiring a comment period, rather than requiring "approval" would keep the<br>> whole process completely open, but allow some possibility of correction of<br>> our current problems.<br>> <br>> Finally, I think we should make it clear to people that if you contribute a<br>> module, you're expected to maintain it, or at least figure out how to get it<br>> maintained. I know there are a number of module contributors who have just<br>> dropped code into CVS and left it there for ever. Perhaps we should ask them<br>> to check a checkbox "I agree to maintain this module".<br>> <br>> -Randy<br>> <br>> On Wed, Nov 18, 2009 at 8:30 AM, Ashraf Amayreh <mistknight@gmail.com>wrote:<br>> <br>> > It seems you misunderstood my reasoning. I'm simply suggesting this to make<br>> > it compulsory for any CVS owner to talk about a possible module on the dev<br>> > list BEFORE being able to create the project node. If the module is new it<br>> > will get a thumbs up and he would get the go, if it's repetitive, the CVS<br>> > owner will need to give good reasoning and then could be allowed to post it,<br>> > and if he can't persuade anyone it would get rejected. Other module<br>> > developers could suggest teaming up or perhaps point him to modules with<br>> > similar functionality that he was unaware of as long as he has to post to<br>> > the dev list before being able to create a new project node (kind of reminds<br>> > me of the node limit module).<br>> ><br>> > I'm simply suggesting this to make sure modules don't spring up in the dark<br>> > without anyone's knowledge rather than trying to oppose repetitive modules.<br>> > Currently, CVS owners are free to add as many project nodes as they want<br>> > when they get their CVS access. Which sounds wrong given that he got his<br>> > access for creating one module.<br>> ><br>> > Suggestions? Flames? Thoughts?<br>> ><br>> > AA<br>> ><br>> ><br>> > On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau <<br>> > pierre.rineau@makina-corpus.com> wrote:<br>> ><br>> >> 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>> >> 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>> >><br>> >> Pierre.<br>> >><br>> >><br>> ><br>> ><br>> > --<br>> > Ashraf Amayreh<br>> > http://aamayreh.org<br>> ><br>> <br>> <br>> <br>> -- <br>> Randy Fay<br>> Drupal Development, troubleshooting, and debugging<br>> randy@randyfay.com<br>> +1 970.462.7450<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/03b56952/attachment-0001.html <br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Wed, 18 Nov 2009 14:55:23 +0100<br>> From: "Daniel F. Kudwien" <news@unleashedmind.com><br>> Subject: Re: [development] CVS Approval Policy: was Re: new features<br>> in D6 core?<br>> To: <development@drupal.org>, <pierre.rineau@makina-corpus.com><br>> Message-ID: <441601ca6856$c6d0cf90$0200a8c0@structworks.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> > My though is that on d.o, it should exist some kind of tag <br>> > like "core team says YAY! to this module" and "core team <br>> > totally disapprove this ugly module", which should help users <br>> > to get stable, maintainable, and non abandoned modules.<br>> > <br>> > Pierre.<br>> <br>> You are basically arguing for installing Flag module on drupal.org, which<br>> would allow this and many other badly needed improvements.<br>> <br>> So please contribute here:<br>> <br>> http://3281d.com/projects/improving-subscriptions<br>> <br>> Thanks.<br>> <br>> sun<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Wed, 18 Nov 2009 15:59:08 +0200<br>> From: Ashraf Amayreh <mistknight@gmail.com><br>> Subject: Re: [development] CVS Approval Policy: was Re: new features<br>> in D6 core?<br>> To: development@drupal.org<br>> Message-ID:<br>> <a53d1b3b0911180559r484c4abdo9817ebdb61428784@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> > My though is that on d.o, it should exist some kind of tag like "core<br>> > team says YAY! to this module" and "core team totally disapprove this<br>> > ugly module", which should help users to get stable, maintainable, and<br>> > non abandoned modules.<br>> ><br>> ><br>> With 5000+ modules it would be impossible for the core team to keep up. Any<br>> option to evaluate modules after they've been submitted isn't practical at<br>> all. As to stable, maintainable and non-abandoned modules, I'm pretty sure<br>> not even the core team has the ability to read into the future :)<br>> <br>> The only alternative is to catch projects before they are even created by<br>> requiring permission per project rather than a CVS account that can create<br>> an unlimited number of projects/modules. Not to mention the added benefit of<br>> introducing the module on the dev list to everyone which is a huge<br>> advantage.<br>> <br>> A comment period would help with this.<br>> ><br>> <br>> I disagree to this. When CVS owners find they won't be able to upload their<br>> modules without getting an administrator's approval they will lean towards<br>> introducing the module before writing code which would save on a lot of<br>> coding work.<br>> <br>> Finally, I think we should make it clear to people that if you contribute a<br>> > module, you're expected to maintain it, or at least figure out how to get it<br>> > maintained. I know there are a number of module contributors who have just<br>> > dropped code into CVS and left it there for ever. Perhaps we should ask them<br>> > to check a checkbox "I agree to maintain this module".<br>> ><br>> <br>> As nice as it may be, this is simply unrealistic.<br>> <br>> AA<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/65704b1e/attachment.html <br>> <br>> ------------------------------<br>> <br>> -- <br>> [ Drupal development list | http://lists.drupal.org/ ]<br>> <br>> End of development Digest, Vol 83, Issue 34<br>> *******************************************<br> <br /><hr />Bing brings you maps, menus, and reviews organized in one place. <a href='http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1' target='_new'>Try it now.</a></body>
</html>