4 ms·
This is also what Google suggests: > Please associate your commit with your google.com email unless: - You have a history of contributing to the repo under a d
by roblaszczak 5y ago
This is also what Google suggests:
> Please associate your commit with your google.com email unless:
- You have a history of contributing to the repo under a different email before your employment at Google
Source: https://opensource.google/docs/patching/ https://opensource.google/docs/patching/
> The release process applies to all types of projects: personal (at home), 20%, and new Google open source releases that aren’t part of and following the release process of an already-established Google open source project (like Chromium or Android).
Source: https://opensource.google/docs/releasing/#patching https://opensource.google/docs/releasing/#patching
It’s a bit less strict, but signing work that I’m doing after job with my job e-mail doesn’t sound fair.
- amw 5y agoAgree, this sounds like no less of an attempt to own the employee's time, it's just better at recognizing the value of open-source contribution to Alphabet's bottom line.