<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Code4Lib: More than a journal</title>
	<link>http://journal.code4lib.org/articles/71</link>
	<description></description>
	<pubDate>Thu, 07 Aug 2008 20:27:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Eric Lease Morgan</title>
		<link>http://journal.code4lib.org/articles/71#comment-97</link>
		<dc:creator>Eric Lease Morgan</dc:creator>
		<pubDate>Wed, 02 Apr 2008 15:37:52 +0000</pubDate>
		<guid>http://journal.code4lib.org/articles/71#comment-97</guid>
		<description>Adam, the editors discussed the pros and cons of publishing the journal in issues vs the continuous release model. The latter model is, in some ways, easier from the editor's point of view. But, we came to agree that publishing issues seemed like the better choice for our particular group dynamic. We also thought that many of our readers still favored discrete issues and a predictable publication schedule. If, in the future, we get more article submissions than we feel we can deal with using this model, we may change our mind rather than adopting a more frequent publication schedule. Nothing is irrevocably set. --ELM</description>
		<content:encoded><![CDATA[<p>Adam, the editors discussed the pros and cons of publishing the journal in issues vs the continuous release model. The latter model is, in some ways, easier from the editor&#8217;s point of view. But, we came to agree that publishing issues seemed like the better choice for our particular group dynamic. We also thought that many of our readers still favored discrete issues and a predictable publication schedule. If, in the future, we get more article submissions than we feel we can deal with using this model, we may change our mind rather than adopting a more frequent publication schedule. Nothing is irrevocably set. &#8211;ELM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Chandler</title>
		<link>http://journal.code4lib.org/articles/71#comment-41</link>
		<dc:creator>Adam Chandler</dc:creator>
		<pubDate>Tue, 25 Mar 2008 14:50:15 +0000</pubDate>
		<guid>http://journal.code4lib.org/articles/71#comment-41</guid>
		<description>Thank you for putting out a fine issue, Eric. I wonder, though, does batching these articles up into an issue really add any value? Why not release the articles through the RSS feed as soon as they make it to the end of the editorial process? I would rather read one here and one there over the course of few weeks.</description>
		<content:encoded><![CDATA[<p>Thank you for putting out a fine issue, Eric. I wonder, though, does batching these articles up into an issue really add any value? Why not release the articles through the RSS feed as soon as they make it to the end of the editorial process? I would rather read one here and one there over the course of few weeks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Giarlo</title>
		<link>http://journal.code4lib.org/articles/71#comment-38</link>
		<dc:creator>Mike Giarlo</dc:creator>
		<pubDate>Tue, 25 Mar 2008 12:45:26 +0000</pubDate>
		<guid>http://journal.code4lib.org/articles/71#comment-38</guid>
		<description>I won't say the karma system is rigged, but that I am currently atop the pile exposes deep and fundamental flaws in it.

Great introduction to the issue and the community, Eric!</description>
		<content:encoded><![CDATA[<p>I won&#8217;t say the karma system is rigged, but that I am currently atop the pile exposes deep and fundamental flaws in it.</p>
<p>Great introduction to the issue and the community, Eric!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
