Of course there is a simple way.
Oh, you want suggestions... ;) Here goes.
On Fri, 2005-08-05 at 23:39 -0400, Justin Lebar wrote:
> Since each of the students will be working on the same project at the
> same time, I set up Apache's permissions so that each student has a
> personal folder that only he and I can view.
You have assignments that you want to hand out. These can have whatever
you'd like in them, PDF, text, sample code or Junit tests and they live
in the world readable assignments directory.
Students have read-only access to assignments, they have full access to
ONLY their login name under /students and /submissions (you might want
to use a pre-commit script to only accept one submissions which will be
a tag). You can think of submissions as a tag directory for marking.
> At the same time, however, I want to be able to push files out to some
> or all of my students. For example, I might want to give each of them
> a copy of some Junit tests to run against their code. Later, I'll
> probably find that I have a bug in my Junit tests and I need to give
> the students a new version of the code.
Tell the students to branch your Junit tests `svn cp` This is easy
because you _will_ put the tests in their own sub-dir of the assignment
directory. When you make changes all they need to do us svn merge the
changes into their branch.
You couldn't "push" them out since you might break the students tests if
you forced them to upgrade, they have to merge them in and check for
conflicts with any local modifications.
> So my question is: How should I go about structuring my repository
> such that I can give my students files and change them with the fewest
> headaches? Surely there's a simple way...
HTH's, you may want to tweak things until you are comfortable.
PGP Public Key: http://www.nesser.org/pgp-key/
23:54:23 up 22 min, 2 users, load average: 0.29, 0.31, 0.27
Received on Sat Aug 6 06:07:08 2005