Ok, I’ve pushed it out, and everything seems to be working. A few comments:

1) I added toggles (per PMC, and on the projects.html page) to show retired 
projects.
2) There’s some cache-buster stuff going on, because I couldn’t get the updated 
js/css to load
3) I’ve committed the .json files to svn. This should probably be a temporary 
measure, until we’re sure that the cronjobs are working correctly. I don’t 
think we want generated files in svn.

Other than that, the “what’s new” in my original message should be accurate.

https://projects.apache.org/chooser.html is still not linked anywhere. I’ll add 
that in once we’ve had some actual new folks run through it and deem it useful.


Still to do - find projects that are still dutifully putting their releases 
into their DOAP files, and tell them they don’t need to do that any more.

—Rich

> On Oct 29, 2026, at 4:31 PM, Rich Bowen <[email protected]> wrote:
> 
> Hi all,
> 
> Following some conversation with Dave on Slack, which reset a few of my
> understandings and expectations about where project data should come
> from, I'm planning to switch projects.apache.org over to the ASF release
> catalog (https://release-catalog.apache.org/project_releases.json), which
> Tooling (Dave) tells me is the authoritative source. Project and release data
> would come from there instead of from DOAP files and scraping dist.
> 
> What changes in scripts/cronjobs:
> 
> - New: parsecatalog.py builds projects.json, projects/<id>.json and
>  releases.json from the catalog, plus active/retired status from the
>  ATR project list.
> - parseprojects.py becomes a thin wrapper that runs parsecatalog.py and
>  then buildchooser.py.
> - parsereleases.py becomes a no-op.
> 
> I've done it that way so the existing crontab keeps working without a
> P6 change.
> 
> On the site:
> 
> - Each project page links to its metadata in ATR, where committers can
>  edit it.
> - Retired and Attic projects are no longer listed.
> - Old project URLs redirect to the new IDs.
> - The About page is rewritten.
> - The DOAP validation report is retired.
> 
> I'll be testing some more this evening, and committing in the morning if
> nothing breaks. Yell if you have strong objections.
> 
> The big advantage here is that projects can edit metadata directly in ATR,
> without mucking about with icky DOAP files ever again. The possible
> disadvantage is if they edited DOAP files since ATR loaded starter data
> from existing DOAP files, there may be a few things out of sync, but that
> should be very quick to rectify now.
> 
> The current revision is r1939678, so it's easy to roll back if needed.
> 
> Rich


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to