Subject: From: Date:

Re: [ECS] ECS Support, custom interfaces (was [ECS] HVAC-INT Bill Freeman Wed, 30 Sep 1998 11:29:53 -0400

---

I absolutely agree that Mark's commitment to support ECS has been outstanding
and that, in order for this to continue, the costs to Mark must be covered in
his business model.   As we consider (suggest) alternative approaches, it seems
to me that it would be helpful to have some additional information regarding
the state of the various ECS offerings and future plans.

As I've noted previously, I am running ECSD rather than ECS, but evidently like
a number of folks, I am evaluating a switch to the W95 product.   It would be
helpful to me if there existed a document (chart?) that compares/contrasts the
two versions of ECS and, in particular, documents that areas that would need
attention in a conversion.  I realize that the multitude of (historical)
versions of ECSD out there make the preparation of such a document difficult,
i.e. the effort to convert depends on where you come from and what
devices/interfaces you actually use.   (What I am thinking about has a bit more
information than that currently available in the UPD.doc document.)

Perhaps more important than the above, would be some view to ECS's future
"roadmap".   Although Mark has frequently referred to his "list" of functions
to be provided and the relative priorities vs. various items being discussed, I
don't recall ever seeing this list.   It would seem to me that it would be
helpful to us all to have some visability to the planned direction and to have
an opportunity to provide comments and/or other input.   If nothing else, this
would seem to provide Mark with valuable information concerning functions that
his customers view as desirable and would allow him to define an update
strategy to optimize the delivery of additional value.   Lastly, such a public
"roadmap" should help us to avoid the situation where hard feelings result due
to  inaccurate assessments of the potential "demand" for future function.

In the 9 months or so I've been using ECS, I've implemented support for two
(previously unsupported) devices via the "serial byte" capabilities of ECS.
(This is a very powerful capability).   I did so because, at the time this work
was started, there was no existing support and little or no apparent general
interest.   (I am also in the process of designing an alternative
implementation to replace ECS's native support for a third serial device to
obtain additional flexibility.)  Timely visability to Mark's plans for future
function should allow many of us to avoid or limit similar effort and would, I
believe, be of significant value.

Regards,

Bill Freeman
Freemanb@us.ibm.com



don@sb.net on 09/30/98 09:09:21 AM
Please respond to ecs-list@vancouver.ml.org
To: michael@michaeldavid.com
cc: ecs-list@vancouver.ml.org
Subject: Re: [ECS] ECS Support, custom interfaces (was [ECS] HVAC-INT


I imagine Wayne had no idea that he would generate this kind of response.
I'm with Michael on the fees. Sounds fair to me.

Don

On 1998-09-29 michael@michaeldavid.com said:
>>>>>>>>>>>> Snip  <<<<<<<<<<<<<<<<<<<<<<<<<

   >Hi Wayne!
   >Ok, I disagree with some of your message, and I agree the rest. :)
   >I think you should have expected that others would have eventually
   >used the functionality for which you and Reddy donated money.  If
   >you are bothered that you paid something for it and others are
   >getting it for free, don't be. After all, you did get the specific
   >functionality you wanted.  For your investment, you got to
   >influence the development of ECS, and achieved support for a device
   >that Mark may not have supported for some time, if ever.
   >Personally, I think Mark is totally awesome for asking so little
   >for, what amounts to, custom programming.  BTW, I have been is the
   >same position as you on this issue, and it really doesn't bother me
   >a bit. Now, that may not have been your point.

   >1) An annual support fee;
   >perhaps $50.00?  Or, maybe $10 per interface used? This fee could
   >cover bug fixes, and Mark's support here on the list. 2) An upgrade
   >fee for new minor, non-bug fix versions; perhaps $25.00? 3) An
   >upgrade fee for new major, non-bug fix versions; perhaps $50.00? 4)
   >An honor system, whereby anyone who uses any of the privately
   >funded interfaces would send Mark a small donation; perhaps $25.00?
   >5) A small fee for any interfaces used beyond the basic ones
   >supported by ECS; again, perhaps $25.00? What do you guys think?

---