Stefan Bellon <[email protected]> wrote: >On Fri, 28 Dec, Richard Hipp wrote: >> When somebody clones the repository,and has a local copy of the >> repository, then they can do anything they want with that local copy >> since it is a file they own. Permissions only come into plan when >> dealing with a remote server. >Right. So, of course, the permissions should already restrict what one >can clone.
They do. It's just that they are at the repository level, not the branch level. But in many senses, a cloned repository *is* a branch. >[push permission] >> The idea is that you trust your developers. >This is not always possible. Back in our university days we had a >stable code branch where only university employees were allowed to >commit, but in certain branches, students were allowed to commit their >work which was merged into trunk by employees. Students were not >allowed to directly commit into trunk. So do that with repositories. Create a stable repository that only employees can commit to. Let students create their own repositories, or (if you feel the need) create a different one they can commit to. Then have employees merge changes from students into the "trunk" repository using an appropriate mechanism. >This is regarding "push permission". Of course, the other direction is >problematic as well. E.g. if there exists 3rd party code that is used >to build the complete product, but for which not each developer has the >required license to see it in source form. Again, just create a repository that only developers that have the appropriate license can see. Making the results of building it available to others is an issue for your CI/OR/etc. system, not your version control system. >Then we'll have to think about moving to Fossil with our main >repositories again. Key word/letter there is "repositorieS". Clones & repositories in fossil (and other DVCS systems) are as cheap as branches in a CVCS, and have a lot of the same properties. Many things that you'd do with a branch in a CVCS you do with a clone in a DVCS. Since merging changes between repositories is only slightly harder than merging changes between branches, this really isn't a problem. -- Sent from my Android tablet with K-9 Mail. Please excuse my swyping. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
