Henri Yandell wrote: > > Right now? Provide a good split-pane of the difference between Jakarta > Commons and Apache Commons as far as the projects themselves are > concerned.
someone from j-c would need to provide that half.. > I think we're all happy to sign-up, once we have a real understanding of > what the contract says and what it's gonna mean. developing bylaws for the project is one of our first tasks. > None of us are really going to budge at the moment if the chance still > exists that we join and then find out that some beaureacrat is demanding > that we release all our code in perl/c++ and tcl too. [a hypothetically > stupid situation]. I do however expect a lot of us to be listening in > though and try to help you get Apache-Commons/Java to the point of being > useful to Jakarta Commons, but I doubt any of us will commit. 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. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"
