Simplify a great deal the CONTRIBUTING file #40
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Travis CI automatically checks for this now
Instead, link to the maintainers corner that contain this information
This information is now available in the maintainers corner
astorije
added
Type: Documentation
|
👍 |
|
I will actually wait for a second 👍 from before merging this. |
|
👍 |
AlMcKinlay
added a commit
that referenced
this pull request
Feb 15, 2016
Simplify a great deal the CONTRIBUTING file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was brought to my attention that, if CONTRIBUTING files are often ignored, way too long CONTRIBUTING files are pretty much always ignored.
Prior to that PR, there were lots of unnecessary, lengthy details that neither casual or involved contributors do not care about.
Casual contributors fix comments, super minor bugs or documentation pieces, all of which we should simply be thankful of.
Involved contributors should rightfully enquire more before starting coding, which this PR details sufficiently (mainly open a PR or discuss on IRC first). Very involved contributors will read our maintainers' corner.