OrgGo/Mainflux.mainflux
1
0
Fork 0
mirror of https://github.com/mainflux/mainflux.git synced 2025-04-27 13:48:49 +08:00
Code Issues Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source
This commit is contained in:
Drasko DRASKOVIC 2017-06-05 21:55:07 +02:00 committed by GitHub
parent 43f1f11964
commit b71de906b3
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -46,14 +46,10 @@ project's developers might not want to merge into the project.
Please adhere to the coding conventions used throughout a project (indentation, Please adhere to the coding conventions used throughout a project (indentation,
accurate comments, etc.) and any other requirements (such as test coverage). accurate comments, etc.) and any other requirements (such as test coverage).
* Follow the [EffectiveGo](https://golang.org/doc/effective_go.html) styleguide
* Follow the [JavaScript](https://github.com/styleguide/javascript) styleguide * Follow the [JavaScript](https://github.com/styleguide/javascript) styleguide
* Follow the [NodeJS](https://github.com/felixge/node-style-guide) styleguide
* Document new code based on the [Documentation Styleguide](#documentation-styleguide) * Document new code based on the [Documentation Styleguide](#documentation-styleguide)
* End files with a newline * End files with a newline
* Place requires in the following order:
* Built in Node Modules (such as `path`)
* Built in Mainflux Modules (such as `coreflux`)
* Local Modules (using relative paths)
Adhering to the following process is the best way to get your work Adhering to the following process is the best way to get your work
included in the project: included in the project: