Hotel-Management-Solutions

      A website, provides hotel management solutions, for smart users and hospitality service providers.

            Preview Available - Link
            Site is Under Construction 🏨

Contribution Guidelines

We ❤️ your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Discussing the current state of the code
• Submitting a fix
• Proposing new features

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We Use Github Flow, So All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

1. Create issue for bug, fix or features and get yourself assigned (to preserve your and others hard-work and time)!
2. After the previous important step, fork the repo and create your branch from master.
3. If you've added code that should be tested, add tests.
4. If you've changed APIs, update the documentation.
5. Ensure the test suite passes.
6. Make sure your code lints.
7. Create pull request and link it to the corresponding issue

Any contributions you make will be under the GNU General Public License v3.0

In short, when you submit code changes, your submissions are understood to be under the same GPL License that covers the project. Feel free to contact the us if that's a concern.

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Write bug reports with detail, background, and sample code

Great Bug Reports tend to have:

• A quick summary and/or background
• Steps to reproduce
  • Be specific!
  • Give sample code if you can.
• What you expected would happen
• What actually happens
• Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports. I'm not even kidding. You can use our bug report template, that would be highly anticipated.

Coding Guidelines

Consistent coding styles have undoubted advantages, but for now we follow a very basic given below. We would request you sticking to these for ease of understanding and a litle bit of consistency.

• 4 spaces or tabs for indentation
• Use descriptive variable names.
• Use camelCasing.
• Comments to thoroughly describe your particular code block's logic.

There are also some basic Guidelines, these are some good practices - you can read and folow.

License

By contributing, you agree that your contributions will be licensed under its GPL License.

References

This document was adapted from this Template