<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Welcome to MediaBugs &#8212; getting started</title>
	<atom:link href="http://mediabugs.org/blog/2009/09/04/welcome-to-mediabugs-getting-started/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediabugs.org/blog/2009/09/04/welcome-to-mediabugs-getting-started/</link>
	<description>Fix the news</description>
	<lastBuildDate>Tue, 23 Sep 2014 03:33:05 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: Richard Pauli</title>
		<link>http://mediabugs.org/blog/2009/09/04/welcome-to-mediabugs-getting-started/comment-page-1/#comment-20</link>
		<dc:creator><![CDATA[Richard Pauli]]></dc:creator>
		<pubDate>Fri, 11 Dec 2009 22:59:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediabugs.org/blog/?p=33#comment-20</guid>
		<description><![CDATA[Nice idea.  It may be worthwhile to see how the software industry files bugs.  It is a fascinating structure to development. 

I went to: https://developer.mozilla.org/en/Bug_writing_guidelines
&quot;Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.
    * Be precise
    * Be clear - explain it so others can reproduce the bug
    * One bug per report
    * No bug is too trivial to report - small bugs may hide big bugs
    * Clearly separate fact from speculation&quot;

================
It is also interesting to hear that bugs are marked as either open, closed or &quot;will not fix&quot;.

I like this idea.   It will be interesting to see how news media regard this effort.]]></description>
		<content:encoded><![CDATA[<p>Nice idea.  It may be worthwhile to see how the software industry files bugs.  It is a fascinating structure to development. </p>
<p>I went to: <a href="https://developer.mozilla.org/en/Bug_writing_guidelines" rel="nofollow">https://developer.mozilla.org/en/Bug_writing_guidelines</a><br />
&#8220;Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.<br />
    * Be precise<br />
    * Be clear &#8211; explain it so others can reproduce the bug<br />
    * One bug per report<br />
    * No bug is too trivial to report &#8211; small bugs may hide big bugs<br />
    * Clearly separate fact from speculation&#8221;</p>
<p>================<br />
It is also interesting to hear that bugs are marked as either open, closed or &#8220;will not fix&#8221;.</p>
<p>I like this idea.   It will be interesting to see how news media regard this effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
