MESSAGE
DATE | 2009-07-27 |
FROM | Simon Fondrie-Teitler
|
SUBJECT | Re: [NYLXS - HANGOUT] Eric Raymond's tips for effective open source
|
From lestw-hangout-at-mrbrklyn.com Mon Jul 27 21:53:16 2009 Received: from www2.mrbrklyn.com (localhost [127.0.0.1]) by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id n6S1rExM008669 for ; Mon, 27 Jul 2009 21:53:16 -0400 Received: (from majordomo-at-localhost) by www2.mrbrklyn.com (8.13.1/8.13.1/Submit) id n6S1rDkr008668 for hangout-outgoings; Mon, 27 Jul 2009 21:53:13 -0400 X-Authentication-Warning: www2.mrbrklyn.com: majordomo set sender to lestw-hangout-at-nylxs.com using -f Received: from mail-bw0-f210.google.com (mail-bw0-f210.google.com [209.85.218.210]) by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id n6S1rAGW008664 for ; Mon, 27 Jul 2009 21:53:12 -0400 Received: by bwz6 with SMTP id 6so2231812bwz.5 for ; Mon, 27 Jul 2009 18:53:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=MenvJ/cqELtGncpzphH9qIiHxTjaKvuz6p70c0wog5U=; b=iX/EcaPnMYwtAp+h78ycrA/U/rs96TpCeBfctzf2zKQxyzkKljgltcyVkrIuZZRL5X fhI7dn8dL+73pmyOEboq6I52oS3Vn1CZh2Ev3Yv02Ahz7+xQvym6TaUNBMzRWRMrzh3C Y7yx1Jjo+zOxOH4tFrDUzKG0wvGnELPUkrD0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=ShK513iXkn33+ivRBeqS9BAynMDxv7f3PVeAUyR51y3LKPtbahK7q3/hrhYotSnUbZ 8nV7JUTnK4ej6EwkEnu2KN5K1XUSld8qakE/ToKivRWGN3ji34rJUxkPzIsR5gjfYijp pPicER8Cbgh6ZPBiOCNLB5/tySlsIcLv+s9xM= MIME-Version: 1.0 Received: by 10.204.60.133 with SMTP id p5mr3738664bkh.143.1248745986192; Mon, 27 Jul 2009 18:53:06 -0700 (PDT) In-Reply-To: <9e8718c60907271822k6efbd86bh3f40acb6b5511c2f-at-mail.gmail.com> References: <9e8718c60907271822k6efbd86bh3f40acb6b5511c2f-at-mail.gmail.com> From: Simon Fondrie-Teitler Date: Mon, 27 Jul 2009 21:52:46 -0400 Message-ID: Subject: Re: [NYLXS - HANGOUT] Eric Raymond's tips for effective open source advocacy To: hangout-at-mrbrklyn.com Content-Type: multipart/alternative; boundary=001636c5b541ebf598046fba54cf Sender: lestw-hangout-at-mrbrklyn.com Precedence: bulk Reply-To: hangout-at-mrbrklyn.com
--001636c5b541ebf598046fba54cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
That might be the least effective slogan I have ever heard.
-------------------------------------------------- Simon Fondrie-Teitler --------------------------------------------------
On Mon, Jul 27, 2009 at 9:22 PM, Joshua Zeidner wrote:
> anyone hear this latest anti-OSS management mantra? > > "Open Source: free as in kittens." > > -jmz > > > On Sun, Jul 26, 2009 at 1:48 PM, Contrarian wrote: > > > > The text at the link I just sent > > > > Eric Raymond's tips for effective open source advocacy > > > > by Rick Moen > > > > If anyone is qualified to tell us how to effectively lobby for the > > wider adoption of open-source software, it's Eric S. Raymond. After > > being propelled -- much to his surprise -- to sudden global prominence > > in 1998 through his involvement in inspiring and launching the Mozilla > > Project, Raymond found himself the de facto spokesman for an entire > > movement, observed that he was fairly good about it, and so set about > > explaining how and why. He briefed a large audience at the recent > > LinuxWorld Conference & Expo on these happenings, and on how the rest > > of us might do likewise, in a talk entitled "Meme Hacking for Fun and > > Profit." > > > > Eric's first step was to figure out why the 1998 effort suddenly > > worked, making business interested in our community's software model, > > after nearly two decades of entirely futile attempts. It wasn't easy. > > > > In May of 1997, Eric published an essay, "The Cathedral and the > > Bazaar" (CatB), explaining his theories of how free software (the only > > term for it, then) gets created, and why the process creates such good > > software so quickly, based on his experience managing a piece of > > utility software called Fetchmail (see Resources). This > > socio-technical analysis, while written to be accessible to a > > nontechnical audience, succeeded only in generating acclaim among > > propeller-beanie Linux users -- preaching to the choir. Eric remained > > better known as Guy Steele's successor in editing the MIT Jargon File, > > one of the cornerstones of "hackish" (computer programmer) culture, > > and as mastermind of the shadowy, tongue-in-cheek (or so They would > > have us think) Eric Conspiracy -- until January 23, 1998. > > > > That morning, Eric received an emailed tip from a friend, suggesting > > he look at the prior day's announcement from Netscape, and cryptically > > commenting "I think someone's been reading your paper." And so Eric > > did -- and was thunderstruck by the fact that a major corporation > > seemed to be implementing his software-management ideas. Indeed, many > > parts of the announcement seemed to be quoting CatB directly. > > > > He cold-called Netscape Communications Corporation's main telephone > > number, working through a bureaucratic maze for fifteen minutes, > > seeming to reach a dead end at a voicemail mailbox. His bewildered > > message went something like, "Hello, my name is Eric Raymond, and I > > think I had something to do with your announcement. Could somebody > > please call me?" Within the hour, Roseanne Cino of Netscape Marketing > > called back, saying, "Yes, all of our top people read your paper and > > loved it. Jim Barksdale is giving your name to the national press, and > > wants to meet you." > > > > As Eric says, "This was the moment of vindication our tribe had been > > waiting for for twenty years." During all that time, the > > technical/Unix community had received essentially nothing but > > brushoffs, being considered impractical freaks in sandals, even though > > it offered clearly better technology. It was clear that the problem > > was not one of substance, but of perception, and Eric saw that Mozilla > > was our key to changing that. > > > > We'd never had a success before, and a procedural analysis of the > > traditional Unix evangelism strategy, typically carried out by > > software engineers within their own companies, showed why. In a such a > > situation, you typically would: > > 1. Become excited by some great technology, and become impressed by > > its potential to change the world for the better. > > 2. Talk it up to your peers. > > 3. Join your peers in approaching the next level of management, > > trying to get them excited, and hope that the excitement trickles > > upward until it reaches the top and changes company policies. > > 4. Sit back and wait for the people at the top to clap their hands to > > their foreheads, and exclaim in a sudden burst of enlightenment, > > "Gosh, we were wrong all along! But we'll change our fundamental > > policies and fix everything!" > > > > Enlightenment doesn't flow uphill > > > > Of course, real authority hierarchies don't work that way. Instead, > > you have, in rough terms, three strata. > > * Decision-makers inhabit the top of the hierarchy. > > * Below them are the middle managers, whose job is to be conservers > > of organisational stability. When asked to change company > > policies, their job is to say "no." > > * At the bottom are the implementers. This is where dwell the > > Unix-loving engineering staff. > > > > The traditional strategy fails because it hits the purposely > > granite-hard wall of middle management, and advocates of open source > > software will wait until Doomsday trying to work past them. And until > > 1998, that's exactly what they were doing. > > > > Mozilla gave us an example to point to, but also material to learn > > from: in that case, enlightenment did not trickle up from below. One > > guy at the top (Jim Clark) encountered a persuasive essay, had a > > moment of enlightenment, and enforced his new vision on everyone > > beneath him. > > > > Clark was convinced, not by moral suasion, but by CatB's pragmatic > > analysis showing why free software yielded shorter time to delivery, > > better code quality, and lower costs. > > > > Ambassador to the suits > > > > Eric could see that the Mozilla code release would be a crucial > > moment, which could yield any of several alternative outcomes: > > * Mozilla could succeed, demonstrating open source's benefits. > > * Mozilla could succeed, but in a way that made it appear to be a > > one-time, freak case. > > * Mozilla might be perceived as having failed, and then become the > > standard reason cited in business circles for not trying again. > > > > He decided that he could help ensure the first outcome by working out > > a credible, coherent explanation of the open source model and its > > benefits that would be amenable to the right sort of audience. That > > target audience would be precisely the one ignored by prior advocates: > > Fortune 500 chief executive officers. > > > > This is easier said than done. As Eric puts it, "Most of us don't play > > golf with Jack Welsh [longtime CEO of General Electric]. We need some > > other way to slip our LSD in their water supply." > > > > Thus, Eric figured, our best bet is a media-centered campaign aimed at > > Fortune 500 CEOs. It might seem at first glance that entrepreneurs > > would be a better bet, but the Fortune 500 are the biggest, most > > influential market that can be reached by a single marketing campaign. > > He decided to concentrate exclusively on the following news outlets: > > the New York Times, the Wall Street Journal, Forbes, Barron's, and the > > Economist. > > > > This list pointedly excludes technical journals, since the people we > > need to reach don't read them, but leave that task to underlings. Eric > > cited what he called Rule Number One of Marketing: "Appeal to the > > prospect's interests and values, not to yours." If the smarter, more > > forward-looking CEOs were convinced to come aboard, the others would > > tend to follow. > > > > The sales pitch > > > > The term "open source," coined by Chris Peterson of the Foresight > > Institute at a strategy session Eric attended in February 1998 after > > the Netscape announcement, followed naturally from this logic. Eric > > feels that the traditional term, "free software," had been a millstone > > around all of our necks, and was simply a nonstarter as rhetoric to > > convince any but the hard-core believers. From the businessman's > > perspective, "free software" sounds at best ambiguous, or possibly > > even threatening: you must explain which meaning of "free" you intend > > (free as in speech, rather than free as in beer), and then clarify > > what free speech has to do with software. Your audience might react, > > "Free? That sounds cheap, shoddy." Or, worse, "Free? That sounds like > > communism." > > > > It's much more effective to sell the concept on the basis of > > reliability, instead. Big corporations lose millions of dollars per > > hour when their datacenters go down. Executives are keenly interested > > in avoiding that. > > > > Also, even concerning their desktop boxes, executives are aware of the > > money drain. Mean time before failure (MTBF) of Windows 9x is less > > than a week. As an installation ages, that shrinks to less than a day. > > With Linux, a box left alone has MTBF of around two years. > > > > Your winning points will be: > > * Total cost of ownership (TCO) > > * Insulation from risk and loss of control > > > > An executive who allows his company to becomes dependent on software > > he is not allowed to see inside, let alone change, has lost control of > > his business, and is on the wrong side of a monopoly relationship with > > a vendor who can thereby control his business. With open source, the > > executive is in control, and nobody can take that away. The > > opportunity to reduce and control business risk is a key concern of > > any CEO. You'll be listened to. > > > > Eric warned that none of this will work without purging one's mind of > > the common techophile's notion that business people are stupid. Eric > > characterised them as "differently optimised," and said that we should > > respect them for their specialty. For one thing, you cannot sell to > > people if you project an attitude of disrespect. Even if you don't > > express it explicitly, it will come through in body language, > > intonation, and other subtle aspects of your demeanour. > > > > Of course, it probably seems reckless to approach one's company CEO > > and advocate changing company policies, and it may well be so. It's > > usually more successful to work on other people's organisations, since > > companies seem oddly resistant to listening to their own technical > > people. Also, partially because most executives will be less inclined > > than Jim Clark to read long essays on the Web, Eric has published "The > > Cathedral and the Bazaar" as part of a book of the same name, > > available from O'Reilly, suitable for leaving as anonymous gifts on > > executive desks. > > > > Dress to persuade > > > > Eric himself tries to adopt the Prince from Another Country stance, a > > term coined by science-fiction writer Norman Spinrad to describe his > > technique for being accepted in multiple communities: You adopt the > > attitude of being a high-ranking member of a different hierarchy, > > which gets you respect without subjecting you to hierarchical > > obligations. Thus, when Spinrad was trying to gain respect in > > Hollywood as a scriptwriter, he conducted himself as a respected > > science fiction author. Conversely, in the science fiction community, > > he billed himself as a leading Hollywood scriptwriter. > > > > Following in the same mold, Eric dresses well but casually, and > > donates his time as a speaker on open source, rather than billing it > > as consulting time. Dressing "well" includes good shoes, meaning, in > > Eric's case, $90 Rockport walking shoes rather than beat-up Reeboks. > > He generally combines these with a neat polo shirt and slacks. > > > > Don't dress like a hacker, Eric warns. Dress the way hackers do in the > > movies. You want to look like a credible, respected member of a > > foreign social system to an audience of executives who've never come > > closer to a real hacker than a Sandra Bullock movie. Therefore, > > "Birkenstocks are right out!" > > > > Even worse than underdressing, as a strategy for being credible to > > executives, would be overdressing. A technology advocate dressed in a > > business suit would tend to come across as a bad imitation of a > > business person -- and thus a person to ignore. It's far safer to > > stick to neat, good-fabric casual wear. > > > > Amy Abascal, head of the Web development team at VA Linux Systems, > > interjected, "But what should the technical woman wear?" I had a brief > > moment of lurid anticipation that Eric might recommend that she > > emulate Carrie-Anne Moss. The daydream passed, and Eric quite rightly > > pointed out that the high-quality black casual wear Amy was wearing > > would serve perfectly. > > > > Local Linux user and magazine columnist Mae Ling Mak shouted out, "But > > what about me?" Eric gazed at Mae Ling's black vinyl cheongsam and > > replied, "Mae Ling, you're a law unto yourself. Never change a thing." > > > > The other sales front > > > > Eric anticipated that his other task would be equally tough: > > convincing free-software advocates to change their rhetoric when > > speaking to business. The Open Source Initiative was founded in > > February 1998 towards that end, with Eric and fellow OSI director > > Bruce Perens advocating the new approach among traditional > > free-software advocates. > > > > To their utter astonishment, they observed 85 percent of the community > > switching the wording on its Web sites within six weeks, suggesting > > pent-up demand in the community for a more effective, less > > confrontational approach. Some organs of the press that used to carry > > what Eric termed "condescending, snarky pieces about free software" > > fell over themselves to speak glowingly of open source. > > > > Talking to the press > > > > Eric's strategy for getting his views across in the press ("press > > manipulation," he freely admits) relies on knowing that most people > > are asleep most of the time. It's impossible to keep your audience > > awake. Therefore, you keep a good stock of attention-getting sound > > bites in reserve, and zap the reporter with them at well-spaced > > intervals. The theory, which Eric claims works quite reliably, is that > > the reporter will remember the sound bites, reproducing them as the > > backbone of his coverage, and discard the parts he half-dozed through. > > (This reporter found the suggestion about as annoying as the wrist > > cramp from his nine pages of lecture notes, but concedes the point may > > be more correct than not. Eric stoked some of our egos a bit by saying > > that technology reporters tended to be way ahead of that curve on > > account of the same hackish traits that got them into that field in > > the first place. Sorry, no kind words for technology readers.) > > > > The other side of the coin > > > > One member of the audience asked how corporations should approach > > relations with the open source community. It's the same problem as > > before, just from the other side: "Appeal to the prospect's interests > > and values, not to yours." Once more, if anyone is qualified to > > address this point, it's Eric. > > * Never lie to geeks. They take it seriously. Most general members > > of the public expect casual prevarication and evasion, but > > technical activists notice it and are offended. > > * Respect community customs. In particular, respect the community's > > software licences. Don't write your own and expect to be greeted > > with open arms. > > * Value your own internal experts. The community doesn't like > > dealing with faceless organisations, and prefers one-on-one > > "horizontal" dealings with individuals. Therefore, identify your > > own people who are likely contacts with the community -- who may > > already be part of it without your being aware of it -- and > > burnish their presence and potential as spokespersons. > > * Give the community members toys; you'll make them happy. > > > > But seriously, folks > > > > As a bit of parting advice, Eric suggested that the most valuable > > skill to pick up is that of effective public speaking. There are a > > variety of groups that aim to teach it, but Eric found his model in > > what at first might seem an unlikely place: stand-up comedy, which he > > says can be effectively studied for tips on timing, punctuation, and > > body language, among other things. > > > > Eric is an animated and extroverted speaker, with a flair for reaching > > out to audiences, and a whimsical sense of fun -- but conceptualising > > him as a Robin Williams or Mike Myers puts him in a new light. > > > > Me: Maybe I'd be a reporter. > > Eric: An evil reporter? > > Me: You always do that! > > > > Resources > > * The Fetchmail utility: > > http://www.tuxedo.org/~esr/fetchmail/ > > * "The Cathedral and the Bazaar," Eric S. Raymond: > > http://www.tuxedo.org/~esr/writings/cathedral-bazaar/ > > * The Jargon File, aka the New Hacker's Dictionary: > > http://www.tuxedo.org/~esr/jargon/ > > * Eric Conspiracy Secret Labs: > > http://www.tuxedo.org/~esr/ecsl/ > > * Netscape's announcement of the planned source code release: > > http://home.netscape.com/newsref/pr/newsrelease558.html > > * The Cathedral and the Bazaar: Musings on Linux and Open Source by > > an Accidental Revolutionary, Eric S. Raymond (O'Reilly and > > Associates, 1999): > > http://www.oreilly.com/catalog/cb/ > > > > Rick Moen is a recovering system administrator in the San Francisco > > Bay Area, who served as primary Bay Area organiser for Windows Refund > > Day, and has been one of the main troublemakers behind Silicon Valley > > Linux User Group's Silicon Valley Tea Party, the Great Linux Revolt of > > '98, and other Bay Area Linux PR events. > > _________________________________________________________________ > > > > Copyright (C) 2000 by Rick Moen, rick-at-linuxmafia.com. > > Article first appeared in LinuxWorld.com > > > >
--001636c5b541ebf598046fba54cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That might be the least effective slogan I have ever heard. "> -------------------------------------------------- Simon Fondrie-T= eitler --------------------------------------------------
On Mon, Jul 27, 2009 at 9:22 PM, Joshua = Zeidner <jjzeid= ner-at-gmail.com> wrote: yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex= ; padding-left: 1ex;">
=C2=A0anyone hear this latest anti-OSS management mantra?
=C2=A0"Open Source: free as in kittens."
=C2=A0-jmz
On Sun, Jul 26, 2009 at 1:48 PM, Contrarian< .net">adrba-at-nyct.net> wrote: > > The text at the link I just sent > > Eric Raymond's tips for effective open source advocacy > > =C2=A0 by Rick Moen > > =C2=A0 If anyone is qualified to tell us how to effectively lobby for = the > =C2=A0 wider adoption of open-source software, it's Eric S. Raymon= d. After > =C2=A0 being propelled -- much to his surprise -- to sudden global pro= minence > =C2=A0 in 1998 through his involvement in inspiring and launching the = Mozilla > =C2=A0 Project, Raymond found himself the de facto spokesman for an en= tire > =C2=A0 movement, observed that he was fairly good about it, and so set= about > =C2=A0 explaining how and why. He briefed a large audience at the rece= nt > =C2=A0 LinuxWorld Conference & Expo on these happenings, and on ho= w the rest > =C2=A0 of us might do likewise, in a talk entitled "Meme Hacking = for Fun and > =C2=A0 Profit." > > =C2=A0 Eric's first step was to figure out why the 1998 effort sud= denly > =C2=A0 worked, making business interested in our community's softw= are model, > =C2=A0 after nearly two decades of entirely futile attempts. It wasn= 39;t easy. > > =C2=A0 In May of 1997, Eric published an essay, "The Cathedral an= d the > =C2=A0 Bazaar" (CatB), explaining his theories of how free softwa= re (the only > =C2=A0 term for it, then) gets created, and why the process creates su= ch good > =C2=A0 software so quickly, based on his experience managing a piece o= f > =C2=A0 utility software called Fetchmail (see Resources). This > =C2=A0 socio-technical analysis, while written to be accessible to a r> > =C2=A0 nontechnical audience, succeeded only in generating acclaim amo= ng
> =C2=A0 propeller-beanie Linux users -- preaching to the choir. Eric re= mained
> =C2=A0 better known as Guy Steele's successor in editing the MIT J= argon File,
> =C2=A0 one of the cornerstones of "hackish" (computer progra= mmer) culture,
> =C2=A0 and as mastermind of the shadowy, tongue-in-cheek (or so They w= ould
> =C2=A0 have us think) Eric Conspiracy -- until January 23, 1998.
>
> =C2=A0 That morning, Eric received an emailed tip from a friend, sugge= sting
> =C2=A0 he look at the prior day's announcement from Netscape, and = cryptically
> =C2=A0 commenting "I think someone's been reading your paper.= " And so Eric
> =C2=A0 did -- and was thunderstruck by the fact that a major corporati= on
> =C2=A0 seemed to be implementing his software-management ideas. Indeed= , many
> =C2=A0 parts of the announcement seemed to be quoting CatB directly.r> >
> =C2=A0 He cold-called Netscape Communications Corporation's main t= elephone
> =C2=A0 number, working through a bureaucratic maze for fifteen minutes= ,
> =C2=A0 seeming to reach a dead end at a voicemail mailbox. His bewilde= red
> =C2=A0 message went something like, "Hello, my name is Eric Raymo= nd, and I
> =C2=A0 think I had something to do with your announcement. Could someb= ody
> =C2=A0 please call me?" Within the hour, Roseanne Cino of Netscap= e Marketing
> =C2=A0 called back, saying, "Yes, all of our top people read your= paper and
> =C2=A0 loved it. Jim Barksdale is giving your name to the national pre= ss, and
> =C2=A0 wants to meet you."
>
> =C2=A0 As Eric says, "This was the moment of vindication our trib= e had been
> =C2=A0 waiting for for twenty years." During all that time, ther> > =C2=A0 technical/Unix community had received essentially nothing butr> > =C2=A0 brushoffs, being considered impractical freaks in sandals, even= though
> =C2=A0 it offered clearly better technology. It was clear that the pro= blem
> =C2=A0 was not one of substance, but of perception, and Eric saw that = Mozilla
> =C2=A0 was our key to changing that.
>
> =C2=A0 We'd never had a success before, and a procedural analysis = of the
> =C2=A0 traditional Unix evangelism strategy, typically carried out by<= br> > =C2=A0 software engineers within their own companies, showed why. In a= such a
> =C2=A0 situation, you typically would:
> =C2=A0 =C2=A01. Become excited by some great technology, and become im= pressed by
> =C2=A0 =C2=A0 =C2=A0 its potential to change the world for the better.=
> =C2=A0 =C2=A02. Talk it up to your peers.
> =C2=A0 =C2=A03. Join your peers in approaching the next level of manag= ement,
> =C2=A0 =C2=A0 =C2=A0 trying to get them excited, and hope that the exc= itement trickles
> =C2=A0 =C2=A0 =C2=A0 upward until it reaches the top and changes compa= ny policies.
> =C2=A0 =C2=A04. Sit back and wait for the people at the top to clap th= eir hands to
> =C2=A0 =C2=A0 =C2=A0 their foreheads, and exclaim in a sudden burst of= enlightenment,
> =C2=A0 =C2=A0 =C2=A0 "Gosh, we were wrong all along! But we'l= l change our fundamental
> =C2=A0 =C2=A0 =C2=A0 policies and fix everything!"
>
> =C2=A0 Enlightenment doesn't flow uphill
>
> =C2=A0 Of course, real authority hierarchies don't work that way. = Instead,
> =C2=A0 you have, in rough terms, three strata.
> =C2=A0 =C2=A0 * Decision-makers inhabit the top of the hierarchy.
> =C2=A0 =C2=A0 * Below them are the middle managers, whose job is to be= conservers
> =C2=A0 =C2=A0 =C2=A0 of organisational stability. When asked to change= company
> =C2=A0 =C2=A0 =C2=A0 policies, their job is to say "no."
> =C2=A0 =C2=A0 * At the bottom are the implementers. This is where dwel= l the
> =C2=A0 =C2=A0 =C2=A0 Unix-loving engineering staff.
>
> =C2=A0 The traditional strategy fails because it hits the purposely > > =C2=A0 granite-hard wall of middle management, and advocates of open s= ource
> =C2=A0 software will wait until Doomsday trying to work past them. And= until
> =C2=A0 1998, that's exactly what they were doing.
>
> =C2=A0 Mozilla gave us an example to point to, but also material to le= arn
> =C2=A0 from: in that case, enlightenment did not trickle up from below= . One
> =C2=A0 guy at the top (Jim Clark) encountered a persuasive essay, had = a
> =C2=A0 moment of enlightenment, and enforced his new vision on everyon= e
> =C2=A0 beneath him.
>
> =C2=A0 Clark was convinced, not by moral suasion, but by CatB's pr= agmatic
> =C2=A0 analysis showing why free software yielded shorter time to deli= very,
> =C2=A0 better code quality, and lower costs.
>
> =C2=A0 Ambassador to the suits
>
> =C2=A0 Eric could see that the Mozilla code release would be a crucial=
> =C2=A0 moment, which could yield any of several alternative outcomes:<= br> > =C2=A0 =C2=A0 * Mozilla could succeed, demonstrating open source's= benefits.
> =C2=A0 =C2=A0 * Mozilla could succeed, but in a way that made it appea= r to be a
> =C2=A0 =C2=A0 =C2=A0 one-time, freak case.
> =C2=A0 =C2=A0 * Mozilla might be perceived as having failed, and then = become the
> =C2=A0 =C2=A0 =C2=A0 standard reason cited in business circles for not= trying again.
>
> =C2=A0 He decided that he could help ensure the first outcome by worki= ng out
> =C2=A0 a credible, coherent explanation of the open source model and i= ts
> =C2=A0 benefits that would be amenable to the right sort of audience. = That
> =C2=A0 target audience would be precisely the one ignored by prior adv= ocates:
> =C2=A0 Fortune 500 chief executive officers.
>
> =C2=A0 This is easier said than done. As Eric puts it, "Most of u= s don't play
> =C2=A0 golf with Jack Welsh [longtime CEO of General Electric]. We nee= d some
> =C2=A0 other way to slip our LSD in their water supply."
>
> =C2=A0 Thus, Eric figured, our best bet is a media-centered campaign a= imed at
> =C2=A0 Fortune 500 CEOs. It might seem at first glance that entreprene= urs
> =C2=A0 would be a better bet, but the Fortune 500 are the biggest, mos= t
> =C2=A0 influential market that can be reached by a single marketing ca= mpaign.
> =C2=A0 He decided to concentrate exclusively on the following news out= lets:
> =C2=A0 the New York Times, the Wall Street Journal, Forbes, Barron'= ;s, and the
> =C2=A0 Economist.
>
> =C2=A0 This list pointedly excludes technical journals, since the peop= le we
> =C2=A0 need to reach don't read them, but leave that task to under= lings. Eric
> =C2=A0 cited what he called Rule Number One of Marketing: "Appeal= to the
> =C2=A0 prospect's interests and values, not to yours." If the= smarter, more
> =C2=A0 forward-looking CEOs were convinced to come aboard, the others = would
> =C2=A0 tend to follow.
>
> =C2=A0 The sales pitch
>
> =C2=A0 The term "open source," coined by Chris Peterson of t= he Foresight
> =C2=A0 Institute at a strategy session Eric attended in February 1998 = after
> =C2=A0 the Netscape announcement, followed naturally from this logic. = Eric
> =C2=A0 feels that the traditional term, "free software," had= been a millstone
> =C2=A0 around all of our necks, and was simply a nonstarter as rhetori= c to
> =C2=A0 convince any but the hard-core believers. From the businessman&= #39;s
> =C2=A0 perspective, "free software" sounds at best ambiguous= , or possibly
> =C2=A0 even threatening: you must explain which meaning of "free&= quot; you intend
> =C2=A0 (free as in speech, rather than free as in beer), and then clar= ify
> =C2=A0 what free speech has to do with software. Your audience might r= eact,
> =C2=A0 "Free? That sounds cheap, shoddy." Or, worse, "F= ree? That sounds like
> =C2=A0 communism."
>
> =C2=A0 It's much more effective to sell the concept on the basis o= f
> =C2=A0 reliability, instead. Big corporations lose millions of dollars= per
> =C2=A0 hour when their datacenters go down. Executives are keenly inte= rested
> =C2=A0 in avoiding that.
>
> =C2=A0 Also, even concerning their desktop boxes, executives are aware= of the
> =C2=A0 money drain. Mean time before failure (MTBF) of Windows 9x is l= ess
> =C2=A0 than a week. As an installation ages, that shrinks to less than= a day.
> =C2=A0 With Linux, a box left alone has MTBF of around two years.
>
> =C2=A0 Your winning points will be:
> =C2=A0 =C2=A0 * Total cost of ownership (TCO)
> =C2=A0 =C2=A0 * Insulation from risk and loss of control
>
> =C2=A0 An executive who allows his company to becomes dependent on sof= tware
> =C2=A0 he is not allowed to see inside, let alone change, has lost con= trol of
> =C2=A0 his business, and is on the wrong side of a monopoly relationsh= ip with
> =C2=A0 a vendor who can thereby control his business. With open source= , the
> =C2=A0 executive is in control, and nobody can take that away. The
> =C2=A0 opportunity to reduce and control business risk is a key concer= n of
> =C2=A0 any CEO. You'll be listened to.
>
> =C2=A0 Eric warned that none of this will work without purging one'= ;s mind of
> =C2=A0 the common techophile's notion that business people are stu= pid. Eric
> =C2=A0 characterised them as "differently optimised," and sa= id that we should
> =C2=A0 respect them for their specialty. For one thing, you cannot sel= l to
> =C2=A0 people if you project an attitude of disrespect. Even if you do= n't
> =C2=A0 express it explicitly, it will come through in body language,r> > =C2=A0 intonation, and other subtle aspects of your demeanour.
>
> =C2=A0 Of course, it probably seems reckless to approach one's com= pany CEO
> =C2=A0 and advocate changing company policies, and it may well be so. = It's
> =C2=A0 usually more successful to work on other people's organisat= ions, since
> =C2=A0 companies seem oddly resistant to listening to their own techni= cal
> =C2=A0 people. Also, partially because most executives will be less in= clined
> =C2=A0 than Jim Clark to read long essays on the Web, Eric has publish= ed "The
> =C2=A0 Cathedral and the Bazaar" as part of a book of the same na= me,
> =C2=A0 available from O'Reilly, suitable for leaving as anonymous = gifts on
> =C2=A0 executive desks.
>
> =C2=A0 Dress to persuade
>
> =C2=A0 Eric himself tries to adopt the Prince from Another Country sta= nce, a
> =C2=A0 term coined by science-fiction writer Norman Spinrad to describ= e his
> =C2=A0 technique for being accepted in multiple communities: You adopt= the
> =C2=A0 attitude of being a high-ranking member of a different hierarch= y,
> =C2=A0 which gets you respect without subjecting you to hierarchicalr> > =C2=A0 obligations. Thus, when Spinrad was trying to gain respect inr> > =C2=A0 Hollywood as a scriptwriter, he conducted himself as a respecte= d
> =C2=A0 science fiction author. Conversely, in the science fiction comm= unity,
> =C2=A0 he billed himself as a leading Hollywood scriptwriter.
>
> =C2=A0 Following in the same mold, Eric dresses well but casually, and=
> =C2=A0 donates his time as a speaker on open source, rather than billi= ng it
> =C2=A0 as consulting time. Dressing "well" includes good sho= es, meaning, in
> =C2=A0 Eric's case, $90 Rockport walking shoes rather than beat-up= Reeboks.
> =C2=A0 He generally combines these with a neat polo shirt and slacks.<= br> >
> =C2=A0 Don't dress like a hacker, Eric warns. Dress the way hacker= s do in the
> =C2=A0 movies. You want to look like a credible, respected member of a=
> =C2=A0 foreign social system to an audience of executives who've n= ever come
> =C2=A0 closer to a real hacker than a Sandra Bullock movie. Therefore,=
> =C2=A0 "Birkenstocks are right out!"
>
> =C2=A0 Even worse than underdressing, as a strategy for being credible= to
> =C2=A0 executives, would be overdressing. A technology advocate dresse= d in a
> =C2=A0 business suit would tend to come across as a bad imitation of a=
> =C2=A0 business person -- and thus a person to ignore. It's far sa= fer to
> =C2=A0 stick to neat, good-fabric casual wear.
>
> =C2=A0 Amy Abascal, head of the Web development team at VA Linux Syste= ms,
> =C2=A0 interjected, "But what should the technical woman wear?&qu= ot; I had a brief
> =C2=A0 moment of lurid anticipation that Eric might recommend that she=
> =C2=A0 emulate Carrie-Anne Moss. The daydream passed, and Eric quite r= ightly
> =C2=A0 pointed out that the high-quality black casual wear Amy was wea= ring
> =C2=A0 would serve perfectly.
>
> =C2=A0 Local Linux user and magazine columnist Mae Ling Mak shouted ou= t, "But
> =C2=A0 what about me?" Eric gazed at Mae Ling's black vinyl c= heongsam and
> =C2=A0 replied, "Mae Ling, you're a law unto yourself. Never = change a thing."
>
> =C2=A0 The other sales front
>
> =C2=A0 Eric anticipated that his other task would be equally tough: > > =C2=A0 convincing free-software advocates to change their rhetoric whe= n
> =C2=A0 speaking to business. The Open Source Initiative was founded in=
> =C2=A0 February 1998 towards that end, with Eric and fellow OSI direct= or
> =C2=A0 Bruce Perens advocating the new approach among traditional
> =C2=A0 free-software advocates.
>
> =C2=A0 To their utter astonishment, they observed 85 percent of the co= mmunity
> =C2=A0 switching the wording on its Web sites within six weeks, sugges= ting
> =C2=A0 pent-up demand in the community for a more effective, less
> =C2=A0 confrontational approach. Some organs of the press that used to= carry
> =C2=A0 what Eric termed "condescending, snarky pieces about free = software"
> =C2=A0 fell over themselves to speak glowingly of open source.
>
> =C2=A0 Talking to the press
>
> =C2=A0 Eric's strategy for getting his views across in the press (= "press
> =C2=A0 manipulation," he freely admits) relies on knowing that mo= st people
> =C2=A0 are asleep most of the time. It's impossible to keep your a= udience
> =C2=A0 awake. Therefore, you keep a good stock of attention-getting so= und
> =C2=A0 bites in reserve, and zap the reporter with them at well-spaced=
> =C2=A0 intervals. The theory, which Eric claims works quite reliably, = is that
> =C2=A0 the reporter will remember the sound bites, reproducing them as= the
> =C2=A0 backbone of his coverage, and discard the parts he half-dozed t= hrough.
> =C2=A0 (This reporter found the suggestion about as annoying as the wr= ist
> =C2=A0 cramp from his nine pages of lecture notes, but concedes the po= int may
> =C2=A0 be more correct than not. Eric stoked some of our egos a bit by= saying
> =C2=A0 that technology reporters tended to be way ahead of that curve = on
> =C2=A0 account of the same hackish traits that got them into that fiel= d in
> =C2=A0 the first place. Sorry, no kind words for technology readers.)<= br> >
> =C2=A0 The other side of the coin
>
> =C2=A0 One member of the audience asked how corporations should approa= ch
> =C2=A0 relations with the open source community. It's the same pro= blem as
> =C2=A0 before, just from the other side: "Appeal to the prospect&= #39;s interests
> =C2=A0 and values, not to yours." Once more, if anyone is qualifi= ed to
> =C2=A0 address this point, it's Eric.
> =C2=A0 =C2=A0 * Never lie to geeks. They take it seriously. Most gener= al members
> =C2=A0 =C2=A0 =C2=A0 of the public expect casual prevarication and eva= sion, but
> =C2=A0 =C2=A0 =C2=A0 technical activists notice it and are offended.r> > =C2=A0 =C2=A0 * Respect community customs. In particular, respect the = community's
> =C2=A0 =C2=A0 =C2=A0 software licences. Don't write your own and e= xpect to be greeted
> =C2=A0 =C2=A0 =C2=A0 with open arms.
> =C2=A0 =C2=A0 * Value your own internal experts. The community doesn= 39;t like
> =C2=A0 =C2=A0 =C2=A0 dealing with faceless organisations, and prefers = one-on-one
> =C2=A0 =C2=A0 =C2=A0 "horizontal" dealings with individuals.= Therefore, identify your
> =C2=A0 =C2=A0 =C2=A0 own people who are likely contacts with the commu= nity -- who may
> =C2=A0 =C2=A0 =C2=A0 already be part of it without your being aware of= it -- and
> =C2=A0 =C2=A0 =C2=A0 burnish their presence and potential as spokesper= sons.
> =C2=A0 =C2=A0 * Give the community members toys; you'll make them = happy.
>
> =C2=A0 But seriously, folks
>
> =C2=A0 As a bit of parting advice, Eric suggested that the most valuab= le
> =C2=A0 skill to pick up is that of effective public speaking. There ar= e a
> =C2=A0 variety of groups that aim to teach it, but Eric found his mode= l in
> =C2=A0 what at first might seem an unlikely place: stand-up comedy, wh= ich he
> =C2=A0 says can be effectively studied for tips on timing, punctuation= , and
> =C2=A0 body language, among other things.
>
> =C2=A0 Eric is an animated and extroverted speaker, with a flair for r= eaching
> =C2=A0 out to audiences, and a whimsical sense of fun -- but conceptua= lising
> =C2=A0 him as a Robin Williams or Mike Myers puts him in a new light.<= br> >
> =C2=A0 Me: Maybe I'd be a reporter.
> =C2=A0 Eric: An evil reporter?
> =C2=A0 Me: You always do that!
>
> =C2=A0 Resources
> =C2=A0 =C2=A0 * The Fetchmail utility:
> =C2=A0 =C2=A0 =C2=A0 /" target=3D"_blank">http://www.tuxedo.org/~esr/fetchmail/
> =C2=A0 =C2=A0 * "The Cathedral and the Bazaar," Eric S. Raym= ond:
> =C2=A0 =C2=A0 =C2=A0 cathedral-bazaar/" target=3D"_blank">http://www.tuxedo.org/~esr/writings/ca= thedral-bazaar/
> =C2=A0 =C2=A0 * The Jargon File, aka the New Hacker's Dictionary:<= br> > =C2=A0 =C2=A0 =C2=A0 target=3D"_blank">http://www.tuxedo.org/~esr/jargon/
> =C2=A0 =C2=A0 * Eric Conspiracy Secret Labs:
> =C2=A0 =C2=A0 =C2=A0 rget=3D"_blank">http://www.tuxedo.org/~esr/ecsl/
> =C2=A0 =C2=A0 * Netscape's announcement of the planned source code= release:
> =C2=A0 =C2=A0 =C2=A0 wsrelease558.html" target=3D"_blank">http://home.netscape.com/newsref/pr/ne= wsrelease558.html
> =C2=A0 =C2=A0 * The Cathedral and the Bazaar: Musings on Linux and Ope= n Source by
> =C2=A0 =C2=A0 =C2=A0 an Accidental Revolutionary, Eric S. Raymond (O= 39;Reilly and
> =C2=A0 =C2=A0 =C2=A0 Associates, 1999):
> =C2=A0 =C2=A0 =C2=A0 rget=3D"_blank">http://www.oreilly.com/catalog/cb/
>
> =C2=A0 Rick Moen is a recovering system administrator in the San Franc= isco
> =C2=A0 Bay Area, who served as primary Bay Area organiser for Windows = Refund
> =C2=A0 Day, and has been one of the main troublemakers behind Silicon = Valley
> =C2=A0 Linux User Group's Silicon Valley Tea Party, the Great Linu= x Revolt of
> =C2=A0 '98, and other Bay Area Linux PR events.
> =C2=A0 =C2=A0 ________________________________________________________= _________
>
> =C2=A0 Copyright (C) 2000 by Rick Moen, fia.com">rick-at-linuxmafia.com.
> =C2=A0 Article first appeared in LinuxWorld.com
>
--001636c5b541ebf598046fba54cf--
--001636c5b541ebf598046fba54cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
That might be the least effective slogan I have ever heard.
-------------------------------------------------- Simon Fondrie-Teitler --------------------------------------------------
On Mon, Jul 27, 2009 at 9:22 PM, Joshua Zeidner wrote:
> anyone hear this latest anti-OSS management mantra? > > "Open Source: free as in kittens." > > -jmz > > > On Sun, Jul 26, 2009 at 1:48 PM, Contrarian wrote: > > > > The text at the link I just sent > > > > Eric Raymond's tips for effective open source advocacy > > > > by Rick Moen > > > > If anyone is qualified to tell us how to effectively lobby for the > > wider adoption of open-source software, it's Eric S. Raymond. After > > being propelled -- much to his surprise -- to sudden global prominence > > in 1998 through his involvement in inspiring and launching the Mozilla > > Project, Raymond found himself the de facto spokesman for an entire > > movement, observed that he was fairly good about it, and so set about > > explaining how and why. He briefed a large audience at the recent > > LinuxWorld Conference & Expo on these happenings, and on how the rest > > of us might do likewise, in a talk entitled "Meme Hacking for Fun and > > Profit." > > > > Eric's first step was to figure out why the 1998 effort suddenly > > worked, making business interested in our community's software model, > > after nearly two decades of entirely futile attempts. It wasn't easy. > > > > In May of 1997, Eric published an essay, "The Cathedral and the > > Bazaar" (CatB), explaining his theories of how free software (the only > > term for it, then) gets created, and why the process creates such good > > software so quickly, based on his experience managing a piece of > > utility software called Fetchmail (see Resources). This > > socio-technical analysis, while written to be accessible to a > > nontechnical audience, succeeded only in generating acclaim among > > propeller-beanie Linux users -- preaching to the choir. Eric remained > > better known as Guy Steele's successor in editing the MIT Jargon File, > > one of the cornerstones of "hackish" (computer programmer) culture, > > and as mastermind of the shadowy, tongue-in-cheek (or so They would > > have us think) Eric Conspiracy -- until January 23, 1998. > > > > That morning, Eric received an emailed tip from a friend, suggesting > > he look at the prior day's announcement from Netscape, and cryptically > > commenting "I think someone's been reading your paper." And so Eric > > did -- and was thunderstruck by the fact that a major corporation > > seemed to be implementing his software-management ideas. Indeed, many > > parts of the announcement seemed to be quoting CatB directly. > > > > He cold-called Netscape Communications Corporation's main telephone > > number, working through a bureaucratic maze for fifteen minutes, > > seeming to reach a dead end at a voicemail mailbox. His bewildered > > message went something like, "Hello, my name is Eric Raymond, and I > > think I had something to do with your announcement. Could somebody > > please call me?" Within the hour, Roseanne Cino of Netscape Marketing > > called back, saying, "Yes, all of our top people read your paper and > > loved it. Jim Barksdale is giving your name to the national press, and > > wants to meet you." > > > > As Eric says, "This was the moment of vindication our tribe had been > > waiting for for twenty years." During all that time, the > > technical/Unix community had received essentially nothing but > > brushoffs, being considered impractical freaks in sandals, even though > > it offered clearly better technology. It was clear that the problem > > was not one of substance, but of perception, and Eric saw that Mozilla > > was our key to changing that. > > > > We'd never had a success before, and a procedural analysis of the > > traditional Unix evangelism strategy, typically carried out by > > software engineers within their own companies, showed why. In a such a > > situation, you typically would: > > 1. Become excited by some great technology, and become impressed by > > its potential to change the world for the better. > > 2. Talk it up to your peers. > > 3. Join your peers in approaching the next level of management, > > trying to get them excited, and hope that the excitement trickles > > upward until it reaches the top and changes company policies. > > 4. Sit back and wait for the people at the top to clap their hands to > > their foreheads, and exclaim in a sudden burst of enlightenment, > > "Gosh, we were wrong all along! But we'll change our fundamental > > policies and fix everything!" > > > > Enlightenment doesn't flow uphill > > > > Of course, real authority hierarchies don't work that way. Instead, > > you have, in rough terms, three strata. > > * Decision-makers inhabit the top of the hierarchy. > > * Below them are the middle managers, whose job is to be conservers > > of organisational stability. When asked to change company > > policies, their job is to say "no." > > * At the bottom are the implementers. This is where dwell the > > Unix-loving engineering staff. > > > > The traditional strategy fails because it hits the purposely > > granite-hard wall of middle management, and advocates of open source > > software will wait until Doomsday trying to work past them. And until > > 1998, that's exactly what they were doing. > > > > Mozilla gave us an example to point to, but also material to learn > > from: in that case, enlightenment did not trickle up from below. One > > guy at the top (Jim Clark) encountered a persuasive essay, had a > > moment of enlightenment, and enforced his new vision on everyone > > beneath him. > > > > Clark was convinced, not by moral suasion, but by CatB's pragmatic > > analysis showing why free software yielded shorter time to delivery, > > better code quality, and lower costs. > > > > Ambassador to the suits > > > > Eric could see that the Mozilla code release would be a crucial > > moment, which could yield any of several alternative outcomes: > > * Mozilla could succeed, demonstrating open source's benefits. > > * Mozilla could succeed, but in a way that made it appear to be a > > one-time, freak case. > > * Mozilla might be perceived as having failed, and then become the > > standard reason cited in business circles for not trying again. > > > > He decided that he could help ensure the first outcome by working out > > a credible, coherent explanation of the open source model and its > > benefits that would be amenable to the right sort of audience. That > > target audience would be precisely the one ignored by prior advocates: > > Fortune 500 chief executive officers. > > > > This is easier said than done. As Eric puts it, "Most of us don't play > > golf with Jack Welsh [longtime CEO of General Electric]. We need some > > other way to slip our LSD in their water supply." > > > > Thus, Eric figured, our best bet is a media-centered campaign aimed at > > Fortune 500 CEOs. It might seem at first glance that entrepreneurs > > would be a better bet, but the Fortune 500 are the biggest, most > > influential market that can be reached by a single marketing campaign. > > He decided to concentrate exclusively on the following news outlets: > > the New York Times, the Wall Street Journal, Forbes, Barron's, and the > > Economist. > > > > This list pointedly excludes technical journals, since the people we > > need to reach don't read them, but leave that task to underlings. Eric > > cited what he called Rule Number One of Marketing: "Appeal to the > > prospect's interests and values, not to yours." If the smarter, more > > forward-looking CEOs were convinced to come aboard, the others would > > tend to follow. > > > > The sales pitch > > > > The term "open source," coined by Chris Peterson of the Foresight > > Institute at a strategy session Eric attended in February 1998 after > > the Netscape announcement, followed naturally from this logic. Eric > > feels that the traditional term, "free software," had been a millstone > > around all of our necks, and was simply a nonstarter as rhetoric to > > convince any but the hard-core believers. From the businessman's > > perspective, "free software" sounds at best ambiguous, or possibly > > even threatening: you must explain which meaning of "free" you intend > > (free as in speech, rather than free as in beer), and then clarify > > what free speech has to do with software. Your audience might react, > > "Free? That sounds cheap, shoddy." Or, worse, "Free? That sounds like > > communism." > > > > It's much more effective to sell the concept on the basis of > > reliability, instead. Big corporations lose millions of dollars per > > hour when their datacenters go down. Executives are keenly interested > > in avoiding that. > > > > Also, even concerning their desktop boxes, executives are aware of the > > money drain. Mean time before failure (MTBF) of Windows 9x is less > > than a week. As an installation ages, that shrinks to less than a day. > > With Linux, a box left alone has MTBF of around two years. > > > > Your winning points will be: > > * Total cost of ownership (TCO) > > * Insulation from risk and loss of control > > > > An executive who allows his company to becomes dependent on software > > he is not allowed to see inside, let alone change, has lost control of > > his business, and is on the wrong side of a monopoly relationship with > > a vendor who can thereby control his business. With open source, the > > executive is in control, and nobody can take that away. The > > opportunity to reduce and control business risk is a key concern of > > any CEO. You'll be listened to. > > > > Eric warned that none of this will work without purging one's mind of > > the common techophile's notion that business people are stupid. Eric > > characterised them as "differently optimised," and said that we should > > respect them for their specialty. For one thing, you cannot sell to > > people if you project an attitude of disrespect. Even if you don't > > express it explicitly, it will come through in body language, > > intonation, and other subtle aspects of your demeanour. > > > > Of course, it probably seems reckless to approach one's company CEO > > and advocate changing company policies, and it may well be so. It's > > usually more successful to work on other people's organisations, since > > companies seem oddly resistant to listening to their own technical > > people. Also, partially because most executives will be less inclined > > than Jim Clark to read long essays on the Web, Eric has published "The > > Cathedral and the Bazaar" as part of a book of the same name, > > available from O'Reilly, suitable for leaving as anonymous gifts on > > executive desks. > > > > Dress to persuade > > > > Eric himself tries to adopt the Prince from Another Country stance, a > > term coined by science-fiction writer Norman Spinrad to describe his > > technique for being accepted in multiple communities: You adopt the > > attitude of being a high-ranking member of a different hierarchy, > > which gets you respect without subjecting you to hierarchical > > obligations. Thus, when Spinrad was trying to gain respect in > > Hollywood as a scriptwriter, he conducted himself as a respected > > science fiction author. Conversely, in the science fiction community, > > he billed himself as a leading Hollywood scriptwriter. > > > > Following in the same mold, Eric dresses well but casually, and > > donates his time as a speaker on open source, rather than billing it > > as consulting time. Dressing "well" includes good shoes, meaning, in > > Eric's case, $90 Rockport walking shoes rather than beat-up Reeboks. > > He generally combines these with a neat polo shirt and slacks. > > > > Don't dress like a hacker, Eric warns. Dress the way hackers do in the > > movies. You want to look like a credible, respected member of a > > foreign social system to an audience of executives who've never come > > closer to a real hacker than a Sandra Bullock movie. Therefore, > > "Birkenstocks are right out!" > > > > Even worse than underdressing, as a strategy for being credible to > > executives, would be overdressing. A technology advocate dressed in a > > business suit would tend to come across as a bad imitation of a > > business person -- and thus a person to ignore. It's far safer to > > stick to neat, good-fabric casual wear. > > > > Amy Abascal, head of the Web development team at VA Linux Systems, > > interjected, "But what should the technical woman wear?" I had a brief > > moment of lurid anticipation that Eric might recommend that she > > emulate Carrie-Anne Moss. The daydream passed, and Eric quite rightly > > pointed out that the high-quality black casual wear Amy was wearing > > would serve perfectly. > > > > Local Linux user and magazine columnist Mae Ling Mak shouted out, "But > > what about me?" Eric gazed at Mae Ling's black vinyl cheongsam and > > replied, "Mae Ling, you're a law unto yourself. Never change a thing." > > > > The other sales front > > > > Eric anticipated that his other task would be equally tough: > > convincing free-software advocates to change their rhetoric when > > speaking to business. The Open Source Initiative was founded in > > February 1998 towards that end, with Eric and fellow OSI director > > Bruce Perens advocating the new approach among traditional > > free-software advocates. > > > > To their utter astonishment, they observed 85 percent of the community > > switching the wording on its Web sites within six weeks, suggesting > > pent-up demand in the community for a more effective, less > > confrontational approach. Some organs of the press that used to carry > > what Eric termed "condescending, snarky pieces about free software" > > fell over themselves to speak glowingly of open source. > > > > Talking to the press > > > > Eric's strategy for getting his views across in the press ("press > > manipulation," he freely admits) relies on knowing that most people > > are asleep most of the time. It's impossible to keep your audience > > awake. Therefore, you keep a good stock of attention-getting sound > > bites in reserve, and zap the reporter with them at well-spaced > > intervals. The theory, which Eric claims works quite reliably, is that > > the reporter will remember the sound bites, reproducing them as the > > backbone of his coverage, and discard the parts he half-dozed through. > > (This reporter found the suggestion about as annoying as the wrist > > cramp from his nine pages of lecture notes, but concedes the point may > > be more correct than not. Eric stoked some of our egos a bit by saying > > that technology reporters tended to be way ahead of that curve on > > account of the same hackish traits that got them into that field in > > the first place. Sorry, no kind words for technology readers.) > > > > The other side of the coin > > > > One member of the audience asked how corporations should approach > > relations with the open source community. It's the same problem as > > before, just from the other side: "Appeal to the prospect's interests > > and values, not to yours." Once more, if anyone is qualified to > > address this point, it's Eric. > > * Never lie to geeks. They take it seriously. Most general members > > of the public expect casual prevarication and evasion, but > > technical activists notice it and are offended. > > * Respect community customs. In particular, respect the community's > > software licences. Don't write your own and expect to be greeted > > with open arms. > > * Value your own internal experts. The community doesn't like > > dealing with faceless organisations, and prefers one-on-one > > "horizontal" dealings with individuals. Therefore, identify your > > own people who are likely contacts with the community -- who may > > already be part of it without your being aware of it -- and > > burnish their presence and potential as spokespersons. > > * Give the community members toys; you'll make them happy. > > > > But seriously, folks > > > > As a bit of parting advice, Eric suggested that the most valuable > > skill to pick up is that of effective public speaking. There are a > > variety of groups that aim to teach it, but Eric found his model in > > what at first might seem an unlikely place: stand-up comedy, which he > > says can be effectively studied for tips on timing, punctuation, and > > body language, among other things. > > > > Eric is an animated and extroverted speaker, with a flair for reaching > > out to audiences, and a whimsical sense of fun -- but conceptualising > > him as a Robin Williams or Mike Myers puts him in a new light. > > > > Me: Maybe I'd be a reporter. > > Eric: An evil reporter? > > Me: You always do that! > > > > Resources > > * The Fetchmail utility: > > http://www.tuxedo.org/~esr/fetchmail/ > > * "The Cathedral and the Bazaar," Eric S. Raymond: > > http://www.tuxedo.org/~esr/writings/cathedral-bazaar/ > > * The Jargon File, aka the New Hacker's Dictionary: > > http://www.tuxedo.org/~esr/jargon/ > > * Eric Conspiracy Secret Labs: > > http://www.tuxedo.org/~esr/ecsl/ > > * Netscape's announcement of the planned source code release: > > http://home.netscape.com/newsref/pr/newsrelease558.html > > * The Cathedral and the Bazaar: Musings on Linux and Open Source by > > an Accidental Revolutionary, Eric S. Raymond (O'Reilly and > > Associates, 1999): > > http://www.oreilly.com/catalog/cb/ > > > > Rick Moen is a recovering system administrator in the San Francisco > > Bay Area, who served as primary Bay Area organiser for Windows Refund > > Day, and has been one of the main troublemakers behind Silicon Valley > > Linux User Group's Silicon Valley Tea Party, the Great Linux Revolt of > > '98, and other Bay Area Linux PR events. > > _________________________________________________________________ > > > > Copyright (C) 2000 by Rick Moen, rick-at-linuxmafia.com. > > Article first appeared in LinuxWorld.com > > > >
--001636c5b541ebf598046fba54cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That might be the least effective slogan I have ever heard. "> -------------------------------------------------- Simon Fondrie-T= eitler --------------------------------------------------
On Mon, Jul 27, 2009 at 9:22 PM, Joshua = Zeidner <jjzeid= ner-at-gmail.com> wrote: yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex= ; padding-left: 1ex;">
=C2=A0anyone hear this latest anti-OSS management mantra?
=C2=A0"Open Source: free as in kittens."
=C2=A0-jmz
On Sun, Jul 26, 2009 at 1:48 PM, Contrarian< .net">adrba-at-nyct.net> wrote: > > The text at the link I just sent > > Eric Raymond's tips for effective open source advocacy > > =C2=A0 by Rick Moen > > =C2=A0 If anyone is qualified to tell us how to effectively lobby for = the > =C2=A0 wider adoption of open-source software, it's Eric S. Raymon= d. After > =C2=A0 being propelled -- much to his surprise -- to sudden global pro= minence > =C2=A0 in 1998 through his involvement in inspiring and launching the = Mozilla > =C2=A0 Project, Raymond found himself the de facto spokesman for an en= tire > =C2=A0 movement, observed that he was fairly good about it, and so set= about > =C2=A0 explaining how and why. He briefed a large audience at the rece= nt > =C2=A0 LinuxWorld Conference & Expo on these happenings, and on ho= w the rest > =C2=A0 of us might do likewise, in a talk entitled "Meme Hacking = for Fun and > =C2=A0 Profit." > > =C2=A0 Eric's first step was to figure out why the 1998 effort sud= denly > =C2=A0 worked, making business interested in our community's softw= are model, > =C2=A0 after nearly two decades of entirely futile attempts. It wasn= 39;t easy. > > =C2=A0 In May of 1997, Eric published an essay, "The Cathedral an= d the > =C2=A0 Bazaar" (CatB), explaining his theories of how free softwa= re (the only > =C2=A0 term for it, then) gets created, and why the process creates su= ch good > =C2=A0 software so quickly, based on his experience managing a piece o= f > =C2=A0 utility software called Fetchmail (see Resources). This > =C2=A0 socio-technical analysis, while written to be accessible to a r> > =C2=A0 nontechnical audience, succeeded only in generating acclaim amo= ng
> =C2=A0 propeller-beanie Linux users -- preaching to the choir. Eric re= mained
> =C2=A0 better known as Guy Steele's successor in editing the MIT J= argon File,
> =C2=A0 one of the cornerstones of "hackish" (computer progra= mmer) culture,
> =C2=A0 and as mastermind of the shadowy, tongue-in-cheek (or so They w= ould
> =C2=A0 have us think) Eric Conspiracy -- until January 23, 1998.
>
> =C2=A0 That morning, Eric received an emailed tip from a friend, sugge= sting
> =C2=A0 he look at the prior day's announcement from Netscape, and = cryptically
> =C2=A0 commenting "I think someone's been reading your paper.= " And so Eric
> =C2=A0 did -- and was thunderstruck by the fact that a major corporati= on
> =C2=A0 seemed to be implementing his software-management ideas. Indeed= , many
> =C2=A0 parts of the announcement seemed to be quoting CatB directly.r> >
> =C2=A0 He cold-called Netscape Communications Corporation's main t= elephone
> =C2=A0 number, working through a bureaucratic maze for fifteen minutes= ,
> =C2=A0 seeming to reach a dead end at a voicemail mailbox. His bewilde= red
> =C2=A0 message went something like, "Hello, my name is Eric Raymo= nd, and I
> =C2=A0 think I had something to do with your announcement. Could someb= ody
> =C2=A0 please call me?" Within the hour, Roseanne Cino of Netscap= e Marketing
> =C2=A0 called back, saying, "Yes, all of our top people read your= paper and
> =C2=A0 loved it. Jim Barksdale is giving your name to the national pre= ss, and
> =C2=A0 wants to meet you."
>
> =C2=A0 As Eric says, "This was the moment of vindication our trib= e had been
> =C2=A0 waiting for for twenty years." During all that time, ther> > =C2=A0 technical/Unix community had received essentially nothing butr> > =C2=A0 brushoffs, being considered impractical freaks in sandals, even= though
> =C2=A0 it offered clearly better technology. It was clear that the pro= blem
> =C2=A0 was not one of substance, but of perception, and Eric saw that = Mozilla
> =C2=A0 was our key to changing that.
>
> =C2=A0 We'd never had a success before, and a procedural analysis = of the
> =C2=A0 traditional Unix evangelism strategy, typically carried out by<= br> > =C2=A0 software engineers within their own companies, showed why. In a= such a
> =C2=A0 situation, you typically would:
> =C2=A0 =C2=A01. Become excited by some great technology, and become im= pressed by
> =C2=A0 =C2=A0 =C2=A0 its potential to change the world for the better.=
> =C2=A0 =C2=A02. Talk it up to your peers.
> =C2=A0 =C2=A03. Join your peers in approaching the next level of manag= ement,
> =C2=A0 =C2=A0 =C2=A0 trying to get them excited, and hope that the exc= itement trickles
> =C2=A0 =C2=A0 =C2=A0 upward until it reaches the top and changes compa= ny policies.
> =C2=A0 =C2=A04. Sit back and wait for the people at the top to clap th= eir hands to
> =C2=A0 =C2=A0 =C2=A0 their foreheads, and exclaim in a sudden burst of= enlightenment,
> =C2=A0 =C2=A0 =C2=A0 "Gosh, we were wrong all along! But we'l= l change our fundamental
> =C2=A0 =C2=A0 =C2=A0 policies and fix everything!"
>
> =C2=A0 Enlightenment doesn't flow uphill
>
> =C2=A0 Of course, real authority hierarchies don't work that way. = Instead,
> =C2=A0 you have, in rough terms, three strata.
> =C2=A0 =C2=A0 * Decision-makers inhabit the top of the hierarchy.
> =C2=A0 =C2=A0 * Below them are the middle managers, whose job is to be= conservers
> =C2=A0 =C2=A0 =C2=A0 of organisational stability. When asked to change= company
> =C2=A0 =C2=A0 =C2=A0 policies, their job is to say "no."
> =C2=A0 =C2=A0 * At the bottom are the implementers. This is where dwel= l the
> =C2=A0 =C2=A0 =C2=A0 Unix-loving engineering staff.
>
> =C2=A0 The traditional strategy fails because it hits the purposely > > =C2=A0 granite-hard wall of middle management, and advocates of open s= ource
> =C2=A0 software will wait until Doomsday trying to work past them. And= until
> =C2=A0 1998, that's exactly what they were doing.
>
> =C2=A0 Mozilla gave us an example to point to, but also material to le= arn
> =C2=A0 from: in that case, enlightenment did not trickle up from below= . One
> =C2=A0 guy at the top (Jim Clark) encountered a persuasive essay, had = a
> =C2=A0 moment of enlightenment, and enforced his new vision on everyon= e
> =C2=A0 beneath him.
>
> =C2=A0 Clark was convinced, not by moral suasion, but by CatB's pr= agmatic
> =C2=A0 analysis showing why free software yielded shorter time to deli= very,
> =C2=A0 better code quality, and lower costs.
>
> =C2=A0 Ambassador to the suits
>
> =C2=A0 Eric could see that the Mozilla code release would be a crucial=
> =C2=A0 moment, which could yield any of several alternative outcomes:<= br> > =C2=A0 =C2=A0 * Mozilla could succeed, demonstrating open source's= benefits.
> =C2=A0 =C2=A0 * Mozilla could succeed, but in a way that made it appea= r to be a
> =C2=A0 =C2=A0 =C2=A0 one-time, freak case.
> =C2=A0 =C2=A0 * Mozilla might be perceived as having failed, and then = become the
> =C2=A0 =C2=A0 =C2=A0 standard reason cited in business circles for not= trying again.
>
> =C2=A0 He decided that he could help ensure the first outcome by worki= ng out
> =C2=A0 a credible, coherent explanation of the open source model and i= ts
> =C2=A0 benefits that would be amenable to the right sort of audience. = That
> =C2=A0 target audience would be precisely the one ignored by prior adv= ocates:
> =C2=A0 Fortune 500 chief executive officers.
>
> =C2=A0 This is easier said than done. As Eric puts it, "Most of u= s don't play
> =C2=A0 golf with Jack Welsh [longtime CEO of General Electric]. We nee= d some
> =C2=A0 other way to slip our LSD in their water supply."
>
> =C2=A0 Thus, Eric figured, our best bet is a media-centered campaign a= imed at
> =C2=A0 Fortune 500 CEOs. It might seem at first glance that entreprene= urs
> =C2=A0 would be a better bet, but the Fortune 500 are the biggest, mos= t
> =C2=A0 influential market that can be reached by a single marketing ca= mpaign.
> =C2=A0 He decided to concentrate exclusively on the following news out= lets:
> =C2=A0 the New York Times, the Wall Street Journal, Forbes, Barron'= ;s, and the
> =C2=A0 Economist.
>
> =C2=A0 This list pointedly excludes technical journals, since the peop= le we
> =C2=A0 need to reach don't read them, but leave that task to under= lings. Eric
> =C2=A0 cited what he called Rule Number One of Marketing: "Appeal= to the
> =C2=A0 prospect's interests and values, not to yours." If the= smarter, more
> =C2=A0 forward-looking CEOs were convinced to come aboard, the others = would
> =C2=A0 tend to follow.
>
> =C2=A0 The sales pitch
>
> =C2=A0 The term "open source," coined by Chris Peterson of t= he Foresight
> =C2=A0 Institute at a strategy session Eric attended in February 1998 = after
> =C2=A0 the Netscape announcement, followed naturally from this logic. = Eric
> =C2=A0 feels that the traditional term, "free software," had= been a millstone
> =C2=A0 around all of our necks, and was simply a nonstarter as rhetori= c to
> =C2=A0 convince any but the hard-core believers. From the businessman&= #39;s
> =C2=A0 perspective, "free software" sounds at best ambiguous= , or possibly
> =C2=A0 even threatening: you must explain which meaning of "free&= quot; you intend
> =C2=A0 (free as in speech, rather than free as in beer), and then clar= ify
> =C2=A0 what free speech has to do with software. Your audience might r= eact,
> =C2=A0 "Free? That sounds cheap, shoddy." Or, worse, "F= ree? That sounds like
> =C2=A0 communism."
>
> =C2=A0 It's much more effective to sell the concept on the basis o= f
> =C2=A0 reliability, instead. Big corporations lose millions of dollars= per
> =C2=A0 hour when their datacenters go down. Executives are keenly inte= rested
> =C2=A0 in avoiding that.
>
> =C2=A0 Also, even concerning their desktop boxes, executives are aware= of the
> =C2=A0 money drain. Mean time before failure (MTBF) of Windows 9x is l= ess
> =C2=A0 than a week. As an installation ages, that shrinks to less than= a day.
> =C2=A0 With Linux, a box left alone has MTBF of around two years.
>
> =C2=A0 Your winning points will be:
> =C2=A0 =C2=A0 * Total cost of ownership (TCO)
> =C2=A0 =C2=A0 * Insulation from risk and loss of control
>
> =C2=A0 An executive who allows his company to becomes dependent on sof= tware
> =C2=A0 he is not allowed to see inside, let alone change, has lost con= trol of
> =C2=A0 his business, and is on the wrong side of a monopoly relationsh= ip with
> =C2=A0 a vendor who can thereby control his business. With open source= , the
> =C2=A0 executive is in control, and nobody can take that away. The
> =C2=A0 opportunity to reduce and control business risk is a key concer= n of
> =C2=A0 any CEO. You'll be listened to.
>
> =C2=A0 Eric warned that none of this will work without purging one'= ;s mind of
> =C2=A0 the common techophile's notion that business people are stu= pid. Eric
> =C2=A0 characterised them as "differently optimised," and sa= id that we should
> =C2=A0 respect them for their specialty. For one thing, you cannot sel= l to
> =C2=A0 people if you project an attitude of disrespect. Even if you do= n't
> =C2=A0 express it explicitly, it will come through in body language,r> > =C2=A0 intonation, and other subtle aspects of your demeanour.
>
> =C2=A0 Of course, it probably seems reckless to approach one's com= pany CEO
> =C2=A0 and advocate changing company policies, and it may well be so. = It's
> =C2=A0 usually more successful to work on other people's organisat= ions, since
> =C2=A0 companies seem oddly resistant to listening to their own techni= cal
> =C2=A0 people. Also, partially because most executives will be less in= clined
> =C2=A0 than Jim Clark to read long essays on the Web, Eric has publish= ed "The
> =C2=A0 Cathedral and the Bazaar" as part of a book of the same na= me,
> =C2=A0 available from O'Reilly, suitable for leaving as anonymous = gifts on
> =C2=A0 executive desks.
>
> =C2=A0 Dress to persuade
>
> =C2=A0 Eric himself tries to adopt the Prince from Another Country sta= nce, a
> =C2=A0 term coined by science-fiction writer Norman Spinrad to describ= e his
> =C2=A0 technique for being accepted in multiple communities: You adopt= the
> =C2=A0 attitude of being a high-ranking member of a different hierarch= y,
> =C2=A0 which gets you respect without subjecting you to hierarchicalr> > =C2=A0 obligations. Thus, when Spinrad was trying to gain respect inr> > =C2=A0 Hollywood as a scriptwriter, he conducted himself as a respecte= d
> =C2=A0 science fiction author. Conversely, in the science fiction comm= unity,
> =C2=A0 he billed himself as a leading Hollywood scriptwriter.
>
> =C2=A0 Following in the same mold, Eric dresses well but casually, and=
> =C2=A0 donates his time as a speaker on open source, rather than billi= ng it
> =C2=A0 as consulting time. Dressing "well" includes good sho= es, meaning, in
> =C2=A0 Eric's case, $90 Rockport walking shoes rather than beat-up= Reeboks.
> =C2=A0 He generally combines these with a neat polo shirt and slacks.<= br> >
> =C2=A0 Don't dress like a hacker, Eric warns. Dress the way hacker= s do in the
> =C2=A0 movies. You want to look like a credible, respected member of a=
> =C2=A0 foreign social system to an audience of executives who've n= ever come
> =C2=A0 closer to a real hacker than a Sandra Bullock movie. Therefore,=
> =C2=A0 "Birkenstocks are right out!"
>
> =C2=A0 Even worse than underdressing, as a strategy for being credible= to
> =C2=A0 executives, would be overdressing. A technology advocate dresse= d in a
> =C2=A0 business suit would tend to come across as a bad imitation of a=
> =C2=A0 business person -- and thus a person to ignore. It's far sa= fer to
> =C2=A0 stick to neat, good-fabric casual wear.
>
> =C2=A0 Amy Abascal, head of the Web development team at VA Linux Syste= ms,
> =C2=A0 interjected, "But what should the technical woman wear?&qu= ot; I had a brief
> =C2=A0 moment of lurid anticipation that Eric might recommend that she=
> =C2=A0 emulate Carrie-Anne Moss. The daydream passed, and Eric quite r= ightly
> =C2=A0 pointed out that the high-quality black casual wear Amy was wea= ring
> =C2=A0 would serve perfectly.
>
> =C2=A0 Local Linux user and magazine columnist Mae Ling Mak shouted ou= t, "But
> =C2=A0 what about me?" Eric gazed at Mae Ling's black vinyl c= heongsam and
> =C2=A0 replied, "Mae Ling, you're a law unto yourself. Never = change a thing."
>
> =C2=A0 The other sales front
>
> =C2=A0 Eric anticipated that his other task would be equally tough: > > =C2=A0 convincing free-software advocates to change their rhetoric whe= n
> =C2=A0 speaking to business. The Open Source Initiative was founded in=
> =C2=A0 February 1998 towards that end, with Eric and fellow OSI direct= or
> =C2=A0 Bruce Perens advocating the new approach among traditional
> =C2=A0 free-software advocates.
>
> =C2=A0 To their utter astonishment, they observed 85 percent of the co= mmunity
> =C2=A0 switching the wording on its Web sites within six weeks, sugges= ting
> =C2=A0 pent-up demand in the community for a more effective, less
> =C2=A0 confrontational approach. Some organs of the press that used to= carry
> =C2=A0 what Eric termed "condescending, snarky pieces about free = software"
> =C2=A0 fell over themselves to speak glowingly of open source.
>
> =C2=A0 Talking to the press
>
> =C2=A0 Eric's strategy for getting his views across in the press (= "press
> =C2=A0 manipulation," he freely admits) relies on knowing that mo= st people
> =C2=A0 are asleep most of the time. It's impossible to keep your a= udience
> =C2=A0 awake. Therefore, you keep a good stock of attention-getting so= und
> =C2=A0 bites in reserve, and zap the reporter with them at well-spaced=
> =C2=A0 intervals. The theory, which Eric claims works quite reliably, = is that
> =C2=A0 the reporter will remember the sound bites, reproducing them as= the
> =C2=A0 backbone of his coverage, and discard the parts he half-dozed t= hrough.
> =C2=A0 (This reporter found the suggestion about as annoying as the wr= ist
> =C2=A0 cramp from his nine pages of lecture notes, but concedes the po= int may
> =C2=A0 be more correct than not. Eric stoked some of our egos a bit by= saying
> =C2=A0 that technology reporters tended to be way ahead of that curve = on
> =C2=A0 account of the same hackish traits that got them into that fiel= d in
> =C2=A0 the first place. Sorry, no kind words for technology readers.)<= br> >
> =C2=A0 The other side of the coin
>
> =C2=A0 One member of the audience asked how corporations should approa= ch
> =C2=A0 relations with the open source community. It's the same pro= blem as
> =C2=A0 before, just from the other side: "Appeal to the prospect&= #39;s interests
> =C2=A0 and values, not to yours." Once more, if anyone is qualifi= ed to
> =C2=A0 address this point, it's Eric.
> =C2=A0 =C2=A0 * Never lie to geeks. They take it seriously. Most gener= al members
> =C2=A0 =C2=A0 =C2=A0 of the public expect casual prevarication and eva= sion, but
> =C2=A0 =C2=A0 =C2=A0 technical activists notice it and are offended.r> > =C2=A0 =C2=A0 * Respect community customs. In particular, respect the = community's
> =C2=A0 =C2=A0 =C2=A0 software licences. Don't write your own and e= xpect to be greeted
> =C2=A0 =C2=A0 =C2=A0 with open arms.
> =C2=A0 =C2=A0 * Value your own internal experts. The community doesn= 39;t like
> =C2=A0 =C2=A0 =C2=A0 dealing with faceless organisations, and prefers = one-on-one
> =C2=A0 =C2=A0 =C2=A0 "horizontal" dealings with individuals.= Therefore, identify your
> =C2=A0 =C2=A0 =C2=A0 own people who are likely contacts with the commu= nity -- who may
> =C2=A0 =C2=A0 =C2=A0 already be part of it without your being aware of= it -- and
> =C2=A0 =C2=A0 =C2=A0 burnish their presence and potential as spokesper= sons.
> =C2=A0 =C2=A0 * Give the community members toys; you'll make them = happy.
>
> =C2=A0 But seriously, folks
>
> =C2=A0 As a bit of parting advice, Eric suggested that the most valuab= le
> =C2=A0 skill to pick up is that of effective public speaking. There ar= e a
> =C2=A0 variety of groups that aim to teach it, but Eric found his mode= l in
> =C2=A0 what at first might seem an unlikely place: stand-up comedy, wh= ich he
> =C2=A0 says can be effectively studied for tips on timing, punctuation= , and
> =C2=A0 body language, among other things.
>
> =C2=A0 Eric is an animated and extroverted speaker, with a flair for r= eaching
> =C2=A0 out to audiences, and a whimsical sense of fun -- but conceptua= lising
> =C2=A0 him as a Robin Williams or Mike Myers puts him in a new light.<= br> >
> =C2=A0 Me: Maybe I'd be a reporter.
> =C2=A0 Eric: An evil reporter?
> =C2=A0 Me: You always do that!
>
> =C2=A0 Resources
> =C2=A0 =C2=A0 * The Fetchmail utility:
> =C2=A0 =C2=A0 =C2=A0 /" target=3D"_blank">http://www.tuxedo.org/~esr/fetchmail/
> =C2=A0 =C2=A0 * "The Cathedral and the Bazaar," Eric S. Raym= ond:
> =C2=A0 =C2=A0 =C2=A0 cathedral-bazaar/" target=3D"_blank">http://www.tuxedo.org/~esr/writings/ca= thedral-bazaar/
> =C2=A0 =C2=A0 * The Jargon File, aka the New Hacker's Dictionary:<= br> > =C2=A0 =C2=A0 =C2=A0 target=3D"_blank">http://www.tuxedo.org/~esr/jargon/
> =C2=A0 =C2=A0 * Eric Conspiracy Secret Labs:
> =C2=A0 =C2=A0 =C2=A0 rget=3D"_blank">http://www.tuxedo.org/~esr/ecsl/
> =C2=A0 =C2=A0 * Netscape's announcement of the planned source code= release:
> =C2=A0 =C2=A0 =C2=A0 wsrelease558.html" target=3D"_blank">http://home.netscape.com/newsref/pr/ne= wsrelease558.html
> =C2=A0 =C2=A0 * The Cathedral and the Bazaar: Musings on Linux and Ope= n Source by
> =C2=A0 =C2=A0 =C2=A0 an Accidental Revolutionary, Eric S. Raymond (O= 39;Reilly and
> =C2=A0 =C2=A0 =C2=A0 Associates, 1999):
> =C2=A0 =C2=A0 =C2=A0 rget=3D"_blank">http://www.oreilly.com/catalog/cb/
>
> =C2=A0 Rick Moen is a recovering system administrator in the San Franc= isco
> =C2=A0 Bay Area, who served as primary Bay Area organiser for Windows = Refund
> =C2=A0 Day, and has been one of the main troublemakers behind Silicon = Valley
> =C2=A0 Linux User Group's Silicon Valley Tea Party, the Great Linu= x Revolt of
> =C2=A0 '98, and other Bay Area Linux PR events.
> =C2=A0 =C2=A0 ________________________________________________________= _________
>
> =C2=A0 Copyright (C) 2000 by Rick Moen, fia.com">rick-at-linuxmafia.com.
> =C2=A0 Article first appeared in LinuxWorld.com
>
--001636c5b541ebf598046fba54cf--
|
|