If you give the teams a reason to use the "CD Standard" then they will use it.
For instance, we create a code depository with every single line of code following the "CD Standard." We also get IFI, or someone who can work closely with IFI to set the default code up in the "CD Standard." Furthermore, make sure that teams can "drag and drop" code from the depository into the default code with little to no effort at all, so that teams can quickly get a working program.
When you set things up, and, well, force the teams to use the "CD Standard," most teams will follow suite and use it. Also, perhaps make a rule that any true C code (not pseudo-code, for obvious reasons) must be in the "CD Standard" for us to quickly give help and answers. Another forum I frequent (Gentoo Linux Forums,
http://forums.gentoo.org), the forum members usually ask for posters to remove comments from their configuration files so they don't waste everyones' time by making them re-read all the comments in XF86Config again. It's a simple request, and yes, it's not the nicest thing to do, but it enforces the standard, which in the end,
should make it easier for everyone.
The thing about a standard is, everyone has to use it, or else it's not really a standard, and you've just basically wasted your time, and we all know that from January to late February, we don't have any time to waste

.