hello world

[boring background]

I'd like to inform all of you, that the company I work for (www.swac.de) has
decided to release one of our key products under opensource license. This
product uses our inhouse developed C++ port of Jakarta Avalon Framework, which
however has never been released to public (though that in CVS and tar.gzips
all code is marked as being released under APL). The release was not made
public basicly because of my lazines and lack of time :-(.

[coming back to avalon stuff]

At this moment I'm needing some assistance (IANAL) regarding the project name,
since before the first release I'd like to make all things clean.

The port is named CCAvalon Framework, since it is developed in C++ and will be
released under APL. I'm not sure whether this name is not conflicting with the
license under which Avalon itself is published because I'm not quite able to
tell whether CCAvalon can be considered as being "derived product", and
whether I'm not using the "Avalon" part of the name CCAvalon to promote the
product itself.

I'd very appreciate if someone can guide me a bit...

I'm not in any way aspiring (at least no yet) at making CCAvalon an official
product of ASF (though I'd be very happy if it happens), but if there will be
any interest, I'm willing to do the necessary.

The sources will be available as soon as the name/license issues are resolved.

I can tell that under hoods we are using log4cpp (log4cpp.sf.net) to do the
logging part and QT Library (www.trolltech.com) (controversal but convenient
decision) to do the strings, hashtables and these lowlevel things. Doxygen
(www.doxygen.org) is used to extract Javadoc-like documentation and the
release is equipped with full set of testcases written using cppunit
(cppunit.sf.net).

The code is compilable/working/tested under Linux and WIN32 and 
Debian/GNU Linux packages are being made regularily.

I'm willing to answer any of the questions that can help to make the project
public ASAP.

sincerly,
Martin Man [the emeritus commiter of the Apache Cocoon II project]

Attachment: signature.asc
Description: Digital signature

Reply via email to