Some sites work best by avoiding all access controls and relying on a sense of team play and cooperation among staff. In situations like this, the administrator’s job is especially easy and involves configuring ACLs to allow full access to configuration management.

To set up a cooperative development environment

In the mks:si ACL, retain all permissions for the everyone principal. This creates a baseline position that provides total access to everyone at the site.

That is all you need to do to create a cooperative development environment. Small sites find this strategy especially useful, because it allows programmers to move from project to project without restriction.

You do not have to define groups because every user is part of the everyone group, and because access to projects is unrestricted, this method does not require numerous ACLs.