incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: Adopting non-ASF AL projects (was Re: [DISCUSS] Kudu incubator proposal)
Date Mon, 30 Nov 2015 11:54:19 GMT

> On Nov 27, 2015, at 10:28 AM, Alex Harui <> wrote:
> Hi Jim,
> In these cases, we are not creating a new PMC around these code bases, we
> are placing it under control of an existing PMC.

Which, in effect, creates a new PMC around those code bases :)

>   Plus, there is
> effectively no community left.  Nobody has made a change to these projects
> in 4 years.  A major contributor from each project has indicated their
> desire to have our PMC take control, but they are unable to hunt down
> every past contributor and get their permission, so the question really is
> about whether the ASF would permit an existing PMC to take over
> change-control for a code base when we don't have permission for every
> line of code.  Since you are VP-Legal, I a willing to abide by your
> answer.  If the answer is a flat "No", then fine, we can continue working
> with it as 3rd party, but if the answer is "Yes, but understand the risks"
> as Ted said, then the PMC is empowered to make the risk/reward trade-off.
> Also can I double-check on your statement of "include, bundle or fork a
> codebase for our usage within a project"?  I assume that "usage" here
> means "placing into the repos for modification" vs straight-up bundling
> where we download some upstream dependency as-is.  I wasn't aware we were
> supposed to ask for as-is bundling.

This is a topic for legal-discuss. I am speaking here as
a member of the Incubator PMC and not as VP Legal or anything
else. Please don't assume.

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

View raw message