Skip to content

Commit 12f3890

Browse files
committed
Create npm continuity policy
1 parent 40c0722 commit 12f3890

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# OpenJS npm Continuity Policy
2+
3+
## Summary
4+
5+
This policy is intended to ensure that OpenJS npm Organizations remain accessible and manageable.
6+
7+
It addresses the following use cases:
8+
9+
* Managing projects and users when maintainers are inactive or unreachable
10+
* [Deprecating packages](https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions) when maintainers are no longer reachable
11+
* Adding or removing npm Organization members in emergency situations
12+
13+
# Continuity Options for Projects
14+
15+
### Option 1: Add an OpenJS Continuity Account to your npm Organization(s) and/or Packages**
16+
17+
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)).
18+
19+
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).
20+
21+
* If you use npm Organizations, you will add this account to your Organization(s) and grant it the Owner role.
22+
* If you don’t use npm Organizations, you will add this account as a Maintainer to your npm Packages.
23+
24+
### Option 2: Opt Out**
25+
26+
Projects that feel their governance is sufficient to provide continuity may opt out of this policy by requesting an exception from the CPC.
27+
28+
To initiate this process, please create an issue in the [CPC repository](https://github.com/openjs-foundation/cross-project-council/issues).
29+
30+
- Organizations with 1-2 maintainers in the Owner role are the highest priority for this policy and are unlikely to be granted an exception.
31+
- 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.

0 commit comments

Comments
 (0)