Emily Fox

@annabellegoth2boss this actually came up during a presentation in yesterday's meeting. CC: @jlk I'm going to try to spend some time on this in the next week or so. See...

Check in to determine if this can be closed. Does the new [project security resources](https://github.com/cncf/tag-security/tree/main/project-resources) in the repo satisfy this issue?

We need to define when its okay to close stale issues versus backlog.

Happy to walk thru how i've been triaging things. Maybe at a future meeting. @lumjjb thoughts?

create a Roadmap label (for things on the roadmap) and a TOC label (for things that are TOC asks or reported to the TOC)

Proposal template should include a checkbox for the submitter to indicate their willingness to be the project lead. If the checkbox is not completed when the proposal is submitted, then...

Triage meetings are to be bi-weekly. We'd like a non-STAG leadership person lead this. that lead gets push access to edit issues, etc. with an assigned STAG leader to assist...

Recommend #672 be modified to place triage responsibilities on Security TAG Leadership as part of their regularly scheduled TL/Co-Chair meeting to expedite issue decisions and PR merging.

Reference architecture issue: https://github.com/cncf/tag-security/issues/679 Updating description to focus on assurance alignment in the checklist

@anvega are there other items to be done to close this out or bring up at a weekly meeting to determine appetite for completion?