<?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: Family Pursuit Adds Private Family Trees</title>
	<atom:link href="http://www.thinkgenealogy.com/2009/01/18/family-pursuit-adds-private-family-trees/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkgenealogy.com/2009/01/18/family-pursuit-adds-private-family-trees/</link>
	<description>genealogy, software, ideas, and innovation</description>
	<lastBuildDate>Wed, 11 Jan 2012 15:38:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.thinkgenealogy.com/2009/01/18/family-pursuit-adds-private-family-trees/comment-page-1/#comment-765</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Mon, 19 Jan 2009 05:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkgenealogy.com/?p=371#comment-765</guid>
		<description>Mark, I realize that you&#039;ve been a tester for FamilyPursuit in the past and was curious about your thoughts, so will look forward to your blogging on the subject.

When I first learned about the website last year, I had high hopes, as it listed some very impressive features and intentions.  It seemed as though development since that time had been coming more slowly than I&#039;d hoped (as the corporate blog had been fairly quiet as to new features put in place as of late), but perhaps I&#039;m just impatient.

Regardless, I was pleased to see the recent announcement.  The family tree entry process other than via GEDCOM is a bit painful, and the site is still devoid of a number of features that one would eventually like to see, but improvements in all areas of the website are expected.  The product is still young and in beta after all.

I certainly hope it succeeds, as its aims are lofty and well-intentioned.  The company appears to answer queries through its feedback boards quite quickly, which is also a good sign.  Perhaps the best way to currently interface with the product is to use your software package of choice and make changes there, while periodically uploading a GEDCOM to the site to put in place any updates for the benefit of others researching your family lines.

We&#039;ll have to see what the future brings.  With respect to that issue, perhaps you have some insights that you&#039;ll be able to share.</description>
		<content:encoded><![CDATA[<p>Mark, I realize that you&#8217;ve been a tester for FamilyPursuit in the past and was curious about your thoughts, so will look forward to your blogging on the subject.</p>
<p>When I first learned about the website last year, I had high hopes, as it listed some very impressive features and intentions.  It seemed as though development since that time had been coming more slowly than I&#8217;d hoped (as the corporate blog had been fairly quiet as to new features put in place as of late), but perhaps I&#8217;m just impatient.</p>
<p>Regardless, I was pleased to see the recent announcement.  The family tree entry process other than via GEDCOM is a bit painful, and the site is still devoid of a number of features that one would eventually like to see, but improvements in all areas of the website are expected.  The product is still young and in beta after all.</p>
<p>I certainly hope it succeeds, as its aims are lofty and well-intentioned.  The company appears to answer queries through its feedback boards quite quickly, which is also a good sign.  Perhaps the best way to currently interface with the product is to use your software package of choice and make changes there, while periodically uploading a GEDCOM to the site to put in place any updates for the benefit of others researching your family lines.</p>
<p>We&#8217;ll have to see what the future brings.  With respect to that issue, perhaps you have some insights that you&#8217;ll be able to share.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

