> > Like using it as a way good individuals to announce they will be > > out of office for part of the day. You send a meeting request to > > your team, no alerts, marked not busy, and no reply requested.
No, no, no, and no. You are using the Calendering system so very very wrong. Don't do it that way, no. As not only a scheduling system user, but as a developer, you are one of "those users" who for some reason insist on publishing the appointments YOU have to the calendars of OTHERS. Calendaring systems work - sanely - by pull, not push. You can share YOUR calendar so others can see it, and THEY can **REQUEST** YOU'RE availability [from the server]. That is how it works. Not-Busy [aka INFO-ONLY] appointments have a utility, but it is a narrow astonishingly small use-case, and most certainly not the one you recommend. > So you are effectively using the calendaring system as a mailing > list? Yep. > > And the point of the exercise is not to tell me how bad the process > > is or what other processes the company could use. Most people use > > outlook and the process isn't going to change. I'm trying to use > > Evolution again, but there always seems to be some little sticking > > point like this. > Evolution is not Outlook ... And the client, nor the server, is relevant. This is BAD PRACTICE. And, no, most certainly "everyone" does **NOT** do it this way. Users who do it this way get sent to training. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
