[Process Decision] Can we improve the way we keep TI content up-to-date in maturity stage applications?

[justaugustus]

We've had at least two instances recently, zarf (#497) and minder (#506) where contributors were interested in updating references to the their projects, which would've involved modifying a previously submitted project lifecycle applications.

In my opinion, these documents should be point-in-time references, with the content remaining static.
That said, with our current versions of the template, we will continue to run into instances like this.

Discussed in the aforementioned issues, as well as the August 5th TAC meeting.

cc: @steiza

---

Ideas

Some combination of these could work:

• Continue to keep the README up-to-date and de-link the lifecycle applications in the readme
• Add a disclaimer in the lifecycle templates that certain content may be out-of-date (and to reference the README instead)
• Create a metadata file for projects
• Create a metadata file (and generator), similar to Kubernetes: https://github.com/kubernetes/community/blob/master/sigs.yaml / https://github.com/kubernetes/community/blob/master/Makefile

[mlieberman85]

I'm very much in favor of this. Would creating a couple of simple scripts to help with some of the issues? I definitely agree that having some sort of metadata file would be nice.