Thus said "j. van den hoff" on Wed, 27 May 2015 12:10:57 +0200: > the "request to work on branch" is the catch: he wants to ensure that > students can never mess up trunk, i.e. must technically not be able to > merge anything into trunk.
Trunk in *which* clone of the repository? Perhaps the teacher should retain a ``golden master'' clone of the repository somewhere to which only he is allowed to push changes and changes are reviewed and corrected first. > in the end he asks for branch-specific user capabilities. my > understanding is that this is not possible in fossil. It depends on what you allow for ``possible.'' If each student clones, pulls, and pushes from a unique clone of the repository then any changes they make will only be synchronized when whoever controls all the repositories syncs them to the aforementioned ``golden master.'' Consider the following where project1 is cloned once for each student and the teacher pulls content from each one into the ``golden master'' only after it has been reviewed and corrections made (e.g. mistakes merged into trunk). Student1 clones http://host/projects/project1/student1 Student2 clones http://host/projects/project1/student2 Student3 clones http://host/projects/project1/student3 For this to work, access to project1/student1 could be temporarily disabled to prevent race conditions with commits arriving after it has been scrutinized but before it has been pulled into the ``golden master.'' > if so, are there any recommendations how a simple and easily > manageable workflow having this functionality (prevent trunk from > getting spoiled) could look like? I'm not sure that what I mentioned above is easy. I imagine it could be made easier with some scripting. But, given that these are students, why not allow them to spoil trunk occasionally? If they are truly students, will not this be a perfect time for them to learn and discover? After all, do not we learn from our mistakes? Just a thought, Andy -- TAI64 timestamp: 400000005565eb5d _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
