Re: Multiple podling status files

> On Aug 14, 2026, at 1:09 AM, sebb <[email protected]> wrote:
> 
> On Fri, 14 Aug 2026 at 08:43, tison <[email protected] <mailto:[email protected]>> wrote:
>> 
>> Some files may support information pages at [1], and other status pages.
>> But I don't have a full picture which one support what page.
>> 
>> [1] https://incubator.apache.org/projects/incubation-status-template.html <https://incubator.apache.org/projects/incubation-status-template.html>
> 
> The status pages are generated from projects/*.xml files.
> When a podling retires, its website is redirected there.
> 
> podlings.xml is used by clutch and to generate the summary listings:
> https://incubator.apache.org/projects/ <https://incubator.apache.org/projects/>
> and the current list on the index page
> It is also used by whimsy and probably other tools either directly or
> via JSON files created by Whimsy

As sebb notes: podlings.xml file is used by several systems outside of the incubator. It acts as the source of record and history of incubator podlings.

Another use is on https://projects.apache.org in various displays and this also hosts json files derived from the xml.

> 
> The podlings/*.yml files are a later addition, but include information
> that is not readiliy available elsewhere.

This file was built a decade ago to move some of the status information out of the project status xml

> 
> Whilst it might be easier to manage the files if they were in Git,
> that is not the issue here.

If the incubator wants to manage podlings.xml file by not hand editing xml then I would suggest creating some python scripts.

Best,
Dave 

> 
> Sebb
> 
>> Best,
>> tison.
>> 
>> 
>> tison <[email protected]> 于2026年8月14日周五 15:41写道：
>> 
>>> I generally consider them as paper work and we may either migrate them
>>> from SVN to make the paper work easy to finish, or just drop them.
>>> 
>>> 
>>> Best,
>>> tison.
>>> 
>>> 
>>> sebb <[email protected]> 于2026年8月14日周五 15:35写道：
>>> 
>>>> There are at least 3 podling status files:
>>>> 
>>>> 
>>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>>>> 
>>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>>>> <podling>.yml
>>>> 
>>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
>>>> <podling>.xml
>>>> 
>>>> Which ones are required by policy, if any?
>>>> And if they are not required, why do they exist?
>>>> Equally, if they are needed, why are they not required?
>>>> 
>>>> Can thiey be simplified?
>>>> Maybe podlings.xml and podlings/*.yml could be combined?
>>>> (e.g. move the info from one into the other, and use that to generate
>>>> the moved data)
>>>> 
>>>> Sebb
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>> 
>>>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] <mailto:[email protected]>
> For additional commands, e-mail: [email protected] <mailto:[email protected]>