xerces-j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Clark <an...@apache.org>
Subject Future of NekoHTML
Date Fri, 20 Apr 2007 01:26:14 GMT
Hello, Xerces-J! It has been a long time since I've
been active in the Xerces community, or even posted to
this mailing list. The primary reason being that I just
don't have the free time I did in years past. New jobs
and new interests have kept me busy and prevented me
from working consistently on the NekoHTML[1] project.

However, during that time, interest in NekoHTML has
remained and many users have inquired about the future
of the code. Since I don't have as much time to work on
the project as before, I am at a crossroads wondering
what to do with the project.

It has always been my wish to donate the code to the
Xerces-J project so that it's an integrated part of the
parser project and is available to all users of Xerces.
In the past, when I suggested donating the code it was
requested that I go through the Incubator process.

Putting aside the fact that taking code through the
Incubator process is a long, laborious process, I never
felt that the Incubator was an appropriate place for
NekoHTML for a number of reasons. First, the purpose of
the Incubator has been to ensure that an incoming project
develops a strong community made up of not only of the
original developers but also from members of the Apache
community. However, NekoHTML is the work of a single
person.

Second, the NekoHTML parser is a self-contained and
complete set of code. No additional work needs to be
done and therefore no community needed to develop it
further. Aside from minor bug fixes and the occasional
updates needed for API changes in the Xerces Native
Interface (XNI), NekoHTML has been solid and in use by
many projects and products since its inception in 2002.

So the question remains: what do I do with the code
moving forward?

My preference is to have it adopted by the Xerces-J
project. Very little effort would be required to
integrate it into the project and minimal resources
would be needed to keep it in sync with changes to
Xerces-J in the future. But the benefit to users
would be tremendous. They would have the ability to
parse HTML documents using the same APIs and tools
that they use for parsing XML documents today. And
since it's built on XNI, it's uniquely integrated
with the Xerces-J parser and its infrastructure.

Regardless of my personal preference, I leave it up
to the community to decide whether it becomes part of
the Xerces-J project. If you feel that it's not the
right place for the code, that's fine. In that case,
I'll start a project at SourceForge so that NekoHTML
has a permanent home for future development.

Thoughts?

[1] http://people.apache.org/~andyc/neko/doc/html/

-- 
Andy Clark * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org


Mime
View raw message