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 Process README.md #219

Merged
merged 7 commits into from
Nov 24, 2023
Merged

Update Process README.md #219

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
dc15171
Update README.md
SecurityCRob Nov 16, 2023
2ce240c
Update README.md
SecurityCRob Nov 16, 2023
25be5fa
Update process/README.md
lehors Nov 21, 2023
3751555
Update process/README.md
lehors Nov 21, 2023
675e33a
Update process/README.md
lehors Nov 21, 2023
cb1db42
Revamp process README
lehors Nov 22, 2023
9f2faba
remove unusued image
lehors Nov 22, 2023
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
10 changes: 9 additions & 1 deletion process/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,16 @@
The process is designed to be flexible to enable a Project to move in and out of a Working Group as deemed appropriate by the TAC.

# II. Lifecycle
<img align="top" src="https://github.com/ossf/tac/blob/main/process/TI-lifecycle-stages.png">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Breaking up walls of text with images is nice, but do we want some sort of lead-in here like "Here are the four stages of the TI lifecycle:"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually don't think that this image really adds anything as it stands, it should at least have some arrows showing the progression from one stage to the other. Otherwise it's just duplicative of the bulleted list.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll add some arrows to illustrate workflow, thanks for the suggestion

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually replaced the image with a mermaid graph that has the arrows.


Working Groups and Projects have a different lifecycle as defined below:
Technical Initiatives (TIs) include Working Groups (WGs), Special Interest Groups (SIGs) and Projects (both code and specificiations). All TIs follow a common lifecyle, with 4 stages:

Check failure on line 27 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

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

Check failure on line 27 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

`specificiations` is not a recognized word. (unrecognized-spelling)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could merge these descriptions / abbreviations with "I. Overview" and just use the abbreviations here?

lehors marked this conversation as resolved.
Show resolved Hide resolved

lehors marked this conversation as resolved.
Show resolved Hide resolved
- Sandbox - for new efforts within the Foundation seeking to get started out within a community of like-minded contributors
- Incubating - for more mature and organized groups that have participated in the community for some period of time
- Graduated - for mature efforts that have a proven track-record of deliverables and adding value to the community
- Archived - for groups that either are feature-complete and retired, or that no longer has active contributions occuring

Check failure on line 32 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

`occuring` is not a recognized word. (unrecognized-spelling)
lehors marked this conversation as resolved.
Show resolved Hide resolved

Each TI will haved equivellent, but slightly different requirements and benefits, depending on their stage in the lifecyle and are defined below:

Check failure on line 34 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

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

Check failure on line 34 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

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

Check failure on line 34 in process/README.md

View workflow job for this annotation

GitHub Actions / Check Spelling 

`lifecyle` is not a recognized word. (unrecognized-spelling)
lehors marked this conversation as resolved.
Show resolved Hide resolved

* [Working Group Life Cycle](working-group-lifecycle.md)
* [Project Life Cycle](project-lifecycle.md)
Expand Down
Loading