Use this commit style?

[nilsnh]

Don't know how rigourus we should be on the commits but it might be smart to get some good habits early on in the project.

Found an informative article which talks about the git commit philosophy over at Cloud 9. The article suggests a general approach with some rules.

Assigning features/user stories to teammates which they develop in branches and submit for code reviews before merging into master seems like a nice way to go. Especially if the project grows and it becomes easier to break it.

Thoughts on what kind of commit philosophy we should have?

[EivindEE]

I agree that we should follow some such method for structuring commits.
As a start I suggest that we follow "rule #1", we create branches, and do not commit directly to the master branch.
I also suggest that we, since we don't have a senior developer, say that the one who accepts pull requests should be different from the one who made it. In other words, don't accept your own pull request.

We should also agree on coding standards, in how rigorous we want to be with testing.
I've allready added a .editorconfig file to the project, which should help us unify on some editor settings as long as we use tools that understand them( vim and sublime both have plugins).