-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update project-lifecycle.md #351
Conversation
per 9july tac call, adjustments to archiving process Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com>
per https://github.com/ossf/tac/blob/main/process/TAC-Decision-Process.md, we have a 15day review period and need no less than 7 TAC members to approve (6 + me) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @SecurityCRob ! A couple comments...
process/project-lifecycle.md
Outdated
1.) Overseeing TI will be moving to "Archived" status | ||
2.) Active subgroups (SIG or project) is still active and desires to continue collaborating | ||
3.) Subgroup reviews active TIs to see if there is alignment of vision and purpose (https://openssf.org/community/openssf-working-groups/) | ||
4.) Subgroup meets with TI leader and group to discuss adoption | ||
5.) New TI agrees to become new oversight group for subgroup | ||
6.) PRs filed in TI and TAC repos to note change of status | ||
7.) Archiving TI has PR filed noting new status |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this list, but I might split this into steps/tasks for the hosting TI vs. the sub-TI that wants to transition. I also think that'll also make it clearer about who's responsible for which of these tasks (TAC vs. TI chairs, vs sub-TIs).
Co-authored-by: Marcela Melara <marcela.melara@intel.com> Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor non-blocking comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for documenting this Crob. Let's push it forward and iterate as needed.
Co-authored-by: Zach Steindler <steiza@github.com> Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates! LGTM!
Fix typo Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
per 9july tac call, adjustments to archiving process