Custom ACL support

[If you dont know what ACL is, this project is not for you :) ] We need a function that lets our users to specify which other user can access their files. We also need this function to be added to our php application. This requires two functions 1. GetMeta (return the current ACL associated with the file) 2. PutMeta (set the ACL) Both functions should take/return a php string (formatted in .ini style with multiple sections). Thus the project scope includes verifying that the structure of the ACL file is OK (e.g., the specified users exist) and also modifying our internal functions (there are 5 of them) to take the ACL into account. ACL info for each user should contain READ/WRITE/LIST priveleges for the file/folder READ/WRITE priveleges for the ACL file itself There are some corner cases (e.g., the user shouldnt be able to out itself from the ACL or if the ACL is missing the parent folder's ACL is used) but they are mostly obvious and will be specified fully. Additional requirements. 1. We are looking for a freelancer for a long term relationship. i.e., please do not apply if you are a company or work with an affiliate. 2. We are looking for experienced php developers. However, I would like to emphasize that we are looking for a long term relationship. Please state your long term availability for additional projects. Also can you confirm that you know how to / will 1) use svn to checkin your code to svn 2) allow your code to run on localhost once checked-out from svn (our admin will install this to our server) 3) create unit test cases for each function. (I expect around 30-50 test cases such as invalid user, wrong format, etc.). We use phpunit 4) use mantis for bug/issue management 5) document (phdocs compatible) your functions. 6) use the coding style promoted by the PEAR project (I can provide a link to the coding style if required). ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform PHP 5.x