4 ms·

Does this mean that one Googler could checkout the complete system, and sell it or put it online? How many people have access to the complete repository? How bi

Does this mean that one Googler could checkout the complete system, and sell it or put it online? How many people have access to the complete repository? How big is one checkout?

nappy-doo 10y ago
There are Googlers who could checkout the complete system, and I guess sell it online. There are pieces that aren't available to all Googlers, but the _large_ majority of the code is there, and browsable by everyone. Generally, you don't checkout all code you're using, just what you modify. You work in repos that exist virtually, because checkouts would be huge.
OneMoreGoogler 10y ago
Checkouts are apparently instantaneous. Behind the scenes, there is a FUSE filesystem that faults in files by querying Google's cloud servers. So it does not require a significant amount of space (but does require fast access to Google's servers, which can be problematic). Almost all engineers have access to the "complete system," which is really Google's server-side software. Other repos like Android have historically been more locked-down, but there's been some recent effort to open them up within Google. Presumably if you tried to copy all of the files, you'd first be rate-limited, then get an access denied, and lastly a visit from corporate security. I wouldn't want to try.
- nevir 10y ago
  > Presumably if you tried to copy all of the files, you'd first be rate-limited, then get an access denied, and lastly a visit from corporate security. I wouldn't want to try. And there's no way it'd fit on a single hard drive.
- caustic 10y ago
  Is it a good idea to try to run the du command in the root directory?
  - arviewer 10y ago
    Probably even better to try sudo -i! ;-)
KallDrexx 10y ago
I worked at a company where our engineering team was working with an engineering team at Google to help Google move one of their systems from one vendor to us. We wanted to send them a script to help with the conversion process and they flipped out and told them not to send them any code until we become authorized in some special capacity. They then decided to tell us how a week or so before a coworker sent himself some code so he could work on something from home (according to him at least), and within 20 minutes of emailing himself that code security was already escorting him out the door. That's 20 minutes for automated filters to catch it, security to review it, HR to process the termination paperwork, and security to go to his desk to escort him out.
packetslave 10y ago
Google has lots of information security engineers and lots of lawyers. Do not taught happy fun argv.

Does this mean that one Googler could checkout the complete system, and sell it or put it online? How many people have access to the complete repository? How big is one checkout?

nappy-doo 10y ago

There are Googlers who could checkout the complete system, and I guess sell it online. There are pieces that aren't available to all Googlers, but the _large_ majority of the code is there, and browsable by everyone. Generally, you don't checkout all code you're using, just what you modify. You work in repos that exist virtually, because checkouts would be huge.

OneMoreGoogler 10y ago

Checkouts are apparently instantaneous. Behind the scenes, there is a FUSE filesystem that faults in files by querying Google's cloud servers. So it does not require a significant amount of space (but does require fast access to Google's servers, which can be problematic). Almost all engineers have access to the "complete system," which is really Google's server-side software. Other repos like Android have historically been more locked-down, but there's been some recent effort to open them up within Google. Presumably if you tried to copy all of the files, you'd first be rate-limited, then get an access denied, and lastly a visit from corporate security. I wouldn't want to try.

nevir 10y ago
> Presumably if you tried to copy all of the files, you'd first be rate-limited, then get an access denied, and lastly a visit from corporate security. I wouldn't want to try. And there's no way it'd fit on a single hard drive.
caustic 10y ago
Is it a good idea to try to run the du command in the root directory?
- arviewer 10y ago
  Probably even better to try sudo -i! ;-)

KallDrexx 10y ago

I worked at a company where our engineering team was working with an engineering team at Google to help Google move one of their systems from one vendor to us. We wanted to send them a script to help with the conversion process and they flipped out and told them not to send them any code until we become authorized in some special capacity. They then decided to tell us how a week or so before a coworker sent himself some code so he could work on something from home (according to him at least), and within 20 minutes of emailing himself that code security was already escorting him out the door. That's 20 minutes for automated filters to catch it, security to review it, HR to process the termination paperwork, and security to go to his desk to escort him out.

packetslave 10y ago

Google has lots of information security engineers and lots of lawyers. Do not taught happy fun argv.