From 6db4bab556ccc1fa1279a0f9c86016dafc557544 Mon Sep 17 00:00:00 2001 From: Lucas Nicodemus Date: Wed, 18 Mar 2015 12:16:44 -0600 Subject: [PATCH] Revert "Add major discussion on change to contributing" This reverts commit 05961692702250deefa235a21bf04c3bf8da948d. Conflicts: CONTRIBUTING.md --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index be44ed48..d6c7ab0e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,7 +34,6 @@ These guidelines are to be followed by all developers with commit level access t - Deprecation of a function guarantees that it will exist in the given release, but may be removed, at any time following, from subsequent releases without further warning. Warning should be given in the release thread prior to it going live. - Updates should be discussed, via pull request of a version tick, prior to release. Only after consensus from active contributing community members has been given can a release happen. - Breaking API changes (excluding removal of already deprecated and warned code) should be forewarned with a one week notice on the forums, which may be given at any time prior to release (as soon as a pull request for a version push has been made, an update can be warned). -- Major changes to the TShock architecture should be discussed in github issue form with the community. These changes include removal of commands, restructuring, improvements, and new features. For example, adding silent command processing or a new REST api level. Consensus is required from at minimum, a majority of contributors present and reachable in the community (plugin authors or commit players) during the last seven days. #### Pull Request Acceptance Guidelines