Lan Barnes wrote:
- Nobody in development knows or understands SCM. It isn't taught in
schools. The academics are just discovering it.
As an "academic", I can speak to this. It has nothing to do with
"discovery".
Administering an SCM in a multi-user academic environment is a *pain in
the ass*. I spent 40-50 hours simply setting up the repository so that
I could use it to do automated code checkout and automated tests.
The problem is that the SCM guys never give any thought to security. I
have 30 students. I should be able to check out and modify their
source, but they should not be able to see and modify each other.
So, how do I set that up without root access to the repository machine?
Try it. It's *hard*. Hint: I used ACL's, but it's annoying.
I welcome any suggestions. I'm hoping that Mercurial gets an Eclipse
plugin soon. The distributed nature of the repositories would alleviate
some of the security problems.
The best way to pitch SCM to "academics" is as a powerful "drop box"
system. Almost all the students have to use some "drop box" to submit
code; normally they use some crappy ftp or email system. Making this
drop box a full SCM system means that the students can learn what they
need to only as required.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
