---
tags: OpenJS, Onboarding
---

# nvm - node version manager

## Project Champion

Jordan Harband - nvm
Jory Burson - OpenJSF CPC

## Description

> A rough description of the project in less than 100 words.

Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

## Statement of alignment with OpenJS Foundation charter and mission

> Please refer to [the Cross Project Council's Charter](https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md).
> Please keep your answer to less than 250 words.

As far as I am aware, nvm is the most common and widely used method to install node.js, and certainly the most common tool to manage installed node.js versions. nvm has coordinated extensively in the past with the wider ecosystem, specifically node.js and io.js, to support users' use cases. By living in the OpenJSF, nvm will be able to ensure governance and CoC enforcement such that the project can survive if its current sole maintainer steps down, to help it grow and gain contributors, and to ensure that one human's whims can't threaten the productivity of users.

## List of all repos that are part of the project

For each repository, please provide:

- **link to repo**: https://github.com/nvm-sh/nvm
- **license information**: MIT: https://github.com/nvm-sh/nvm/blob/master/LICENSE.md
- **issue tracker** https://github.com/nvm-sh/nvm/issues
- **link to code of conduct**: TBD: will adopt foundation's CoC
- **any vendored dependencies**: N/A, nothing vendored

## Governance Structure

* **Is there a leadership team?** Yes, just Jordan
* **Who are the members of the leadership team?** see above
* **How are members of the leadership team nominated?** Arbitrarily and unilaterally
* **How are individuals outside of leadership given commit access?** see above
* **Please share links to all existing documentation e.g. GOVERNANCE.md / CONTRIBUTING.md**: N/A

**Additional Historical Context for nvm:**
Initially, Tim Caswell (@creationix) was the creator and sole maintainer. He then added @croach, I believe around 2011 - but they have only contributed twice, and nothing since 2013. Tim then added @ljharb in 2013, who since v0.2.0 (currently v0.34.0) has been the sole maintainer. In 2019, @creationix transferred the `nvm` repo to the newly created `nvm-sh` org, with the intention of making it easier to transition the project into a foundation.

## Desired Initial Project Phase

> Please refer to [Section III, Stages - Definitions & Expectations](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_PROGRESSION.md#iii-stages---definitions--expectations) of PROJECT_PROGRESSION.md.

At Large

## Official Communication Channels

> List current channels e.g.: Slack / IRC / Mailing lists

#nvm on freenode IRC
https://gitter.im/creationix/nvm

## Project Website

just github repo (and http://nvm.sh redirector URL)

## Social Media Accounts

**Links to social media accounts:**
N/A

## Existing Financial Sponsorship

> Does your project currently receive funds? Who do they come from and what are the funds used for?

I'm a Github Sponsor, but that's not project-specific; I'm signed up to "lift" nvm on Tidelift, but it's not currently receiving any funds, although I might in the future as subscribers join Tidelift and indicate they depend on nvm.

## Infrastructure Needs or Requests

> What needs will your project have from the foundation? Feel free to provide a list.

- ensure no single point of failure for nvm.sh domain, github repo access, npm nvm project, etc
- set up SSL for nvm.sh redirector, and ensure I can retain access to DNS records
- design a project logo

## Onboarding Checklist

> This is an informational checklist to help projects onboard into the OpenJS Foundation - tasks we will complete together after your project has been accepted into the incubation process. If you have any questions or need help, the OpenJS Foundation CPC is available to assist.

- [ ] Adopt the OpenJS Foundation Code of Conduct
- [ ] Update project CoC reporting methods to include OpenJS Foundation escalation path
- [ ] Transfer official domains to OpenJS Foundation
- [x] Identify and document other core project infrastructure
* nvm-sh github org
* nvm.sh domain
* https://www.npmjs.com/package/nvm
- [n/a] If choosing to use a Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO), make selection and implement appropriate tool
- [n/a] Add or Update Governance.md document (required for Impact stage)
- [ ] Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
- [ ] Project Charter is published on website or github
- [ ] Update legal copyright notice on project website and github
- [ ] Add OpenJS Foundation logo to project website
- [ ] Add Project logo to OpenJS Foundation website; update PROJECTS.md file
- [ ] Transfer logomark to the OpenJS Foundation
- [ ] If project is using crowdfunding platforms, add disclaimer to platforms
- [x] Identify individuals from the project to join the CPC
- [ ] Document project and foundation contacts for:
* marketing & social media
* infrastructure
* legal/governance help

## Questions?

> What questions do you have? What questions might arise during your application?
>
None at this time