> From: Henri Yandell [mailto:[EMAIL PROTECTED] > Sent: 21 October 2002 16:30
[...] >>>> no, forcing multi-language implementation is 'way off the radar, and >>>> destry-on-sight as a concept. having a place where non-java stuff can >>>> live alongside java *is* in scope and one of the goals. >>> >>> It's in scope until the scope is defined though. Currently joining Apache >>> Commons is akin to using proprietary s/w, no clue which direction it's >>> going to go right now. >> >> This is a bit harsh don't you think. If you look at the STATUS file >> and the resolution that was passed by the Board you should at least get >> some general sense of the direction we wish to take Commons. > > It's a bit bombastic I agree, but is only really covered by the weakly > defined 'language-agnostic' bit. But the issues being voted on should at least give you some sense of direction. Don't you agree? > Interesting that the resolution makes no mention of server-side > functionality. Why should it? Commons is about reusable components (and maybe even tools), not restricted to server-side. Sander
