incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hen <>
Subject Re: Update README for retired podlings?
Date Mon, 06 Nov 2017 09:21:43 GMT
On Fri, Nov 3, 2017 at 4:29 AM, Shane Curcuru <> wrote:

> Dave Fisher wrote on 11/2/17 11:13 PM:
> >> On Nov 2, 2017, at 7:06 PM, John D. Ament <>
> wrote:
> >>> On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <>
> wrote:
> >>>>> On Nov 2, 2017, at 3:08 PM, sebb <> wrote:
> >>>>> On 2 November 2017 at 21:07, Dave Fisher <>
> wrote:
> ...snip...
> >> I'm not even sure I agree with deleting the websites.  It was a project.
> >> Now it's not.  That doesn't mean the information should no longer be
> >> available.  But not sure the resources need to be covered.
> >
> > Either the IPMC should review the policy or we should ask the board to
> set/confirm the policy for “retired” podlings.
> Podlings in incubation are not Apache projects - by definition.  They
> are podlings effectively managed within the incubator.  So it would be
> best for the IPMC to come up with a specific policy or plan for this,
> vote on it, and then just let the board know "Hey, here's how we're
> going to formally handle retiring podling assets".
> Personally, I think it depends on how long the podling was around (i.e.
> how many likely other people were attempting to use the project) and
> what the state of it's IP clearance is.  In particular, if IP clearance
> weren't complete, I would vote for deleting the repos, just to ensure
> that we're not distributing (even via source control) IP that the ASF
> isn't assured of having under our license.
I'd argue that being under our license is not important.

If we have code in our source control that can't be distributed, it should
be deleted (regardless of project). If we have a retired Incubator podling
with code that didn't get sufficiently relicensed from another open source
license, no big deal (provided that's clear).

My vote (unsurprisingly) would be for treating a retired podling the same
way a retired project is treated.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message