My name is Berin Loritsch and I am the Release Manager for the Jakarta Avalon
projects, as well as a committer on the Cocoon projects. Recently, my employer
asked me to develop a solution using Turbine. The reason was two-fold: Cocoon
documentation is still on the slim side, and the learning curve is high. I am
still very dedicated to the Avalon and Cocoon projects, however I am open to
how turbine does things.
I am interested in helping Turbine integrate more seamlessly with Cocoon, and
will be willing to do some of the hard work. I am intimately familiar with
the architecture of Cocoon and Avalon, so I would be able to offer suggestions
that will provide a smooth migration path to something that is embeddable.
One of the things that I would like to work on in Turbine (once I am familiar
with it) is to update the configuration system. I find property files to be
tedious, and can provide some insights on how to maintain backward compatibility
while moving to an XML based configuration. While there are "competing"
portions of Turbine and Cocoon (notable Actions and DB connection pooling),
I can help with providing hooks to allow the use of Turbine utilities.
I hope you will find my contributions both worthwile, and valuable. I know
there will have to be some cooperation between the projects, and I can provide
that cooperation. I will post my user related questions to the user list,
but any proposals I will post here.
S/MIME Cryptographic Signature
