I got into a good-natured spat with a fellow worker about the nature of the sticky bit.
My contention, working from the chmod man page was the the sticky bit, if set, allows only the owner to delete or rename files:
RESTRICTED DELETION FLAG OR STICKY BIT The restricted deletion flag or sticky bit is a single bit, whose interpretation depends on the file type. For directories, it prevents unprivileged users from removing or renaming a file in the directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp. For regular files on some older systems, the bit saves the program's text image on the swap device so it will load more quickly when run; this is called the sticky bit.
My colleague is adamant that the authoritative answer is an article on a Yale forum from 1996 that instructs how the sticky bit is used to set the group inherited rights for the directory. (http://www.library.yale.edu/wsg/docs/permissions/sgid.htm)
Accordingly, I have installed setafcl and set acl as an option on mount (as detailed here: http://superuser.com/questions/264383/set-file-permissions-so-that-new-files-inherit-same-permissions .
Would anyone like to help settle this dispute... I believe I could drag a milkshake out of the guy if I am right.