We're currently in the process of evaluating what our customer want with the Reseller Client Library, and I've been assigned with vetting the opinions of techies who use OpenSRS and have decision-making authority within their organization. If you think you fall into this category, I'd like you to answer the questionnaire below and send your answers to me at [EMAIL PROTECTED] I'll post a tally of all the results I get and present them in a report to Product Management.

(Yes, this survey is the same survey as the one on "The Farm", the Tucows developer blog -- http://dev.r.tucows.com. If you've already answered there, you've already answered the survey.)

I am here to be your representative, so the more you tell me, the better!

-- Joey deVilla, TC/DC


RCL SURVEY ==========

Implementation and Deployment
=============================

What platform is your OpenSRS-based system running on?
- Unix (Linux/BSD)
- Windows

What is your preferred programming language?
- C#
- Java servlets
- Perl
- PHP
- VB.NET
- VBScript
- "other"

What if we distributed client binaries instead of client code, with modifable web page templates? Would that be sufficent for your needs?

If we were to change the language in which the OpenSRS client code is written (currently Perl), what deployment concerns would you have?

What do you use to access OpenSRS?
- The "standard" client, either unmodified or with changes only to the HTML displayed to reflect the "look and feel" of your company's web site.
- The "SourceForge" client, either unmodified or with changes only to the HTML displayed to reflect the "look and feel" of your company's web site.
- The "standard" client, modified to implement features that it does not have.
- The "SourceForge" client, modified to implement features that it does not have.
- Your own code, written from the ground up, using our code and the API documentation as a reference.


Which client do you prefer?
- The "standard" client
- The "SourceForge" client

Web services
- Do you use Web services?
- Would you like it if the OpenSRS API were exposed as a Web service? Would problems would it solve?


How do you keep up with API development, specifically new API calls not implemented in the RCL?


Upgrading =========

How often do you upgrade your OpenSRS client?

Would you upgrade more often if we made the process easier?

Who initiates the upgrade process?
- Business manager
- Technical manager
- Someone else

When do you typically upgrade your OpenSRS client?
- Whenever a new release comes out
- Whenever a new feature is implemented
- During regularly-scheduled maintenance period
- When it's a slow time at your company


Business Needs ==============

Would you like to see a payment gateway implemented in the RCL?

Would you like "shopping cart" functionality built into the client? Would you rather that database be local to your server, or would you prefer it be on the OpenSRS servers?

How do you typically charge your end-users for services?
- Monthly
- Yearly
- Some combination that depends of the type of service they're buying

_________________________________________________
Joey deVilla - Tucows, Inc. - [EMAIL PROTECTED]
TC/DC (Technical Community Development Coordinator)
"Nerdy Deeds Done Dirt Cheap"



Reply via email to