Idea: a public progress dashboard?

General
1

Hi all,

Quick idea I wanted to float before building anything: would a public progress dashboard be useful for the project?

The roadmap on the homepage already lays out clear phases and goals (Independent / Governance / Education), but right now there’s no easy way for someone to see at a glance where things actually stand against them, specifically CI/cache status, package freshness, SIG activity, docs updates, that kind of thing. A lightweight dashboard page could surface that without anyone having to dig through commit history.

I’d want to start small, a standalone page, not a homepage change; and would be glad to put together a first draft if there’s interest. Curious what people think, and whether there’s an existing process (AEP?) or SIG this should go through.

Thanks,

Chris

2

I was thinking that some kind of visibility could be good. In my mind a blog with semi-regular posts could help to give insight into where the project is. Right now we only have Aux Lib, Aux Foundation. Tidepool (the package set) isn’t usable yet, so no packages or infrastructure for them exists.

We could probably also surface projects on the website so people can know what projects there even are. What do you think?

3

Good point on Tidepool/packages not existing yet; agree a blog covers the “what’s happening and why” side well, and it’s easy to start regardless of what’s built.

Is there a halfway point though? I could put together a small standalone dashboard now, but only showing things that actually have real data behind them today, eg. Aux Lib/Foundation activity, docs updates, SIG activity from the forum. CI infrastructure (buildbot-nix) could show up too, honestly labelled as “in development” rather than implying it’s live. Package/Tidepool status would just show as “not yet” until there’s something real to report, no point faking a metric that doesn’t exist.

I’d build it structured around the Roadmap/Goals sections already on the homepage rather than inventing new categories, so it’s easy to see it as filling a gap in the existing story rather than a separate thing. If that goes well, the idea would be to eventually fold it into the homepage itself rather than keep it as a separate page long-term.

Would that be a welcome direction? And what’s the right process here for something like this, just open a PR, or is there someone/somewhere I should run the idea past first?

Thanks,

Chris

4

Apologies if I am wrong here, but are you using an LLM to compose your posts? I have been noticing some AI-isms and wanted to ask for clarification.