Readiness dashboard

Hello @bcotton, hello #project:commops team.

I don’t know if this is the right place to discuss this, or if this is the right category… but why not?

About your idea you talked about during the readiness meeting related to a dashboard for reporting readiness, why not using this Discourse instance?

Discourse allows to draw tables and to use checkboxes. People could start reporting readiness sooner and asynchronously here, and they can discuss things (again asynchronously) replying to the topic.

Team Contact Status Notes
Fedora Project Leader @mattdm Always ready for a release
Marketing @x3mboy Release announcement Written and sent to mattdm
Marketing @x3mboy Could have used more love, TBH

What do you think?

1 Like

Just curious, what is the purpose of the dashboard to report on status? I suppose someone else could pitch Taiga as another tool to use too.

1 Like

Remember, that wouldn’t work for users like myself that don’t visit the
Discourse web UI.

Additionally, the use of mailing lists and similar allow one to reply,
asynchronously, to anything, with proper threading… Something which isn’t
available on Discourse, unfortunately.

Yeah. Taiga could be another option.

The point is, as you can read in the report, that few people from various teams participate to the release Readiness Meetings, and many teams supposed to take part don’t have any representative in this meeting. This fact leads to raise a thought: that I’m not sure this meeting provides much in the way of value.

And probably the problem is not a lack of commitment, but it is always difficult to coordinate people from a wide range of teams in real time; and for people it is difficult to have the time to attend meetings.

So, since Readiness coordination around a release is still important and valuable, @bcotton was thinking about a change that would potentially make this more useful where people would start reporting readiness sooner and asynchronously.
I thought to Discourse, but Taiga could work better.

I hadn’t thought of it, but I don’t think it will work. Apart from the issues @JohnMH raised, edits would have to be done by me, which slows the process down (particularly if I’m on PTO). My idea would have a JSON file for each area (example) that would get automatically rendered to the live version. “Expected” people could then publish the updates without intervention.

This might actually be simpler as a wiki page. I’m trying to move away from those for permanent artifacts, but this would really only need to live for a few weeks each release.