Mircea Toma wrote:
I would like to move a few components I published on sourceforge.net to Avalon, but I'm not sure where to put them.
We previously decided to not let any new components in that are not in use in avalon container. Basic reason for this was the really-really-big size of avalon. "focus on our core art", "do one thing and do it well", "not a dumping ground", comments like that. We moved avalon-apps stuff elsewhere or killed it off. Same with large parts of cornerstone and excalibur.
That's the background "mindset". Now, Jakarta has:
http://jakarta.apache.org/site/newproject.html
its is a bit extensive a requirement for a few new components, but what I would still like to see is a bit of an explanation how adding these components will benefit the avalon project as a whole (and the components themselves).
-----
Here's what you'll be up against:
- these components are "avalon components" using avalon-framework.
Unfortunately, we cannot let that be a judging ground. Avalon's codebase would swell to be about the size of the whole of jakarta :D
- these are quality components and they need some exposure so more people can also benefit from them.
Exposure you can get with a link from http://avalon.apache.org/components/ and some posts to user mailing lists. Experience shows that hosting something in avalon doesn't automatically mean lots of exposure. Especially because there are so many components already :D
- I would like to support object (de)serialization in container X using the marshaller.
Ah, that might be a neat idea! You patch the container (with docs and tests) to support that feature, and if that's a change that goes through, sure, we'll throw the marshaller into avalon-components.
-----
Not to want to critize you (its cool that you make your comps open source and that you build them using avalon), but wanting to point out why we need to be so picky.
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
