You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by Andy Clark <an...@apache.org> on 2007/04/20 03:26:14 UTC
Future of NekoHTML
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-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Future of NekoHTML
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Andy,
For external codebases brought into the ASF I think the Incubator PMC
needs some involvement these days. That doesn't necessarily imply that the
code needs to incubate. There's a lighter weight IP clearance [1] process
which can be used for contributions to an existing project. That said, I
think there's some expectation that the code also comes in with a
community to support it. I'd be concerned if the code is orphaned or in
hibernation from day one or soon after. If there are folks who are (or are
interested in becoming) active here including yourself that will volunteer
to maintain the code, answer user questions, etc... now and in the future
that's great. If not, then perhaps what Neil suggested (Apache Labs) is a
better idea.
Thanks.
[1] http://incubator.apache.org/ip-clearance/index.html
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Andy Clark <an...@apache.org> wrote on 04/19/2007 09:26:14 PM:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Future of NekoHTML
Posted by Andy Clark <an...@cyberneko.net>.
Looking over the Labs website, it doesn't appear that
it is appropriate for NekoHTML, either. Apache Labs
seems more suited for new research experiements than
existing projects that are complete and don't require
further development and/or community support.
----- Original Message -----
From: "Neil Graham" <ne...@ca.ibm.com>
Subject: Re: Future of NekoHTML
Just wanted to make sure you're aware of the new Apache Labs project [*].
It's designed to be a place where committers can put interesting code
where the goal isn't necessarily to develop a community. So you get SVN
infrastructural support etc.
After Xerces-J's experience with the WML DOM and the HTML DOM, I would
venture to guess there would be a certain amount of unease at the prospect
of accepting a code base without an active developer community. Perhaps
this is the source (aside from Apache practice these days that is) for the
suggestion that the Incubator would be the right place to start. But
since I'm even less active than you are these days :(, definitely for
others to decide!
--
Andy Clark - andy@cyberneko.net
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Future of NekoHTML
Posted by Neil Graham <ne...@ca.ibm.com>.
Hi Andy,
Just wanted to make sure you're aware of the new Apache Labs project [*].
It's designed to be a place where committers can put interesting code
where the goal isn't necessarily to develop a community. So you get SVN
infrastructural support etc.
After Xerces-J's experience with the WML DOM and the HTML DOM, I would
venture to guess there would be a certain amount of unease at the prospect
of accepting a code base without an active developer community. Perhaps
this is the source (aside from Apache practice these days that is) for the
suggestion that the Incubator would be the right place to start. But
since I'm even less active than you are these days :(, definitely for
others to decide!
Cheers,
Neil
[*]: http://labs.apache.org/
Neil Graham
Manager, C++ Compiler Front-End and Runtime Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
Andy Clark <an...@apache.org>
04/19/07 09:26 PM
Please respond to
j-dev@xerces.apache.org
To
Xerces-J Dev <j-...@xerces.apache.org>, Xerces-J Users
<j-...@xerces.apache.org>
cc
Subject
Future of NekoHTML
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Future of NekoHTML
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Hi Andy,
For external codebases brought into the ASF I think the Incubator PMC
needs some involvement these days. That doesn't necessarily imply that the
code needs to incubate. There's a lighter weight IP clearance [1] process
which can be used for contributions to an existing project. That said, I
think there's some expectation that the code also comes in with a
community to support it. I'd be concerned if the code is orphaned or in
hibernation from day one or soon after. If there are folks who are (or are
interested in becoming) active here including yourself that will volunteer
to maintain the code, answer user questions, etc... now and in the future
that's great. If not, then perhaps what Neil suggested (Apache Labs) is a
better idea.
Thanks.
[1] http://incubator.apache.org/ip-clearance/index.html
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Andy Clark <an...@apache.org> wrote on 04/19/2007 09:26:14 PM:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org