<?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: Going with and &#8220;forking&#8221; VUFind</title>
	<atom:link href="http://robotlibrarian.billdueber.com/going-with-and-forking-vufind/feed/" rel="self" type="application/rss+xml" />
	<link>http://robotlibrarian.billdueber.com/going-with-and-forking-vufind/</link>
	<description>Disclaimer: I'm not actually a robot.</description>
	<lastBuildDate>Thu, 01 Dec 2011 18:10:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: The Koha fork and being the change you want to see &#124; Librarians Matter</title>
		<link>http://robotlibrarian.billdueber.com/going-with-and-forking-vufind/comment-page-1/#comment-138</link>
		<dc:creator>The Koha fork and being the change you want to see &#124; Librarians Matter</dc:creator>
		<pubDate>Sat, 19 Sep 2009 02:39:28 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=91#comment-138</guid>
		<description>&lt;p&gt;[...] Open Source Software, VuFind has several forks and this seems to be the community choice, see Going With and Forking VuFind for more details .This is &lt;em&gt;not&lt;/em&gt; the first fork of Koha &#8211; there is already Koha Plus at [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Open Source Software, VuFind has several forks and this seems to be the community choice, see Going With and Forking VuFind for more details .This is <em>not</em> the first fork of Koha &#8211; there is already Koha Plus at [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: George Duimovich</title>
		<link>http://robotlibrarian.billdueber.com/going-with-and-forking-vufind/comment-page-1/#comment-111</link>
		<dc:creator>George Duimovich</dc:creator>
		<pubDate>Wed, 19 Aug 2009 14:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=91#comment-111</guid>
		<description>&lt;p&gt;I enjoy your updates on &quot;vuFork&quot; (lol). Kudos to you and your colleagues for proceeding on this!&lt;/p&gt;

&lt;p&gt;I really like your very quotable statement:&lt;/p&gt;

&lt;p&gt;&quot;The ability to actually (try to) implement the collective intelligence of the library and embody it in a public-facing system is a rush compared to fighting with the ILS.&quot;&lt;/p&gt;

&lt;p&gt;Sums up things nicely..&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I enjoy your updates on &#8220;vuFork&#8221; (lol). Kudos to you and your colleagues for proceeding on this!</p>

<p>I really like your very quotable statement:</p>

<p>&#8220;The ability to actually (try to) implement the collective intelligence of the library and embody it in a public-facing system is a rush compared to fighting with the ILS.&#8221;</p>

<p>Sums up things nicely..</p>]]></content:encoded>
	</item>
	<item>
		<title>By: till</title>
		<link>http://robotlibrarian.billdueber.com/going-with-and-forking-vufind/comment-page-1/#comment-110</link>
		<dc:creator>till</dc:creator>
		<pubDate>Wed, 19 Aug 2009 11:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=91#comment-110</guid>
		<description>&lt;p&gt;I think we have taken the same road with our &quot;Suchkiste&quot; project based on VuFind. VuFind was a convenient user interface for our Solr index that we could deploy quickly to have some kind of prototype interface to show our ideas (the Solr XML interface is not that sexy in public demonstrations :-).
And I think we experienced similar disappointment with the state of the VuFind community and so decided to do our own thing as well.
Today I think, that is wrong. It just doesn&#039;t make sense, that we all redundantly fix the same issues in our VuFind based projects (and there is still a lot to fix). And I think, it is a good idea to commit new features and improvements back to the main trunk to ensure their sustainability. You are right, that did not work in the past.
But on the other hand: We can&#039;t complain about a missing community around VuFind. We are the ones that form (or not) that community. Of course you need to put some efforts into engagement in a community, but I think that pays off by what you may get back.
And I feel, just at the moment there is a chance to make VuFind a real community project. But that depends on us individuals.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think we have taken the same road with our &#8220;Suchkiste&#8221; project based on VuFind. VuFind was a convenient user interface for our <acronym title="Solr isn\'t an acronym, silly!">Solr</acronym> index that we could deploy quickly to have some kind of prototype interface to show our ideas (the <acronym title="Solr isn\'t an acronym, silly!">Solr</acronym> <acronym title="Extensible Markup Language">XML</acronym> interface is not that sexy in public demonstrations :-).
And I think we experienced similar disappointment with the state of the VuFind community and so decided to do our own thing as well.
Today I think, that is wrong. It just doesn&#8217;t make sense, that we all redundantly fix the same issues in our VuFind based projects (and there is still a lot to fix). And I think, it is a good idea to commit new features and improvements back to the main trunk to ensure their sustainability. You are right, that did not work in the past.
But on the other hand: We can&#8217;t complain about a missing community around VuFind. We are the ones that form (or not) that community. Of course you need to put some efforts into engagement in a community, but I think that pays off by what you may get back.
And I feel, just at the moment there is a chance to make VuFind a real community project. But that depends on us individuals.</p>]]></content:encoded>
	</item>
</channel>
</rss>

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

