Create CONTRIBUTING.md

To enable developers contribute to the project

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing to this project
+
+When contributing to this repository, please first discuss the change you wish to make via issue with the owners of this repository before making a change.
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Types of Contributions
+
+### Pull Request Process
+
+If you wish to make suggestions to this project's code, please keep this few considerations in mind before pushing your _Pull Requests_:
+
+* Ensure any install or build dependencies are removed before the end of the layer when doing a build.
+* Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
+* This project code is a work in progress, so there is always room for improvement, but there is no need to impoverish the code base quality; have that in mind when submitting your suggestions and _Pull Requests_.
+* Until a better release cycle is implemented,the branch _master_ is the most recent, most stable code base.
+* Always push your _PR_ to _develop_ branch, any other will not be considered, and giving the case is easy to do, we guess there will be no difficulties with that.
+* Any code submitted should have it's own UnitTest added inside the same code structure the project has right now.
+* This projects uses Unittest, Coverage, Flake8 and PyLint for testing and static analysis, install them and use them for your development process.
+* Before submitting code to the project, run Unittest on the code base.
+* Before submitting code to the project, run Flake8 and PyLint (which we are still tuning so beware of false alarms there, if you detect them, feel free to fix it through your _PR_), look at the reports and fix those lines where there is need to.
+* Try your best to validate your signature on GitHub, that way your commits will be signed and validated by the platform.
+
+### Report Bugs
+
+Report bugs at the issues section of [this project](https://github.com/iyanuashiri/meethub/issues).
+
+If you find a bug, try your best to provide the necessary information to replicate the resulting error, the expected result and the actual one, if there is additional information you think will be useful, please add it, please include at least:
+
+* Your operating system name and version.
+* Any details about your local setup that might be helpful in troubleshooting.
+* Detailed steps to reproduce the bug.
+
+### Fix Bugs
+
+Look through the GitHub issues for bugs. Anything tagged with "bug" is open to whoever wants to implement it.
+
+### Implement Features
+
+Look through the GitHub issues for features. Anything tagged with "feature" is open to whoever wants to implement it.
+
+### Write Documentation
+
+MeetHub could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such.
+
+### Submit Feedback
+
+The best way to send feedback is to file an issue at the issues section of [this project](https://github.com/iyanuashiri/meethub/issues).
+
+If you are proposing a feature:
+
+* Explain in detail how it would work.
+* Keep the scope as narrow as possible, to make it easier to implement.
+* Remember that this is a volunteer-driven project, and that contributions are welcome :)
+
+### Issues and support
+
+We will try our best to provide help and orientation with this project implementation, but keep in mind than this is done in our spare time, and that has a lot of implications, please, be patient.