fga-gpp-mds/2017.2-QueroCultura

View on GitHub
CONTRIBUTING.md

Summary

Maintainability
Test Coverage
## How to contribute to QueroCultura

#### **Did you find a bug?**

* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/fga-gpp-mds/2017.2-QueroCultura/issues).

* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/fga-gpp-mds/2017.2-QueroCultura/issues/new) and add the bug label. Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.

### Do you intend to add a new feature or change an existing one?

* **Ensure there is no issue with the same purpose** by searching on GitHub under [Issues](https://github.com/fga-gpp-mds/2017.2-QueroCultura/issues).
* Open a new issue **describing what you want to do** and add the labels that makes sense with your proposal.
* After a maintainer validation, you probably will have the endorsement to work on your idea.

### Do you have questions about the source code?

* You can open an issue with the label **question** and describe your questions.

### Issues

* All Issues must have a **descriptive title** and a **comment with a full description of your idea**
* All Issues must have **acceptance criterias**
* All Issues has to be labeleds with at least **one label**, if you think there is no label that describe well what you propose, **feel free** to create a new label.

### Pull Requests

* All Pull Requests must be **assigned to an issue**.
* The Pull Request title has to be as **descriptive as possible** and must have **one comment** with de word "Resolved" followed by **number of the issue**.
* A comment **describing what you have done** also must be made.