> > Our issue is handling multiple companies doing development on the same > > project. Various restrictions (e.g. licensing) prevent us from sharing > > all project files with everyone involved. It's a tricky use case. We > > also have additional considerations which require us to control project > > read access within a project even within the same company. > > So, you have a branch for each company, and that's why you need > specific read permissions on each branch? If that's the case, I can > see why you want to restrict reading privileges on a per-branch basis. > How do you handle branching and tags in that case? Do you branch > branches and tags off the company branches?
We're rolling like this at the moment. We have a top-level 'main' project folder which is for us only. We use path-based authorization to restrict access here for our users. We've also added another top-level folder 'product' which is a subset copy of 'main.' Every company involved in the product does development in 'product/trunk'. We use path-based authorization to remove read access from the trunk before development work begins. As tags or branches are created for the product, and as new top-level product directories are created we'll need to add a pre-commit hook to remind people to edit httpd.conf for path- based authorization. We've considered removing the restricted source code From the product folder, but the reason for leaving it is because product-specific changes to the restricted code are needed. I'd love to hear any ideas or improvements. Thanks!
