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 <humbed...@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-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
