Ground Rule

Ground Rule

Scrum

• Share our schedules as detail as possible
• Off-line: 14:00 @Code-squad
• On-line: @Zoom (any personal issues -> notice before an hour)

Documentation - Meeting

• Upload to Team Repository as an issue

Branch Rule

• default branch : dev
• {feat}/{feature}

Commit Rule

Reference: http://karma-runner.github.io/1.0/dev/git-commit-msg.html

• Message subject(first line)

Type	Contents
feat	new feature for the user, not a new feature for build script
fix	bug fix for the user, not a fix to a build script
docs	changes to the documentation
refactor	refactoring production code, eg. renaming a variable
style	formatting, missing semi colons, etc; no production code change
test	adding missing tests, refactoring tests; no production code change)
chore	updating grunt tasks etc; no production code change

• Message Body

  • uses the imperative, present tense: “change” not “changed” nor “changes”
  • includes motivation for the change and contrasts with previous behavior

• Message footer

  • Reference issues

• Example

  refactor: Refactor subsystem X for readability 
  
  {body...}
  
  Issue #1 // not closed
  Resolves #1 // closed
  

Blog Posting

• Upload posts by topics (more than twice in a week)

• Contents

  • Project plan
  • Trouble shooting
  • Collaboration

• Poogle Blog

• Lena Blog