Thats was a very good starting point, but there are some concerns, the most important one is the full access to project over source control which will cause the entire source code to be exposed to third parties. How to solve this concern? im using plastic scm as soruce control and there is no option to limit that unfortunatly.
I've seen a couple ways to deal with this, and the most common is to just include some NDA language in the contract. I'm no lawyer so I can't tell you specifically what that is though. At the end of the day people have to have access to do their job so it's difficult to avoid. IIRC you can specify per-user branch permissions in Plastic though it has been some time since I used it. I commonly do that with git-based systems to protect things like "you can't delete the main repo". Another option like (that @jpnzo2k12 mentioned below) is to separate the portion of your code that our into a separate repo and have to new contractor/employee work there. As long as you can easily segment off the work they're doing, that can work well. It can be really messy to merge though if it's a deeper piece of work. I'd def recommend you do routine merges of this instead of waiting until the end to do it once.
Doing great, keep it up!
Super useful video, thanks man!
❤
Thats was a very good starting point, but there are some concerns, the most important one is the full access to project over source control which will cause the entire source code to be exposed to third parties. How to solve this concern? im using plastic scm as soruce control and there is no option to limit that unfortunatly.
MicroProjects. Then merge them
I've seen a couple ways to deal with this, and the most common is to just include some NDA language in the contract. I'm no lawyer so I can't tell you specifically what that is though. At the end of the day people have to have access to do their job so it's difficult to avoid. IIRC you can specify per-user branch permissions in Plastic though it has been some time since I used it. I commonly do that with git-based systems to protect things like "you can't delete the main repo".
Another option like (that @jpnzo2k12 mentioned below) is to separate the portion of your code that our into a separate repo and have to new contractor/employee work there. As long as you can easily segment off the work they're doing, that can work well. It can be really messy to merge though if it's a deeper piece of work. I'd def recommend you do routine merges of this instead of waiting until the end to do it once.