<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 23 May 2012 12:48:11 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Davey Shafik's Blog: Karma-Based Mailing Lists (or: how to automate a meritocracy)]]></title>
      <guid>http://www.phpdeveloper.org/news/12785</guid>
      <link>http://www.phpdeveloper.org/news/12785</link>
      <description><![CDATA[<p>
In <a href="http://daveyshafik.com/archives/686-karma-based-mailing-lists-or-how-to-automate-a-meritocracy.html">this new post</a> to his blog <i>Davey Shafik</i> looks at a problem plaguing several mailing lists out there (including some of the PHP ones) - that they're a "free for all". What's his solution to help it? Karma.
</p>
<blockquote>
In the real world, communications pass through a hierarchy of people, escalating as necessary, passing from person to person up the chain. This means that, given enough time, any mailing list starts to have a large noise:signal ratio, at least for any given person's take on the list; they want to read what they want to read, and don't need to be distracted ignoring the stuff they don't want to read.
</blockquote>
<p>
His <a href="http://daveyshafik.com/archives/686-karma-based-mailing-lists-or-how-to-automate-a-meritocracy.html">solution</a> involves defining a hierarchy for the lists and the karma attached to them (based on user CVS level or a timescale or other measurement) to allow the "more interesting" things to filter back up to the correct places. His examples use some of the PHP lists as a sample structure. 
</p>]]></description>
      <pubDate>Tue, 30 Jun 2009 13:30:53 -0500</pubDate>
    </item>
  </channel>
</rss>

