On Tuesday, Feb 25, 2003, at 20:57 US/Pacific, Jeff Turner wrote:
What would removal of the Scratchpad force on the community?
* More controlled innovation. Instead of anybody using it as their personal playground, it would force the development to be more in the face of the community.
Hence schecoon would have been shot down in flames, as people -1'ed it on
the syntax.
I definitely agree here!
* If the community doesn't want to support it, move it someplace else. IOW if the community doesn't want some code in the main trunk it is for a very good reason. The proposing developer would be encouraged to incubate the project elsewhere.
Playgrounds *have* to exist. The question is, do they happen in the
scratchpad or on someone's hard disk. At least in the scratchpad, there
is a chance of half-baked code inspiring others, and forming a nucleus
for further development.
I agree, there is a real problem in that scratchpad code tends to hang around in limbo forever, never accepted nor rejected.
So how about assigning each scratchpad module a "lease"; being a predefined period (say 3 months) after which the code's presence in CVS must be reviewed. When the lease expires, a vote is held, and the code either becomes official, or is rejected, or has the lease renewed.
For every unit of alpha-quality code (block, scratchpad segment), we could have a status file (as Tony Collen suggested) indicating things like: - code owners (cocoon-dev is not the owner yet) - description (eg links to mailing list discussions) - lease expiry
Managed inclusion rather than exclusion.
+1
We do need a place for people to experiment with ideas, and the scratchpad is a good place.
Cheers, Ovidiu
-- Ovidiu Predescu <[EMAIL PROTECTED]> http://www.google.com/search?btnI=&q=ovidiu (I'm feeling lucky)
