Any suggestions on best practices for providing access to subversion to a 3rd party development team. We’ve hired the team to work on a small iteration of the project and I don’t want to give them access to the whole respository. We use BeanStalk to host our subversion so granular access control down to just a branch isn’t possible (I don’t know if beanstalk is the limit here or svn in general).
Instead of creating a branch in my main repository I created a new repository and gave them access to that with only the most recent snapshot of code that they’ll need. I figure I’ll have to merge their changes manually either way.
What would you have done?
I think I’d dumped an existing repository, then loaded relevan pieces into a new one and then gave access to that new repository to a third-party team, so they would have an existing codebase to start working on. The ultimate reason I’d gone to such lengths is that in this scenario I’d be able to generate a more or less sensible diff, so that manual merging would not be such a daunting task.