turbo

Merged from https://github.com/joelparkerhenderson/git_commit_message and https://chris.beams.io/posts/git-commit/

General Rules

• Commit messages must have a subject line and may have body copy. These must be separated by a blank line.
• The subject line must not exceed 50 characters
• The subject line should be capitalized and must not end in a period
• The subject line must be written in imperative mood (Fix, not Fixed / Fixes etc.)
• The body copy must be wrapped at 72 columns
• The body copy must only contain explanations as to what and why, never how. The latter belongs in documentation and implementation.

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

pgburt

Recording

• Set Audacity to use the External mic.
• Ensure you're recording in 16-bit PCM + 44100Hz.
• Do a sound check, record everyone in the room speaking. You want the lighter part of the meter bar (the green or red bar at the top) to bounce between -12db and -6db while people are talking. It's hard to achieve this... so just settle for as close as you can get, without the bars going off the scale :)
• Play it back and tweak levels until it sounds good @ 60% speaker volume.
• Save the Project BEFORE recording live :D (prevents quality issues)

Edit for Content

• Join recordings to one track.
• Listen to it + Edit bad content out.