Path: utzoo!attcan!uunet!zephyr.ens.tek.com!tektronix!sequent!mntgfx!plogan From: plogan@mentor.com (Patrick Logan) Newsgroups: comp.groupware Subject: Re: Groupware Effects on Hierarchies Message-ID: <1990Jul7.185933.1366@mentor.com> Date: 7 Jul 90 18:59:33 GMT References: <1990Jun24.130413.16511@zorch.SF-Bay.ORG> <2092@east.East.Sun.COM> <1990Jul1.210621.13137@zorch.SF-Bay.ORG> <1984@aurora.cs.athabascau.ca> Organization: engr Lines: 24 In-reply-to: kevinc@cs.AthabascaU.CA's message of 6 Jul 90 04:06:53 GMT In article <1984@aurora.cs.athabascau.ca> kevinc@cs.AthabascaU.CA (Kevin Crocker) writes: > Normally I wouldn't stick my neck into this discussion as I've not had > any experience with groupware (alas the poor unfortunate soul!) but in > the following message... > > [Main text deleted.] > > Kevin Crocker > kevinc@cs.athabascau.ca -or- {alberta,...}!atha!kevinc I'm writing this with the same disadvantage. I have just one observation. That is, even within one organization various people have their own preferences for maintaining their calendar[s]. Shouldn't a scheduling application be flexible enough to accomodate the range of preferences as long as it accomplishes the organization's goal of speedier, accurate scheduling? What attempts have been made along these lines? I'm very ignorant of groupware in general. -- Patrick Logan uunet!mntgfx!plogan | Mentor Graphics Corp. 8500 SW Creekside P | Beaverton, Oregon 97005-7191 |