[development] development Digest, Vol 83, Issue 34
David Burns
dburns at hotmail.com
Wed Nov 18 15:46:30 UTC 2009
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.
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:
1. Open CVS Repo for anyone to contribute. "Drupal Alpha Repository"
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
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.
This may have possibly been suggested before. I apologize if it has, I just re-enabled myself to this mailing list.
> From: development-request at drupal.org
> Subject: development Digest, Vol 83, Issue 34
> To: development at drupal.org
> Date: Wed, 18 Nov 2009 13:59:41 +0000
>
> Send development mailing list submissions to
> development at drupal.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.drupal.org/mailman/listinfo/development
> or, via email, send a message with subject or body 'help' to
> development-request at drupal.org
>
> You can reach the person managing the list at
> development-owner at drupal.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of development digest..."
>
>
> Today's Topics:
>
> 1. Re: CVS Approval Policy: was Re: new features in D6 core?
> (Ashraf Amayreh)
> 2. Re: CVS Approval Policy: was Re: new features in D6 core?
> (Pierre Rineau)
> 3. Re: CVS Approval Policy: was Re: new features in D6 core?
> (Randy Fay)
> 4. Re: CVS Approval Policy: was Re: new features in D6 core?
> (Daniel F. Kudwien)
> 5. Re: CVS Approval Policy: was Re: new features in D6 core?
> (Ashraf Amayreh)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 18 Nov 2009 15:30:15 +0200
> From: Ashraf Amayreh <mistknight at gmail.com>
> Subject: Re: [development] CVS Approval Policy: was Re: new features
> in D6 core?
> To: development at drupal.org, pierre.rineau at makina-corpus.com
> Message-ID:
> <a53d1b3b0911180530k57fab7c3h8cfc34ca382f02fb at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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).
>
> 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.
>
> Suggestions? Flames? Thoughts?
>
> AA
>
> On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau <
> pierre.rineau at makina-corpus.com> wrote:
>
> > On Wed, 2009-11-18 at 14:08 +0200, Ashraf Amayreh wrote:
> > > 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.
> > >
> > > 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.
> > >
> > > Suggestions? Flames? Thoughts?
> >
> > FLAAAAAAAAAAAAAAAAAAAAME! Repetitive modules are good, they always have
> > subtile differences!
> >
> > Please, project owners, do describe why your module is unique on your
> > project page!
> >
> > Pierre.
> >
> >
>
>
> --
> Ashraf Amayreh
> http://aamayreh.org
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/18090e10/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Wed, 18 Nov 2009 14:42:21 +0100
> From: Pierre Rineau <pierre.rineau at makina-corpus.com>
> Subject: Re: [development] CVS Approval Policy: was Re: new features
> in D6 core?
> To: Ashraf Amayreh <mistknight at gmail.com>
> Cc: development at drupal.org
> Message-ID: <1258551741.4350.16.camel at guinevere.makina-nantes.net>
> Content-Type: text/plain
>
> On Wed, 2009-11-18 at 15:30 +0200, Ashraf Amayreh wrote:
> > 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).
>
> It was some kind of joke, don't worry :)
>
> I agree with the fact a lot of modules shouldn't even exists. But this
> MY judgement, and because I'm a simple human, my judgement is not the
> only one which is right (and is probably wrong btw).
>
> It's difficult to define what is a good reasoning, because every man
> which will review appliances for a new project CVS will have a different
> opinion about this.
>
> My though is that on d.o, it should exist some kind of tag like "core
> team says YAY! to this module" and "core team totally disapprove this
> ugly module", which should help users to get stable, maintainable, and
> non abandoned modules.
>
> Pierre.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 18 Nov 2009 08:49:31 -0500
> From: Randy Fay <randy at randyfay.com>
> Subject: Re: [development] CVS Approval Policy: was Re: new features
> in D6 core?
> To: development at drupal.org
> Message-ID:
> <15c957090911180549t7e612de6sc25647db7a67e592 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> A comment period would help with this.
>
> One problem with all the approval strategies is that there are so many
> modules nobody has enough bandwidth to pay attention.
>
> 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.
>
> 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.
>
> 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".
>
> -Randy
>
> On Wed, Nov 18, 2009 at 8:30 AM, Ashraf Amayreh <mistknight at gmail.com>wrote:
>
> > 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).
> >
> > 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.
> >
> > Suggestions? Flames? Thoughts?
> >
> > AA
> >
> >
> > On Wed, Nov 18, 2009 at 2:23 PM, Pierre Rineau <
> > pierre.rineau at makina-corpus.com> wrote:
> >
> >> On Wed, 2009-11-18 at 14:08 +0200, Ashraf Amayreh wrote:
> >> > 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.
> >> >
> >> > 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.
> >> >
> >> > Suggestions? Flames? Thoughts?
> >>
> >> FLAAAAAAAAAAAAAAAAAAAAME! Repetitive modules are good, they always have
> >> subtile differences!
> >>
> >> Please, project owners, do describe why your module is unique on your
> >> project page!
> >>
> >> Pierre.
> >>
> >>
> >
> >
> > --
> > Ashraf Amayreh
> > http://aamayreh.org
> >
>
>
>
> --
> Randy Fay
> Drupal Development, troubleshooting, and debugging
> randy at randyfay.com
> +1 970.462.7450
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/03b56952/attachment-0001.html
>
> ------------------------------
>
> Message: 4
> Date: Wed, 18 Nov 2009 14:55:23 +0100
> From: "Daniel F. Kudwien" <news at unleashedmind.com>
> Subject: Re: [development] CVS Approval Policy: was Re: new features
> in D6 core?
> To: <development at drupal.org>, <pierre.rineau at makina-corpus.com>
> Message-ID: <441601ca6856$c6d0cf90$0200a8c0 at structworks.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > My though is that on d.o, it should exist some kind of tag
> > like "core team says YAY! to this module" and "core team
> > totally disapprove this ugly module", which should help users
> > to get stable, maintainable, and non abandoned modules.
> >
> > Pierre.
>
> You are basically arguing for installing Flag module on drupal.org, which
> would allow this and many other badly needed improvements.
>
> So please contribute here:
>
> http://3281d.com/projects/improving-subscriptions
>
> Thanks.
>
> sun
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 18 Nov 2009 15:59:08 +0200
> From: Ashraf Amayreh <mistknight at gmail.com>
> Subject: Re: [development] CVS Approval Policy: was Re: new features
> in D6 core?
> To: development at drupal.org
> Message-ID:
> <a53d1b3b0911180559r484c4abdo9817ebdb61428784 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > My though is that on d.o, it should exist some kind of tag like "core
> > team says YAY! to this module" and "core team totally disapprove this
> > ugly module", which should help users to get stable, maintainable, and
> > non abandoned modules.
> >
> >
> With 5000+ modules it would be impossible for the core team to keep up. Any
> option to evaluate modules after they've been submitted isn't practical at
> all. As to stable, maintainable and non-abandoned modules, I'm pretty sure
> not even the core team has the ability to read into the future :)
>
> The only alternative is to catch projects before they are even created by
> requiring permission per project rather than a CVS account that can create
> an unlimited number of projects/modules. Not to mention the added benefit of
> introducing the module on the dev list to everyone which is a huge
> advantage.
>
> A comment period would help with this.
> >
>
> I disagree to this. When CVS owners find they won't be able to upload their
> modules without getting an administrator's approval they will lean towards
> introducing the module before writing code which would save on a lot of
> coding work.
>
> 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".
> >
>
> As nice as it may be, this is simply unrealistic.
>
> AA
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.drupal.org/pipermail/development/attachments/20091118/65704b1e/attachment.html
>
> ------------------------------
>
> --
> [ Drupal development list | http://lists.drupal.org/ ]
>
> End of development Digest, Vol 83, Issue 34
> *******************************************
_________________________________________________________________
Bing brings you maps, menus, and reviews organized in one place.
http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20091118/1f8e8216/attachment-0001.html
More information about the development
mailing list