Google has various programs under which employees can release code without having to care too much about the broad copyright assumptions in their contracts.
IARC should be quite suitable for projects on "contentious" topics like politics or religion: Google generally stays clear of these topics (so there won't be a conflict of interest in building something like that, as Google just isn't active in that market), and the company won't have to deal with being associated with one team (versus all the others) through some side hustle they can barely control.
(Disclosure: working at Google, but far from the licensing folks. I found them reasonable to argue with, though.)
I would find it surprising that Google would be OK with that, particularly because it could be construed as them contributing to some campaign. An employee writing a check to the campaign? That’s perfectly fine, Google has no say over that. An employee producing IP for a campaign? Well, Google does technically have a say over that and would have to waive their right of ownership of said IP...
The two most popular are https://opensource.google.com/docs/releasing/ (which is for open source code, with (C) Google, because with open source you mostly don't have to care much about that line) and https://opensource.google.com/docs/iarc/ (author retains copyright, no open source requirement or association with Google at all).
IARC should be quite suitable for projects on "contentious" topics like politics or religion: Google generally stays clear of these topics (so there won't be a conflict of interest in building something like that, as Google just isn't active in that market), and the company won't have to deal with being associated with one team (versus all the others) through some side hustle they can barely control.
(Disclosure: working at Google, but far from the licensing folks. I found them reasonable to argue with, though.)