[DOC] fga-eps-mds/2018.2-GamesBI#131 Community topics

Signed-off-by: Nukdown <belchior.emanoel@gmail.com>

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Code of Conduct
+
+## 1. Purpose
+
+A primary goal of 2018.2 Game Color Bi is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in 2018.2 Game Color Bi to help us create safe and positive experiences for everyone.
+
+## 2. Open Source Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open source citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+*   Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+*   Exercise consideration and respect in your speech and actions.
+*   Attempt collaboration before conflict.
+*   Refrain from demeaning, discriminatory, or harassing behavior and speech.
+*   Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+*   Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+*   Violence, threats of violence or violent language directed against another person.
+*   Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+*   Posting or displaying sexually explicit or violent material.
+*   Posting or threatening to post other people’s personally identifying information ("doxing").
+*   Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+*   Inappropriate photography or recording.
+*   Inappropriate physical contact. You should have someone’s consent before touching them.
+*   Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+*   Deliberate intimidation, stalking or following (online or in person).
+*   Advocating for, or encouraging, any of the above behavior.
+*   Sustained disruption of community events, including talks and presentations.
+
+## 5. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
+
+## 6. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. rocha.carla@gmail.com.
+
+
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+## 7. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify Fga Eps Mds with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
+
+
+
+## 8. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+## 9. Contact info
+
+rocha.carla@gmail.com
+
+## 10. License and attribution
+
+This Code of Conduct is distributed under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
+
+Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
+
+Retrieved on November 22, 2016 from [http://citizencodeofconduct.org/](http://citizencodeofconduct.org/)

.github/CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# Contribuindo com o projeto
+
+Coisas nas quais você pode ajudar:
+ - [Documentação](#documentacao)
+ - [Criação de novas features](#novas-features)
+ - [Issues](#issues)
+     - [Bugs](#bugs)
+     - [Sugestões de melhoria](#sugestoes-de-melhoria)
+
+## Fluxo de trabalho
+
+Todos os contribuidores do projeto devem seguir os seguintes passos:
+
+ 1. Crie um fork do projeto na sua conta pessoal
+ 2. Trabalhe nas suas mudanças em uma branch no seu fork
+ 3. Crie um pull request para o repositório oficial
+ 4. A integração contínua irá verificar as suas alterações
+ 5. Um mantenedor do projeto irá avaliar e realizar o merge da sua contribuição
+
+## Desenvolvendo
+
+  1. Clone o repositório
+  ```bash
+  git clone https://github.com/fga-eps-mds/2018.2-GameColorBI.git
+  ```
+  2. Abra o projeto 
+  3. Faça as suas contribuições
+
+## Documentação
+
+Mais documentação é sempre apreciada e é algo que você pode contribuir de forma simples:
+
+  1. Clone o repositório
+  ```bash
+  git clonehttps://github.com/fga-eps-mds/2018.2-GameColorBI.git
+  ```  
+  2. Acesse a pasta docs
+  ```bash
+  cd 2018.2-GameColorBI/docs
+  ```
+  3. Edite ou crie novas documentações e salve-as na pasta correspondente
+
+## Criação de novas features
+
+Para a criação de novas features, siga os seguintes passos:
+
+  1. Crie uma issue com um dos templates disponíveis
+  2. Insira _labels_ que estejam relacionados com a issue criada
+  3. Aguarde o feedback de algum mantenedor que irá validar a feature sugerida
+  4. Caso o feedback for positivo, dê assign da issue para você mesmo
+  5. Inicie o desenvolvimento
+  6. No pull request, faça o link do PR com a issue criada previamente (o link só é possível utilizando a extensão ZenHub)
+  7. Aguarde aprovação
+
+## Issues
+
+Você pode ajudar-nos criando novas issues ou corrigindo issues existentes
+
+#### Bugs
+Caso encontre algum bug no projeto, sinta-se à vontade para criar uma issue nos reportando:
+
+  1. Crie a issue seguindo um dos templates disponíveis no campo de criação da issue
+  2. Insira _labels_ que estejam relacionados com a issue criada
+  3. Aguarde feedback de um mantenedor
+
+#### Sugestões de melhoria
+Caso tenha alguma sugestão de melhoria ou feature siga os seguintes passos:
+
+  1. Crie a issue seguindo um dos templates disponíveis no campo de criação da issue
+  2. Insira _labels_ que estejam relacionados com a issue criada
+  3. Aguarde feedback de um mantenedor
+  4. Caso queira contribuir com a implementação, verifique os passos para a [criação de novas features](#criacao-de-novas-features)
+
+## Atribuição
+
+Este documento é uma adaptação do artefato do projeto [opsdroid](https://github.com/opsdroid/opsdroid), acessado em 27 de março de 2018.

.github/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,25 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here.
+
+---
+
+---
+name: Issue Template
+about: Issue template for to standardize repo issues
+
+---
+
+## Issue Title
+
+## Description
+<!--- Describe the reason of the issue, what is the problem you want to solve, the bug you want to fix, etc -->
+
+## Tasks
+- [ ] task 1
+- [ ] task 2
+
+## Acceptance criteria
+<!--- describe what needs to be done so this issue can be closed -->
+
+## How this will benefit the project?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!--- Provide a general resume of yours modifications -->
+
+## Description
+<!--- Describe your modifications in detail -->
+
+## Related _Issue_
+<!--- This project only accept _pull requests_ from open _issues_. -->
+<!--- If you are proposing a new feature or modification, first, discuss it with a issue -->
+<!--- Please, link the issue below: -->
+
+## Motivation and Context
+<!--- Why is this modification necessary? Which problem it solves?  -->
+
+## How it was tested?
+<!--- Please, write all details of how your modifications where tested -->
+
+## Screenshots:
+
+## Type of modifications
+<!--- Which type of modifications -->
+- [ ] _Bug fix_
+- [ ] New _feature_
+- [ ] _Breaking change_ (Modification that changes the status of current implemented features)
+
+## Checklist:
+- [ ] My code follows the implemented style sheet
+- [ ] My _commits_ follows the repo commits policy.
+- [ ] My modifications requires modification on the current documentation.
+- [ ] I updated the documentation
+- [ ] I read the repo contributing guide (**CONTRIBUTING**).
+- [ ] I added testes to cover my modifications
+- [ ] All tests passed