On Thu, 25 Oct 2001, Nathan Torkington wrote: > I can have p5ee.perl.org created, and set up people to edit the > content, but I want to see some progress before p5ee gets 'blessed' > like that. Similarly, I'll make a CVS repository when we have code > to version :-) Like wise, code shouldn't be written until it has been clearly spec'd. Like wise, spec's shouldn't be written until we know our requirements. Like wise, requirements's won't be known until we understand the language and nature of the model we're modling.
The suggestion for an RFC process is probably initially the way to go whilst de-buzzyfying the J2EE buzzwords. There seems to be a tendency of prematurly jumping to define higherlevel structures. I'm really in favour of Ajit's suggested framework - the first blessing should involve getting a group to start turning raw ideas into a design spec; after collating those ideas, that is. My .02 Euros -- Rafiq Ismail Software Engineer and Systems Administrator http://www.codix.net "All the best people in life seem to like Linux." - Steve Wozniak
