Access control: the ability to constrain developers to operating in specific areas of the tree, implement branch-based policy restrictions, as well as to enforce policy such as tagging of commits for developers working outside their normal areas. Implementing these via hooks would not be a regression from what we currently do in CVS.

Hg is distributed and has a “a repository per branch” feature meaning that every developer has his/her own copy of the repositories he/she has an interest in as a set of private directories.

These copies can be published thus are also clone/push/pull-able.

Access control to these will be controlled by an HTTP server (the preferred way of publishing) thus will use the server way of authencating access.

For the reference trees, I'd expect the [“Patch Queue Manager”] to deal with write access.

Partially Supported

A single [“Monotone”] database can contain any number of branches, revisions and files. A server (or any user) can serve any subset of the branches contained in his database. Read/write-permissions are currently managed using [http://venge.net/monotone/docs/Hooks.html Lua hooks] (specifically get_netsync_read_permitted (branch, identity) and get_netsync_write_permitted (identity)), or using the default hooks that are based on two permission files.

A fully featured ACL system (branch-based policy restrictions and much more) is in the works and will be available “soon”.