Once upon a time I tried to extract "best practices" for TODOs based on what I could find in large #golang codebases. Turns out this mostly matches Google's (only lightly externally documented) practices. 
I've heard there's a growing consensus that TODO(bug #) is more useful than TODO(username) given that maintainers and owners move over time.
A static code analyzer for annotated TODO comments:
- ensure all TODOs have bug numbers
- ensure all referenced bugs are still open
github.com/preslavmihaylo…
- ensure all TODOs have bug numbers
- ensure all referenced bugs are still open
github.com/preslavmihaylo…
Added my rules to github.com/dgryski/awesom…
