Re: OpenSRS API Question

Wed, 15 Jan 2003 14:03:38 -0800 

On Wed, 15 Jan 2003 15:35:57 -0500
 "Chris R Chapman" <[EMAIL PROTECTED]> wrote:
I just had to pick up on this exchange as I think it illustrates a really
interesting paradigm:

------------------------------------------------------------------------
You say OpenSRS doesn't support Windows? So bug OpenSRS
support. If they can't meet your needs, and you can't code your own
solution, go elsewhere.


As I stated in my first post I did contact OpenSRS tech

support by phone before I ever started posting here. In

fact I had no idea this "forum" even existed until 
OpenSRS

told me about it.




*THEY* told me to ask the question here.



------------------------------------------------------------------------



PRECISELY!



THIS is the triumph of "open" projects like OpenSRS;  why 
have "OpenSRS

Techs" at all?  "They" haven't the foggiest beyond a 
static list of yes/no

Q&As, so why not outsource the solution to the listserv 
for next to no cost?



Actually, for the non API questions I've asked via Tucows 
Phone Support, I've found that Tucows Tech Support people 
*REALLY KNOW THEIR STUFF*! This is another reason I'm 
trying so hard to use them exclusively as well as 
demonstrate my willingness to allways give credit where 
credit it due.



That said OpenSRS just is'nt is the domain of phone 
support and thus I support Chris' statement that this is 
the place to be.




The trouble is, they represent the sponsors of the 
"Standard", which is by

no means a fait accomplis.  I think it behooves them to 
be a little more on

the ball when developers need assistance.



And as I've said I don't think the docs are as bad as the 
comments in *OTHER THREADS* suggest! I just think OpenSRS 
needs to pull everything together somehow. I made my 
suggestions how to do it, but like Chris said this is a 
live document thus OpenSRS needs to decides how to do it. 



I've 
encountered the same

indifferent attitude when asking questions of the techs 
as well.  Stock

reply is "go to the listserv"-- even when its a matter of 
pointing out

inconsistencies between the API documentation and their 
own PERL scripts.



Sure, it gives us consultants some work, but the flipside 
is that even we

are stymied from time to time and with little help beyond 
the empty chasms

of newsgroups and listservs where you hope to find a 
kindred soul who can

lead you out of the wilderness.


Ahhh, the team spirit is not dead afterall! ;-)























					Reply via email to