From 3a27b3f12e4c896bdf7bf3c66fe6b0e3b18a2d12 Mon Sep 17 00:00:00 2001 From: Erin Schnabel Date: Thu, 16 Apr 2026 13:58:25 -0400 Subject: [PATCH 1/3] Revise partner reference requirements in terms and conditions Updated partner reference guidelines to require mentioning all vendors providing EOL support. --- agreements/project-contribution/terms-and-conditions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agreements/project-contribution/terms-and-conditions.md b/agreements/project-contribution/terms-and-conditions.md index b132a53..7391811 100644 --- a/agreements/project-contribution/terms-and-conditions.md +++ b/agreements/project-contribution/terms-and-conditions.md @@ -168,7 +168,7 @@ for users seeking continued support. **Partner support references:** Projects are not required to name individual OSSI partners on project pages. A link to the Foundation’s OSSI page is sufficient. -If a project chooses to reference individual partners, it should do so in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. +If a project chooses to reference an individual partner, then the project must reference all vendors which provide EOL support in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. ## Intellectual Property Management From c92a1ace378ee07fd2668dbd60d2bbe26bf16bfe Mon Sep 17 00:00:00 2001 From: Erin Schnabel Date: Wed, 22 Apr 2026 11:34:29 -0400 Subject: [PATCH 2/3] Update agreements/project-contribution/terms-and-conditions.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Yoann Rodière --- agreements/project-contribution/terms-and-conditions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agreements/project-contribution/terms-and-conditions.md b/agreements/project-contribution/terms-and-conditions.md index 7391811..641bc07 100644 --- a/agreements/project-contribution/terms-and-conditions.md +++ b/agreements/project-contribution/terms-and-conditions.md @@ -168,7 +168,7 @@ for users seeking continued support. **Partner support references:** Projects are not required to name individual OSSI partners on project pages. A link to the Foundation’s OSSI page is sufficient. -If a project chooses to reference an individual partner, then the project must reference all vendors which provide EOL support in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. +If a project chooses to reference an individual partner, then the project must reference all vendors part of the open-source sustainability initiative which provide EOL support for this project in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. ## Intellectual Property Management From 72228fb0c5f145f33fecebe4e7196079e3c22096 Mon Sep 17 00:00:00 2001 From: Erin Schnabel Date: Wed, 22 Apr 2026 11:38:08 -0400 Subject: [PATCH 3/3] tighten language (still all or none) --- agreements/project-contribution/terms-and-conditions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agreements/project-contribution/terms-and-conditions.md b/agreements/project-contribution/terms-and-conditions.md index 641bc07..d70d6ee 100644 --- a/agreements/project-contribution/terms-and-conditions.md +++ b/agreements/project-contribution/terms-and-conditions.md @@ -168,7 +168,7 @@ for users seeking continued support. **Partner support references:** Projects are not required to name individual OSSI partners on project pages. A link to the Foundation’s OSSI page is sufficient. -If a project chooses to reference an individual partner, then the project must reference all vendors part of the open-source sustainability initiative which provide EOL support for this project in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. +If a project chooses to reference an individual partner, it must also reference all other OSSI partners that provide EOL support for that project, in a fair and non-misleading manner consistent with the Foundation’s Trademark Policy and Code of Conduct. ## Intellectual Property Management