|
|
|
|
|
by jetti
2151 days ago
|
|
Where I am at now we can see all the repos for all projects in the company regardless of team. The only pre-req is to be added to the company's github organization. We have a lot of cross team work, though, and I have worked on a few services that aren't related to my team and it would be a pain to have to request access. At my last job, however, everything was locked down and you had to request access to just about every repo. It was a pain in the ass and there was no real valid reason to do so. |
|
In general it is simply good practice to only make this sort of information available to employees who need it to carry out their jobs. It is not a problem because there is usually no reason to study the code of another product/module/team/whatever, and if there is a reason then access can be granted, and is granted.
If your side needs to interact with another team's code and you cannot see their source code it at least forces everyone to have properly documented APIs.