The actual requirement is that there is a code now, and another colleague needs to expand and develop based on some functions of this code. Later, colleagues will gradually participate in the development of other modules. I would like to ask whether it is better to use SVN or GIT for multi-person collaborative development, and how to ensure that the core code can be protected
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There is no doubt that git is used for this, svn is a legacy product of history. Git’s workflow and branch strategy are completely popular with svn. With svn, it is very laborious for multiple people to collaborate and pull branches independently. It is not as light and flexible as git. svn can only be used as a simple code synchronization tool. With git, You can refer to the git workflow. The release and iteration of the entire project can be controlled through the git workflow
There is no point in discussing this kind of issue. Just talking about good and bad: pros and cons of SVN and GIT
Answer the revised question:
As long as everyone involved in the development of core modules has access to the code, there is no other way to protect the core code other than formulating relevant contract terms.
I think the main answer to the question is:
It doesn’t matter whether the company uses git or svn, the key is!
The server must be deployed in an intranet environment
The project should be decoupled and developed according to modules. Each module has one project and is hosted in a code warehouse. The relevant project team members only provide the code of this warehouse.