Skip to content

Commit

Permalink
Update project-lifecycle.md
Browse files Browse the repository at this point in the history
per 9july tac call, adjustments to archiving process

Signed-off-by: CRob <[email protected]>
  • Loading branch information
SecurityCRob authored Jul 9, 2024
1 parent 42d1590 commit 6acd690
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion process/project-lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Check failure on line 152 in process/project-lifecycle.md

View workflow job for this annotation

GitHub Actions / Check Spelling

`particpation` is not a recognized word. (unrecognized-spelling)

#### Archiving Considerations

Expand All @@ -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.
Expand Down

0 comments on commit 6acd690

Please sign in to comment.