Mailing lists are not the only source of "input" -- I'm sure suggestions come
from many directions.
I've found that no matter what, my vendors don't always do things that make
me happy. I'm anxious to see automated RSP transfers, but they aren't here
yet. Many complained about the renewal process (which was IMHO badly broken)
but it works right now.
Maybe what OpenSRS really needs to do is open a new list
([EMAIL PROTECTED]) so that those who feel a need can use that list,
and those who gripe privately won't have to read it here.
Thanks -- Lynn
-----Original Message-----
From: Robert L Mathews
Sent: Tuesday, April 17, 2001 12:17 PM
To: Lynn W. Taylor
Cc: [EMAIL PROTECTED]
Subject: RE: you make it sound like we don't care
At 4/17/01 11:00 AM, Charles Daminato wrote:
>I appreciate your comments - there's pull from many of you to "put more
>stuff in"
What mailing list are *you* reading?! :-)
I haven't seen much of this at all, unless you count things like
"implement automated RSP transfers" as "put more stuff in" (I consider
that a bug fix).
There wasn't exactly a clamor among the masses for certificates and
multilingual domains, for example. Sure, a few people asked, but it
hardly balanced the number of people complaining about renewal problems,
RSP transfers, etc.
So I find it a little hard to accept the suggestion that OpenSRS
development priorities have been the result of what RSPs have asked for;
that's blaming the victim. Let's be honest and admit that development
priorities have mainly been subject to profit motive -- OpenSRS people
have said as much in the past. I don't begrudge you a profit, but I hope
you'll see that offering reliable, usable services means more to your
long-term profit than introducing new unreliable services.
>And we're now announcing which bugs were fixed with
>which release, as well as establishing a protocol (starting this month!)
>whereby we tell you, the reseller, what's being worked on now and in some
>cases why.
That's definitely a step in the right direction. Thanks!
(Even better would be a bugzilla database or something interactive so
we'd know we're seeing the current info. If it's going to be a separately
maintained list you announce to us, human nature tells you it'll fall
behind the actual development process.)
--
Robert L Mathews, Tiger Technologies
