Closed macosforgebot closed 13 years ago
@wsanchez originally submitted this as comment:1:ticket:330
Hrm. We removed calendaring for groups because the scheduling implications of groups are pretty gnarly. ie. we don't know what it means to invite a group to a meeting.
Of course we assumed nobody uses groups, since iCal doesn't support them. Are you cheating and adding the group account URL into account prefs?
jduffas1@… originally submitted this as comment:2:ticket:330
but ical does support groups... anyway, I did use it in ical (perhaps not the good way...) if you use group in the account.xml file, you can use it in ical by creating a ney account in ical : enter a member name of the group as user, and it's pass. the url must be : http://www.iyour_server:8008/principals/groups/name_of_the_group/
am I wrong ?
jean
@wsanchez originally submitted this as comment:3:ticket:330
That's one hack to get it a group in there, but it's a hack.
jduffas1@… originally submitted this as comment:4:ticket:330
ok, I didn't know it was not the "normal" way. anyway, how could I reactivate groups ? witch lignes do I have to change, in witch file ?
thank you.
jean
@agx originally submitted this as comment:5:ticket:330
Replying to wsanchez@…:
Hrm. We removed calendaring for groups because the scheduling implications of groups are pretty gnarly. ie. we don't know what it means to invite a group to a meeting.
Of course we assumed nobody uses groups, since iCal doesn't support them. Are you cheating and adding the group account URL into account prefs?
Sure, lots of us are using groups with e.g. Thunderbird/Lightning. This is what makes shared calendaring actually useful. Any chance this comes back by default (maybe without any scheduling for groups).
jduffas1@… originally submitted this as comment:6:ticket:330
so, how could I reactivate groups ? do you plan to reactivate it in next days ?
thank you.
@wsanchez originally submitted this as comment:7:ticket:330
I'm still mulling over the implications of this long-term. At CalConnect in June, we plan to talk about shared calendars and work out some ideas about any standards implications.
I'd be more willing if we could refuse to allow attendees on group calendars (which would trigger scheduling), but I'm not sure that this would satisfy everyone or whether that would require much effort to enforce (guessing not much effort).
@agx originally submitted this as comment:8:ticket:330
I'd be more willing if we could refuse to allow attendees on group calendars (which would trigger scheduling), but I'm not sure that this would satisfy everyone or whether that would require much effort to enforce (guessing not much effort).
I'd say let's try without attendees. That's much better than no group calendars.
jduffas1@… originally submitted this as comment:9:ticket:330
Replying to agx@…:
I'd be more willing if we could refuse to allow attendees on group calendars (which would trigger scheduling), but I'm not sure that this would satisfy everyone or whether that would require much effort to enforce (guessing not much effort).
I'd say let's try without attendees. That's much better than no group calendars.
I agree with you, I do need groups, but attendees can be desabled.
@wsanchez originally submitted this as comment:10:ticket:330
@wsanchez originally submitted this as comment:11:ticket:330
jduffas1@… originally submitted this as attachment:group.png:ticket:330
jduffas1@… originally submitted this as comment:12:ticket:330
hello,
any news about reintegrating calendars in groups ? I sent a image to show that it can be used with no problem in older versions.
thank you.
jean
@wsanchez originally submitted this as comment:13:ticket:330
Still thinking about a real shared calendar solution. Discussions at the last CalConnect meeting made some useful progress here.
@wsanchez originally submitted this as comment:14:ticket:330
cory@… originally submitted this as comment:15:ticket:330
for what it's worth, there definitely is a need for shared/group calendars. and it would be great if the groups are based off of open directory/ldap groups (which is what snow leopard wiki groups provide). here at pixar we're trying to move away from MeetingMaker, and iCal is our current front-runner. the wiki group calendar (with iCal manual prefs cheat) makes group calendaring possible, and this is a requirement of any calendar we'll switch to... any thought on making group/shared calendaring easier?
@wsanchez originally submitted this as comment:16:ticket:330
Shared calendars are supported in trunk (v3).
Groups still can't have calendars, but other principals type can share individual calendars.
So a user can share a calendar with other users (read-only or read/write). MobileMe rolled out a version of this already, which iCal supports, and Calendar Server v3 supports a similar workflow. I think that addresses the needs expressed here.
cory@… originally submitted this as comment:17:ticket:330
just to make sure i'm being clear:
in our movie workflow we have lots of different calendars (many per film, and we release a film per year). ldap/opendirectory groups are created for each movie as well, and we'd like to have the ease of setup such that calendars are able to "just work" based on ldap/opendirectory groups (allowing users in said groups to be able to see/edit the calendar). i do understand that the macos x server wiki calendar feature can do this, but it requires a wiki calendar be explicitly set up for each ldap/opendirectory group manually, and requires adding the url trick for each user's ical client (/principals/uids/wiki-CALENDAR/).
yes, i do realize that none of this is really supported, but i wanted to make clear what we'd prefer, and why it'd be helpful for film industry workflow.
@wsanchez originally submitted this as comment:18:ticket:330
Cory, you are off of the CalendarServer project into the Wiki server and what Apple can do to meet your needs, which aren't topics for this tracker.
Also, stop doing the "url trick" because one of these day's I'll find a way to break that and you'll get grumpy and I'll say I told you so but you'll still be grumpy and all I'll be able to do is point and laugh or something. :-)
cory@… originally submitted this as comment:19:ticket:330
Haha, ok. We can take this over to our Alliance Support contract or something so it's not ruining the purity of the calendar server project trac. ;)
@agx originally submitted this as comment:20:ticket:330
What cory describes looks a lot like group calendars and it'd be great to have them back ;)
@wsanchez originally submitted this as comment:21:ticket:330
OK, I'm going to reopen this as a request to enable shared calendars accessible by a group or ACL list without requiring the wiki server, which I think is pretty reasonable.
@wsanchez originally submitted this as comment:22:ticket:330
@wsanchez originally submitted this as comment:23:ticket:330
We have shared calendars in 3.0
@wsanchez originally submitted this as comment:24:ticket:330
cory@… originally submitted this as comment:25:ticket:330
Does this mean you've decided against making the change to allow group calendars (as opposed to the existing wiki shared calendars)?
@wsanchez originally submitted this as comment:26:ticket:330
Still thinking about an equivalent to the wiki calendar sharing without requiring the wiki, but there's no plan to reinstate group calendars as they were.
jduffas1@… originally submitted this as ticket:330
I upgraded to the latest version, and all my groups are broken. iCal says that there is no home calendar for group, and when I look in the server terminal, it says : 2009-03-30 17:18:22+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] [twistedcaldav.static#info] Directory record <XMLDirectoryRecord[groups@21927289-115a-5605-8596-cd1b708d3750(icalconsult Realm)] F2F2B56A-7B0E-498C-816F-1DA30D8A4167(nous_deux) 'nous deux'> is not enabled for calendaring
I use the accounts.xml file.