Skip to content

Create third-party-services-documentation-policy.md #1482

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.

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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

ruddermann
Copy link
Contributor

This is the proposed Third Party Services Documentation Policy discussed in #1425.

This is the proposed Third Party Services Documentation Policy discussed in openjs-foundation#1425.
@ruddermann ruddermann requested a review from a team as a code owner June 15, 2025 23:54
@Koki1610

This comment was marked as off-topic.

Copy link
Member

@bjohansebas bjohansebas left a comment

Choose a reason for hiding this comment

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

LGTM


## **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), [[email protected]](mailto:[email protected])) and OpenJS Director of Program Management Ben Sternthal ([@bensternthal](https://www.github.com/bensternthal), [[email protected]](mailto:[email protected])).
Copy link
Contributor

Choose a reason for hiding this comment

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

Not that I foresee any changes here... 😉 But should we include concrete people in such documents? If anyone decides to step down, we may have a lot of docs to update.

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed. This has come up in different places. What about we have a list of staff members / functions in the repo and just reference those from here?

Copy link
Member

Choose a reason for hiding this comment

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

I agree with @tobie's suggestion.

Copy link
Member

Choose a reason for hiding this comment

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

Could aliases be used here too? Such as operations@

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 defer to @bensternthal on this since he and @rginn will be the ones operationalizing this.

Copy link
Contributor

Choose a reason for hiding this comment

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

@ovflowd Brings up a good point, an alias would save us a lot of effort if/when folks leave. I'd suggest we start with that and handle edge cases when they pop up.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok I'll update this and the npm continuity policy use the aliases instead.

ruddermann and others added 10 commits June 30, 2025 20:16
Co-authored-by: Michał Gołębiowski-Owczarek <[email protected]>
Signed-off-by: rudd <[email protected]>
@ruddermann
Copy link
Contributor Author

Resolved all the comments and feedback, lmk if I missed anything.

@ruddermann
Copy link
Contributor Author

Everything is updated based on feedback - check things out and if we're good to go then we're finished!

@tobie
Copy link
Contributor

tobie commented Jul 23, 2025

Notes from July 8 CPC call:

  • still a few comments unresolved
  • needs more reviews

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants