intake process and prioritization #296
Conversation
|
To address #281 |
|
Is the intake priority queue going to live somewhere in the repo as well? Or is it something that is going to be managed through an issue (or github project)? |
|
Currently the "priority queue" is a matrix and there's some discussing about refactoring that #309 and #206 -- I guess I could link to the matrix and we can just remember to fix the link if it gets renamed. Will wait for @JustinCappos review of this PR and see what he thinks |
|
There are a couple of comments that I still need to review, but most of the feedback has been addressed. Would welcome any new set of eyes to take a look! |
|
I think this is ready to go! |
There was a problem hiding this comment.
@ultrasaurus Thoughts? I'm fine merging, but would prefer to make edits like I describe.
| * The project has identified a project lead and has a written self-assessment | ||
|
|
||
| # Intake priorities | ||
|
|
There was a problem hiding this comment.
| Note, this is meant to be informational, not a set of rules that must be followed. These guidelines are meant to give some | |
| rationale for our thought process, but these are not binding rules. | |
There was a problem hiding this comment.
added text to address this to clarify how this would work as guidance -- a lightweight process for us to manage exceptions, keeping TOC in the loop
|
|
||
| # Updates and renewal | ||
|
|
||
| The Security Assessment team will aim to review assessed projects annually, |
There was a problem hiding this comment.
This somewhat conflicts with 2 above.
There was a problem hiding this comment.
I changed this to "aim to" in response to your earlier comment. does that help?
addressing feedback from Justin Cappos added a description of priorities as guidance, where we'll communicate what we're doing on a regular heartbeat and facilitator and named chair coordinate
chatted with JustinCappos via Slack who agreed this can be addressed as separate PR
intake process and prioritization
Moving doc to pull request. Reviewed by TOC Liaissons @lizrice and @jbeda and co-chairs
Additional feedback welcome!