sigonasr2/jmonkeyengine
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source 
Typos and extra sections.
This commit is contained in:
Erlend Sogge Heggen 2014-03-23 23:00:22 +01:00
parent 5d00132fd9
commit 0682044cb5
1 changed files with 7 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
CONTRIBUTING.md
View File

@ -7,7 +7,7 @@ If you'd like to contribute with something other than code, read this (WIP).
## Getting Started ## Getting Started
Communication always comes first. All code changes should start with the [forum](http://hub.jmonkeyengine.org/forum/). Make a thread to explain your change and show us your code. If the code is too long to be posted within the forum’s <code> tags, please paste your code in http://jmonkeyengine.pastebin.com/ or a Gist and link to the submission in your thread. You are required to register on our website in order to create threads. Communication always comes first. All code changes should start with the [forum](http://hub.jmonkeyengine.org/forum/). Make a thread to explain your change and show us your code. If the code is too long to be posted within the forum’s code tags, please paste your code in a Gist or pastebin and link to the submission in your thread. You are required to register on our website in order to create threads.
When you're ready to submit your code, just make a [pull request](https://help.github.com/articles/using-pull-requests). When you're ready to submit your code, just make a [pull request](https://help.github.com/articles/using-pull-requests).
@ -19,22 +19,14 @@ Developers in the Contributors team can push directly to Main instead of submitt
- When committing, always be sure to run an update before you commit. If there is a conflict between the latest revision and your patch after the update, then it is your responsibility to track down the update that caused the conflict and determine the issue (and fix it). In the case where the breaking commit has no thread linked (and one cannot be found in the forum), then the contributor should contact an administrator and wait for feedback before committing. - When committing, always be sure to run an update before you commit. If there is a conflict between the latest revision and your patch after the update, then it is your responsibility to track down the update that caused the conflict and determine the issue (and fix it). In the case where the breaking commit has no thread linked (and one cannot be found in the forum), then the contributor should contact an administrator and wait for feedback before committing.
- If your code is committed and it introduces new functionality, please edit the wiki accordingly. We can easily roll back to previous revisions, so just do your best; point us to it and we’ll see if it sticks! - If your code is committed and it introduces new functionality, please edit the wiki accordingly. We can easily roll back to previous revisions, so just do your best; point us to it and we’ll see if it sticks!
## Git essentials ### Git essentials
rebase... rebase...
## Testing ### Code style
### Reporting bugs
### Testing
## Documentation ## Documentation
## Code style
* [General GitHub documentation](http://help.github.com/)
* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
* #puppet-dev IRC channel on freenode.org
How to get involved with jME development and contribute back to the project.
WIP