INOVISAO

The INOVISAO is a group of researchers and students created in 2004 in the Dom Bosco Catholic University (Universidade Católica Dom Bosco - UCDB) whose main objective is the integration of research, development and innovation to contribute to the development of the state of Mato Grosso do Sul The group has several computer vision projects facing applications in agribusiness and other areas relevant to the region. Through partnerships with industry, other research institutions and agencies, the INOVISAO has been successful in obtaining investments for research in the state, which has already resulted in several publications and some softwares. The group has assisted in organizing various events in the area like CIARP, IWCIA, PSIVT, and COMPIMAGE VIPIMAGE, having helped to bring to Campo Grande the SIBGRAPI Congress in 2008.

Politics

New project

Only the git administrator should create a new project. The rules are described below:

Every project must own the gitignore script.
The developer who requested the creation of the new project is responsible for creating the gitignore script.
At a minimum, the gitignore script must block the sending of images and videos to the repository.
The creation of the file readme of the project is the responsibility of the administrator.
The developer who requested the creation of the new project is responsible for editing the readme file of the project.

Commits

The rules to commits are described below:

Commits must be written in English or Portuguese.
They must be simple and concise, with short titles.
They must be started with capital letters.
They must be started with a verb in the infinitive and briefing its purpose. Example: "Create new classifier based on syntactic methods".
Do not commit image dataset.

Branches

Branch master - It must own production-level code.

Branch develop - It is the branch that own level-preparatory code to next deploy.

The rules for branches are described below:

For each new feature, a new branch must be created based on branch develop.
When new features are completed, they must be merged with the develop branch.
It must define administrators of each project to merge the develop branch with the master branch. The administrator must approve the merge request (integrate separate changes that have been made in the project, in different branches).
To registering the software, it must create a master branch tag in order to "freeze" a release version, since it is necessary to create a key for the release version.
For each merge between the develop branch and master branch, it must create a new tag to specify a new project version.
Any conflict must be resolved between the developer responsible for the conflict and the project administrator.