Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Mar 1999 15:39:08 -0700
From:      Wes Peters <wes@softweyr.com>
To:        "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc:        Steve Price <sprice@hiwaay.net>, advocacy@FreeBSD.ORG
Subject:   Re: Linux emulation != FreeBSD sale (was Re: Netscape browser)
Message-ID:  <36F2D20C.5813EB8A@softweyr.com>
References:  <52250.921876798@zippy.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" wrote:
> 
> > Try as I might I can't get Netscape to record anywhere that
> > I'm downloading a copy of the Linux version only to run it on
> > a FreeBSD box.  This is very bad!  I download the Linux version.
> 
> I'm afraid that this is something of a red-herring argument, albeit
> probably unintentionally.  To explain why, let's examine the process
> which goes on behind the scenes in producing something like the
> Netscape directory server product and how you, the user, fit into all
> of this:
> 
> [...]
>
> It's sadly not at all inconceivable to imagine that we could well end
> up doing this AGAIN to some other ISV if we just blindly demanded
> FreeBSD native versions in knee-jerk fashion without actually checking
> to see if there's a *market* for them, and it's not enough to say that
> this is the ISV's problem and not ours since we're the ones trying to
> establish some credibility for ourselves - it IS our problem if the
> ISV goes away again in disgust.
> 
> That, in a mere 5000 words, is why I'm now a pragmatist. :-)

It's important to establish a relationship with a vendor before attempting
to yank them around also.  That's the compelling part of sending them a
brand if their product already works; they don't have to do the work.  Once
that has happened, we can wedge our foot further and further into the door.
Here's an ideal sequence:

1) We tell vendor that their Linux product works on FreeBSD.  We've created
   a package that will install it, and we'd like them to stick our little
   logo and a link to the package file on their web site.

   They say "sure" and do it.

2) The app, whatever it is, achieves a level of satisfaction among FreeBSD
   users.  It's becoming apparent that people are using it on FreeBSD, so
   we ask them to track how many FreeBSD vs. Linux downloads they're getting.

   They say "sure" and do it.

3) The app starts getting popular, FreeBSD people are clicking for it in
   droves.  The advocacy group has cautioned people not to share it, but
   to download from the vendor so they get an accurate view of how many
   FreeBSD users they're getting.  Now, there are just these few little
   bugs we see in FreeBSD, or this nice feature.  If they'd just add some
   code to check to see if this is a FreeBSD machine, and if so, add this
   little extra function...

   They say "sure" and it comes out in the next release.

4) The app gets wildly popular.  FreeBSD downloads are (nearly) outstripping
   Linux downloads.  The vendor calls Jordan and says "can you recommend a
   good FreeBSD-savvy programmer who wants to work from home and get paid
   boatloads of money to make a FreeBSD-native version of our app?"  Jordan
   gives them my name, and we *all* live happily ever after, but me especially.

See what a great plan this is?  'Sbeautiful, man!  ;^)

-- 
             Where am I, and what am I doing in this handbasket?

Wes Peters                                                     +1.801.915.2061
Softweyr LLC                                                  wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-advocacy" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36F2D20C.5813EB8A>