<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: issuetracking</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/issuetracking.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-03-25T20:09:53+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Michal Migurski</title><link href="https://simonwillison.net/2010/Mar/25/issues/#atom-tag" rel="alternate"/><published>2010-03-25T20:09:53+00:00</published><updated>2010-03-25T20:09:53+00:00</updated><id>https://simonwillison.net/2010/Mar/25/issues/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://www.iamcal.com/issue-tracking/#comment1188"&gt;&lt;p&gt;We've got a rule of thumb inside Stamen that issue names must read like imperatives: "improve variable names", "delete blah functionality", "fix broken jimmy-jammers", etc. Nothing focuses the mind of the reporter like being asked to specify what exactly they'd like to see done, and it's much easier for a developer to scan a list with actual tasks right in the sentence construction.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.iamcal.com/issue-tracking/#comment1188"&gt;Michal Migurski&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bugs"&gt;bugs&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/bugtracking"&gt;bugtracking&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/issuetracking"&gt;issuetracking&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/michal-migurski"&gt;michal-migurski&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/stamen-design"&gt;stamen-design&lt;/a&gt;&lt;/p&gt;



</summary><category term="bugs"/><category term="bugtracking"/><category term="issuetracking"/><category term="michal-migurski"/><category term="stamen-design"/></entry></feed>