[DISCUSS] Retirement Policy for Artifacts

[Dave Fisher]

In INCUBATOR-198 Infra asked us to clean up Release artifacts from 
archive.apache.org  for retired podlings. I created 
INCUBATOR-233 so that we can make sure we are clear about the policy before we 
undertake proper cleanup.

When a Podling retires from the Incubator there are two exit states that might 
happen:

(1) Development simply stops.
(2) Development moves elsewhere. Either back to the donating entity or simply 
elsewhere.

Artifacts that are left that relate to code that may or may not be compliant 
with Apache Policy are:

(A) Code Repositories.
(B) Release Archives.
(C) Release Distributions.
(D) Dev Distributions. (These should always be deleted.)

A simple answer would be to keep everything where it is, and that would be easy 
except when the code has not been cleared for licensing issues. Fortunately, 
assuming that the podling PPMC or its Mentors have maintained the Podling 
Status Page we do have dates for licensing clearance that can be used. These 
are the dates in the “Copyright” and “Verify Distribution Rights” sections. Are 
there other dates to check? Are we over to the dates in 
content/podlings/.yml. Once we agree on the correct “date" to use. I 
propose that we adopt the following policy for retiring podlings:

(1) If the “date” is empty then we remove every Release and Repository. (We can 
allow a delay for people to grab “historical” copies.)
(2) If the "date" is filled in then the Repositories are marked Read Only and 
all Releases prior to that “date" are removed.

The effect is that we only preserve artifacts and code that can be considered 
to be conforming with Apache Release Policy and Code that is likely to be in 
good shape with respect to licensing.

I’d like to go for LAZY CONSENSUS after discussion for the next week or so.

Regards,
Dave

Re: [DISCUSS] Retirement Policy for Artifacts

[Henk P. Penning]

On Wed, 27 Mar 2019, Dave Fisher wrote:


Date: Wed, 27 Mar 2019 16:10:00 +
From: Dave Fisher 
To: general@incubator.apache.org
Subject: [DISCUSS] Retirement Policy for Artifacts

In INCUBATOR-198 Infra asked us to clean up Release artifacts from
archive.apache.org <http://archive.apache.org/> for retired podlings.
I created INCUBATOR-233 so that we can make sure we are clear about
the policy before we undertake proper cleanup.


  Nothing should be removed from archive.apache.org,
  except, parhaps, for legal reasons.

  Groeten,

  HPP

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


When a Podling retires from the Incubator there are two exit states that might 
happen:

(1) Development simply stops.
(2) Development moves elsewhere. Either back to the donating entity or simply 
elsewhere.

Artifacts that are left that relate to code that may or may not be compliant 
with Apache Policy are:

(A) Code Repositories.
(B) Release Archives.
(C) Release Distributions.
(D) Dev Distributions. (These should always be deleted.)

A simple answer would be to keep everything where it is, and that would be easy except 
when the code has not been cleared for licensing issues. Fortunately, assuming that the 
podling PPMC or its Mentors have maintained the Podling Status Page we do have dates for 
licensing clearance that can be used. These are the dates in the “Copyright” and “Verify 
Distribution Rights” sections. Are there other dates to check? Are we over to the dates in 
content/podlings/.yml. Once we agree on the correct “date" to use. I 
propose that we adopt the following policy for retiring podlings:

(1) If the “date” is empty then we remove every Release and Repository. (We can 
allow a delay for people to grab “historical” copies.)
(2) If the "date" is filled in then the Repositories are marked Read Only and all 
Releases prior to that “date" are removed.

The effect is that we only preserve artifacts and code that can be considered 
to be conforming with Apache Release Policy and Code that is likely to be in 
good shape with respect to licensing.

I’d like to go for LAZY CONSENSUS after discussion for the next week or so.

Regards,
Dave



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

Re: [DISCUSS] Retirement Policy for Artifacts

[Dave Fisher]

> On Mar 27, 2019, at 9:30 AM, Henk P. Penning  wrote:
> 
> On Wed, 27 Mar 2019, Dave Fisher wrote:
> 
>> Date: Wed, 27 Mar 2019 16:10:00 +
>> From: Dave Fisher 
>> To: general@incubator.apache.org
>> Subject: [DISCUSS] Retirement Policy for Artifacts
>> In INCUBATOR-198 Infra asked us to clean up Release artifacts from
>> archive.apache.org <http://archive.apache.org/> for retired podlings.
>> I created INCUBATOR-233 so that we can make sure we are clear about
>> the policy before we undertake proper cleanup.
> 
>  Nothing should be removed from archive.apache.org,
>  except, parhaps, for legal reasons.

Fair enough. Sorry I should have been more explicit.

Do we have Legal Concerns carrying archives, releases and repositories that 
have never had Podling IP Clearance signoff?

Has anything fallen through the cracks?

Regards,
Dave

> 
>  Groeten,
> 
>  HPP
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 
>> When a Podling retires from the Incubator there are two exit states that 
>> might happen:
>> 
>> (1) Development simply stops.
>> (2) Development moves elsewhere. Either back to the donating entity or 
>> simply elsewhere.
>> 
>> Artifacts that are left that relate to code that may or may not be compliant 
>> with Apache Policy are:
>> 
>> (A) Code Repositories.
>> (B) Release Archives.
>> (C) Release Distributions.
>> (D) Dev Distributions. (These should always be deleted.)
>> 
>> A simple answer would be to keep everything where it is, and that would be 
>> easy except when the code has not been cleared for licensing issues. 
>> Fortunately, assuming that the podling PPMC or its Mentors have maintained 
>> the Podling Status Page we do have dates for licensing clearance that can be 
>> used. These are the dates in the “Copyright” and “Verify Distribution 
>> Rights” sections. Are there other dates to check? Are we over to the dates 
>> in content/podlings/.yml. Once we agree on the correct “date" to 
>> use. I propose that we adopt the following policy for retiring podlings:
>> 
>> (1) If the “date” is empty then we remove every Release and Repository. (We 
>> can allow a delay for people to grab “historical” copies.)
>> (2) If the "date" is filled in then the Repositories are marked Read Only 
>> and all Releases prior to that “date" are removed.
>> 
>> The effect is that we only preserve artifacts and code that can be 
>> considered to be conforming with Apache Release Policy and Code that is 
>> likely to be in good shape with respect to licensing.
>> 
>> I’d like to go for LAZY CONSENSUS after discussion for the next week or so.
>> 
>> Regards,
>> Dave
>> 
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org


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