<?xml version="1.0" encoding="iso-8859-1"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">Joseph Reagle</title>
<subtitle type="html"><![CDATA[
Open Communities, Media, Source, and Standards
]]></subtitle>
<id>http://reagle.org/joseph/blog/social/wikipedia/how-communities-work-well</id>
<link rel="alternate" type="text/html" href="http://reagle.org/joseph/blog" />
<link rel="self" type="application/atom+xml" href="http://reagle.org/joseph/blog/social/wikipedia/how-communities-work-well?flav=atom" />


<author>
<name>Joseph Reagle</name>
<uri>http://reagle.org/joseph/blog/social/wikipedia/how-communities-work-well</uri>
<email></email>
</author>
<rights>Copyright 2003-2010 Joseph Reagle</rights>
<generator uri="http://pyblosxom.sourceforge.net/" version="1.4.3 01/10/2008">
PyBlosxom http://pyblosxom.sourceforge.net/ 1.4.3 01/10/2008
</generator>

<updated>2006-08-23T13:59:28Z</updated>
<!-- icon?  logo?  -->

<entry>
<title type="html">How online communities work well</title>
<category term="" />
<id>http://reagle.org/joseph/blog/2006/08/23/how-communities-work-well</id>
<updated>2006-08-23T13:59:28Z</updated>
<published>2006-08-23T13:59:28Z</published>
<link rel="alternate" type="text/html" href="http://reagle.org/joseph/blog/social/wikipedia/how-communities-work-well.html" />
<content type="html">

&lt;p&gt;In 1999, while I was a fellow at the Berkman Center, I wrote a paper on &lt;a
href=&quot;http://cyber.law.harvard.edu/people/reagle/regulation-19990326.html#_Native&quot;&gt;Why
the Internet is Good&lt;/a&gt;; in it, I noted 10 factors in Internet community
policy formation (e.g., IETF) that contribute to their success. When I
consider other open content communities I still find this framework to be
useful, even in the case of the Wikipedia.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;p&gt;Open Participation: IETF (mostly), WP (more so).&lt;/p&gt;
    &lt;p&gt;No one is really excluded from the IETF, but you do have to pay the
    meeting attendance fee and have the interest in this sort of technical
    subject. Nearly any literate person might have an interest in the
    Wikipedia.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;No Kings, but Elders?: IETF (mostly), WP (slightly less so).&lt;/p&gt;
    &lt;p&gt;Both the IETF and the Wikipedia have meritocratic governance
    structures, which I now call &lt;a
    href=&quot;http://reagle.org/joseph/2005/ethno/leadership.html#heading12&quot;&gt;paramount
    leadership&lt;/a&gt;. I think the main difference here is that many Wikipedians
    can live very happily without ever encountering questions of governance;
    they can work on their own particular interests and make substantive
    contributions as they are. At the IETF, everyone is striving for a single
    standard.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Consensus and Competitive Scaling: IETF (partly), WP (partly).&lt;/p&gt;
    &lt;p&gt;In my 1999 essay I speak about the difficulties of consensus scaling
    but note it can work when combined with many of the later factors: &quot;This
    is because of competitive scaling: a small group of people get to produce
    their best work under consensus, and then compete, coordinate, cooperate,
    and learn with other groups.&quot; In the standards arena it is possible for
    small groups of people to work on informally competing specifications,
    and let the best one win. (I talk further about this in &lt;a
    href=&quot;http://goatee.net/2003/07.html#_02we-a&quot;&gt;design by committee&lt;/a&gt; and
    the possibilities of red/blue team design.)&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Implementation and Enforcement: IETF (mostly), WP (not really).&lt;/p&gt;
    &lt;p&gt;At the Wikipedia it can be difficult to dispassionately test whether a
    given policy is unambiguously better than another policy. In the
    technical domain one has the capability to implement alternatives and see
    whether they work.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Limitation of Scope: IETF (yes), WP (yes).&lt;/p&gt;
    &lt;p&gt;Just as &quot;a Working Group to be extremely rigorous in defining and
    enforcing the scope of its activity&quot; the Wikipedia community has been
    strict in specifying what their mission is, an Encyclopedia, and what it
    is not.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Funded Mandates and Lack of Fiat: IETF (mostly), WP (mostly).&lt;/p&gt;
    &lt;p&gt;&quot;The implementation and operational use of a technical policy
    demonstrate an interest and ability to deploy the policy at large.&quot;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Uniform Enforcement: IETF (mostly), WP (mostly).&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Descriptive Policy: IETF (mostly), WP (mostly).&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Policy Deprecation: IETF (partly), WP (not much).&lt;/p&gt;
    &lt;p&gt;&quot;It is useful for a policy that is no longer in operation to be
    stricken from the books; it simplifies the understanding one must have
    about one&apos;s regulatory environment.&quot; This is basically Shirky&apos;s
    observation about the formation of policy.&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;p&gt;Metrics: IETF (mostly), WP (less so).&lt;/p&gt;
    &lt;p&gt;This is tied to the implementation issue, but in the technical domain
    it can be very nice to know that a particular algorithm works 20% faster
    than the old way of doing things. The realm of natural language and human
    meaning is less amenable to these types of metrics.&lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;
</content>
</entry>
</feed>
