Work methodology

Slack

To have better comunications between different works groups we need next channels on Slack to speak to a especific groups or a specific topic:

• Managers
• Frontend
• Backend
• Meetings
• Marketing
• Off-Topics

GitFlow

To better work flow we will use a reduced GitFlow with the next branches:

• master: only for stables version.
• develop: only for version in development, when the version is finished, this branch will be merged with Master.
• feature-[FeatureName]: you have to create a branch from develop with this format to develop a feature, when it is finished, this branch will be merged with develop.
• hotfix-[HotFixName]: when you have to do a hotfix, you have to create a branch from master and when you finish the hotfix, you will merge this branch with master.

Commits

You have to do a commit for each work block or when going stop work, the title of the commit always have to start with one of the followings heads (including ":"):

• Feat: when you have worked on a feature.
• Doc: when you have worked on documentation.
• Fix: when you have worked on a fast fix that isn't a feature.
• HotFix: when you have worked on a Hot-Fix.

After the head you have to explain what you have done on one line and use the body to explain troubles or special topics and reference the issue of you work. (Ex. of reference: " refences #[number of issue] " )

If the commit closes the issue then you have to use " close #[number of issue] " or " resolve #[number of issue] "