From c5a4e4db00557926bc679233216da68a5c330386 Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Thu, 20 Jun 2024 13:20:13 -0700 Subject: [PATCH 1/6] Add clarity wrt SIGs that need to be projects When SIGs produce code or specification, they need to be projects, but this was not fully clear before. Aiming to clarify this. Signed-off-by: Mihai Maruseac --- process/Technical_Initiative_Lifecycle.md | 2 +- process/sig-lifecycle.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/process/Technical_Initiative_Lifecycle.md b/process/Technical_Initiative_Lifecycle.md index 8965753d..dbb42675 100644 --- a/process/Technical_Initiative_Lifecycle.md +++ b/process/Technical_Initiative_Lifecycle.md @@ -21,7 +21,7 @@ flowchart TD 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. -A SIG can be developed within a WG or Project to address a specific need. +A SIG can be developed within a WG or Project to address a specific need. Note that a SIG cannot produce code or specifications. # II. Lifecycle diff --git a/process/sig-lifecycle.md b/process/sig-lifecycle.md index 9fdf2658..93238678 100644 --- a/process/sig-lifecycle.md +++ b/process/sig-lifecycle.md @@ -22,7 +22,7 @@ The SIG life cycle begins with interested contributors deciding to undertake thi * SIGs may have regular meetings separate from their governing body, if so: * They should appear on the OpenSSF calendar * They should have a document with upcoming agendas and notes from past meetings -* If the SIG starts to produce code or specifications, they should consider becoming a [project](./project-lifecycle.md) instead +* If the SIG starts to produce code or specifications, they must migrate to a [project](./project-lifecycle.md) instead ## To become `Incubating`: From f040bddd1b3005e1e6136a15cb841f8535121e9b Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Sat, 22 Jun 2024 09:15:47 -0700 Subject: [PATCH 2/6] Apply suggestions from code review Signed-off-by: Mihai Maruseac --- process/Technical_Initiative_Lifecycle.md | 2 +- process/sig-lifecycle.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/process/Technical_Initiative_Lifecycle.md b/process/Technical_Initiative_Lifecycle.md index dbb42675..4ff73b7d 100644 --- a/process/Technical_Initiative_Lifecycle.md +++ b/process/Technical_Initiative_Lifecycle.md @@ -21,7 +21,7 @@ flowchart TD 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. -A SIG can be developed within a WG or Project to address a specific need. Note that a SIG cannot produce code or specifications. +A SIG can be developed within a WG or Project to address a specific need. Note that a SIG purpose is not to primary produce code or specifications (it can produce them as secondary goals, or as experimental POCs). # II. Lifecycle diff --git a/process/sig-lifecycle.md b/process/sig-lifecycle.md index 93238678..a2fb7e80 100644 --- a/process/sig-lifecycle.md +++ b/process/sig-lifecycle.md @@ -22,7 +22,7 @@ The SIG life cycle begins with interested contributors deciding to undertake thi * SIGs may have regular meetings separate from their governing body, if so: * They should appear on the OpenSSF calendar * They should have a document with upcoming agendas and notes from past meetings -* If the SIG starts to produce code or specifications, they must migrate to a [project](./project-lifecycle.md) instead +* If the SIG starts to produce code or specifications, they should consider becoming a [project](./project-lifecycle.md) instead, especially if this becomes the main scope of the SIG. ## To become `Incubating`: From 3870e07e1053351995b2842f18670c0b6aae4f48 Mon Sep 17 00:00:00 2001 From: Kenny Paul <44849153+KennyPaul@users.noreply.github.com> Date: Wed, 26 Jun 2024 10:33:58 -0700 Subject: [PATCH 3/6] Added Q3 & 4 dates (#346) Signed-off-by: Kenny Paul --- process/TI Funding Request Process.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/process/TI Funding Request Process.md b/process/TI Funding Request Process.md index 5acf364a..a1a1e301 100644 --- a/process/TI Funding Request Process.md +++ b/process/TI Funding Request Process.md @@ -40,9 +40,14 @@ This process details how an eligible OpenSSF Technical Initiative can petition f - Accepted requests published: June 26, 2024 ### Q3 2024 + - Request submission deadline: Sep. 06, 2024 + - TAC review period: Sep. 09 - 13, 2024 + - Decisions announced (in writing): No later than Sep. 20, 2024 + - Accepted requests published: Sep. 25, 2024 -Mid-September; exact dates TBD -### Q4 2024 - -Mid-December; exact dates TBD +### Q4 2024 (for Q1 2025) + - Request submission deadline: Nov. 29, 2024 + - TAC review period: Dec. 02 - 06, 2024 + - Decisions announced (in writing): No later than Dec. 13, 2024 + - Accepted requests published: Dec. 18, 2024 From 1468b65dc7c85d6ee559dcbdb85009280df435ab Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Thu, 27 Jun 2024 13:20:37 -0700 Subject: [PATCH 4/6] Accept revision Co-authored-by: Marcela Melara Signed-off-by: Mihai Maruseac --- process/Technical_Initiative_Lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/Technical_Initiative_Lifecycle.md b/process/Technical_Initiative_Lifecycle.md index 4ff73b7d..3f1dd6c0 100644 --- a/process/Technical_Initiative_Lifecycle.md +++ b/process/Technical_Initiative_Lifecycle.md @@ -21,7 +21,7 @@ flowchart TD 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. -A SIG can be developed within a WG or Project to address a specific need. Note that a SIG purpose is not to primary produce code or specifications (it can produce them as secondary goals, or as experimental POCs). +A SIG can be developed within a WG or Project to address a specific need. Note that a SIG's primary purpose is not to produce code or specifications (it can produce them as secondary goals, or as experimental POCs). # II. Lifecycle From 82206062f4d58b7eb7ab2740d0a5d9c958a0b747 Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Thu, 27 Jun 2024 16:55:50 -0400 Subject: [PATCH 5/6] Update the changelog to match PR Signed-off-by: Mihai Maruseac --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ddce072a..516ee380 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,6 @@ # OpenSSF TAC Changelog +* 2024-06-27: Add clarity regarding SIG and projects (PR [#348](https://github.com/ossf/tac/pull/348)) * 2024-06-11: Update funding application to include specific TI, lifecycle, and amount (PR [#344](https://github.com/ossf/tac/pull/344)) * 2024-05-24: Improve election process and timeline * 2024-05-22: Add TI funding request to TAC decision process doc (PR [#329](https://github.com/ossf/tac/pull/329)) From 998d91c6747e8745a304940ddb96cef3ae891d8d Mon Sep 17 00:00:00 2001 From: Carlos O'Donell Date: Fri, 5 Jul 2024 15:02:34 -0400 Subject: [PATCH 6/6] Update README.md Provide link to CTI git repo. Signed-off-by: Carlos O'Donell --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1cc305ac..0284fb0e 100644 --- a/README.md +++ b/README.md @@ -93,7 +93,7 @@ The following Technical Initiatives have been approved by the TAC. You may learn | Name | Repository | Notes | Status | | -------------------------- | ----------------------------------- | ----- | ------ | -| Core Toolchain Infrastructure | Coming Soon | TBD | TBD | +| Core Toolchain Infrastructure | https://git.coretoolchain.dev/ | TBD | TBD | | Alpha Omega | https://github.com/ossf/alpha-omega | TBD | TBD | ### Special Interest Groups (SIGs) - *To Be Completed*