diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 5e1e87158c..0000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,26 +0,0 @@ -# Contributing to docker-node - -Thank you for your contribution. Here are a set of guidelines for contributing to the docker-node project. - -## Version Updates - -New **Node.js** releases are released as soon as possible. - -New **NPM** releases are not tracked. We simply use the NPM version bundled in the corresponding Node.js release. - -**Yarn** is updated to the latest version only when there is a new Node.js SemVer PATCH release (unless Yarn has received a security update), and it's updated only in the branch with the new release, preferably in the same PR. The `update.sh` script does this automatically when invoked with a specific branch, e.g. `./update.sh 6.10`. - -### Submitting a PR for a version update - -If you'd like to help us by submitting a PR for a version update, please do the following: - -1. [Fork this project.](https://docs.github.com/en/get-started/quickstart/fork-a-repo) -1. [Clone the forked repository.](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) -1. Create a branch for the update PR. For example, `git checkout main; git checkout -b version-update`. -1. Run `./update.sh`. You can see additional options by using accessing the built-in help documentation with `./update.sh -h`. This script will automatically update the appropriate files with the latest versions and checksums. -1. Commit the modified files to the `version-update` branch and push the branch to your fork. -1. [Create a PR to merge the branch from your fork into this project's default branch.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). - -## Adding dependencies to the base images - -NodeJS is a big ecosystem with a variety of different use cases. The docker images for node are designed to provide the minimum for running core node. Additional dependencies (including dependencies for npm or yarn such as git) will not be included in these base images and will need to be included in descendent image. diff --git a/GOVERNANCE.md b/GOVERNANCE.md deleted file mode 100644 index fb0b9a698f..0000000000 --- a/GOVERNANCE.md +++ /dev/null @@ -1,145 +0,0 @@ -# Docker Working Group - -The Node.js Docker project is jointly governed by a Working Group (WG) -that is responsible for high-level guidance of the project. - -The WG has final authority over this project including: - -* Technical direction -* Project governance and process (including this policy) -* Contribution policy -* GitHub repository hosting -* Conduct guidelines -* Maintaining the list of additional Collaborators - -For the current list of WG members, see the project -[README.md](./README.md#people). - -## Collaborators - -The [nodejs/docker-node](https://github.com/nodejs/docker-node) GitHub -repository is maintained by the WG and additional Collaborators who -are added by the WG on an ongoing basis. - -Individuals making significant and valuable contributions are made -Collaborators and given commit-access to the project. These -individuals are identified by the WG and their addition as -Collaborators is discussed as a pull request to this project's -[README.md](./README.md#people). - -_Note:_ If you make a significant contribution and are not considered -for commit-access log an issue or contact a WG member directly. - -Modifications of the contents of the -[nodejs/docker-node](https://github.com/nodejs/docker-node) repository -are made on a collaborative basis. Anybody with a GitHub account may -propose a modification via pull request and it will be considered by -the project Collaborators. All pull requests must be reviewed and -accepted by a Collaborator with sufficient expertise who is able to -take full responsibility for the change. In the case of pull requests -proposed by an existing Collaborator, an additional Collaborator is -required for sign-off. Consensus should be sought if additional -Collaborators participate and there is disagreement around a -particular modification. See _Consensus Seeking Process_ below for -further detail on the consensus model used for governance. - -Collaborators may opt to elevate significant or controversial -modifications, or modifications that have not found consensus to the -WG for discussion by assigning the ***WG-agenda*** label to a pull -request or issue. The WG should serve as the final arbiter where -required. - -For the current list of Collaborators, see the project -[README.md](./README.md#people). - -## WG Membership - -WG seats are not time-limited. There is no fixed size of the WG. -However, the expected target is between 6 and 12, to ensure adequate -coverage of important areas of expertise, balanced with the ability to -make decisions efficiently. - -There is no specific set of requirements or qualifications for WG -membership beyond these rules. - -The WG may add, or remove, members to and from the WG. A WG member may -choose to be removed from the WG by voluntary resignation. - -Changes to WG membership should be posted in the -[nodejs/docker-node](https://github.com/nodejs/docker-node) repository -as an issue or pull request with the ***WG-agenda*** label followed by -the consensus seeking process described below. - -No more than 1/3 of the WG members may be affiliated with the same -employer. If removal or resignation of a WG member, or a change of -employment by a WG member, creates a situation where more than 1/3 of -the WG membership shares an employer, then the situation must be -immediately remedied by the resignation or removal of one or more WG -members affiliated with the over-represented employer(s). - -## WG Meetings - -This working group does not meet. All discussions and decisions -happen in the -[nodejs/docker-node](https://github.com/nodejs/docker-node) repository -in issues and pull requests. Items that requires a decision by the -WG can be flagged with the ***WG-agenda*** label. - -When an issue is tagged with ***WG-agenda***, the WG may invite -persons or representatives from certain projects to participate in the -discussion in a non-voting capacity. - -## Consensus Seeking Process - -The WG follows a [Consensus -Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) -decision-making model. - -All proposed changes to the project must be made in the form of a pull -request to the repository (directly committing to a production branch -of the repository is not permitted). The consensus seeking process -will then follow via discussion by the WG members on that pull -request. Changes deemed trivial by WG members may be merged instantly -by any WG member, without waiting for consensus, so long as they leave -a note explaining the reason for the merge. - -When an agenda item has appeared to reach a consensus any WG member -may ask "Does anyone object?" as a final call for dissent from the -consensus. - -If an agenda item cannot reach a consensus a WG member can call for a -closing vote. The call for a vote must be seconded by a majority of -the WG or else the discussion will continue. Simple majority wins. - - - -## Developer's Certificate of Origin 1.1 - -By making a contribution to this project, I certify that: - -* (a) The contribution was created in whole or in part by me and I - have the right to submit it under the open source license - indicated in the file; or - -* (b) The contribution is based upon previous work that, to the best - of my knowledge, is covered under an appropriate open source - license and I have the right under that license to submit that - work with modifications, whether created in whole or in part - by me, under the same open source license (unless I am - permitted to submit under a different license), as indicated - in the file; or - -* (c) The contribution was provided directly to me by some other - person who certified (a), (b) or (c) and I have not modified - it. - -* (d) I understand and agree that this project and the contribution - are public and that a record of the contribution (including all - personal information I submit with it, including my sign-off) is - maintained indefinitely and may be redistributed consistent with - this project or the open source license(s) involved. - -## Code of Conduct - -The Node.js Code of Conduct, which applies to this project, can be found at -. diff --git a/LICENSE b/LICENSE index 6ad4fb741f..7ffe7004c9 100644 --- a/LICENSE +++ b/LICENSE @@ -1,3 +1,20 @@ +# This project contains IP governed by two licenses + +This project originated from the Open Source contributions to {{ Product }}, which is licensed under the license(s) listed below or as may be included in the source code files. As such, all unmodified code and materials are subject to the terms of {{ Product }}'s original license(s). +All other materials, including new files or modifications to existing files (the "Updates" or "Services") are original works of HeroDevs, Inc. and licensed under the HeroDevs NES License. +Access to this project, via any medium, is restricted to parties explicitly authorized by HeroDevs, Inc. Contact to learn more. + +## HeroDevs NES License + +Copyright © 2023-present, HeroDevs, Inc. All Rights Reserved. + +Access to this source code is restricted, regardless of medium, to parties who have a current commercial agreement with HeroDevs that authorizes such access. Unless otherwise executed in writing by HeroDevs, Inc., use of this source code, as well as any other associated asset, is subject to the terms and conditions of the applicable agreement located at . + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. + +-------- + The MIT License (MIT) Copyright (c) 2015 Joyent, Inc. diff --git a/README.md b/README.md index fc778a31e5..f91b219eff 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,5 @@ # Node.js -[![dockeri.co](https://dockerico.blankenship.io/image/node)](https://hub.docker.com/_/node) - -[![GitHub issues](https://img.shields.io/github/issues/nodejs/docker-node.svg "GitHub issues")](https://github.com/nodejs/docker-node) -[![GitHub stars](https://img.shields.io/github/stars/nodejs/docker-node.svg "GitHub stars")](https://github.com/nodejs/docker-node) - -The official Node.js docker image, made with love by the node community. - ## Table of Contents @@ -29,11 +22,6 @@ The official Node.js docker image, made with love by the node community. - [License](#license) - [Supported Docker versions](#supported-docker-versions) - [Supported Node.js versions](#supported-nodejs-versions) -- [Governance and Current Members](#governance-and-current-members) - - [Docker Working Group Members](#docker-working-group-members) - - [Docker Working Group Collaborators](#docker-working-group-collaborators) - - [Emeritus](#emeritus) - - [Docker Working Group Members](#docker-working-group-members-1) @@ -243,30 +231,3 @@ upgrade your Docker daemon. ## Supported Node.js versions This project will support Node.js versions as still under active support as per the [Node.js release schedule](https://github.com/nodejs/Release). - -## Governance and Current Members - -The Node.js Docker Image is governed by the Docker Working Group. See -[GOVERNANCE.md](GOVERNANCE.md) -to learn more about the group's structure and [CONTRIBUTING.md](CONTRIBUTING.md) for guidance -about the expectations for all contributors to this project. - -### Docker Working Group Members - -- Hans Kristian Flaatten ([starefossen](https://github.com/starefossen)) -- Hugues Malphettes ([hmalphettes](https://github.com/hmalphettes)) -- John Mitchell ([jlmitch5](https://github.com/jlmitch5)) - -### Docker Working Group Collaborators - -- Mikeal Rogers ([mikeal](https://github.com/mikeal)) -- Laurent Goderre ([LaurentGoderre](https://github.com/LaurentGoderre)) -- Simen Bekkhus ([SimenB](https://github.com/SimenB)) -- Peter Dave Hello ([PeterDaveHello](https://github.com/PeterDaveHello)) - -### Emeritus - -#### Docker Working Group Members - -- Christopher Horrell ([chorrell](https://github.com/chorrell)) -- Peter Petrov ([pesho](https://github.com/pesho)) diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index a820a3f551..0000000000 --- a/SECURITY.md +++ /dev/null @@ -1,12 +0,0 @@ -# Security Policy - -## Reporting a Vulnerability - -Security issues relating to Node.js project should follow the process documented on . - -CVEs for the base image packages should be reported to those repositories. Nothing to address those CVEs is in the hands of this repos. - -- [Alpine](https://github.com/alpinelinux/docker-alpine) -- [Debian (bullseye, bookworm)](https://github.com/debuerreotype/docker-debian-artifacts) - -When base images are patched, the images are rebuilt and rolled out to the Docker hub without intervention by this repo. This process is explained in .