<?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: Improving Launchpad Bug Workflow for Opportunistic Programmers</title>
	<atom:link href="http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/</link>
	<description>David Siegel</description>
	<lastBuildDate>Wed, 08 Sep 2010 16:29:35 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bram Bonné</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2247</link>
		<dc:creator>Bram Bonné</dc:creator>
		<pubDate>Wed, 26 May 2010 17:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2247</guid>
		<description>This is an awesome idea. Ground Control [1] could probably be used as a means of getting the original source and publishing the modified source from/to launchpad.

I love the fact that seemingly the launchpad devs are already working on this kind of thing :)

[1] http://ground-control.org/</description>
		<content:encoded><![CDATA[<p>This is an awesome idea. Ground Control [1] could probably be used as a means of getting the original source and publishing the modified source from/to launchpad.</p>
<p>I love the fact that seemingly the launchpad devs are already working on this kind of thing :)</p>
<p>[1] <a href="http://ground-control.org/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/ground-control.org/?referer=');">http://ground-control.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liz</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2034</link>
		<dc:creator>Liz</dc:creator>
		<pubDate>Fri, 05 Feb 2010 06:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2034</guid>
		<description>I like the idea.

And your browser could have a little button that&#039;s a count box of quick fix bugs so that you feel motivated to bring down the total count.

But by the time anyone&#039;s triaged a bug enough to figure out if it&#039;s quick to fix and could go in this category, they might have a hard time not just fixing it then and there.</description>
		<content:encoded><![CDATA[<p>I like the idea.</p>
<p>And your browser could have a little button that&#8217;s a count box of quick fix bugs so that you feel motivated to bring down the total count.</p>
<p>But by the time anyone&#8217;s triaged a bug enough to figure out if it&#8217;s quick to fix and could go in this category, they might have a hard time not just fixing it then and there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stoffe</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2031</link>
		<dc:creator>Stoffe</dc:creator>
		<pubDate>Sun, 31 Jan 2010 18:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2031</guid>
		<description>Amazing idea.</description>
		<content:encoded><![CDATA[<p>Amazing idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebz</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2026</link>
		<dc:creator>Sebz</dc:creator>
		<pubDate>Wed, 27 Jan 2010 20:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2026</guid>
		<description>Hi David, nice user story. 
I&#039;m an eclipse plugin developer and your use case is &quot;almost&quot;  what I&#039;m doing every day. 
Did you hear about Mylyn (http://www.eclipse.org/mylyn/) ?

Basically it let you manage your issues/bugs/tasks within eclipse, and creates a context with every modified resources during the time working on the bug. This context is automatically attached to the bug when you close it. It is also integrated with VCS and automatically creates a commit message. 

Maybe all you need is a Mylyn Connector for Launchpad.


My 2 cents.</description>
		<content:encoded><![CDATA[<p>Hi David, nice user story.<br />
I&#8217;m an eclipse plugin developer and your use case is &#8220;almost&#8221;  what I&#8217;m doing every day.<br />
Did you hear about Mylyn (<a href="http://www.eclipse.org/mylyn/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.eclipse.org/mylyn/?referer=');">http://www.eclipse.org/mylyn/</a>) ?</p>
<p>Basically it let you manage your issues/bugs/tasks within eclipse, and creates a context with every modified resources during the time working on the bug. This context is automatically attached to the bug when you close it. It is also integrated with VCS and automatically creates a commit message. </p>
<p>Maybe all you need is a Mylyn Connector for Launchpad.</p>
<p>My 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2024</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 27 Jan 2010 02:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2024</guid>
		<description>@Luis I encourage no such thing. Furthermore, Ubuntu is catagorically in favor of pushing any patches submitted to Launchpad upstream.

@Sandy Yeah, we might need to use a VM. Maybe have a root VM image that gets forked and preped to build each package. &quot;Quickly fixing&quot; a bug in a package like Nautilus could make testing tricky.

@Christoph That sounds insane! I bet that would require a lot more work, though.

@Bruce *No, only patches the Ubuntu community is producing and posting to Launchpad. We&#039;re writing patches, applying them to our distro, and creating a system to share them with the original authors... What should we do differently? Not write the patches? Not send them upstream?

@twilightomni If Ubuntu doesn&#039;t produce patches, it makes enemies. When it does produce patches, it&#039;s accused of hording them/forcing them upstream. I don&#039;t think we can convince everyone that we&#039;re just trying to improve free software and share those improvements with everyone...

@Jonathan, awesome! Good to hear.

@Jewel, awesome! I love it.</description>
		<content:encoded><![CDATA[<p>@Luis I encourage no such thing. Furthermore, Ubuntu is catagorically in favor of pushing any patches submitted to Launchpad upstream.</p>
<p>@Sandy Yeah, we might need to use a VM. Maybe have a root VM image that gets forked and preped to build each package. &#8220;Quickly fixing&#8221; a bug in a package like Nautilus could make testing tricky.</p>
<p>@Christoph That sounds insane! I bet that would require a lot more work, though.</p>
<p>@Bruce *No, only patches the Ubuntu community is producing and posting to Launchpad. We&#8217;re writing patches, applying them to our distro, and creating a system to share them with the original authors&#8230; What should we do differently? Not write the patches? Not send them upstream?</p>
<p>@twilightomni If Ubuntu doesn&#8217;t produce patches, it makes enemies. When it does produce patches, it&#8217;s accused of hording them/forcing them upstream. I don&#8217;t think we can convince everyone that we&#8217;re just trying to improve free software and share those improvements with everyone&#8230;</p>
<p>@Jonathan, awesome! Good to hear.</p>
<p>@Jewel, awesome! I love it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jewel</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2022</link>
		<dc:creator>Jewel</dc:creator>
		<pubDate>Tue, 26 Jan 2010 18:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2022</guid>
		<description>In the past I worked on something similar: http://github.com/jewel/apt-hack

Once apt-hack is installed, your workflow is:

apt-hack fork f-spot
cd ~/src/f-spot
gedit src/...
apt-hack build
apt-hack install

It&#039;s not perfect by any means, and my goals were a little different, but the premise is the same.</description>
		<content:encoded><![CDATA[<p>In the past I worked on something similar: <a href="http://github.com/jewel/apt-hack" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/github.com/jewel/apt-hack?referer=');">http://github.com/jewel/apt-hack</a></p>
<p>Once apt-hack is installed, your workflow is:</p>
<p>apt-hack fork f-spot<br />
cd ~/src/f-spot<br />
gedit src/&#8230;<br />
apt-hack build<br />
apt-hack install</p>
<p>It&#8217;s not perfect by any means, and my goals were a little different, but the premise is the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2019</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 25 Jan 2010 16:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2019</guid>
		<description>Great idea. 

Hopefully people can comment on the idea rather than start an Ubuntu-upstream debate again :-)</description>
		<content:encoded><![CDATA[<p>Great idea. </p>
<p>Hopefully people can comment on the idea rather than start an Ubuntu-upstream debate again :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Azzopardi</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2018</link>
		<dc:creator>Jean Azzopardi</dc:creator>
		<pubDate>Mon, 25 Jan 2010 15:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2018</guid>
		<description>I&#039;ve tried mucking around before, and I agree, getting everything working is a big hassle.

If you manage to get this thing working on Launchpad, it would be a great help.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried mucking around before, and I agree, getting everything working is a big hassle.</p>
<p>If you manage to get this thing working on Launchpad, it would be a great help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Lange</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2017</link>
		<dc:creator>Jonathan Lange</dc:creator>
		<pubDate>Mon, 25 Jan 2010 13:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2017</guid>
		<description>Hey David,

Great idea. Karl Fogel went through almost exactly this story at the last Launchpad team meeting. We might well have even written it up somewhere on http://dev.launchpad.net

Anyway, this is exactly the kind of story we&#039;re working on right now on Launchpad.

Keep the dream alive!

jml</description>
		<content:encoded><![CDATA[<p>Hey David,</p>
<p>Great idea. Karl Fogel went through almost exactly this story at the last Launchpad team meeting. We might well have even written it up somewhere on <a href="http://dev.launchpad.net" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/dev.launchpad.net?referer=');">http://dev.launchpad.net</a></p>
<p>Anyway, this is exactly the kind of story we&#8217;re working on right now on Launchpad.</p>
<p>Keep the dream alive!</p>
<p>jml</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oliver</title>
		<link>http://davidsiegel.org/improving-bug-workflow-for-opportunistic-programmers/comment-page-1/#comment-2016</link>
		<dc:creator>oliver</dc:creator>
		<pubDate>Mon, 25 Jan 2010 10:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://davidsiegel.org/621/#comment-2016</guid>
		<description>That would be a really useful feature. For me, the part about packaging the fixed code and uploading it to PPA for users to test is the most complicated part (I always have to sift through the useful but long Ubuntu Help pages to find the right dch/debuild/dput commands).

Btw. maybe this feature could even be integrated into applications itself: similar to Help -&gt; Report a Problem in this Application there could be a &quot;Modify this Application&quot;, inviting users to toy around with the code for an app.</description>
		<content:encoded><![CDATA[<p>That would be a really useful feature. For me, the part about packaging the fixed code and uploading it to PPA for users to test is the most complicated part (I always have to sift through the useful but long Ubuntu Help pages to find the right dch/debuild/dput commands).</p>
<p>Btw. maybe this feature could even be integrated into applications itself: similar to Help -&gt; Report a Problem in this Application there could be a &#8220;Modify this Application&#8221;, inviting users to toy around with the code for an app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
