Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/webtorrent/webtorrent.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFeross Aboukhadijeh <feross@feross.org>2016-02-28 04:04:29 +0300
committerFeross Aboukhadijeh <feross@feross.org>2016-02-28 04:04:29 +0300
commitef1a78e8398f1f55bf9872e30217d547a3adf754 (patch)
treeff1af768e23eb373583fe2cb41588422d1685e0c /CONTRIBUTING.md
parentacd4492067e836b1aada587c84e171c64c6a1b14 (diff)
add GitHub ISSUE_TEMPLATE.md
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md35
1 files changed, 0 insertions, 35 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index 3ac2c69..0000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# WebTorrent Contributing Guidelines
-
-- Always use WebTorrent for legal downloads.
-- Always search for a related issue before starting a new issue.
-- Always choose a concise, helpful issue name.
-- Always stay on-topic. If you've got a new bug report or feature request, put it in its own issue.
-- Always be polite to other people.
-- Never post private information, such as torrent or tracker names, IP addresses, etc.
-
-Issues that break the rules may be deleted and locked without warning.
-
-## WebTorrent is an OPEN Open Source Project
-
-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** or modifying the Git history in any way.
-1. **External API changes and significant modifications** should be subject to a **pull request** to solicit feedback from other contributors.
-1. Pull requests to solicit feedback are *encouraged* for any other non-trivial contribution but left to the discretion of the contributor.
-1. Use a non-`master` branch for ongoing work.
-1. Contributors should attempt to adhere to the prevailing code style.
-1. Run `npm test` locally before submitting your PR to catch easy-to-miss style & testing issues
-
-## 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 is subject to pull requests or changes by contributors where you believe you have something valuable to add or change.
-
-*Thanks to [Rod Vagg](https://github.com/rvagg) and the [LevelUP](https://github.com/rvagg/node-levelup) project for coming up with this model of open source contribution.*