Does the GNU GPL v2 that Git comes under allow you to create and use your own version control system in your organization?

Question

git

What restrictions might the GNU GPL v2 lead to?
Also, the same question, but with the condition that this system will then be distributed to subsidiaries on a free basis, will there be any problems with the license? And if it will be sold to third companies as a service (SaaS) or a product?
How is Apache SVN doing in this regard?
I would like to hear the answer from the legal and technical side (licenses and feasibility). Thank you.

Answer 1

The main provisions of the GPL V2:
- provide the user with a binary - provide the source code or a written obligation to provide it upon request;
- you take the source code released under the GPL and use it in your products - the license of the final product must be GPL;
- you can not transfer the product to a user who cannot, for any legal (court order, local laws) reasons, distribute it further under the same license.
Apache 2.0 license:
- the product can be distributed without source codes;
- a mandatory indication of the use of open source is required with a listing of the products used (libraries, engines ...).
- in used products it is forbidden to change the name and exclude information about copyrights and / or patents.