Skip to content
This repository has been archived by the owner. It is now read-only.

Configurable options for exposing free/busy info for and enabling invitations to a user #304

Closed
macosforgebot opened this issue Jul 5, 2010 · 4 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Jul 5, 2010

jduffas1@… originally submitted this as ticket:383


hello,

we should have the choice, as in zimbra :

  • Allow both internal and external users to see my free/busy information
  • Allow only local users to see my free/busy information
  • Don't let anyone see my free/busy information
  • Allow only the following local users to see my free/busy information :...

and :

  • Allow both internal and external users to invite me to meetings
  • Allow only local users to invite me to meetings
  • Don't let anyone to invite me to meetings
  • Allow only the following local users to invite me to meetings:...
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Feb 20, 2011

@wsanchez originally submitted this as comment:1:⁠ticket:383

  • Radar deleted
  • Description modified
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Feb 20, 2011

@wsanchez originally submitted this as comment:2:⁠ticket:383

  • Milestone changed from CalendarServer-3.x to Later

Right now, there is no such thing as external users or local users as distinct from internal users, so having options to configure them seems superfluous.

There's no UI in any calendar client I know of that supports changing these settings, so we'd have to have a web UI for users to configure their preferences. Until there is such a web UI, getting this done isn't likely.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Nov 30, 2011

@wsanchez originally submitted this as comment:3:⁠ticket:383

  • Summary changed from something missing : to Configurable options for exposing free/busy info for and enabling invitations to a user
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Apr 6, 2015

@wsanchez originally submitted this as comment:4:⁠ticket:383

  • Status changed from new to closed
  • Resolution set to Not to be fixed

Expiring old bugs with unknown impact

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.