Skip to content
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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Jul 23, 2024
Merged

Update project-lifecycle.md #351

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6acd690
Update project-lifecycle.md
SecurityCRob Jul 9, 2024
a922668
Update process/project-lifecycle.md
SecurityCRob Jul 18, 2024
41d600a
Update process/project-lifecycle.md
SecurityCRob Jul 23, 2024
66d0278
Update process/project-lifecycle.md
lehors Jul 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion process/project-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@

### 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)
lehors marked this conversation as resolved.
Show resolved Hide resolved

#### Archiving Considerations

Expand All @@ -159,6 +159,16 @@
* 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
SecurityCRob marked this conversation as resolved.
Show resolved Hide resolved
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
Copy link
Contributor

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).


#### Archive Process

Archived projects are no longer in active development and are only archived after a TAC vote.
Expand Down
Loading