[Suggestion] Provide better process around getting a proposal to project

[TheFoxAtWork]

trafficstars

Description: Make this much more clear. expand this PR to more clearly define the actual turn of a proposal to a project.

Impact: expedite corralling works in progress to be balanced with the workload of the TAG

Scope: Not much.

[TheFoxAtWork]

@ultrasaurus things in my head on this. Want to talk about something?

1. Review existing issues, if not there Create an issue,
2. add it to the planned meeting template,
3. bring it up in the meeting, present it, work through scope, invite collaboration, determine interest.
4. If interest, have them comment on the issue and nominate a project lead. No interest, close the issue
5. get a co-chair or tech lead to sponsor it.
6. Nominate a project lead.
7. start planning and present the plan to the STAG leadership sponsor. Co-chair will review and determine if its ready to move to project or needs scheduled for later.

[TheFoxAtWork]

Before it becomes a project it needs a scope, a project lead, and a sponsor.

[lumjjb]

For closing issues - wait a certain amount of time i.e. 90 days for stale bot to close it

[lumjjb]

Interest should be issue based, meeting should be an optional but highly recommended step to accommodate for those who are not able to attend meetings.

[TheFoxAtWork]

related to this particular file: https://github.com/cncf/tag-security/blob/main/governance/process.md

[stale[bot]]

This issue has been automatically marked as inactive because it has not had recent activity.

[lumjjb]

@TheFoxAtWork is this issue closed with https://github.com/cncf/tag-security/commit/a2b1131348646f64476e9732010a4acb513c198f#diff-786d2899dd9c5edc902945f769f76a1194eebeccc1a8c017a9647bd72654ff0c, or do you think there are more specific things we need to address?

[TheFoxAtWork]

concur this can be closed.

[stale[bot]]

This issue has been automatically marked as inactive because it has not had recent activity.