You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Andy Clark <an...@apache.org> on 2006/01/31 19:43:45 UTC

Incubation vs. Donating Code to Existing Project

/me removes Zimbra hat.

For the past several years, I've wanted to donate my HTML
parser code built on Xerces-J to the Xerces project. It is
written using the Xerces Native Interface and provides HTML
parsing with XML APIs.

When I mentioned donating the code to the project, it was
suggested that I go through the incubator process. But
after getting to know more about the incubator through
the Kabuki proposal, I'm not sure if the incubator is
appropriate.

Here's the deal: I have a piece of code that relies
directly on Xerces-J and cannot be used without it. It's
a relatively small piece of code so it's not really a full
project by itself. And, unlike other projects considered
for incubation, there is no community because I have been
the sole implementor. So the incubator doesn't seem like
the right place for it but that's what the Xerces-J folks
have suggested.

Thoughts?

-- 
Andy Clark * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Incubation vs. Donating Code to Existing Project

Posted by Leo Simons <ma...@leosimons.com>.
On Tue, Jan 31, 2006 at 10:43:45AM -0800, Andy Clark wrote:
> /me removes Zimbra hat.
> 
> For the past several years, I've wanted to donate my HTML
> parser code built on Xerces-J to the Xerces project. It is
> written using the Xerces Native Interface and provides HTML
> parsing with XML APIs.
> 
> When I mentioned donating the code to the project, it was
> suggested that I go through the incubator process. But
> after getting to know more about the incubator through
> the Kabuki proposal, I'm not sure if the incubator is
> appropriate.
> 
> Here's the deal: I have a piece of code that relies
> directly on Xerces-J and cannot be used without it. It's
> a relatively small piece of code so it's not really a full
> project by itself. And, unlike other projects considered
> for incubation, there is no community because I have been
> the sole implementor. So the incubator doesn't seem like
> the right place for it but that's what the Xerces-J folks
> have suggested.
> 
> Thoughts?

If the Xerces community wants to accept this stuff as something
integral to xerces, there's no new committers or community coming
in and no need for those, and its all precisely within its scope,
its PMC can decide to do just that:

  http://incubator.apache.org/ip-clearance/index.html

This is "going through incubation" in terms of IP clearance and
not in terms of community.

I don't know enough about Xerces to assert whether this is an
applicable process here. If the xerces people referred to the
incubator, perhaps they meant that its not.

LSD

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Incubation vs. Donating Code to Existing Project

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
In this case, if the Xerces folks don't want to take responsibility for
creating the community / committment to the code, then they absolutely
can ask for the code to undergo the full incubuation process.  But if they
choose instead to assume responsibility for the long term committment to
this accepted code, then they can choose the IP Clearance route.

It's the PMC's choice - really for discussion on that project list.  You
are right Jeremias - going through a full incubation process is not
necessary (going through the Incubator IP clearance process is!) - but
if an only if Xerces made that choice.  And it seems Andy said that the
Xerces project prefers full incubation, that was their choice.  Unless that
changes there is only route for this example to be picked up by the ASF.



Jeremias Maerki wrote:
> IMO, going through the Incubator is not mandatory. The Xerces PMC could
> decide to integrate CyberNeko (right?) into Xerces-J as an additional
> component/feature. If it depends on Xerces-J and is a useful addition to
> Xerces but has too little mass to lead a life on its own, I'd say it
> could make a fine addition to Xerces-J. If Xerces chose to adopt
> CyberNeko the only things that would need to be done are: vote on
> adoption by the Xerces PMC and go through the IP clearance process. Just
> my thoughts...
> 
> On 31.01.2006 19:43:45 Andy Clark wrote:
> 
>>/me removes Zimbra hat.
>>
>>For the past several years, I've wanted to donate my HTML
>>parser code built on Xerces-J to the Xerces project. It is
>>written using the Xerces Native Interface and provides HTML
>>parsing with XML APIs.
>>
>>When I mentioned donating the code to the project, it was
>>suggested that I go through the incubator process. But
>>after getting to know more about the incubator through
>>the Kabuki proposal, I'm not sure if the incubator is
>>appropriate.
>>
>>Here's the deal: I have a piece of code that relies
>>directly on Xerces-J and cannot be used without it. It's
>>a relatively small piece of code so it's not really a full
>>project by itself. And, unlike other projects considered
>>for incubation, there is no community because I have been
>>the sole implementor. So the incubator doesn't seem like
>>the right place for it but that's what the Xerces-J folks
>>have suggested.
>>
>>Thoughts?
> 
> 
> 
> 
> Jeremias Maerki
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 
> 
> .
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Incubation vs. Donating Code to Existing Project

Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
IMO, going through the Incubator is not mandatory. The Xerces PMC could
decide to integrate CyberNeko (right?) into Xerces-J as an additional
component/feature. If it depends on Xerces-J and is a useful addition to
Xerces but has too little mass to lead a life on its own, I'd say it
could make a fine addition to Xerces-J. If Xerces chose to adopt
CyberNeko the only things that would need to be done are: vote on
adoption by the Xerces PMC and go through the IP clearance process. Just
my thoughts...

On 31.01.2006 19:43:45 Andy Clark wrote:
> /me removes Zimbra hat.
> 
> For the past several years, I've wanted to donate my HTML
> parser code built on Xerces-J to the Xerces project. It is
> written using the Xerces Native Interface and provides HTML
> parsing with XML APIs.
> 
> When I mentioned donating the code to the project, it was
> suggested that I go through the incubator process. But
> after getting to know more about the incubator through
> the Kabuki proposal, I'm not sure if the incubator is
> appropriate.
> 
> Here's the deal: I have a piece of code that relies
> directly on Xerces-J and cannot be used without it. It's
> a relatively small piece of code so it's not really a full
> project by itself. And, unlike other projects considered
> for incubation, there is no community because I have been
> the sole implementor. So the incubator doesn't seem like
> the right place for it but that's what the Xerces-J folks
> have suggested.
> 
> Thoughts?



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org