Add contributing md

.github/Contributing.md

@@ -0,0 +1,120 @@
+<p align="center">
+  <img src="https://cdn.ocsinventory-ng.org/common/banners/banner660px.png" height=300 width=660 alt="Banner">
+</p>
+
+<h1 align="center">OCS Inventory</h1>
+<p align="center">
+  <b>Some Links:</b><br>
+  <a href="http://ask.ocsinventory-ng.org">Ask question</a> |
+  <a href="#COMMING_SOON_STAY_CONNECTED">Installation</a> |
+  <a href="https://www.ocsinventory-ng.org/?utm_source=github-ocs">Website</a>
+</p>
+
+# OCS Inventory Contributing Guidelines
+
+## Pull Request Process
+
+1. Fork it!
+2. Create your feature branch: `git checkout -b my-new-feature`
+3. Add your changes: `git add folder/file1.php`
+4. Commit your changes: `git commit -m 'Add some feature'`
+5. Push to the branch: `git push origin my-new-feature`
+6. Submit a pull request !
+
+## Pull Request Informations
+
+When contributing, please open an issue before or contact the team using mail. This will prevent all the duplicate of work.
+Also, check if your contribution is not already in the roadmap or affiliated to an issue.
+
+If you are contributing on a small scale (translation, a few line modification), you don't need open an issue or contact the team but you will need to explain what you've done in the Pull Request comment and provide as accurate commit messages as possible.
+Cf. Commits Messages Name Informations
+
+If you need to discuss about a big change or need some help of our team during the development of your contribution,
+we can use other communication method like Telegram, IRC, Skype.
+
+## Commits Messages Name Informations
+
+Try to create as accurate as possible commit messages.
+This will help us to speed up the review process and to reduce the misunderstanding (which can lead to a Pull Request to be rejected)
+
+There is no commit messages convention but here are some examples :
+1. Create as short as possible commit name
+2. One commit for one modification
+3. Always leave the second commit line blank
+
+If it seems difficult to summarize what your commit does, it may be because it includes several logical changes or bug fixes, and are better split up into several commits using `git add -p`.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at `[email protected]` . All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/