On Wed, 27 May 2015 18:49:46 +0200, David Mason <[email protected]> wrote:
I use Fossil in 2 ways with students.
1) for each research project I have a Fossil, and all Grad students
working
on that project (and I) have commit access. There are few enough people
that it works out.
I think that's what my colleague has in mind (small group using a 'star
topology'). his idea was to put each student on a separate branch but that
only he was going (and is "allowed") to do merges of changes intro trunk
from which in turn all students could merge back the aggegated changes
into their branches. this works but only on the condition of "mutual
agreement" that everybody is playing to the rules. if not, trunk could be
spoiled by direct checkins or merges performed by some student updating to
trunk. personally I would agree with richard ('no real problem here') as
well as andy ('let them make mistakes and find out the hard way what
problems this causes') but he (and sure other users as well) feels
differently. so I'm following this thread with some interest, what will be
the final consensus (dont' touch or some new idea turning up).
thx/j
2) for assignments, I create a Fossil per student and the student plus
the
marker(s) and I have commit access.
The biggest problem is people committing binary blobs to the repo. But
they can be shunned, if necessary, to manage repo size.
../Dave
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
