4 ms·

As a side note, their github hosts 1600 repos. Just wanted to say thank you, google.

by imglorp 7y ago

arthurcolle 7y ago
Wow, that is really a huge number of repos. I wonder how many are just forks though.
- guessmyname 7y ago
  I will teach you how to check that: https://i.imgur.com/HjhAmQW.gif https://i.imgur.com/HjhAmQW.gif Here are the statistics just in case anyone else is interested: 1,519 Sources 38 Forks 18 Archived 6 Mirrors -------------- 1,581 Total Source: https://github.com/google https://github.com/google
- timsneath 7y ago
  Also worth noting that a significant quantity of Google open source projects and contributions are in other GitHub orgs. For example http://github.com/flutter http://github.com/flutter, https://github.com/tensorflow https://github.com/tensorflow, https://github.com/angular https://github.com/angular, https://github.com/golang https://github.com/golang and https://github.com/dart-lang https://github.com/dart-lang. (Disclosure: I'm a Googler.)
ipsum2 7y ago
I would wager that a vast majority of them are personal projects. If you work at Google and want to do some open source project on the side, the code is owned by Google and is under Github.com/google. See: https://news.ycombinator.com/item?id=15592968 https://news.ycombinator.com/item?id=15592968
- 9nGQluzmnq3M 7y ago
  Not necessarily: here's Chris DiBona explaining how it works. https://news.ycombinator.com/item?id=15594045 https://news.ycombinator.com/item?id=15594045
- zamadatix 7y ago
  Here I am just wishing my company would even allow me to post the source of a project I've worked on with any license and apparently Google isn't worth praise for hosting all such projects with an Apache license by default and a review process if you'd like to try to keep copyright. https://opensource.google.com/docs/iarc/ https://opensource.google.com/docs/iarc/
  - dmitrygr 7y ago
    If you live in CA, you're good to do it: https://codes.findlaw.com/ca/labor-code/lab-sect-96.html https://codes.findlaw.com/ca/labor-code/lab-sect-96.html as long as you do it on your time, using your own resources, and do not compete with your workplace. The fact that google (or other employers) do not go out of their way to tell you this is, of course, understandable.
    - jefftk 7y ago
      > do not compete with your workplace Google does enough different things that this is often unclear. The IARC program lets you get a clear opinion from the company on whether they consider your work to be fully separate.
    - saagarjha 7y ago
      For any large company this effectively means that almost all of your side projects can be construed as falling afoul of this law.
    - kccqzy 7y ago
      No, the point is Google goes beyond the typical organization in that it provides 20% time which can, if you desire, be used to work on personal projects even with Google equipment. That's better than using after-work hours and your own resources.
      - dmitrygr 7y ago
        20% time hasn't existed in 8 years at least (source: spent 7.5 of them working at Google, various teams)
- WalterGR 7y ago
  If you work at Google and want to do some open source project on the side, the code is owned by Google and is under Github.com/google. Not necessarily. See this comment - https://news.ycombinator.com/item?id=15592993 https://news.ycombinator.com/item?id=15592993 - which is a child comment of the one you linked to.
- tylerl 7y ago
  Mine isn't. https://github.com/tylerl/filterpipes https://github.com/tylerl/filterpipes Since I wrote it on my own time, I had my pick of going the IARC route vs going the Google open-source route, and I picked open-source with a Google copyright because it was simpler (though I fully intend to go with IARC on another project just to try it out). It's on my own github instead of Google's because (again) it was simpler. Since it contains zero Google-specific anything and wasn't made on company time, they didn't care which I picked at the time. In retrospect it probably would have been cooler to publish it under their name instead of mine, but aw well.

As a side note, their github hosts 1600 repos. Just wanted to say thank you, google.

arthurcolle 7y ago

Wow, that is really a huge number of repos. I wonder how many are just forks though.

guessmyname 7y ago
I will teach you how to check that: https://i.imgur.com/HjhAmQW.gif https://i.imgur.com/HjhAmQW.gif Here are the statistics just in case anyone else is interested: 1,519 Sources 38 Forks 18 Archived 6 Mirrors -------------- 1,581 Total Source: https://github.com/google https://github.com/google
timsneath 7y ago
Also worth noting that a significant quantity of Google open source projects and contributions are in other GitHub orgs. For example http://github.com/flutter http://github.com/flutter, https://github.com/tensorflow https://github.com/tensorflow, https://github.com/angular https://github.com/angular, https://github.com/golang https://github.com/golang and https://github.com/dart-lang https://github.com/dart-lang. (Disclosure: I'm a Googler.)

ipsum2 7y ago

I would wager that a vast majority of them are personal projects. If you work at Google and want to do some open source project on the side, the code is owned by Google and is under Github.com/google. See: https://news.ycombinator.com/item?id=15592968 https://news.ycombinator.com/item?id=15592968

9nGQluzmnq3M 7y ago
Not necessarily: here's Chris DiBona explaining how it works. https://news.ycombinator.com/item?id=15594045 https://news.ycombinator.com/item?id=15594045
zamadatix 7y ago
Here I am just wishing my company would even allow me to post the source of a project I've worked on with any license and apparently Google isn't worth praise for hosting all such projects with an Apache license by default and a review process if you'd like to try to keep copyright. https://opensource.google.com/docs/iarc/ https://opensource.google.com/docs/iarc/
- dmitrygr 7y ago
  If you live in CA, you're good to do it: https://codes.findlaw.com/ca/labor-code/lab-sect-96.html https://codes.findlaw.com/ca/labor-code/lab-sect-96.html as long as you do it on your time, using your own resources, and do not compete with your workplace. The fact that google (or other employers) do not go out of their way to tell you this is, of course, understandable.
  - jefftk 7y ago
    > do not compete with your workplace Google does enough different things that this is often unclear. The IARC program lets you get a clear opinion from the company on whether they consider your work to be fully separate.
  - saagarjha 7y ago
    For any large company this effectively means that almost all of your side projects can be construed as falling afoul of this law.
  - kccqzy 7y ago
    No, the point is Google goes beyond the typical organization in that it provides 20% time which can, if you desire, be used to work on personal projects even with Google equipment. That's better than using after-work hours and your own resources.
    - dmitrygr 7y ago
      20% time hasn't existed in 8 years at least (source: spent 7.5 of them working at Google, various teams)
WalterGR 7y ago
If you work at Google and want to do some open source project on the side, the code is owned by Google and is under Github.com/google. Not necessarily. See this comment - https://news.ycombinator.com/item?id=15592993 https://news.ycombinator.com/item?id=15592993 - which is a child comment of the one you linked to.
tylerl 7y ago
Mine isn't. https://github.com/tylerl/filterpipes https://github.com/tylerl/filterpipes Since I wrote it on my own time, I had my pick of going the IARC route vs going the Google open-source route, and I picked open-source with a Google copyright because it was simpler (though I fully intend to go with IARC on another project just to try it out). It's on my own github instead of Google's because (again) it was simpler. Since it contains zero Google-specific anything and wasn't made on company time, they didn't care which I picked at the time. In retrospect it probably would have been cooler to publish it under their name instead of mine, but aw well.