Determine Conventions

[oliver-pham]

There are conventions to enhance communication, collaboration, and productivity. Before we start developing our project, I think we should decide on a few conventions below:

• Commit message
• Branch name
• Pull request template #12
• Customize Issue Templates #8

I think these naming conventions are a great start. Maybe we can use them.

Feel free to create a new issue and suggest a convention for each item. This issue is used for tracking all the conventions to be implemented.

Resources:

• https://namingconvention.org/

[hlavu]

I suggest writing all commit messages in the same structure like V + N such as Create sign-in form.
For branch name we can make use of the issue id like issue#id.
About PR desc we should provide what have been done, which packages have been used and a screenshot (if necessary).

[tuanthanh2067]

@hlavu Yeah, okay so I'm gonna create a PR about this convention in CONTRIBUTING.md. It will be under docs folder.

[minhhang107]

For branch name, we should separate new feature and bugfix. We can also use descriptive branch name like: type/issue#-issue-name

eg:
docs/9-determine-conventions (not sure if we need this type or should just put it into feature?)
feature/13-add-landing-page
bugfix/100-fix-button-on-landing-page