/tmp/policy.html
text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <!--Converted with LaTeX2HTML 98.1p1 release (March 2nd, 1998) originally by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds * revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan * with significant contributions from: Jens Lippmann, Marek Rouchal, Martin Wilck and others --> <HTML> <HEAD> <TITLE>The Behavior of Open-Source Support Companies</TITLE> <META NAME="description" CONTENT="The Behavior of Open-Source Support Companies"> <META NAME="keywords" CONTENT="26405"> <META NAME="resource-type" CONTENT="document"> <META NAME="distribution" CONTENT="global"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <LINK REL="STYLESHEET" HREF="26405.css"> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#FF0000" VLINK="#A00000" ALINK="#0000FF"> <P> <P> <P> <H1 ALIGN="CENTER">The Behavior of Open-Source <BR> Support Companies</H1> <P ALIGN="CENTER"><STRONG>Bruce Momjian</STRONG></P> <P ALIGN="LEFT"></P> <P><B>DRAFT</B> <P> <P> <H1><A NAME="SECTION00010000000000000000"> Introduction</A> </H1> <P> Open-source support companies face unique challenges. This article explores a few of them: <P> <UL> <LI>The unusual inter-company issues faced by open-source support companies. <LI>The paradox of why, sometimes, doing the best for your company may be the wrong thing to do. <LI>Why companies should work together to preserve their shared open-source asset. </UL> <P> <H1><A NAME="SECTION00020000000000000000"> Open-Source As a Shared Resource</A> </H1> <P> Traditional companies have their own marketing, sales, research/development, and manufacturing departments. They are self-contained organizations that share very little with other companies in the same market. <P> Open-source support companies are different. The open-source software they support is a <EM>shared resource.</EM> All support companies rely on the health of that shared resource for their livelihood, and because they rely on it, companies take actions to maximize the value they derive from that shared resource. However, these actions can make things worse. <P> <H1><A NAME="SECTION00030000000000000000"> Self-interest and Non-optimal Results -- The Prisoner's Dilemma</A> </H1> <P> How can acting in your self-interest actually be counter to your self-interest? The <EM>prisoner's dilemma</EM> illustrates such a case. Two prisoners are captured by police and placed in separate cells. The police have enough evidence to convict each of a minor crime that will result in a one-year prison term. However, the police know the prisoners have committed a more serious crime. Each prisoner is told that if he confesses and the other prisoner does not confess, he will go free, and the other will receive a twenty-year prison term. If they both confess, they will each receive a ten years prison term. <P> For each prisoner, the decision in their self-interest is to confess<EM>.</EM> Each prisoner does not know what the other will do. However, confessing produces better results no matter what the other prisoner does: <P> <UL> <LI>``Suppose the other prisoner confesses. If I confess too, I get ten years instead of twenty.'' <LI>``Suppose the other prisoner does <EM>not</EM> confess. If I confess, I go free instead of serving one year in jail.'' </UL>The interesting effect of the prisoner's dilemma is that each prisoner, acting in their own self-interest, produces a worse result, two ten-year jail terms, than if both had not confessed and gotten only one-year jail terms. <P> The prisoner's dilemma, first formulated by Albert W. Tucker in the 1950s, has been applied to many fields, including economics, foreign policy. and philosophy[<A HREF="26405.html#Blumen">Blumen</A>]. The prisoner's dilemma even applies to open-source support companies. Each company is like a prisoner in a cell. Each wants to dominate the open-source community, and fears other companies will do the same. Unfortunately, domination by multiple companies only diminishes the health of the open-source community, yielding a worse result than if they had not acted. <P> Perhaps <EM>dominate</EM> is too strong a word, but companies do position themselves to receive maximum benefit. When all companies do that, they can destroy the shared resource they rely upon. In prisoner's dilemma terms, they receive ten years in jail instead of one. They reason, ``If I dominate the shared resource, and the other companies don't, I win. If they do, and I don't, my business suffers.'' Unfortunately, if they both do, the community suffers, and the companies along with them. <P> <H1><A NAME="SECTION00040000000000000000"> Company Behavior</A> </H1> <P> The good news that the prisoner's dilemma is not played just once. It is played by open-source companies over and over again, in the little and big things they do that affect their shared resource. And with repetition, there is hope. When companies realize how their actions to control the shared resource cause other companies to do the same, an <EM>arms race</EM> occurs. And once they realize that, they can start to seek a truce, where companies respect the shared resource, rather than dominate it at every opportunity. With such cooperation, companies get the maximum benefit, because the shared resource remains healthy and vibrant, and all companies prosper. <P> <H1><A NAME="SECTION00050000000000000000"> Conclusion </A> </H1> <P> This paper describes how open-source software companies can analyze their actions in cases the affect the open-source community. Restraint is often the best practice. Fortunately, 99% of a company actions have no affect on the open-source community, so they can behave just like normal companies, seeking to grow and prosper. <P> <P> <P> <P> <H1 ALIGN="CENTER">The Behavior of Open-Source <BR> Support Companies</H1> <P ALIGN="CENTER"><STRONG>Bruce Momjian</STRONG></P> <P ALIGN="LEFT"></P> <P><B>DRAFT</B> <P> <P> <H1><A NAME="SECTION00070000000000000000"> Introduction</A> </H1> <P> Open-source support companies face unique challenges. This article explores a few of them: <P> <UL> <LI>The unusual inter-company issues faced by open-source support companies. <LI>The paradox of why, sometimes, doing the best for your company may be the wrong thing to do. <LI>Why companies should work together to preserve their shared open-source asset. </UL> <P> <H1><A NAME="SECTION00080000000000000000"> Open-Source As a Shared Resource</A> </H1> <P> Traditional companies have their own marketing, sales, research/development, and manufacturing departments. They are self-contained organizations that share very little with other companies in the same market. <P> Open-source support companies are different. The open-source software they support is a <EM>shared resource.</EM> All support companies rely on the health of that shared resource for their livelihood, and because they rely on it, companies take actions to maximize the value they derive from that shared resource. However, these actions can make things worse. <P> <H1><A NAME="SECTION00090000000000000000"> Self-interest and Non-optimal Results -- The Prisoner's Dilemma</A> </H1> <P> How can acting in your self-interest actually be counter to your self-interest? The <EM>prisoner's dilemma</EM> illustrates such a case. Two prisoners are captured by police and placed in separate cells. The police have enough evidence to convict each of a minor crime that will result in a one-year prison term. However, the police know the prisoners have committed a more serious crime. Each prisoner is told that if he confesses and the other prisoner does not confess, he will go free, and the other will receive a twenty-year prison term. If they both confess, they will each receive a ten years prison term. <P> For each prisoner, the decision in their self-interest is to confess<EM>.</EM> Each prisoner does not know what the other will do. However, confessing produces better results no matter what the other prisoner does: <P> <UL> <LI>``Suppose the other prisoner confesses. If I confess too, I get ten years instead of twenty.'' <LI>``Suppose the other prisoner does <EM>not</EM> confess. If I confess, I go free instead of serving one year in jail.'' </UL>The interesting effect of the prisoner's dilemma is that each prisoner, acting in their own self-interest, produces a worse result, two ten-year jail terms, than if both had not confessed and gotten only one-year jail terms. <P> The prisoner's dilemma, first formulated by Albert W. Tucker in the 1950s, has been applied to many fields, including economics, foreign policy. and philosophy[<A HREF="26405.html#Blumen">Blumen</A>]. The prisoner's dilemma even applies to open-source support companies. Each company is like a prisoner in a cell. Each wants to dominate the open-source community, and fears other companies will do the same. Unfortunately, domination by multiple companies only diminishes the health of the open-source community, yielding a worse result than if they had not acted. <P> Perhaps <EM>dominate</EM> is too strong a word, but companies do position themselves to receive maximum benefit. When all companies do that, they can destroy the shared resource they rely upon. In prisoner's dilemma terms, they receive ten years in jail instead of one. They reason, ``If I dominate the shared resource, and the other companies don't, I win. If they do, and I don't, my business suffers.'' Unfortunately, if they both do, the community suffers, and the companies along with them. <P> <H1><A NAME="SECTION000100000000000000000"> Company Behavior</A> </H1> <P> The good news that the prisoner's dilemma is not played just once. It is played by open-source companies over and over again, in the little and big things they do that affect their shared resource. And with repetition, there is hope. When companies realize how their actions to control the shared resource cause other companies to do the same, an <EM>arms race</EM> occurs. And once they realize that, they can start to seek a truce, where companies respect the shared resource, rather than dominate it at every opportunity. With such cooperation, companies get the maximum benefit, because the shared resource remains healthy and vibrant, and all companies prosper. <P> <H1><A NAME="SECTION000110000000000000000"> Conclusion </A> </H1> <P> This paper describes how open-source software companies can analyze their actions in cases the affect the open-source community. Restraint is often the best practice. Fortunately, 99% of a company actions have no affect on the open-source community, so they can behave just like normal companies, seeking to grow and prosper. <P> <H2><A NAME="SECTIONREF">Bibliography</A> </H2> <DL COMPACT><DD><P></P><DT><A NAME="Axelrod"><STRONG>Axelrod</STRONG></A> <DD>Axelrod, Robert, <EM>The Complexity of Cooperation: Agent-Based Models of Competition and Collaboration,</EM> Princeton University Press, 1997. <P></P><DT><A NAME="Blumen"><STRONG>Blumen</STRONG></A> <DD>Blumen, Jonathan, <EM>The Ethical Spectacle,</EM> <A NAME="tex2html5" HREF="http://www.spectacle.org/995/">http://www.spectacle.org/995/</A>. <P></P><DT><A NAME="Britanica"><STRONG>Britanica</STRONG></A> <DD>Encyclopedia Britanica, <EM><</EM>#54#>``The prisoners' dilemma,'' http://www.britannica.com/bcom/eb/article/5/0,5716,117275+10+109420,00.html?query=prisoners <P></P><DT><A NAME="Helfrich"><STRONG>Helfrich</STRONG></A> <DD>Helfrich, Serge, <EM>The Prisoner's Dilemma,</EM> <A NAME="tex2html7" HREF="http://www.xs4all.nl/ helfrich/prisoner/">http://www.xs4all.nl/ helfrich/prisoner/</A>. <P></P><DT><A NAME="Rawles"><STRONG>Rawles</STRONG></A> <DD>Rawls, John, <EM>A Theory of Justice,</EM> Belknap Press, 1999. </DL><BR> </BODY> </HTML>