[Tickets #2117] Make Horde Permissions inheritable

Mon Jun 13 20:59:08 PDT 2005

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2117
-----------------------------------------------------------------------
 Ticket             | 2117
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Make Horde Permissions inheritable
 Queue              | Horde Framework Packages
 State              | Feedback
 Priority           | 2. Medium
 Type               | Enhancement
 Owners             | 
-----------------------------------------------------------------------

Chuck Hagenbuch <chuck at horde.org> (2005-06-13 20:59) wrote:

> That would be a reason not to do this by default IMO, because it may 
> change a lot of existing permissions unintentially. I think we should 
> only do this case-by-case for example for the turba:sources perms 
> where you're probably heading at.

If you really think this is a deal breaker then I think we should just
forget it completely; I don't want to have to keep track of where
permissions are inherited and which aren't, and I can't imagine users do.

Then again, if we do it not case-by-case, exactly, but depending on how the
function is called (include a $parentPerms parameter or whatever), then it'd
match the group API... that may have been what you meant? I still feel
uneasy about the inconsistency here, but maybe.

I don't think this is a deal-breaker, fwiw; I just think we need to think it
through, do it carefully, supply upgrade scripts where appropriate, and
announce it loudly.