New answers tagged

0

What should we be considering in order to make this decision? You should be considering the downsides. I (along with others) successfully encouraged my current employer to stop hosting the company's crown intellectual property jewels on a private github repo. Don't take me wrong; github is fantastic for open source software. In the case of closed ...


3

A part of this decision process could be a little testing, trial and error. Take a small project and have a few members try out some of the different sites. This should cover the usability by the team, but there are other considerations. Current Infrastructure - Some companies already have servers, internet connections, VPN, and people on staff with the ...


9

Obviously its a question of trust in the provider and how much you value your source code. However, I thinks its clear that, at least in the past, people over valued their source code. For 'business process automation' products; where an in house team creates websites and other software specifically for the needs of the business. The value of that ...


18

As a pro, If your company's office burns down, the code is still on the server. If your company's office doesn't burn down, but the server on which your git repository is located DOES, then you still have a local copy. If you host your repository on your server in your company's office building (like you would with a Network shared drive...?), then if the ...



Top 50 recent answers are included