<?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: Open-process Academic Publishing</title>
	<atom:link href="http://hackthestate.org/2009/12/16/open-process-academic-publishing-v1-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackthestate.org/2009/12/16/open-process-academic-publishing-v1-2/</link>
	<description>Armed revolutionaries and anarchists hate the state. Social democrats want to be the state. I say we better hack it.</description>
	<lastBuildDate>Sat, 06 Mar 2010 11:46:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrick</title>
		<link>http://hackthestate.org/2009/12/16/open-process-academic-publishing-v1-2/comment-page-1/#comment-602</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Mon, 08 Feb 2010 19:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://hackthestate.org/?p=718#comment-602</guid>
		<description>I find the whole idea quite interesting, and the fact that it works for softwares can certainly give us hopes. A few points though:

1. I wouldn&#039;t emphasise as much the software paradigm, and would probably scrap the part &quot;What if software were developed through closed models&quot;. I don&#039;t think it brings a lot to the discussion of publication, except to show that open processes are successful in programming.

2. The speed of innovation is not as clear cut... True, opensource softwares have been at the hear of important innovations. But commercial companies also have been very quick to foster major developments... They also have more focus on usability/GUI than open source contributors might do.

3. I am also at the LSE (Economics) and have certainly been given the opposite advice: to be bold and daring! So no generalisation... it&#039;s probably highly dependant on the topic, and its internal dynamism (the two issues being obviously linked in both directions).

4. Also, I think one point that you do not mention at all is the potential unintended consequences of non-anonymous refereeing.

In a given specialty, there are not that many people worldwide that can comment. It means that people working on the same topic as you are going to be people you interact repeatedly within your career.
If you are not anonymous anymore, and you get rejected for (what you believe to be) the wrong reason, you&#039;d probably be mad at the referee and will want to reject his next work... In the long term, it&#039;s probably for the quality of the research if it&#039;s very hard to publish and everyone tries to shoot down bad ideas, but one also needs to think about the incentives on the writer&#039;s side... If it&#039;s so hard, maybe it&#039;s not that fun as a career.
The argumetn goes also the way around: if you have to ref someone who is known to be influential (not necess. for publication but for other academic issues), you might not want to reject that person if you are going to apply to his university for instance.

Just to say that these &quot;reputation&quot; issue should be taken into account when considering non-anonymous refereeing, which is part of the Open-Process you propose.</description>
		<content:encoded><![CDATA[<p>I find the whole idea quite interesting, and the fact that it works for softwares can certainly give us hopes. A few points though:</p>
<p>1. I wouldn&#8217;t emphasise as much the software paradigm, and would probably scrap the part &#8220;What if software were developed through closed models&#8221;. I don&#8217;t think it brings a lot to the discussion of publication, except to show that open processes are successful in programming.</p>
<p>2. The speed of innovation is not as clear cut&#8230; True, opensource softwares have been at the hear of important innovations. But commercial companies also have been very quick to foster major developments&#8230; They also have more focus on usability/GUI than open source contributors might do.</p>
<p>3. I am also at the LSE (Economics) and have certainly been given the opposite advice: to be bold and daring! So no generalisation&#8230; it&#8217;s probably highly dependant on the topic, and its internal dynamism (the two issues being obviously linked in both directions).</p>
<p>4. Also, I think one point that you do not mention at all is the potential unintended consequences of non-anonymous refereeing.</p>
<p>In a given specialty, there are not that many people worldwide that can comment. It means that people working on the same topic as you are going to be people you interact repeatedly within your career.<br />
If you are not anonymous anymore, and you get rejected for (what you believe to be) the wrong reason, you&#8217;d probably be mad at the referee and will want to reject his next work&#8230; In the long term, it&#8217;s probably for the quality of the research if it&#8217;s very hard to publish and everyone tries to shoot down bad ideas, but one also needs to think about the incentives on the writer&#8217;s side&#8230; If it&#8217;s so hard, maybe it&#8217;s not that fun as a career.<br />
The argumetn goes also the way around: if you have to ref someone who is known to be influential (not necess. for publication but for other academic issues), you might not want to reject that person if you are going to apply to his university for instance.</p>
<p>Just to say that these &#8220;reputation&#8221; issue should be taken into account when considering non-anonymous refereeing, which is part of the Open-Process you propose.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
