On Tue, Feb 22, 2011 at 07:09:14AM +0200, Ron Aaron wrote: > One feature "missing" from Fossil is a way to restrict checkins on the > 'trunk' > (or other branch) to certain people. > > This is necessary in a group where the methodology is for a "gatekeeper" to > approve integration into the main line of development. > > Has there been any thought along those lines? In my perfect scenario, a > branch (including trunk) may have an ACL list which would restrict who could > do what operations on it. > > The way I envision it working is that if a branch has an ACL, it would get > checked against the current user and kind of access, which would be approved > accordingly. > > Thoughts?
As fossil keeps any history, users can do more than checkins, and they can do that in their own repository copies, I think this feature you want looks hard to achieve making all happy. If any user acts in a way you don't like, I think fossil makes you should have a personal conversation with him, and you will have to restore the trunk state from history. But maybe someone has a different view, and comes with a great idea to solve the situation with technical means. :) Regards, Lluís. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
