The point is that Google will claim copyright of everything that you do. If you write a game about chickens in your spare time, for example, then Google owns the copyright, despite not having had any input into it. I fail to see how that's fair or reasonable, and I'd be very interested to see what laws apply - I suspect that cdibona is trying to blow smoke up our collective asses.
What is unreasonable is that if you did it at home, with no Google resources, that they would still ask you to assign them ownership.
(I, fortunately, don't have this problem. Part of the official open-sourcing process involves deleting any reference to our company, even in the copyright, so that nobody sues them if it breaks. Example internal app that was open-sourced: http://openefs.org/)
I've got a 20% project that, to my knowledge, my manager doesn't even know about. It grew out of my 80% project - we needed a library that doesn't seem to exist yet. When it gets to a semi-functional state, I'll open-source it through cdibona's office, with copyright assigned to Google. Why not? It'll end up exactly the same for end-users, with an Apache license, and it's much less of a bureaucratic hassle to just do it with a Google copyright.