Re: Archives Suppor [was:Re: Hyperlink in email]
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43398
interpreted = N
texte = I'm looking for an October rollout of the Developer Resource Center. Shortly after, we'll add partner program details. In the meantime, I can give you the 30,000 foot view. Your comments on that are welcome.A while back, Kim Ingram took a little talk list poll where she asked everyone to categorize themselves as one of 4 developer types:1) Independent Developers 2) Developers Employed by Business 3) Owners of Development Business (more than 1 employee) 4) Other I might have looked at it another way:1) Developers who independently or as an employee of a company offers goods and services to other companies. (reseller of WebDNA licenses)2) Developers who are employed by a company to deploy or maintain their own WebDNA installation. (Resembles an end user customer)The needs of both groups are similar. Some of you will find yourselves in both categories. ALL are developers who require support in various forms from Smith Micro.Much of the functionality of the DRC will benefit all visitors; developers, potential customers, potential developers, etc. Access to some of the DRC will be limited to those developers with whom we have created a closer relationship with. The idea of a partner program is to offer leads, a higher level of support, marketing opportunities and other benefits to those who make it a business to offer and support your product. Those who fall into the second category (end user customer) will not find this level of support necessary but will find ample resources in the DRC. Those who are in the first category will find those benefits very useful and will want to be a part of the program. What Smith Micro wants in return is a partnership that helps us evangelize WebDNA and ultimately sell more product. There are many ways for a potential member to show how they might qualify. Perhaps they pay a membership fee. Or maybe buy a certain amount of product within a certain amount of time. Or become certified. I've seen some programs where all you had to do was fog glass to join. Smith Micro's program will not have a financial bar to clear. I know that any developer who makes a living selling their services and who takes the time to learn WebDNA WILL be our evangelist and revenue catalyst. As a matter of formality, we will ask potential partners to tell us about their business in a profile/application form. We will also expect that the developer demonstrates a commitment to WebDNA. Since you're on the talk list and it's quite clear you're supporting WebDNA, the criteria should not represent an obstacle or hardship. We may, for example (remember- this is 30,000 foot) ask that a potential partner produce evidence of a recent purchase of a WebDNA product, be that a license or training program. Or we may look for a developer to offer white papers or case studies to the DRC. Or some combination. The bottom line is that we want the partnership to benefit both parties.This is about all I can say about the program at this moment. Hopefully it gives you some idea of what to expect. Again, your comments are welcome!Doug -----Original Message----- From: Donovan [mailto:donovan@ns1.ddbproductions.org] Sent: Friday, September 13, 2002 12:04 PM To: WebDNA-Talk@talk.smithmicro.com Subject: Re: Archives Suppor [was:Re: Hyperlink in email] Doug Deck wrote:> Donovan, > > Thanks for the timely comments. > > WebDNA without the developer community is a box of code. Obviously we have > revenue targets to keep in mind, but we know the surest way to achieve those > goals is by developing a tighter partnership with developers. The > soon-to-be-launched Developer Resource Center (DRC) is designed with that > goal in mind. Tutorials, case studies, white papers, a forum and an > application showcase where partners can upload examples are all part of the > DRC. Once launched, I'm sure I'll get comments and suggestions for DRC > improvements. I've noticed many members of the talk list are not shy about > offering comments! :-)It's all in the spirit of making a better WebDNA enviro. me thinks. (so don't take it personally.)> > > Smith Micro will continue to offer hosting and consulting services, but I > don't see this as a competitive function. For the most part, our engineers > are focusing on upcoming products.good.> But working on select high-profile > projects will help us deliver more appropriate solutions and also promotes > WebDNA recognition.No problems here.> At the same time, the DRC will showcase our partners > and their hosting and consulting capabilities. We're here to compliment > rather than compete.O.K.> > > Parallel to establishing the DRC is the lead creation effort. WebDNA + > developer partners + customers = $$ for all of us. As we step up the > marketing effort and begin herding opportunities to our door, what will we > do with the leads? The answer is for us to assist in qualifying the needs > and ultimately directing the opportunity to the DRC.This is fine but the caveat is that you have to be a paid member to get the leads right?> If the customer has > in-house WebDNA talent and is only buying a license, they can do that there. > If they need the services of a WebDNA professional, they will find *you* > there. > > You mentioned small writing or condition type of stuff in our new > direction. Can you help me understand what you are referring to?In my understanding there were different levels of participation depending on what you opt in for. I think the levels confuse things.> I'm not > interested in making it complicated to do business with Smith Micro.Then can you explain in a simple way the new levels?(not trying to be rebelious here, but I don't understand your proposed pay service)thanks, Donovan> > > Thanks again for the comments!-- ------------------------------------------------------------------------ ------------------------------------------------------------------------<><> Donovan Brooke <><>->ï ------------------------------------------------------------------------ ------------------------------------------------------------------------ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I'm looking for an October rollout of the Developer Resource Center. Shortly after, we'll add partner program details. In the meantime, I can give you the 30,000 foot view. Your comments on that are welcome.A while back, Kim Ingram took a little Talk List poll where she asked everyone to categorize themselves as one of 4 developer types:1) Independent Developers 2) Developers Employed by Business 3) Owners of Development Business (more than 1 employee) 4) Other I might have looked at it another way:1) Developers who independently or as an employee of a company offers goods and services to other companies. (reseller of WebDNA licenses)2) Developers who are employed by a company to deploy or maintain their own WebDNA installation. (Resembles an end user customer)The needs of both groups are similar. Some of you will find yourselves in both categories. ALL are developers who require support in various forms from Smith Micro.Much of the functionality of the DRC will benefit all visitors; developers, potential customers, potential developers, etc. Access to some of the DRC will be limited to those developers with whom we have created a closer relationship with. The idea of a partner program is to offer leads, a higher level of support, marketing opportunities and other benefits to those who make it a business to offer and support your product. Those who fall into the second category (end user customer) will not find this level of support necessary but will find ample resources in the DRC. Those who are in the first category will find those benefits very useful and will want to be a part of the program. What Smith Micro wants in return is a partnership that helps us evangelize WebDNA and ultimately sell more product. There are many ways for a potential member to show how they might qualify. Perhaps they pay a membership fee. Or maybe buy a certain amount of product within a certain amount of time. Or become certified. I've seen some programs where all you had to do was fog glass to join. Smith Micro's program will not have a financial bar to clear. I know that any developer who makes a living selling their services and who takes the time to learn WebDNA WILL be our evangelist and revenue catalyst. As a matter of formality, we will ask potential partners to tell us about their business in a profile/application form. We will also expect that the developer demonstrates a commitment to WebDNA. Since you're on the Talk List and it's quite clear you're supporting WebDNA, the criteria should not represent an obstacle or hardship. We may, for example (remember- this is 30,000 foot) ask that a potential partner produce evidence of a recent purchase of a WebDNA product, be that a license or training program. Or we may look for a developer to offer white papers or case studies to the DRC. Or some combination. The bottom line is that we want the partnership to benefit both parties.This is about all I can say about the program at this moment. Hopefully it gives you some idea of what to expect. Again, your comments are welcome!Doug -----Original Message----- From: Donovan [mailto:donovan@ns1.ddbproductions.org] Sent: Friday, September 13, 2002 12:04 PM To: WebDNA-Talk@talk.smithmicro.com Subject: Re: Archives Suppor [was:Re: Hyperlink in email] Doug Deck wrote:> Donovan, > > Thanks for the timely comments. > > WebDNA without the developer community is a box of code. Obviously we have > revenue targets to keep in mind, but we know the surest way to achieve those > goals is by developing a tighter partnership with developers. The > soon-to-be-launched Developer Resource Center (DRC) is designed with that > goal in mind. Tutorials, case studies, white papers, a forum and an > application showcase where partners can upload examples are all part of the > DRC. Once launched, I'm sure I'll get comments and suggestions for DRC > improvements. I've noticed many members of the Talk List are not shy about > offering comments! :-)It's all in the spirit of making a better WebDNA enviro. me thinks. (so don't take it personally.)> > > Smith Micro will continue to offer hosting and consulting services, but I > don't see this as a competitive function. For the most part, our engineers > are focusing on upcoming products.good.> But working on select high-profile > projects will help us deliver more appropriate solutions and also promotes > WebDNA recognition.No problems here.> At the same time, the DRC will showcase our partners > and their hosting and consulting capabilities. We're here to compliment > rather than compete.O.K.> > > Parallel to establishing the DRC is the lead creation effort. WebDNA + > developer partners + customers = $$ for all of us. As we step up the > marketing effort and begin herding opportunities to our door, what will we > do with the leads? The answer is for us to assist in qualifying the needs > and ultimately directing the opportunity to the DRC.This is fine but the caveat is that you have to be a paid member to get the leads right?> If the customer has > in-house WebDNA talent and is only buying a license, they can do that there. > If they need the services of a WebDNA professional, they will find *you* > there. > > You mentioned small writing or condition type of stuff in our new > direction. Can you help me understand what you are referring to?In my understanding there were different levels of participation depending on what you opt in for. I think the levels confuse things.> I'm not > interested in making it complicated to do business with Smith Micro.Then can you explain in a simple way the new levels?(not trying to be rebelious here, but I don't understand your proposed pay service)thanks, Donovan> > > Thanks again for the comments!-- ------------------------------------------------------------------------ ------------------------------------------------------------------------<><> Donovan Brooke <><>->ï ------------------------------------------------------------------------ ------------------------------------------------------------------------ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Doug Deck
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
problems with 2 tags shakur (1997)
WC2f3 (1997)
Random sort is not random at all..... (2000)
'does not contain' operator needed ... (1997)
Frames and WebCat (1997)
[WebDNA] WebDNA code on reCAPTCHA wiki (2009)
Credit Card Number checking (1997)
IIS4b2 and WebCatalog b19 (1997)
[WebDNA] Is [math] on a number with too many digits the only way that I can get scientific notation out of webdna? (2011)
WebCat2 Append problem (B14Macacgi) (1997)
Erotic Sites (1997)
WebCatalog can't find database (1997)
referrer usage (1997)
Stripping attachments in shared pop (2005)
remotely creating and populating a stock inventory db -almostthere! (1999)
authenticating a second user, the sequel (1997)
Webcat memory usage Q (2002)
E-mailer application times out (1998)
WebCat2final1 crashes (1997)
Email Formatting and Encryption (1998)