[Tickets #11713] Re: Kolab backend: Newly created calendars lose all permissions

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11713
------------------------------------------------------------------------------
  Ticket             | 11713
  Updated By         | Gunnar Wrobel <wrobel at horde.org>
  Summary            | Kolab backend: Newly created calendars lose all
                     | permissions
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Jan Schneider
------------------------------------------------------------------------------


Gunnar Wrobel <wrobel at horde.org> (2012-11-22 18:32) wrote:

The analysis from Thomas is correct: The section "// Process creator  
permissions." within Kronolith::readPermsForm currently removes all  
creator permissions.

I'm totally fine with removing the permission mapping between  
"creator" and "share owner". There is no correct mapping between the  
Horde permission world and the Kolab permission world at the moment.

The question is how much the removal of the creator permission mapping  
would impair usability. Would it still be displayed even with the  
Kolab backend and even though any setting there has no effect? Of  
course the current Kronolith "DELEGATE" permission currently has the  
same problem.

In the long run one would probably need to modify Horde so that it  
allows for different permission models depending on the selected  
backend. But I guess that would be a major undertaking.

Right now I don't see how I can fix anything here. I could apply Jan's  
fix but would rather leave that to him.