Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!sequent!mntgfx!plogan
From: plogan@mentor.com (Patrick Logan)
Newsgroups: comp.groupware
Subject: Re: Groupware Effects on Hierarchie
Message-ID: <1990Jul23.004917.6139@mentor.com>
Date: 23 Jul 90 00:49:17 GMT
References: <1835688710@JANSSEN.90Jul18175044@holmes.par> <1138200037@cdp>
Organization: engr
Lines: 28
In-reply-to: reaton@cdp.UUCP's message of 20 Jul 90 05:19:00 GMT

In article <1138200037@cdp> reaton@cdp.UUCP writes:
  >Gentlemen,
  >    About this calendar argument.  Am I missing something?  Would
  >not a good piece of groupware facilitate the calendar interaction
  >without forcing anything?
  >     You want to put something on someone else's calendar?  Ok,
  >go ahead.  But the system translates your posting into an e-mail
  >invitation which the recipient can post to his calendar by some
  >simple mechanism such as pushing a "calendarize" button.
  >     Or am I missing something?
  >     			  Roger Eaton  (PeaceNet)

I was thinking of the same thing. People could make public (perhaps to
varying degrees) their schedules. [Sort of an elaborate .plan] Then to
schedule an appointment, a person could use a typical e-mail interface
or some other interface, like a calendar combining the known
appointments of everyone being invited.

The receivers may choose to see appointment requests as "penciled in"
in their calendar or as an e-mail message or something else.
Attributes of the "request" may alter the appearance or method of
reception. E.g. a boss' request would be in RED in the calendar. Some
other request may show up in the trash can.

-- 
Patrick Logan  uunet!mntgfx!plogan        |
Mentor Graphics Corp. 8500 SW Creekside P |
Beaverton, Oregon 97005-7191              |