From 1b7ba16e34e176678a83f9154c32cbcc81826456 Mon Sep 17 00:00:00 2001 From: rudd Date: Sun, 15 Jun 2025 16:46:22 -0700 Subject: [PATCH 01/13] Create third-party-services-documentation-policy.md This is the proposed Third Party Services Documentation Policy discussed in https://github.com/openjs-foundation/cross-project-council/issues/1425. --- ...ird-party-services-documentation-policy.md | 121 ++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 project-resources/third-party-services-documentation-policy.md diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md new file mode 100644 index 000000000..e71eaa225 --- /dev/null +++ b/project-resources/third-party-services-documentation-policy.md @@ -0,0 +1,121 @@ +# **OpenJS Third Party Services Documentation Policy** + +## **Summary** + +This policy establishes communications and documentation guidelines that allow the OpenJS Foundation to maintain visibility of the third party services OpenJS hosted projects are currently using or planning to in the future. + +The Foundation wishes to leverage this information to: + +* Identify opportunities for strategic vendor partnerships +* Provide support and guidance for vendor partnerships +* Understand development infrastructure needs across Foundation projects + +This policy is intended to be structured in a way that enables the Foundation to understand and foster partnerships while respecting project autonomy and security considerations. + +# **Policy: Notify the Foundation before changing existing significant service providers or engaging new ones** + +Before engaging with a significant third-party SaaS or infrastructure provider, projects are asked to contact the OpenJS Foundation (Robin Ginn and Ben Sternthal) at [operations@openjsf.org](operations@openjsf.org). The Foundation may have an existing arrangement or might want to establish a new partnership. + +# **Policy: Maintain documentation of services** + +All projects hosted by the OpenJS Foundation are asked to maintain a service registry file that documents significant third-party SaaS products and infrastructure providers used by the project. An example of the content and structure of this file can be found below under [services.md content and format](#services.md-content-and-format). + +This policy has three components: 1) have the file, 2) make it accessible to OpenJS, 3) keep the file up to date and notify OpenJS. + +Projects may choose to use an OpenJS services.md file or their own service registry documentation. + +**Policy Table of Contents** + +- [1) Have a service registry file](#have-a-service-registry-file) + - [Option 1: Use an OpenJS services.md file](#option-1:-use-a-services.md-file) + - [Option 2: Use your own service registry documentation](#option-2:-use-your-own-services-registry-documentation) +- [2) Ensure the service registry is accessible to the OpenJS Foundation](#ensure-the-service-registry-is-accessible-to-the-openjs-foundation) +- [3) Keep the service registry file up to date and notify the OpenJS Foundation of changes](#keep-the-service-registry-file-up-to-date-and-notify-the-openjs-foundation-of-changes) + +## **1. Have a service registry file** + +Projects have two options for how to : + +* **Option 1**: Use an `services.md` file +* **Option 2:** Use their own service registry file that contains at least the equivalent detail as an OpenJS `services.md` file + +Regardless of their choice, the file must be shared with the OpenJS Foundation (Robin Ginn and Ben Sternthal). + +### **Option 1: Use a services.md file** {#option-1:-use-a-services.md-file} + +Project maintainers can choose to use a `services.md` file to document significant third-party SaaS products and infrastructure providers used by the project. + +`Services.md` may be as simple as a Markdown list like the one illustrated below.. This example is illustrative and not intended to necessarily be comprehensive on what could be included as each project may have additional items unique to them. + +#### **`Services.md` content and format** + +``` +# Third-Party Services Used + +This project relies on the following third-party services: + +## Hosting & Infrastructure +- **Cloud Provider:** AWS (EC2, S3) +- **CDN:** Cloudflare +- **DNS Provider:** Namecheap + +## Development & CI/CD +- **Code Repository:** GitHub +- **CI/CD:** GitHub Actions, Travis CI +- **Artifact Storage:** Docker Hub, NPM + +## Monitoring & Security +- **Logging:** Datadog +- **Error Tracking:** Sentry +- **Dependency Management:** Dependabot +- **Security Scanning:** CodeQL + +## Communication & Support +- **Email Provider:** SendGrid +- **Issue Tracking:** GitHub Issues +``` + +Keep entries high-level. Do not include sensitive information such as vendor contacts, contract or license information, or specific data about the infrastructure itself, especially if the file is expected to be public. + +### **Option 2: Use your own services registry documentation** + +Project maintainers may choose to continue using their own existing service registry or create a more customized service registry file. The only requirement for this is that the service registry file contains the same level of detail as an OpenJS `services.md` file. + +## **2. Ensure the service registry is accessible to the OpenJS Foundation** {#ensure-the-service-registry-is-accessible-to-the-openjs-foundation} + +Projects have two options on how to approach storing and granting OpenJS access to their service registry file. Regardless of the approach, the service registry file must be accessible to the OpenJS Executive Director Robin Ginn ([@rginn](https://www.github.com/rginn), [rginn@openjsf.org](mailto:rginn@openjsf.org)) and OpenJS Director of Program Management Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal), [bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)). + +* **Option 1: Store the service registry file in the Project’s own GitHub organization** +* **Option 2: Store the service registry file elsewhere** + +Project maintainers must proactively inform the Foundation of where their service registry file is located by emailing [operations@openjsf.org](mailto:operations@openjsf.org). + +### **Option 1:** **Store the service registry file in the Project’s own GitHub organization** + +Projects may choose, at their own discretion, to place this file anywhere in their GitHub organization in either a public or private repository. The level of detail expected of the `services.md` file is typically not sensitive and often easily discovered, however the Foundation leaves the decision of where the file is stored to each project's preferences and governance. + +### **Option 2: Store the service registry file in elsewhere** + +Projects are free to choose another location, such as a Google Workspace or hackmd.io, to store their service registry file. + +## **3. Keep the service registry file up to date and notify the OpenJS Foundation of changes** + +The service registry file is to be updated as necessary to remain an accurate reflection of the current state of the project. Under certain circumstances, such as during a transition, it may be appropriate for the service registry file to also contain credible plans for future or in progress changes. + +When considering or performing updates to the service registry file, regardless of where it is stored, inform Robin Ginn and Ben Sternthal by: + +* Contacting [operations@openjsf.org](mailto:operations@openjsf.org) in advance of making a change. +* Including [@rginn](https://www.github.com/rginn) and [@bensternthal](https://www.github.com/bensternthal) on issues, discussions, and pull requests regarding the change. + +**If the service registry is stored in GitHub:** + +* Include Robin Ginn ([@rginn](https://www.github.com/rginn)) and Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal)) as collaborators with read access to the repository containing the service registry file so they can watch the repository for changes. + +**If the service registry is stored elsewhere:** + +* Grant Robin Ginn ([rginn@openjsf.org](mailto:rginn@openjsf.org)) and Ben Sternthnal ([bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)) adequate permissions so that they can monitor the file for changes. + +## **Questions and Support** + +For questions about this policy or assistance with implementation, please contact the [OpenJS Foundation](operations@openjsf.org). + From 5b6b89028985ed3359276064311ffc887bf00325 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:16:12 -0700 Subject: [PATCH 02/13] Update project-resources/third-party-services-documentation-policy.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Michał Gołębiowski-Owczarek Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index e71eaa225..5f30ecdb6 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -1,4 +1,4 @@ -# **OpenJS Third Party Services Documentation Policy** +# OpenJS Third Party Services Documentation Policy ## **Summary** From 33bab1fd2d8a1aba1e7fb24993b647075241eede Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:18:43 -0700 Subject: [PATCH 03/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 5f30ecdb6..ea84ff4b2 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -45,7 +45,7 @@ Regardless of their choice, the file must be shared with the OpenJS Foundation ( Project maintainers can choose to use a `services.md` file to document significant third-party SaaS products and infrastructure providers used by the project. -`Services.md` may be as simple as a Markdown list like the one illustrated below.. This example is illustrative and not intended to necessarily be comprehensive on what could be included as each project may have additional items unique to them. +`Services.md` may be as simple as a Markdown list like the one illustrated below. This example is illustrative and not intended to necessarily be comprehensive on what could be included as each project may have additional items unique to them. #### **`Services.md` content and format** From 59b72af155bdfb1f79c0cd95f425f7652f3b2a1a Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:18:54 -0700 Subject: [PATCH 04/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index ea84ff4b2..9833c9b97 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -34,7 +34,7 @@ Projects may choose to use an OpenJS services.md file or their own service regis ## **1. Have a service registry file** -Projects have two options for how to : +Projects have two options for how to: * **Option 1**: Use an `services.md` file * **Option 2:** Use their own service registry file that contains at least the equivalent detail as an OpenJS `services.md` file From 5ab73b71bdf2f6449f767093911cbf5215211b33 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:19:04 -0700 Subject: [PATCH 05/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 9833c9b97..405b837d6 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -92,7 +92,7 @@ Project maintainers must proactively inform the Foundation of where their servic ### **Option 1:** **Store the service registry file in the Project’s own GitHub organization** -Projects may choose, at their own discretion, to place this file anywhere in their GitHub organization in either a public or private repository. The level of detail expected of the `services.md` file is typically not sensitive and often easily discovered, however the Foundation leaves the decision of where the file is stored to each project's preferences and governance. +Projects may choose, at their own discretion, to place this file anywhere in their GitHub organization in either a public or private repository. The level of detail expected of the `services.md` file is typically not sensitive and often easily discovered; however, the Foundation leaves the decision of where the file is stored to each project's preferences and governance. ### **Option 2: Store the service registry file in elsewhere** From 2eb886b740dd1d45265ebc543d52f02014d612f2 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:19:52 -0700 Subject: [PATCH 06/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 405b837d6..8e52f1e61 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -94,7 +94,7 @@ Project maintainers must proactively inform the Foundation of where their servic Projects may choose, at their own discretion, to place this file anywhere in their GitHub organization in either a public or private repository. The level of detail expected of the `services.md` file is typically not sensitive and often easily discovered; however, the Foundation leaves the decision of where the file is stored to each project's preferences and governance. -### **Option 2: Store the service registry file in elsewhere** +### **Option 2: Store the service registry file elsewhere** Projects are free to choose another location, such as a Google Workspace or hackmd.io, to store their service registry file. From 9e362bbb121cca23a002a63e1be259984fe1b4ab Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:20:02 -0700 Subject: [PATCH 07/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 8e52f1e61..6d798ab01 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -20,7 +20,7 @@ Before engaging with a significant third-party SaaS or infrastructure provider, All projects hosted by the OpenJS Foundation are asked to maintain a service registry file that documents significant third-party SaaS products and infrastructure providers used by the project. An example of the content and structure of this file can be found below under [services.md content and format](#services.md-content-and-format). -This policy has three components: 1) have the file, 2) make it accessible to OpenJS, 3) keep the file up to date and notify OpenJS. +This policy has three components: 1) have the file, 2) make it accessible to OpenJS, and 3) keep the file up to date and notify OpenJS. Projects may choose to use an OpenJS services.md file or their own service registry documentation. From 49b3a0aecb4b8d56ef271c1d0ded2b8c5f8c2531 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:20:31 -0700 Subject: [PATCH 08/13] Update project-resources/third-party-services-documentation-policy.md Co-authored-by: Mohammed Keyvanzadeh Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 6d798ab01..3f844198b 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -36,7 +36,7 @@ Projects may choose to use an OpenJS services.md file or their own service regis Projects have two options for how to: -* **Option 1**: Use an `services.md` file +* **Option 1:** Use a `services.md` file * **Option 2:** Use their own service registry file that contains at least the equivalent detail as an OpenJS `services.md` file Regardless of their choice, the file must be shared with the OpenJS Foundation (Robin Ginn and Ben Sternthal). From 2479da9971919c38eb5525fc6f4edce5eb488b66 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:27:19 -0700 Subject: [PATCH 09/13] Update third-party-services-documentation-policy.md Signed-off-by: rudd --- .../third-party-services-documentation-policy.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 3f844198b..c033d74ec 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -26,11 +26,11 @@ Projects may choose to use an OpenJS services.md file or their own service regis **Policy Table of Contents** -- [1) Have a service registry file](#have-a-service-registry-file) - - [Option 1: Use an OpenJS services.md file](#option-1:-use-a-services.md-file) - - [Option 2: Use your own service registry documentation](#option-2:-use-your-own-services-registry-documentation) -- [2) Ensure the service registry is accessible to the OpenJS Foundation](#ensure-the-service-registry-is-accessible-to-the-openjs-foundation) -- [3) Keep the service registry file up to date and notify the OpenJS Foundation of changes](#keep-the-service-registry-file-up-to-date-and-notify-the-openjs-foundation-of-changes) +- [1) Have a service registry file + - Option 1: Use an OpenJS services.md file + - Option 2: Use your own service registry documentation +- [2) Ensure the service registry is accessible to the OpenJS Foundation +- [3) Keep the service registry file up to date and notify the OpenJS Foundation of changes ## **1. Have a service registry file** @@ -41,7 +41,7 @@ Projects have two options for how to: Regardless of their choice, the file must be shared with the OpenJS Foundation (Robin Ginn and Ben Sternthal). -### **Option 1: Use a services.md file** {#option-1:-use-a-services.md-file} +### **Option 1: Use a services.md file** Project maintainers can choose to use a `services.md` file to document significant third-party SaaS products and infrastructure providers used by the project. From 1b9f954b0fc87bbb52831728defb07e5a17a00ed Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:28:28 -0700 Subject: [PATCH 10/13] Update third-party-services-documentation-policy.md Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index c033d74ec..fd83ae4be 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -18,7 +18,7 @@ Before engaging with a significant third-party SaaS or infrastructure provider, # **Policy: Maintain documentation of services** -All projects hosted by the OpenJS Foundation are asked to maintain a service registry file that documents significant third-party SaaS products and infrastructure providers used by the project. An example of the content and structure of this file can be found below under [services.md content and format](#services.md-content-and-format). +All projects hosted by the OpenJS Foundation are asked to maintain a service registry file that documents significant third-party SaaS products and infrastructure providers used by the project. An example of the content and structure of this file can be found below under **services.md content and format**. This policy has three components: 1) have the file, 2) make it accessible to OpenJS, and 3) keep the file up to date and notify OpenJS. From 2c45458dc0be09939a68810dcbcb064ee2cd3859 Mon Sep 17 00:00:00 2001 From: rudd Date: Mon, 30 Jun 2025 20:29:17 -0700 Subject: [PATCH 11/13] Update third-party-services-documentation-policy.md Signed-off-by: rudd --- project-resources/third-party-services-documentation-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index fd83ae4be..47d54c0f6 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -81,7 +81,7 @@ Keep entries high-level. Do not include sensitive information such as vendor con Project maintainers may choose to continue using their own existing service registry or create a more customized service registry file. The only requirement for this is that the service registry file contains the same level of detail as an OpenJS `services.md` file. -## **2. Ensure the service registry is accessible to the OpenJS Foundation** {#ensure-the-service-registry-is-accessible-to-the-openjs-foundation} +## **2. Ensure the service registry is accessible to the OpenJS Foundation** Projects have two options on how to approach storing and granting OpenJS access to their service registry file. Regardless of the approach, the service registry file must be accessible to the OpenJS Executive Director Robin Ginn ([@rginn](https://www.github.com/rginn), [rginn@openjsf.org](mailto:rginn@openjsf.org)) and OpenJS Director of Program Management Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal), [bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)). From e6238f9dbbc951cd204037fe71885f1cc38862a2 Mon Sep 17 00:00:00 2001 From: rudd Date: Wed, 2 Jul 2025 15:25:06 -0700 Subject: [PATCH 12/13] Update third-party-services-documentation-policy.md Signed-off-by: rudd --- ...ird-party-services-documentation-policy.md | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index 47d54c0f6..b72f2f21d 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -1,6 +1,6 @@ # OpenJS Third Party Services Documentation Policy -## **Summary** +## Summary This policy establishes communications and documentation guidelines that allow the OpenJS Foundation to maintain visibility of the third party services OpenJS hosted projects are currently using or planning to in the future. @@ -12,11 +12,11 @@ The Foundation wishes to leverage this information to: This policy is intended to be structured in a way that enables the Foundation to understand and foster partnerships while respecting project autonomy and security considerations. -# **Policy: Notify the Foundation before changing existing significant service providers or engaging new ones** +# Policy: Notify the Foundation before changing existing significant service providers or engaging new ones Before engaging with a significant third-party SaaS or infrastructure provider, projects are asked to contact the OpenJS Foundation (Robin Ginn and Ben Sternthal) at [operations@openjsf.org](operations@openjsf.org). The Foundation may have an existing arrangement or might want to establish a new partnership. -# **Policy: Maintain documentation of services** +# Policy: Maintain documentation of services All projects hosted by the OpenJS Foundation are asked to maintain a service registry file that documents significant third-party SaaS products and infrastructure providers used by the project. An example of the content and structure of this file can be found below under **services.md content and format**. @@ -32,22 +32,22 @@ Projects may choose to use an OpenJS services.md file or their own service regis - [2) Ensure the service registry is accessible to the OpenJS Foundation - [3) Keep the service registry file up to date and notify the OpenJS Foundation of changes -## **1. Have a service registry file** +## 1. Have a service registry file Projects have two options for how to: -* **Option 1:** Use a `services.md` file -* **Option 2:** Use their own service registry file that contains at least the equivalent detail as an OpenJS `services.md` file +* Option 1: Use a `services.md` file +* Option 2: Use their own service registry file that contains at least the equivalent detail as an OpenJS `services.md` file Regardless of their choice, the file must be shared with the OpenJS Foundation (Robin Ginn and Ben Sternthal). -### **Option 1: Use a services.md file** +### Option 1: Use a services.md file Project maintainers can choose to use a `services.md` file to document significant third-party SaaS products and infrastructure providers used by the project. `Services.md` may be as simple as a Markdown list like the one illustrated below. This example is illustrative and not intended to necessarily be comprehensive on what could be included as each project may have additional items unique to them. -#### **`Services.md` content and format** +#### `Services.md` content and format ``` # Third-Party Services Used @@ -77,28 +77,28 @@ This project relies on the following third-party services: Keep entries high-level. Do not include sensitive information such as vendor contacts, contract or license information, or specific data about the infrastructure itself, especially if the file is expected to be public. -### **Option 2: Use your own services registry documentation** +### Option 2: Use your own services registry documentation Project maintainers may choose to continue using their own existing service registry or create a more customized service registry file. The only requirement for this is that the service registry file contains the same level of detail as an OpenJS `services.md` file. -## **2. Ensure the service registry is accessible to the OpenJS Foundation** +## 2. Ensure the service registry is accessible to the OpenJS Foundation Projects have two options on how to approach storing and granting OpenJS access to their service registry file. Regardless of the approach, the service registry file must be accessible to the OpenJS Executive Director Robin Ginn ([@rginn](https://www.github.com/rginn), [rginn@openjsf.org](mailto:rginn@openjsf.org)) and OpenJS Director of Program Management Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal), [bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)). -* **Option 1: Store the service registry file in the Project’s own GitHub organization** -* **Option 2: Store the service registry file elsewhere** +* Option 1: Store the service registry file in the Project’s own GitHub organization +* Option 2: Store the service registry file elsewhere Project maintainers must proactively inform the Foundation of where their service registry file is located by emailing [operations@openjsf.org](mailto:operations@openjsf.org). -### **Option 1:** **Store the service registry file in the Project’s own GitHub organization** +### Option 1: Store the service registry file in the Project’s own GitHub organization Projects may choose, at their own discretion, to place this file anywhere in their GitHub organization in either a public or private repository. The level of detail expected of the `services.md` file is typically not sensitive and often easily discovered; however, the Foundation leaves the decision of where the file is stored to each project's preferences and governance. -### **Option 2: Store the service registry file elsewhere** +### Option 2: Store the service registry file elsewhere Projects are free to choose another location, such as a Google Workspace or hackmd.io, to store their service registry file. -## **3. Keep the service registry file up to date and notify the OpenJS Foundation of changes** +## 3. Keep the service registry file up to date and notify the OpenJS Foundation of changes The service registry file is to be updated as necessary to remain an accurate reflection of the current state of the project. Under certain circumstances, such as during a transition, it may be appropriate for the service registry file to also contain credible plans for future or in progress changes. @@ -115,7 +115,7 @@ When considering or performing updates to the service registry file, regardless * Grant Robin Ginn ([rginn@openjsf.org](mailto:rginn@openjsf.org)) and Ben Sternthnal ([bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)) adequate permissions so that they can monitor the file for changes. -## **Questions and Support** +## Questions and Support For questions about this policy or assistance with implementation, please contact the [OpenJS Foundation](operations@openjsf.org). From 981e20fb94c01f480df59eb43ff16b04b769321d Mon Sep 17 00:00:00 2001 From: rudd Date: Wed, 2 Jul 2025 15:34:21 -0700 Subject: [PATCH 13/13] Update third-party-services-documentation-policy.md Signed-off-by: rudd --- ...third-party-services-documentation-policy.md | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/project-resources/third-party-services-documentation-policy.md b/project-resources/third-party-services-documentation-policy.md index b72f2f21d..02b6b408f 100644 --- a/project-resources/third-party-services-documentation-policy.md +++ b/project-resources/third-party-services-documentation-policy.md @@ -14,7 +14,7 @@ This policy is intended to be structured in a way that enables the Foundation to # Policy: Notify the Foundation before changing existing significant service providers or engaging new ones -Before engaging with a significant third-party SaaS or infrastructure provider, projects are asked to contact the OpenJS Foundation (Robin Ginn and Ben Sternthal) at [operations@openjsf.org](operations@openjsf.org). The Foundation may have an existing arrangement or might want to establish a new partnership. +Before engaging with a significant third-party SaaS or infrastructure provider, projects are asked to contact the OpenJS Foundation at [operations@openjsf.org](operations@openjsf.org). The Foundation may have an existing arrangement or might want to establish a new partnership. # Policy: Maintain documentation of services @@ -83,7 +83,7 @@ Project maintainers may choose to continue using their own existing service regi ## 2. Ensure the service registry is accessible to the OpenJS Foundation -Projects have two options on how to approach storing and granting OpenJS access to their service registry file. Regardless of the approach, the service registry file must be accessible to the OpenJS Executive Director Robin Ginn ([@rginn](https://www.github.com/rginn), [rginn@openjsf.org](mailto:rginn@openjsf.org)) and OpenJS Director of Program Management Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal), [bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)). +Projects have two options on how to approach storing and granting OpenJS access to their service registry file. Regardless of the approach, the service registry file must be accessible to the OpenJS Leadership ([operations@openjsf.org](mailto:operations@openjsf.org)). * Option 1: Store the service registry file in the Project’s own GitHub organization * Option 2: Store the service registry file elsewhere @@ -105,17 +105,8 @@ The service registry file is to be updated as necessary to remain an accurate re When considering or performing updates to the service registry file, regardless of where it is stored, inform Robin Ginn and Ben Sternthal by: * Contacting [operations@openjsf.org](mailto:operations@openjsf.org) in advance of making a change. -* Including [@rginn](https://www.github.com/rginn) and [@bensternthal](https://www.github.com/bensternthal) on issues, discussions, and pull requests regarding the change. - -**If the service registry is stored in GitHub:** - -* Include Robin Ginn ([@rginn](https://www.github.com/rginn)) and Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal)) as collaborators with read access to the repository containing the service registry file so they can watch the repository for changes. - -**If the service registry is stored elsewhere:** - -* Grant Robin Ginn ([rginn@openjsf.org](mailto:rginn@openjsf.org)) and Ben Sternthnal ([bsternthal@linuxfondation.org](mailto:bsternthal@linuxfondation.org)) adequate permissions so that they can monitor the file for changes. - + ## Questions and Support -For questions about this policy or assistance with implementation, please contact the [OpenJS Foundation](operations@openjsf.org). +For questions about this policy or assistance with implementation, please contact the [OpenJS Foundation](mailto:operations@openjsf.org).