From: Joachim Werner (joe_at_suse.de)
Date: Mon Aug 02 2004 - 10:35:00 CEST
Message-ID: <410DFCB4.4050407@suse.de> Date: Mon, 02 Aug 2004 10:35:00 +0200 From: Joachim Werner <joe@suse.de> Subject: Re: [taskjuggler-devel] TaskJuggler - Hardware Resources?
Matthias Welwarsky schrieb:
> None, of course. I was unsure if you didn't mistakenly say "rate" instead of
> load or maxeffort. I just fail to see what setting "rate 0" as attribute of a
> resource would do. I thought that "rate" is only about accounting and has no
> effect on workload and effort calculations...
Yes, that's true. But if you think of hardware as something that does
not have an hourly rate or rent you have to pay but is "just there" it
makes sense to set a rate of zero.
>>>There's another fact to consider: If a "hardware" resource is allocated
>>>to a task, that doesn't mean that the task can be started without a
>>>"human" resource. You have to work around that by always allocating human
>>>resources as "mandatory" together with "hardware": those two types do not
>>>form alternatives.
But that's no real difference from having two human resources that form
a team that only can work together. So I think Chris is true that you
don't need another type of resource to model hardware. If you want to be
able to filter for hardware in your reports you can just have all
hardware in one resource tree with the parent resource "hardware" and/or
use flags for that.
> OK. It's kind of inconvenient, but it'll do.
I'm curious. What would be a more convenient solution for that problem?
Cheers
Joachim
-- Joachim Werner SUSE RD-TPM -- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Mon Aug 02 2004 - 10:35:24 CEST