The clear goal was to do what you said - at least from what I gathered from the list before I unsubscribed in disgust at how pointless it all was. Achieving it was the problem. | [reply] |
I was on the list pretty much from day one, and there was never an agreement that creating a special distribution of CPAN modules was a goal. Most of the talk was about creating an API similar to J2EE that existing modules could be glued into. That's a big task with little payoff for people who already have working solutions, and it got nowhere. There was a meeting at OSCON that year where we explicitly discussed what the goal of the project was. At the end of that conversation, it was clear that the only thing everyone really wanted out of it was marketing and promotion of Perl as an enterprise solution. That conversation was basically the end of the project as far as I was concerned, since there was no technical goal and we were not prepared to become a marketing group.
| [reply] |
I'm a tad confused, do you think you could elaborate what exactly you are suggesting here? All I've gotten out of it was "choose a group of modules and distribute them". Choose which modules? Why? | [reply] |
Fatvamp is complaining that too much of CPAN is not good, and that QA is needed. I am suggesting that rather than reject things from CPAN, the solution is to make a "best of" distribution of QA'ed modules from CPAN.
| [reply] |