<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gavin Baker &#187; FOSS</title>
	<atom:link href="http://www.gavinbaker.com/category/foss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gavinbaker.com</link>
	<description>A Journal of Insignificant Inquiry</description>
	<lastBuildDate>Fri, 28 Oct 2011 14:56:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Comments on NSF&#8217;s Merit Review Criteria</title>
		<link>http://www.gavinbaker.com/2011/03/15/nsf-review/</link>
		<comments>http://www.gavinbaker.com/2011/03/15/nsf-review/#comments</comments>
		<pubDate>Wed, 16 Mar 2011 03:52:41 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Academia]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Open access]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/?p=370</guid>
		<description><![CDATA[Today, I submitted these comments to the consultation on the National Science Foundation&#8217;s Task Force on Merit Review (see). They are provided solely in my personal capacity. What do you see as the strengths and weaknesses of each criterion? The &#8230; <a href="http://www.gavinbaker.com/2011/03/15/nsf-review/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Today, I submitted these comments to the <a href="http://www.nsf.gov/funding/meritreviewform.cfm">consultation</a> on the National Science Foundation&#8217;s Task Force on Merit Review (<a href="http://www.nsf.gov/nsb/publications/2011/01_19_mrtf.jsp">see</a>). They are provided solely in my personal capacity.</p>
<p><i>What do you see as the strengths and weaknesses of each criterion?</i></p>
<p>The current Broader Impacts merit review criterion includes the consideration, &#8220;Will the results be disseminated broadly to enhance scientific and technological understanding?&#8221; NSF should retain and strengthen this consideration of the merit review.</p>
<p>Broad dissemination must be a high priority for NSF-funded research. As a federal agency operating with taxpayer funding, NSF has a responsibility to maximize return on investment by removing barriers to access for the scientific community, as well as to ensure access for taxpayers. In addition, broad and equitable dissemination of scientific information advances the goals of the Universal Declaration of Human Rights, which affirms that &#8220;everyone has the right freely to &#8230; share in scientific advancement and its benefits,&#8221; and the International Covenant on Economic, Social and Cultural Rights, in which governments agree to take the steps &#8220;necessary for the conservation, the development and the diffusion of science;&#8221; the United States is a signatory to both documents.</p>
<p>Under the current criteria, which are more than a decade old, proposals may be inadequately reviewed with regard to the dissemination consideration. During that time, the landscape of scholarly publishing and information has undergone significant changes. In particular, the exceptional opportunities created by the Internet behoove NSF to ensure that its funded research takes full advantage of the new technology to maximize cost-effective dissemination.</p>
<p>At present, broad dissemination of results is promoted through two avenues at NSF: the merit review criteria, which investigators must address in their proposals, and the Award and Administration Guide (AAG), which governs projects after an award is issued. This dual approach is beneficial and should be maintained and strengthened.</p>
<p>NSF establishes minimum requirements for dissemination in Chapter VI.D.4 of the AAG. In particular:</p>
<ul>
<li>&#8220;Investigators are expected to promptly prepare and submit for publication &#8230; all significant findings from work conducted under NSF grants;&#8221; and</li>
<li>&#8220;Investigators are expected to share with other researchers, at no more than incremental cost and within a reasonable time, the primary data, samples, physical collections and other supporting materials created or gathered in the course of work under NSF grants.&#8221;</li>
</ul>
<p>This policy is underpinned by Sec. 7011 of the America COMPETES Act of 2007, which requires NSF to enforce the standards by making any researcher who fails to comply ineligible for future funding. </p>
<p>Additionally, Sec. 7010 of the 2007 COMPETES Act requires NSF to make project reports freely available to the public online, along with citations to any publications resulting from NSF funding. This provision of the law is implemented by Chapter II.E.3 of the AAG, which requires grantees to submit a report describing the project outcomes, written specifically for the public, to be made freely available via Research.gov.</p>
<p>In addition to the baseline standards of the AAG, investigators are required to address the dissemination consideration of the Broader Impacts merit review criterion. This dual approach is beneficial because it encourages creative approaches to dissemination beyond the minimum, as appropriate to the proposed activity. Moreover, by including dissemination in the merit review criteria rather than only in post-award requirements, NSF ensures that investigators plan for dissemination beginning from the proposal stage, a valuable way to keep dissemination in mind throughout the project&#8217;s life cycle.</p>
<p>Unfortunately, both aspects of this approach currently are insufficient. Both the dissemination requirements of the AAG and the dissemination consideration of the Broader Impacts criterion should be updated and strengthened.</p>
<p>While NSF is to be recognized for its leadership in recently requiring investigators to develop data management plans, in other regards the AAG is outdated and should be reformed. Most importantly, NSF has not implemented a requirement that its funded investigators provide public access to resulting peer-reviewed manuscripts, rather than merely the citations to those publications. Among federal science agencies, the National Institutes of Health (NIH) is the current leader in this area, having adopted a mandatory public access policy as required by Sec. 218 of the Consolidated Appropriations Act, 2008. Dozens of other public and private research foundations worldwide have successfully adopted similar policies. NSF should incorporate a similar mandatory policy in the AAG. Furthermore, NSF should improve on the NIH policy by reducing the &#8220;embargo&#8221; period when manuscripts can be withheld from public access from the current maximum of twelve months to a six-month maximum, as several other research funders worldwide have done.</p>
<p>However, as this comment is directed to the Task Force on Merit Review, I will focus on the dissemination consideration of the Broader Impacts criterion, rather than the requirements of the AAG. To be clear, even if the dissemination requirements of the AAG are strengthened, the dissemination consideration of the merit review criteria also should be retained and strengthened.</p>
<p>The first regard in which the dissemination consideration of the merit review criteria is inadequate is its construction. Currently, broad dissemination is a consideration only of the Broader Impacts criterion, not the Intellectual Merit criterion. However, dissemination is properly understood as fundamental to both the intellectual merits of the proposed activity as well as its broader impacts. </p>
<p>The thrust of the current consideration is that maximizing the social value of the funded project requires communicating the project&#8217;s results to relevant audiences outside the research community, such as industry and policymakers, and to the public to enhance the public understanding of science. This is useful strategy to increase the broader impact of NSF funding and should be maintained. In particular, it supports the requirements of Sec. 526 of the America COMPETES Reauthorization Act of 2010, which directs NSF&#8217;s Broader Impacts criterion to advance the goal of &#8220;increased public scientific literacy.&#8221;</p>
<p>However, even within the academic community, the broad dissemination of research results cannot be taken for granted. Access barriers imposed by the high and rising cost of serials and monographs can significantly hamper the circulation of knowledge. These barriers can be particularly imposing to researchers and students at smaller institutions and in developing countries. Additionally, reticence to share data or materials with other researchers, or delays in doing so, also hinder the progress of science.</p>
<p>Thankfully, online technologies enable innovative approaches to the broad dissemination of research information which previously was only shared in small circles. These approaches already have begun to bear fruit. For instance, the NIH-supported Alzheimer’s Disease Neuroimaging Initiative was recently highlighted by the <cite>New York Times</cite> for its innovative approach to data sharing which is already being emulated. Given the promise of openness, the Board should ensure that the merit review criteria promote the broadest possible dissemination of results.</p>
<p><i>What changes, if any, would you like to see made to the merit review criteria?</i></p>
<p>If the Board retains the current criteria, it should add a consideration for broad dissemination in the Intellectual Merit criterion, in addition to the current consideration in the Broader Impacts criterion. Such a consideration might read, &#8220;Will the proposed activity ensure the broadest possible access to its results within its own field or across different fields?&#8221; </p>
<p>Alternatively, the Board might adopt a single consideration that addresses broad dissemination both within and beyond the research community.</p>
<p><i>What role should the institution play to ensure that the intellectual merit and broader impacts in NSF proposals can be realized?</i></p>
<p>NSF should provide additional guidance to proposers on how best to address the dissemination consideration. The Task Force will be aware of Sec. 526 of the COMPETES Reauthorization Act, which directs NSF to better inform proposers as well as staff and reviewers about the Broader Impacts criterion&#8217;s requirements, among other changes. The process of implementing these statutory provisions offers a timely opportunity for NSF to suggest &#8220;proven strategies and models&#8221; for cost-effective broad dissemination.</p>
<p>Currently, NSF provides a list of examples of representative activities for the dissemination consideration. These examples should be updated to better take advantage of proven strategies. Most critically, NSF should encourage investigators to provide open access to their publications by publishing them in an open access journal or by depositing them in an open access repository immediately upon publication, under an open copyright license. NSF could also encourage investigators to consider the impact of their publishers&#8217; policies and pricing on the broad dissemination of their research. Further, NSF should encourage investigators to post their data online for free public access, and to freely distribute online any software created resulting from NSF funding under a free software license, depositing both in appropriate repositories as applicable.</p>
<p>Beyond mere suggestions of activities, NSF should refer investigators to resources on how to accomplish these activities, such as existing guides prepared by the library community and others. NSF should also encourage institutions to play a more proactive role in supporting investigators in maximizing the dissemination of their research, including collaboratively sharing resources and strategies between institutions.</p>
<p>Additionally, NSF should ensure that these resources and guidance are available to its reviewers and staff, and that they duly take into account these activities in reviewing proposals&#8217; commitment to broad dissemination of research.</p>
<p><i>What impact, if any, has NSF&#8217;s two review criteria had on how you think about developing your research projects?</i></p>
<p><i>Any other comments?</i></p>
<p>Thank you for the opportunity to comment on the merit review criteria. Please do not hesitate to contact me with any questions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2011/03/15/nsf-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to improve OJS: a reader&#8217;s perspective</title>
		<link>http://www.gavinbaker.com/2008/12/31/how-to-improve-ojs-a-readers-perspective/</link>
		<comments>http://www.gavinbaker.com/2008/12/31/how-to-improve-ojs-a-readers-perspective/#comments</comments>
		<pubDate>Wed, 31 Dec 2008 21:04:09 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Open access]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/12/31/how-to-improve-ojs-a-readers-perspective/</guid>
		<description><![CDATA[Open Journal Systems is a free and open source software package for journal publishing. It&#8217;s probably the most widely-deployed platform for publishing open access journals; at least 2,000 journals use OJS. As such, it&#8217;s critical infrastructure for the OA movement: &#8230; <a href="http://www.gavinbaker.com/2008/12/31/how-to-improve-ojs-a-readers-perspective/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://pkp.sfu.ca/ojs">Open Journal Systems</a> is a free and open source software package for journal publishing. It&#8217;s probably the most widely-deployed platform for publishing open access journals; <a href="http://www.earlham.edu/~peters/fos/2008/10/2000-journals-using-ojs.html">at least 2,000 journals use OJS</a>. As such, it&#8217;s critical infrastructure for the OA movement: authors&#8217;, editors&#8217;, referees&#8217;, publishers&#8217;, and readers&#8217; impression of OJS has a big impact on their impression of OA.</p>
<p>I haven&#8217;t used OJS as an author, editor, referee, publisher, nor as a sysadmin, but I have used it as a reader. It&#8217;s generally very usable, although there are a few areas, mostly related to current awareness, where some simple tweaks to the defaults would make things easier.</p>
<ul>
<li><strong>Make subscribing easier and more obvious.</strong> When you visit an OJS using a standard theme, there&#8217;s no big button that says &#8220;subscribe&#8221; or a similar term. Instead, there are two options that lead down that path: &#8220;Register&#8221; and &#8220;For Readers&#8221;.
<p>The &#8220;For Readers&#8221; page, by default, directs readers to register to receive the table of contents of new issues via email. The &#8220;Register&#8221; page, by default, requires you to create a username and password, fill out a captcha, and give your full name in addition to your email address. It also asks, optionally, for your gender, mailing address, and other information. That&#8217;s a lot of effort just to get an email when new issues are released.</p>
<p>There&#8217;s a reason: OJS uses the same page to register authors and reviewers &#8212; situations where more information than just an email address is required. There may be a bit of wishful thinking here, too: the hope of converting readers into authors and reviewers. But let&#8217;s cross that bridge when we come to it. For now, let&#8217;s just get people on the mailing list. This is a tenant of Web design (and publicity generally): convert one visit into future contacts. That&#8217;s why <a href="http://www.barackobama.com/">barackobama.com</a> started with a splash page which asked for one thing: your email address.</p>
<p>A journal should make a prominent pitch for visitors to subscribe before they navigate away from the page and forget about the journal. More subscribers leads to more readers, which leads to more authors and referees and commentary.</p>
<p>The OJS default themes should include a sidebar section that says &#8220;Enter your email to receive free announcements when a new issue is released&#8221;. It should ask for <em>only</em> an email address. (The confirmation email can ask subscribers to register a username, if desired.)</li>
<li><strong>RSS feeds by default.</strong> OJS includes a <a href="http://pkp.sfu.ca/ojs_plugins">plugin</a> to produce RSS feeds, but it doesn&#8217;t appear to be on by default; many OJS journals don&#8217;t offer RSS feeds. See above comments about the importance of turning visitors into subscribers.</li>
<li><strong>OpenID support.</strong> With 2,000 OJS journals floating around, it seems a bit silly to have to create an account at each one, doesn&#8217;t it? OpenID would give users a single login not only across other OJS journals, but any site supporting OpenID. Good news, though: OpenID support is in the <a href="http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap">OJS roadmap</a>.</li>
</ul>
<p>As a closing comment, I&#8217;ll point out that OJS is under active development and progressing quickly. I was going to make a comment on how feed display is ugly, based on <a href="http://www.openmedicine.ca/"><cite>Open Medicine</cite></a> as an example, but I thought I ought to check the versions first, to make sure the problem hadn&#8217;t been resolved. Sure enough, <cite>Open Medicine</cite> is using OJS 2.1.1; the release notes of more recent versions mention improvements to feed handling, so this may have been fixed already.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/12/31/how-to-improve-ojs-a-readers-perspective/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Towards autono.my</title>
		<link>http://www.gavinbaker.com/2008/07/16/towards-autonomy/</link>
		<comments>http://www.gavinbaker.com/2008/07/16/towards-autonomy/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 22:02:47 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Personal]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/07/16/towards-autonomy/</guid>
		<description><![CDATA[I&#8217;ve been an advocate for freedom in Web services for, well, years now. So I was happy to learn of the launch of open microblogging service identi.ca recently, and of autonomo.us and its Franklin Street Statement on Freedom and Network &#8230; <a href="http://www.gavinbaker.com/2008/07/16/towards-autonomy/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been an advocate for freedom in Web services for, well, years now. So I was happy to learn of the launch of open microblogging service <a href="http://identi.ca/">identi.ca</a> recently, and of <a href="http://autonomo.us/">autonomo.us</a> and its <a href="http://autonomo.us/2008/07/franklin-street-statement/">Franklin Street Statement on Freedom and Network Services</a>. Pleasantly, the <a href="http://autonomo.us/wiki/Main_Page">autonomo.us wiki</a> already links to my <a href="http://www.freesoftwaremagazine.com/articles/free_software_vs_software_service">article</a> and <a href="http://www.gavinbaker.com/presentations/fls-2008/">talk</a> on the subject.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/07/16/towards-autonomy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FOSS and socially responsible investing</title>
		<link>http://www.gavinbaker.com/2008/06/30/foss-and-socially-responsible-investing/</link>
		<comments>http://www.gavinbaker.com/2008/06/30/foss-and-socially-responsible-investing/#comments</comments>
		<pubDate>Mon, 30 Jun 2008 23:40:10 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/06/30/foss-and-socially-responsible-investing/</guid>
		<description><![CDATA[Check out the post at the SFLC blog. I&#8217;ve said for some time that free culture is a matter of social responsibility &#8212; I think it&#8217;s a good frame for the issue, and helps people understand why it matters.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.softwarefreedom.org/blog/2008/jun/28/social-responsible-investing/">Check out the post at the SFLC blog.</a> I&#8217;ve said for some time that free culture is a matter of social responsibility &#8212; I think it&#8217;s a good frame for the issue, and helps people understand why it matters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/06/30/foss-and-socially-responsible-investing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My latest column on Web apps and FOSS</title>
		<link>http://www.gavinbaker.com/2008/06/03/my-latest-column-on-web-apps-and-foss/</link>
		<comments>http://www.gavinbaker.com/2008/06/03/my-latest-column-on-web-apps-and-foss/#comments</comments>
		<pubDate>Wed, 04 Jun 2008 03:23:41 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Personal]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/06/03/my-latest-column-on-web-apps-and-foss/</guid>
		<description><![CDATA[(I had accidentally posted this in the wrong place earlier; posting it here now.) My new column for Free Software Magazine is titled &#8220;Free software vs. software-as-a-service: Is the GPL too weak for the Web?&#8221;. It looks at the rise &#8230; <a href="http://www.gavinbaker.com/2008/06/03/my-latest-column-on-web-apps-and-foss/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>(I had accidentally posted this in the wrong place earlier; posting it here now.)</p>
<p>My new column for <cite>Free Software Magazine</cite> is titled <a href="http://www.freesoftwaremagazine.com/articles/free_software_vs_software_service">&#8220;Free software vs. software-as-a-service: Is the GPL too weak for the Web?&#8221;</a>. It looks at the rise of the Web application &#8212; including Facebook, Flickr, Google Apps, and the like &#8212; and how to preserve user freedom in this new environment. You can <a href="http://www.freesoftwaremagazine.com/articles/free_software_vs_software_service">read the article</a> or <a href="http://www.freesoftwaremagazine.com/node/2726/pdf">download it as a PDF</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/06/03/my-latest-column-on-web-apps-and-foss/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speaking @ Fla. Linux Show on FOSS vs. SaaS</title>
		<link>http://www.gavinbaker.com/2008/02/11/speaking-fla-linux-show-on-foss-vs-saas/</link>
		<comments>http://www.gavinbaker.com/2008/02/11/speaking-fla-linux-show-on-foss-vs-saas/#comments</comments>
		<pubDate>Mon, 11 Feb 2008 05:06:09 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Florida]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Personal]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/02/11/speaking-fla-linux-show-on-foss-vs-saas/</guid>
		<description><![CDATA[I&#8217;m giving a presentation at the Florida Linux Show in Jacksonville on Monday, Feb. 11. My presentation is on Software as a Service: Implications of Web Apps for Software Freedom (a topic I previously ranted about at GatorLUG); it&#8217;s at &#8230; <a href="http://www.gavinbaker.com/2008/02/11/speaking-fla-linux-show-on-foss-vs-saas/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m giving a presentation at the <a href="http://www.floridalinuxshow.com/">Florida Linux Show</a> in Jacksonville on Monday, Feb. 11. My presentation is on <a href="http://www.floridalinuxshow.com/index.php?pr=Gavin_Baker">Software as a Service: Implications of Web Apps for Software Freedom</a> (a topic I <a href="http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/">previously ranted about at Gator<abbr title="Linux Users Group">LUG</abbr></a>); it&#8217;s at 9:30 am. I&#8217;ll post the slides here when they&#8217;re available.</p>
<p><ins datetime="2008-02-11T17:15:13+00:00"><strong>Update:</strong> <a href="http://www.gavinbaker.com/presentations/fls-2008/">Slides are here.</a> Thanks to a great audience!</ins></p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/02/11/speaking-fla-linux-show-on-foss-vs-saas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FSF to libraries: boycott DRM</title>
		<link>http://www.gavinbaker.com/2008/02/07/fsf-to-libraries-boycott-drm/</link>
		<comments>http://www.gavinbaker.com/2008/02/07/fsf-to-libraries-boycott-drm/#comments</comments>
		<pubDate>Fri, 08 Feb 2008 04:58:14 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Libraries]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/02/07/fsf-to-libraries-boycott-drm/</guid>
		<description><![CDATA[Sometimes, different interests of mine will intersect in fascinating ways. Here&#8217;s one: the Free Software Foundation&#8217;s DefectiveByDesign.org campaign is asking libraries to boycott DRM, digital restrictions on content the library purchases or subscribes to. Specifically, DbD is targeting the Boston &#8230; <a href="http://www.gavinbaker.com/2008/02/07/fsf-to-libraries-boycott-drm/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Sometimes, different interests of mine will intersect in fascinating ways. Here&#8217;s one: the Free Software Foundation&#8217;s DefectiveByDesign.org campaign <a href="http://www.defectivebydesign.org/LibraryAction.html">is asking libraries to boycott <abbr title="Digital Rights Management">DRM</abbr>,</a> digital restrictions on content the library purchases or subscribes to. Specifically, <abbr title="DefectiveByDesign.org">DbD</abbr> is targeting the Boston Public Library for its use of <a href="http://www.overdrive.com/products/dlr/">OverDrive&#8217;s Digital Library Reserve</a> platform.</p>
<p>I would expect libraries to be receptive to the message of eliminating <abbr title="Digital Rights Management">DRM</abbr> &#8212; <abbr title="Digital Rights Management">DRM</abbr> is diametrically opposed to libraries&#8217; missions of access and preservation, and is an awful abuse of copyright law against the public interest. But it&#8217;s hard to argue that libraries should forgo access altogether to <abbr title="Digital Rights Management">DRM</abbr>-crippled content if they can&#8217;t negotiate out of it or acquire the content from another source. (Exhibit A: <a href="http://www.livejournal.com/manage/subscriptions/comments.bml?journal=johnsu01&#038;talkid=214479">The Boston library&#8217;s response</a>.) With that said, there&#8217;s plenty of room for library pushback against <abbr title="Digital Rights Management">DRM</abbr>, which could further signal vendors that there&#8217;s no market for it. We&#8217;ll see how this turns out.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/02/07/fsf-to-libraries-boycott-drm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EPrints sells out free software: more Apple crippleware prizes</title>
		<link>http://www.gavinbaker.com/2007/10/30/eprints-sells-out-free-software-more-apple-crippleware-prizes/</link>
		<comments>http://www.gavinbaker.com/2007/10/30/eprints-sells-out-free-software-more-apple-crippleware-prizes/#comments</comments>
		<pubDate>Tue, 30 Oct 2007 14:56:16 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Open access]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2007/10/30/eprints-sells-out-free-software-more-apple-crippleware-prizes/</guid>
		<description><![CDATA[EPrints, the important FOSS open archive project &#8212; widely used by open access repositories &#8212; is organizing a call for plugins. Unfortunately, EPrints has followed Mozilla&#8217;s lead and is awarding DRM-crippled, proprietary Apple products as prizes. The EPrints package is &#8230; <a href="http://www.gavinbaker.com/2007/10/30/eprints-sells-out-free-software-more-apple-crippleware-prizes/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.eprints.org/software/">EPrints</a>, the important <abbr title="free and open source software">FOSS</abbr> open archive project &#8212; widely used by open access repositories &#8212; is organizing a <a href="http://www.eprints.org/software/cfp.php">call for plugins</a>. Unfortunately, EPrints has followed <a href="http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/" title="Why is Mozilla selling out free software?">Mozilla&#8217;s lead</a> and is awarding <abbr title="digital rights management">DRM</abbr>-crippled, proprietary Apple products as prizes.</p>
<p>The EPrints package is even <a href="http://directory.fsf.org/project/EPrints/">included in the <abbr title="GNU's Not Unix">GNU</abbr> Project</a>. I am very disappointed in this move; they should know better. Supporting Apple&#8217;s <a href="http://www.defectivebydesign.org/">anti-competitive business practices</a> that limit <a href="http://www.fsf.org/licensing/essays/free-sw.html">users&#8217; freedoms</a> is not in the public interest.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2007/10/30/eprints-sells-out-free-software-more-apple-crippleware-prizes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why is Mozilla selling out free software?</title>
		<link>http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/</link>
		<comments>http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/#comments</comments>
		<pubDate>Tue, 23 Oct 2007 22:39:10 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/</guid>
		<description><![CDATA[Promote Firefox, win a Mac full of proprietary software. Wait, what? You do realize that OS X doesn&#8217;t even come with Firefox pre-loaded, right? And you do realize that other manufacturers offer laptops pre-loaded with Firefox and Linux, right? So &#8230; <a href="http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.operationfirefox.com/">Promote Firefox, win a Mac full of proprietary software.</a> Wait, what?</p>
<p>You do realize that OS X doesn&#8217;t even come with Firefox pre-loaded, right?</p>
<p>And you do realize that <a href="http://www.dell.com/open" title="Dell: Ubuntu">other manufacturers</a> offer laptops pre-loaded with Firefox and Linux, right?</p>
<p>So why in the world should the prize for promoting open source be closed?</p>
<p><ins datetime="2007-10-27T21:19:19+00:00"><strong>Update:</strong> Mozilla is also giving away a Macbook for their <a href="http://labs.mozilla.com/contests/extendfirefox/index.php">Extend Firefox</a> contest. For the avoidance of doubt: &#8220;Apple is not a sponsor of the Extend Firefox competition.&#8221;</ins></p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2007/10/23/why-is-mozilla-selling-out-free-software/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Upcoming presentation in Gainesville, Fla.: software as a service</title>
		<link>http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/</link>
		<comments>http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/#comments</comments>
		<pubDate>Wed, 17 Oct 2007 04:17:24 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Personal]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/</guid>
		<description><![CDATA[On Wednesday, 16 17 October 2007, I am giving a presentation on &#8220;Software as a Service (or, Why I Hate Facebook)&#8221;. The presentation is at the GatorLUG meeting at 6 pm at Virtually Cuban (2409 SW 13th St.). I&#8217;ll post &#8230; <a href="http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>On Wednesday, <del datetime="2007-11-08T15:47:03+00:00">16</del> <ins datetime="2007-11-08T15:47:03+00:00">17</ins> October 2007, I am giving a presentation on &#8220;Software as a Service (or, Why I Hate Facebook)&#8221;. The presentation is at the <a href="http://www.gatorlug.org/">Gator<abbr title="Linux Users Group">LUG</abbr></a> meeting at 6 pm at <a href="http://www.virtuallycuban.com/">Virtually Cuban</a> (2409 SW 13th St.).</p>
<p>I&#8217;ll post the presentation here when I have a chance.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2007/10/16/upcoming-presentation-in-gainesville-fla-software-as-a-service/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

