Re[2]: [PEAR-DEV] Looking docs on a site. QA

Hello Greg, >> Why? Every problem has a solution. Can you plug a script into >> /CVSROOT/commitinfo to fetch information about current developers >> permissions and to allow/deny access based on that setting? >> There also can be interface for developers so they can add or remove >> people from CVS access to thier modules. GB> This is a huge security risk. Not all developers are excellent judges GB> of character, it's better that approval be a bit slower but more regulated. GB> If CVS was completely separate for each pear module, it would be a GB> different story. Many developers have full access the the PEAR CVS GB> tree, and probably should not be granting complete control to unknown folks. I mean that lead developers can grant access only to their own modules. Every module has corresponding directory in CVS. At first commitinfo script should check if developer is granted access to all repository. If he isn't then script should check user for developer, who is maintainer of accessed package. If he isn't when script should check if the person is one, who has been granted access by maintainers to commit a patch, for example. This access can have a timeout. Also if this access is granted too often, maintainer of a package can have an option to make that person one of maintainers. Also while speaking about authorship even if somebody is willing to take over orphaned package, status of original author or founder must be preserved for a person who commited the package. I haven't found information that guarantee that. -- TiP