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.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.