You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Daniel Gruno <hu...@apache.org> on 2023/07/31 10:51:23 UTC

Feedback requested - How to deal with retired podling resources

Hi incubator folks,
over at Infra, we occasionally have requests to retire podlings, and 
while we do have a specific set of policies for TLPs, it gets a bit 
vague when it comes to podlings. I have tried looking for the IPMC's own 
guidelines, but it seems that the retirement guide does not exist ( 
https://incubator.apache.org/guides/retirement.html 404s!).

Thus, I would like to get the incubator's official opinion on how 
podling retirements should be effectuated:

- Do we keep the podling foo.apache.org hostname in perpetuity?
- Are repositories and other material removed? handed to the attic? 
moved to a special incubator-retired-* prefix?
- What happens to the podling websites?

With regards,
Daniel on behalf of ASF Infra.

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


Re: Feedback requested - How to deal with retired podling resources

Posted by Ruslan Kulynych <rk...@apache.org>.
Hi Justin,

We already have discussion in dev mailing list, should we move it to general?

Best regards,
Ruslan

On 2023/08/01 07:23:05 Justin Mclean wrote:
> Hi,
> 
> I would assume there a discussion about retirment first before calling a vote.
> 
> Kind Regards,
> Justin
> 
> > On 1 Aug 2023, at 5:16 pm, Ruslan Kulynych <rk...@apache.org> wrote:
> > 
> > Hello Justin,
> > 
> > I have a question about the retirement voting of the project. Should the general mailing list include only the voting, or is it also appropriate to have discussion along with the voting?
> > 
> > Best regards,
> > Ruslan
> > 
> > On 2023/08/01 00:28:11 Justin Mclean wrote:
> >> Hi,
> >> 
> >> I’m not sure what happen to that page or why it doesn’t exist. It did recenly:
> >> https://web.archive.org/web/20230327140005/https://incubator.apache.org/guides/retirement.html
> >> 
> >> Justin
> > 
> > ---------------------------------------------------------------------
> > 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
> 
> 

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


Re: Feedback requested - How to deal with retired podling resources

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

I would assume there a discussion about retirment first before calling a vote.

Kind Regards,
Justin

> On 1 Aug 2023, at 5:16 pm, Ruslan Kulynych <rk...@apache.org> wrote:
> 
> Hello Justin,
> 
> I have a question about the retirement voting of the project. Should the general mailing list include only the voting, or is it also appropriate to have discussion along with the voting?
> 
> Best regards,
> Ruslan
> 
> On 2023/08/01 00:28:11 Justin Mclean wrote:
>> Hi,
>> 
>> I’m not sure what happen to that page or why it doesn’t exist. It did recenly:
>> https://web.archive.org/web/20230327140005/https://incubator.apache.org/guides/retirement.html
>> 
>> Justin
> 
> ---------------------------------------------------------------------
> 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: Feedback requested - How to deal with retired podling resources

Posted by Ruslan Kulynych <rk...@apache.org>.
Hello Justin,

I have a question about the retirement voting of the project. Should the general mailing list include only the voting, or is it also appropriate to have discussion along with the voting?

Best regards,
Ruslan

On 2023/08/01 00:28:11 Justin Mclean wrote:
> Hi,
> 
> I’m not sure what happen to that page or why it doesn’t exist. It did recenly:
> https://web.archive.org/web/20230327140005/https://incubator.apache.org/guides/retirement.html
> 
> Justin

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


Re: Feedback requested - How to deal with retired podling resources

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

I’m not sure what happen to that page or why it doesn’t exist. It did recenly:
https://web.archive.org/web/20230327140005/https://incubator.apache.org/guides/retirement.html

Justin

Re: Feedback requested - How to deal with retired podling resources

Posted by Daniel Gruno <hu...@apache.org>.
On 2023-07-31 22:46, Julian Hyde wrote:
> In regard to assets, I see no particular reason to treat retired podlings differently from graduated podlings. Keep the foo.apache.org <http://foo.apache.org/> hostname; retain the repository (read-only); keep the website (tagged with a notice ’This podling has retired. It may be contacted at …’.)
> 
> It is certainly useful for people to be able to access the podling’s source code as of the day it retired.
> 
> If there are other considerations (cost, security, legal) then we could reconsider.

I believe this covers two of the questions, but I have not gotten an 
answer on the middle question; who handles the retired resources?
We can keep the repositories as is and just archive/lock them, but infra 
is not going to start editing websites and READMEs to add the retirement 
notices. That responsibility still rests with the Incubator.

> 
> Julian
> 
>> On Jul 31, 2023, at 3:51 AM, Daniel Gruno <hu...@apache.org> wrote:
>>
>> Hi incubator folks,
>> over at Infra, we occasionally have requests to retire podlings, and while we do have a specific set of policies for TLPs, it gets a bit vague when it comes to podlings. I have tried looking for the IPMC's own guidelines, but it seems that the retirement guide does not exist ( https://incubator.apache.org/guides/retirement.html 404s!).
>>
>> Thus, I would like to get the incubator's official opinion on how podling retirements should be effectuated:
>>
>> - Do we keep the podling foo.apache.org hostname in perpetuity?
>> - Are repositories and other material removed? handed to the attic? moved to a special incubator-retired-* prefix?
>> - What happens to the podling websites?
>>
>> With regards,
>> Daniel on behalf of ASF Infra.
>>
>> ---------------------------------------------------------------------
>> 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: Feedback requested - How to deal with retired podling resources

Posted by Julian Hyde <jh...@gmail.com>.
In regard to assets, I see no particular reason to treat retired podlings differently from graduated podlings. Keep the foo.apache.org <http://foo.apache.org/> hostname; retain the repository (read-only); keep the website (tagged with a notice ’This podling has retired. It may be contacted at …’.)

It is certainly useful for people to be able to access the podling’s source code as of the day it retired.

If there are other considerations (cost, security, legal) then we could reconsider.

Julian

> On Jul 31, 2023, at 3:51 AM, Daniel Gruno <hu...@apache.org> wrote:
> 
> Hi incubator folks,
> over at Infra, we occasionally have requests to retire podlings, and while we do have a specific set of policies for TLPs, it gets a bit vague when it comes to podlings. I have tried looking for the IPMC's own guidelines, but it seems that the retirement guide does not exist ( https://incubator.apache.org/guides/retirement.html 404s!).
> 
> Thus, I would like to get the incubator's official opinion on how podling retirements should be effectuated:
> 
> - Do we keep the podling foo.apache.org hostname in perpetuity?
> - Are repositories and other material removed? handed to the attic? moved to a special incubator-retired-* prefix?
> - What happens to the podling websites?
> 
> With regards,
> Daniel on behalf of ASF Infra.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>