Skip to content

Latest commit

 

History

History
40 lines (23 loc) · 2.5 KB

CONTRIBUTING.md

File metadata and controls

40 lines (23 loc) · 2.5 KB
Raw

Contribution Guidelines

I'm thrilled that you're interested in contributing to this open-source book! Your contributions will help improve the quality and impact of the content for the benefit of the community. Please take a moment to read through the guidelines outlined below before you start contributing.

How to Contribute

You can contribute to this open-source book by submitting Pull Requests (PRs) for various improvements, such as code snippets, explanations, clarifications, and more. We appreciate your efforts in helping to make this resource better.

If you're unsure about a particular word, phrase, or concept used in the book, or if you have any doubts, please consider opening an issue to discuss it before creating a PR. We believe that collaboration and open communication lead to better results.

Content Contributions

By contributing content to this repository, you acknowledge and agree to the following:

License: Any content you contribute to this repository is provided under the terms of the MIT license. This means that you grant the repository owner a non-exclusive license to use, modify, and distribute your contributed content for the purposes of the book.

Non-Exclusive: This license is non-exclusive, which means you retain the right to use your contributed content elsewhere.

Attribution: Your contributions will be appropriately attributed to you within the book, in the contributors section.

Getting Started

  1. Fork the repository to your GitHub account.

  2. Create a new branch for your contributions. This helps in isolating changes and making your PRs more manageable.

  3. Make your desired changes or additions to the content.

  4. Test your changes to ensure they fit seamlessly with the existing content. For example, hyperlinks.

  5. Commit your changes with clear and descriptive commit messages.

  6. Create a Pull Request (PR) from your forked repository's branch to the main repository's branch.

  7. Provide a (somewhat) detailed description of your changes in the PR, along with any relevant context.

  8. Engage in any discussions or feedback related to your PR. Be open to suggestions and improvements.

  9. Once your PR is approved, it will be merged into the main repository.

Code of Conduct

By participating in this project, you agree to adhere to the Code of Conduct. We aim to maintain a respectful and inclusive environment for all contributors.

Thank you for being a part of Learn Nodejs the Hard way! Your contributions make a difference in the community.