-
Notifications
You must be signed in to change notification settings - Fork 204
Create npm Continuity Policy #1483
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
Merged
ljharb
merged 8 commits into
openjs-foundation:main
from
ruddermann:npm-continuity-policy
Jul 8, 2025
+35
−0
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
12f3890
Create npm continuity policy
ruddermann 4eb1a4f
Update project-resources/npm-continuity-policy.md
ruddermann a939989
Update project-resources/npm-continuity-policy.md
ruddermann 2ba6044
Update npm-continuity-policy.md
ruddermann 5f45cfe
Update project-resources/npm-continuity-policy.md
ruddermann e87075d
Update project-resources/npm-continuity-policy.md
ruddermann acdd1c0
Update project-resources/npm-continuity-policy.md
ruddermann f392fff
Update npm-continuity-policy.md
ruddermann File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# OpenJS npm Continuity Policy | ||
|
||
## Summary | ||
|
||
This policy is intended to ensure that OpenJS npm Organizations remain accessible and manageable. | ||
|
||
It addresses the following use cases: | ||
|
||
* Managing projects and users when maintainers are inactive or unreachable | ||
* [Deprecating packages](https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions) when maintainers are no longer reachable | ||
* Adding or removing npm Organization members in emergency situations | ||
|
||
# Continuity Options for Projects | ||
|
||
### Option 1: Add an OpenJS Continuity Account to your npm Organization(s) and/or Packages** | ||
ruddermann marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
If you select this option a new, dedicated OpenJS account will be created specifically for your Project. This account will be managed by the OpenJS Executive Director (Robin Ginn, [@rginn](https://github.com/rginn)). | ||
ruddermann marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
To initiate this process, please create an issue in the [Infrastructure repository](https://github.com/openjs-foundation/infrastructure/issues/new?template=IT-SUPPORT-REQUEST.yml). | ||
|
||
* If you use npm Organizations, you will add this account to your Organization(s) and grant it the Owner role. | ||
* If you don’t use npm Organizations, you will add this account as a Maintainer to your npm Packages. | ||
ruddermann marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
### Option 2: Opt Out** | ||
ruddermann marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
Projects that feel their governance is sufficient to provide continuity may opt out of this policy by requesting an exception from the CPC. | ||
|
||
To initiate this process, please create an issue in the [CPC repository](https://github.com/openjs-foundation/cross-project-council/issues). | ||
|
||
- Organizations with 1-2 maintainers in the Owner role are the highest priority for this policy and are unlikely to be granted an exception. | ||
- Organizations with 3 or more maintainers in the Owner role who have been active in the past [6||12] months will be considered for an exception. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.