3 ms·

It's probably less than half due to people using person email addresses instead of @google.com. The author didn't verify that people who had non-google addresse

It's probably less than half due to people using person email addresses instead of @google.com. The author didn't verify that people who had non-google addresses didn't actually work for Google. One thing I'd be curious to know is how many of the committers didn't ever work for Google. I suspect some of the non-Googlers on the committer list maybe former Googlers...

chocolatebunny 7y ago
In the context of this discussions why would it matter if someone never worked at Google vs someone who used to work at Google. They're not acting on behalf of Google when they make the contribution.
- mbreese 7y ago
  I don’t think it would necessarily matter. But it might be an indication of how “open” Google is to complete outsiders as opposed to people who were insiders but now just happen to not work for Google. Whether or not that matters is another question entirely. But like I said, I don’t think it matters in the context of how much control Google has over the language. Many successful languages are either driven by an individual benevolent dictator or a company. As far as I can tell, languages controlled by community/committees tend to evolve more slowly. That’s okay at some point in a project. But there is something to be said for a person/company having the ability to rapidly push through changes.
Carpetsmoker 7y ago
You need to sign a CLA to work on Go, like most Google projects. You can't accidentally use your personal email address, and setting up the CLA signing stuff is somewhat involved.
- dmoy 7y ago
  But you can (and are encouraged to?) sign up using your personal email while still employed at Google.
  - joshuamorton 7y ago
    The opposite is true. You are explicitly asked to make all contributions while at Google (to all projects) under your @google email.
    - dmoy 7y ago
      Ok that's curious, cus I've spent the last two years working on a project at Google that's half open source, and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. But this is also like a developed-in-open-source project, not a built-internally-and-copied-outside, so maybe the guidance differs there? Or is that a go team specific thing?
      - joshuamorton 7y ago
        > and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. This is correct. Use an existing github account, but your contributions should be under your @google email address. There's nothing that ties your github account to a git email. I've committed through github from like 4 different email addresses (@google, @gmail, @uni.edu, and a shared organizational one for a project from a shared machine).
        dmoy 7y ago
        Ah gotcha, yes we're agreed then. The underlying commits are supposed to be tied to your @google account (though a not insignificant number slip through)

chocolatebunny 7y ago

In the context of this discussions why would it matter if someone never worked at Google vs someone who used to work at Google. They're not acting on behalf of Google when they make the contribution.

mbreese 7y ago
I don’t think it would necessarily matter. But it might be an indication of how “open” Google is to complete outsiders as opposed to people who were insiders but now just happen to not work for Google. Whether or not that matters is another question entirely. But like I said, I don’t think it matters in the context of how much control Google has over the language. Many successful languages are either driven by an individual benevolent dictator or a company. As far as I can tell, languages controlled by community/committees tend to evolve more slowly. That’s okay at some point in a project. But there is something to be said for a person/company having the ability to rapidly push through changes.

Carpetsmoker 7y ago

You need to sign a CLA to work on Go, like most Google projects. You can't accidentally use your personal email address, and setting up the CLA signing stuff is somewhat involved.

dmoy 7y ago
But you can (and are encouraged to?) sign up using your personal email while still employed at Google.
- joshuamorton 7y ago
  The opposite is true. You are explicitly asked to make all contributions while at Google (to all projects) under your @google email.
  - dmoy 7y ago
    Ok that's curious, cus I've spent the last two years working on a project at Google that's half open source, and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. But this is also like a developed-in-open-source project, not a built-internally-and-copied-outside, so maybe the guidance differs there? Or is that a go team specific thing?
    - joshuamorton 7y ago
      > and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. This is correct. Use an existing github account, but your contributions should be under your @google email address. There's nothing that ties your github account to a git email. I've committed through github from like 4 different email addresses (@google, @gmail, @uni.edu, and a shared organizational one for a project from a shared machine).
      - dmoy 7y ago
        Ah gotcha, yes we're agreed then. The underlying commits are supposed to be tied to your @google account (though a not insignificant number slip through)