"Farr, Aaron" <[EMAIL PROTECTED]> writes:
I uploaded a simple example of an "Avalon is Closed" notice at:
http://avalon.apache.org/closed.html
I still don't understand why the "common" components like Framework
or LogKit are not moved back to Avalon.
These are core components from which all projects benefit, no matter whether they are called Excalibur, Metro or anything else.
There seemed to be at least some agreement between the fractions that keeping compatibility to these parts is an intention of everyone. So why not put them back here?
Because the Excalibur team is going to manage those assets. They have demonstrated a better ability to do so in a way that is not offensive to dependant projects. The hiding of these parts from the "products" page, yet having them as "products" on the download page was one confusion. Not to mention the confusion of finding the documentation for the logger and framework. Lastly documenting framework apart from merlin code.
The thing is that having a TLP just for two small projects that amount to about 80-100K combined (uncompressed) seemed a waste of resources. Added to that the fact that they are pretty mature and are not likely to need any fixes. What community can be built around that?
The bottom line is that it makes the most sense to provide support for the two libraries in a place that is both familiar with the libraries and has a community that can support it already. Since the life has left Avalon, what better place than Excalibur?
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
