At 07:48 PM 11/4/2001 +0000, Matt Sergeant wrote: >On Sun, 4 Nov 2001, Jonathan Stowe wrote: >> On Sun, 4 Nov 2001, Matt Sergeant wrote: >> ... > ... >Look, we need some sort of voting procedure here, otherwise we're going to >go back and forth with issues like this. What scares me is we have at the >moment a situation similar to the Perl 6 process, whereby anyone can throw >ideas out. But we don't have a Larry, who we (well, most people) trust. >And we don't have an Apache-like meritocracy. So how do we make decisions? ><Matt/> .... and copied from elsewhere in the same thread ... At 07:02 AM 11/5/2001 +0000, Greg McCarroll wrote: >* Chris Winters (chris@cwinters.com) wrote: >> Second, the Perl community (or maybe just hackers in general) can be a >> little, um, volatile with projects like this -- no code yet, lots of >> ideas flinging around, many foundations to be laid. I don't want to >> give the appearance that I'm trying to impose what I think is The Way >> of Persistence on the project. (Of course, there is no 'The' way...) > >I think the nature of this sort of project is exactly the reason why >people have to impose their ideas and, if you pardon my french, JFDI. >Greg Hi, I propose the following two things. 1. a P5EEX (P5EE-eXperimental) namespace along with the P5EE namespace to support the JFDI (just frankly do it) method 2. a voting procedure for promoting things from the P5EEX namespace to the "official" P5EE namespace This will allow for a CVS repository with both the P5EE and P5EEX namespaces. Chris could choose a code name for his experimentation (i.e. "Green"), and work on his stuff under "P5EEX::Green". Other people could team with Chris or copy and modify in "P5EEX::Yellow", "P5EEX::Red", etc. A meritocracy would emerge from committers to the P5EEX namespace, and voting rights could then be assigned. Voting would occur to promote things to the P5EE namespace, and naturally, every owner of a "P5EEX::*" namespace would convert their experimental code to work with the "official release". I'm not sure what exactly Nathan Torkington wants to see before he sets up a CVS repository at perl.org, but I submit that this process allows for * the proving of ideas through real code according to JFDI * the careful deliberation and review that should rightly be associated with the P5EE namespace StephenThread Previous | Thread Next