ACL status (with completion estimates)

[Alexey M. <al...@hs...>]

Current status of ACL implementation is as follows:

libcvsacl:

 + does the basic ACL manipulation/checking (ignoring branch, working
   only on trunk) for:

   + branch-level ACLs;

   + directory-level ACLs;

   + default file ACLs;

 + the code is fully auto-verified;


command-line client:

 + 'cvs acl' subcommand for managing the ACLs is mostly implemented
   (setting branch-level and directory ACLs works);

 + actual ACL checking is done only partially: for the most
   important and simple commands; adding new checks is rather easy;

 + the client code is fully auto-verified; 



TODO:

 + complete ACL checking (there is no formal way to make sure that
   "everything" is ACL-controlled, BTW) (est. 1 day);

 + complete the CVS client (actual usability testing should be done)
   (est. 1 day);

 + user groups support; (est. 2 days)

 + fully support branches (est. 2 days);

 + module-level ACL support: both in libcvsacl and in client;
   'cvs racl' subcommand; (est. 3 days)

 + ACL administrators support; (est. 2 days)

where "day" is about 10 hours;

--alexm