> 1. Do you know enough about P5EEx::Blue to vote for it > to become the P5EE code base? If not, what more do > you need to know? What are the attributes of a code > base that would cause you to vote for it to be the > P5EE code base?
Similar to others, i have not audited/tested Blue much. Of course it looks promising, and there is a dearth of alternatives. I don't know if i could vote now, as a "final" spec/implementation, but it is mostly based on lack of direct experience. > 2. If a P5EE code base exists, will you use it? > What would it need to do for you in order for you to > use it? For development testing, not much other than docs. For production, test suite is crucial. Esp. with another layer of code on top of base modules. Raul Goodness [EMAIL PROTECTED]
