It was not a good description.



A user "FOO"'s calendar was not viewable from other group members.



This happens when "FOO"'s calendar gets created before the group gets created.



I had to manually add an entry into horde_datatree_attributes table to 
make it viewable for other group members. Following is the entry I 
added.



horde=# select * from horde_datatree_attributes where datatree_id = 10 
and attribute_name = 'perm_groups';

  datatree_id | attribute_name | attribute_key | attribute_value

-------------+----------------+---------------+-----------------

           10 | perm_groups    | 7             | 14

(1 row)



I noticed that all other group members who's calendar gets created 
after the group gets created this 'perm_groups' entry.

Let me clarify the problem.



A user "FOO" who already had a calendar, and joined to a group.

Other group members do not see the "FOO"'s calendar, only when "FOO" 
happens to have the calendar before the group is created.



From what you described here, I think that my problem is indeed a bug then.

Not that it really matters but I said the current behavior was 
reasonable, not that your request was unreasonable.
If you add a user to a group, that user can then see all calendars for 
that group. It doesn't mean anything about who can access that user's 
calendar.

Please kindly explain why it is unreasonable.

Say, if you have 100's of users, created at different times.

You create a new group, and these users join a group, but, there is no 
way to share the calendar.

After designating users to a group, if a user happens to be not have 
the calendar in backend, it is shared. If you happen to already have a 
calendar in backend at the time of joining the group, it is not shared.

I do not understand that joining a user to group does not 
automatically allow some sort of sharing, and sharing only happens 
when and only when the particular user happens to not have the 
calendar object in backend.

I'd appriciate your help. Thank you!

Not sure why you would expect it to, either. This is completely 
reasonable and intended behavior.

User "A" gets created first. "A" starts to use the calendar, so the 
calendar already exists in the database.

The group "G" gets created second.

When "A" joins the group "G", existing calendar does not get the 
necessary attribute in horde_datatree_attributes for the group to 
share the calendar.

In short, attribute_name "perm_group" does not get created when a user 
joins a group when the user's calendar already exists.