<?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"
	>
<channel>
	<title>Comments on: context-aware access to a software project memory</title>
	<atom:link href="http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/feed/" rel="self" type="application/rss+xml" />
	<link>http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/</link>
	<description>jeremy's nest</description>
	<pubDate>Tue, 06 Jan 2009 02:38:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jeremy</title>
		<link>http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/#comment-25387</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Sat, 23 Feb 2008 16:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/#comment-25387</guid>
		<description>Hi Neil, thanks for your comment!  I think this work would have something to learn from Mylyn if someone were to take it further: Mylyn's task context model of inferring context based on interaction history is similar.

Ideally, this work would integrate with all types of artifact repositories in a software project: wiki systems, ticketing systems, email archives, and source code repositories.  It's  similar to Hipikat in that respect.

As you said, Mylyn's workflow requires some dedication.  I think it would be great to completely automate context inference and the goal would be to draw on the project memory to find artifacts relevant to the context.  Instead of requiring developers to activate tasks, this system might incorporate user feedback after-the-fact to rate an artifact recommendation's relevance to the context.</description>
		<content:encoded><![CDATA[<p>Hi Neil, thanks for your comment!  I think this work would have something to learn from Mylyn if someone were to take it further: Mylyn&#8217;s task context model of inferring context based on interaction history is similar.</p>
<p>Ideally, this work would integrate with all types of artifact repositories in a software project: wiki systems, ticketing systems, email archives, and source code repositories.  It&#8217;s  similar to Hipikat in that respect.</p>
<p>As you said, Mylyn&#8217;s workflow requires some dedication.  I think it would be great to completely automate context inference and the goal would be to draw on the project memory to find artifacts relevant to the context.  Instead of requiring developers to activate tasks, this system might incorporate user feedback after-the-fact to rate an artifact recommendation&#8217;s relevance to the context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Ernst</title>
		<link>http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/#comment-25313</link>
		<dc:creator>Neil Ernst</dc:creator>
		<pubDate>Sun, 17 Feb 2008 23:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://aperte.org/2008/02/15/context-aware-access-to-a-software-project-memory/#comment-25313</guid>
		<description>Hi Jeremy, what relation does this work have to Mylyn? The notion of automatic inference of context seems similar to me. One of the big pluses for Mylyn has been its integration with ticketing systems like Trac. But it does require pretty faithful dedication to its workflow (activate task, only work on that task, etc).

I'm working on a case study that will examine how an organization (team?) makes changes to an existing software system. Your interests in artifacts and history seem aligned</description>
		<content:encoded><![CDATA[<p>Hi Jeremy, what relation does this work have to Mylyn? The notion of automatic inference of context seems similar to me. One of the big pluses for Mylyn has been its integration with ticketing systems like Trac. But it does require pretty faithful dedication to its workflow (activate task, only work on that task, etc).</p>
<p>I&#8217;m working on a case study that will examine how an organization (team?) makes changes to an existing software system. Your interests in artifacts and history seem aligned</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.732 seconds -->
