After some weeks, yesterday I tried to get a fresh SVN checkout running again. First, I had to change this to check out some dependencies at the "./run -s" step successfully: Index: run =================================================================== --- run (revision 1125) +++ run (working copy) @@ -296,7 +296,7 @@ fi; else echo "Checking out ${name}..."; - svn checkout -r "${revision}" "${uri}@${revision}" "${path}"; + svn checkout -r "${revision}" "${uri}" "${path}"; apply_patches "${name}" "${path}"; fi; After I got the server running (this time on Linux and without LDAP directory binding), I was curious what has changed regarding access control. I still just don't understand which of the limitations of this calendar service compared to usual WebCAL access are intended and which are not. Since it's claimed to conceptually be an extension of WebCAL I would expect to be able to create hierarchies and to adjust ACLs as usual, but in many locations this seems to be not working. I'm not sure whether you (the core developers) are interested in a discussion of this in more detail. (I've sent comments in the past without a response.) I could perfectly understand, if you are not, due to other more important things to work on first. I guess, time is pressing a bit. :-) *If* you like to get more helpful input, IMHO we need more documentation. What's the intended purpose of items in the hierarchy layout (e.g., sudoers, locations, resources)? How can people adjust access control? Where can people put own hierarchies and calendars? Unfortunately, my time is too limited to try to find out everything on my own at this stage of the project where things keep changing.