[development] CVS Approval Policy: was Re: new features in D6 core?
mistknight at gmail.com
Wed Nov 18 13:30:15 UTC 2009
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?
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!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development