I usually track the developments of such best practices on Jeff Wexler's forum, which seems to be where people are going when they tire of the craziness on RAMPS. :-) The amount of info there can get very camera-specific, which is very handy for search purposes. It seems like most people there usually work backwards from the film speed and the telecine company's needs, make heavy use of smart slates, run at the appropriate 23.976 or 29.97 rates, and seem to prefer TOD (time of day) timecode, while admitting that free-run and rec-run have their uses. When last I checked. :-)
SIDENOTE: Me, though, I've recently been avoiding timecode altogether! :-) I only pitch in for production sound help on HDSLR shoots (or when I do such shoots myself as camera operator or director). We shoot double-system and use a manual slate for sync (following proper practice and tail-slating when appropriate). With Sound Devices recorders, we don't lose sync for at least 10 minutes, two minutes shorter than the max HDSLR clip length and way longer than any single take I've seen on-set under normal circumstances. Handy, that. We shoot audio at 24b96k for latitude. When manual sync in post isn't time-efficient (despite that it's pretty easy), we use the PluralEyes plugin to auto-sync to the on-camera scratch track. For sync sound for longer takes like interviews, we mix externally and then feed the camera bypassing its preamps. FCP is used for post, which isn't really that timecode savvy. No time code needed in that workflow! (I was both a grip and 2nd AC back in my video days, so I'm loving being TC free for a while.)