3 ms·
Alternative take: when I was there he was tyrannical and constantly blocking employees from open sourcing code developed on their own weekends and evenings, pur
by fidgewidge 4y ago
Alternative take: when I was there he was tyrannical and constantly blocking employees from open sourcing code developed on their own weekends and evenings, purely on a personal whim. People had to fight internal battles to get like little video games and stuff put up on github. You'd think head of OSPO would do whatever it took to get code open sourced but no far from it. Loads of grumbling about how he was just an ex-Slashdot editor who couldn't even code, on a power trip abusing contract ip clauses.
- enneff 4y agoThat couldn’t be further from my experience of working with Chris on open source at google for the last 13 years.