May I suggest a more radical approach? I think I've seen similar
suggestions on these lists.
Tucows should abandon the development of ALL client side code. They should
concentrate on making changes to the API, and, even more importantly, making
the API simpler to use by varied clients. Emphasis should be on backward
compatiblity and bug fixes. Additional features added should not break
previously implemented API calls.
The user base of OpenSRS is large enough that the development of client side
code, in numerous languages and environments, will be taken up by developers
all around the world. Clients in Perl, PHP, ASP, Cold Fusion, other
languages would be developed and maintained by users. Expect bug fixes to
be much faster, new features added as the API supports them.
I think the current Tucows approach has run out of steam. Moreover, it's a
BAD way to release the software that your customers rely upon.
Jim
----- Original Message -----
From: "Duane Cook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2001 12:34 PM
Subject: Re: you make it sound like we don't care
>
> I agree, with Joe and Dave, when you release new version every few weeks
> with some minor fixes
> or some new features that no one wants (multilingual is a good example)
then
> we are forced to redo our systems as well. It does seem like you are more
> concerned
> about add new features, then fixing bugs, and adding the things people
have
> been requesting for months, ie, being able to export list of all domains.
