From 6acd69099611cc7b7d9b465b91127a4598cedd1f Mon Sep 17 00:00:00 2001 From: CRob <69357996+SecurityCRob@users.noreply.github.com> Date: Tue, 9 Jul 2024 14:01:27 -0400 Subject: [PATCH 1/4] Update project-lifecycle.md per 9july tac call, adjustments to archiving process Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com> --- process/project-lifecycle.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/process/project-lifecycle.md b/process/project-lifecycle.md index ee5e5fdd..adbac701 100644 --- a/process/project-lifecycle.md +++ b/process/project-lifecycle.md @@ -149,7 +149,7 @@ See [Submission Process](#submission-process) below and [Graduation application] ### Archived -Open source projects have a lifecycle and there are times when projects become inactive due to a variety of reasons. There are also cases where a project may no longer want to be supported by the OpenSSF, or the OpenSSF TAC may no longer wish to recommend the use of a project. Archiving happens through a vote of the TAC, and can be requested by the corresponding project's lead(s) or a TAC member. +Open source projects have a lifecycle and there are times when projects become inactive due to a variety of reasons. There are also cases where a project may no longer want to be supported by the OpenSSF, the given effort no longer has broad community interest and particpation, or the OpenSSF TAC may no longer wish to recommend the use of a project. Archiving happens through a vote of the TAC, and can be requested by the corresponding project's lead(s) or a TAC member. TI's that are dormant, with no activity for 9 months (meetings, mailing lists, or other publicly viewable channels) in a row should be considered good candidates for Archiving. #### Archiving Considerations @@ -159,6 +159,16 @@ When voting on a proposal to archive a project, TAC members may consider: * If the project's inactivity or inconsistent maintenance presents a user security risk. * If the project's design or approach is no longer a recommended best practice. +#### Considerations when Archiving a TI that has sub-efforts embedded within #### + +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 + #### Archive Process Archived projects are no longer in active development and are only archived after a TAC vote. From a9226687252e20b0ac52ad8d91172be38ee3248d Mon Sep 17 00:00:00 2001 From: CRob <69357996+SecurityCRob@users.noreply.github.com> Date: Thu, 18 Jul 2024 13:03:15 -0400 Subject: [PATCH 2/4] Update process/project-lifecycle.md Co-authored-by: Marcela Melara Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com> --- process/project-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/project-lifecycle.md b/process/project-lifecycle.md index adbac701..356b0e2b 100644 --- a/process/project-lifecycle.md +++ b/process/project-lifecycle.md @@ -162,7 +162,7 @@ When voting on a proposal to archive a project, TAC members may consider: #### Considerations when Archiving a TI that has sub-efforts embedded within #### 1.) Overseeing TI will be moving to "Archived" status -2.) Active subgroups (SIG or project) is still active and desires to continue collaborating +2.) Whether subgroups/-TIs (SIG or project) are still active and desire 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 From 41d600a044a58928db39db23d0d2f692ec6215e6 Mon Sep 17 00:00:00 2001 From: CRob <69357996+SecurityCRob@users.noreply.github.com> Date: Tue, 23 Jul 2024 09:05:18 -0400 Subject: [PATCH 3/4] Update process/project-lifecycle.md Co-authored-by: Zach Steindler Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com> --- process/project-lifecycle.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/process/project-lifecycle.md b/process/project-lifecycle.md index 356b0e2b..04d54311 100644 --- a/process/project-lifecycle.md +++ b/process/project-lifecycle.md @@ -161,13 +161,13 @@ When voting on a proposal to archive a project, TAC members may consider: #### Considerations when Archiving a TI that has sub-efforts embedded within #### -1.) Overseeing TI will be moving to "Archived" status -2.) Whether subgroups/-TIs (SIG or project) are still active and desire 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 +1. Overseeing TI will be moving to "Archived" status +2. Whether subgroups/-TIs (SIG or project) are still active and desire 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 #### Archive Process From 66d02780fe7ca367cf2c1f58d448a383a07f5b2a Mon Sep 17 00:00:00 2001 From: Arnaud J Le Hors Date: Tue, 23 Jul 2024 20:35:58 +0200 Subject: [PATCH 4/4] Update process/project-lifecycle.md Fix typo Signed-off-by: Arnaud J Le Hors --- process/project-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/project-lifecycle.md b/process/project-lifecycle.md index 04d54311..49c7b69f 100644 --- a/process/project-lifecycle.md +++ b/process/project-lifecycle.md @@ -149,7 +149,7 @@ See [Submission Process](#submission-process) below and [Graduation application] ### Archived -Open source projects have a lifecycle and there are times when projects become inactive due to a variety of reasons. There are also cases where a project may no longer want to be supported by the OpenSSF, the given effort no longer has broad community interest and particpation, or the OpenSSF TAC may no longer wish to recommend the use of a project. Archiving happens through a vote of the TAC, and can be requested by the corresponding project's lead(s) or a TAC member. TI's that are dormant, with no activity for 9 months (meetings, mailing lists, or other publicly viewable channels) in a row should be considered good candidates for Archiving. +Open source projects have a lifecycle and there are times when projects become inactive due to a variety of reasons. There are also cases where a project may no longer want to be supported by the OpenSSF, the given effort no longer has broad community interest and participation, or the OpenSSF TAC may no longer wish to recommend the use of a project. Archiving happens through a vote of the TAC, and can be requested by the corresponding project's lead(s) or a TAC member. TI's that are dormant, with no activity for 9 months (meetings, mailing lists, or other publicly viewable channels) in a row should be considered good candidates for Archiving. #### Archiving Considerations