incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin" <>
Subject RE: Bypassing Incubator
Date Mon, 15 Jun 2009 10:19:35 GMT

> -----Original Message-----
> From: Noel J. Bergman []
> Sent: Monday, 15 June 2009 2:15 PM
> To:
> Subject: RE: Bypassing Incubator
> Tim Ellison wrote:
> > Niclas Hedhman wrote:
> > > 1. Any substantial codebase needs at least IP Clearance in Incubator,
> > > which is effectively just a record of where/when/how it came from, and
> > > an opportunity for Incubator PMC members to have a look and make sure
> > > that there is no flagrant IP issues.
> > I never understood this part.  Why is the Incubator PMC any more
> > qualified to decide if incoming code contains a "fragrant IP issue"
> > than the destination TLP PMC?  After all, the TLP PMC are doing that
> > check continuously for the day to day contributions received.
> And they, the PMC responsible for clearing the IP, must record that
> clearance in the Incubator, which was designated by the Board as the
> repository for all of those IP clearance documents.  That fact that there
> are additional eyes is a bonus.
> 	--- Noel

Ok, so thanks everyone for your replies/clarifications.

The cause of my question and confusion was I saw a request on Infra Jira for
a mailing list and other infrastructure to be created for a Lucene
Sub-Project OpenRelevance[1].

So, now I get that is quite alright to do that. The only question remains is
that of IP clearance. I haven't had time to take a closer look as of yet.

Is that part of Incubators role, to police around the whole of the ASF
projects looking for IP violations and stuff that stinks of 'hey that should
come through Incubator' , or is not the job of Incubator because it has
never touched Incubator so is someone elses job to look into if everything
is kosha or otherwise ?



[1] - URL:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message