<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.81 (http://www.squarespace.com/) on Sun, 12 Feb 2012 18:28:12 GMT--><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Copyleft Currents</title><link>http://www.heathermeeker.com/news/</link><description></description><lastBuildDate>Sun, 12 Feb 2012 18:17:48 +0000</lastBuildDate><copyright></copyright><language>en-US</language><generator>Squarespace Site Server v5.11.81 (http://www.squarespace.com/)</generator><item><title>Live Free or Die (Whichever is Cost-Effective)</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 07 Feb 2012 22:16:10 +0000</pubDate><link>http://www.heathermeeker.com/news/2012/2/7/live-free-or-die-whichever-is-cost-effective.html</link><guid isPermaLink="false">457655:5143975:14921414</guid><description><![CDATA[<div>In a precedent-setting move, New Hampshire has <a href="http://www.nhliberty.org/bills/view/2012/HB418">enacted HB 418-FN</a>,&nbsp;a bill that directs administrative agencies in the state to consider open source on a level economic playing field with proprietary software, and to favor open standards. &nbsp;State agencies are required to "Consider whether proprietary or open source software offers the most cost  effective software solution for the agency, based on consideration of all  associated acquisition, support, maintenance, and training costs" and to "Avoid the acquisition of products that do not comply with open  standards for interoperability or data storage."<em> &nbsp;</em></div>
<div></div>
<div></div>
<div>The bill contains a definition of open source software that is not dissimilar to, but not quite the same as, the <a href="http://www.opensource.org/osd.html">Open Source Definition</a> and the <a href="http://www.gnu.org/philosophy/free-sw.html">Free Software Definition</a>:&nbsp;(a) Unrestricted use of the software for any  purpose;&nbsp;(b) Unrestricted access to the respective  source code;&nbsp;(c) Exhaustive inspection of the working  mechanisms of the software;&nbsp;(d) Use of the internal mechanisms and  arbitrary portions of the software, to adapt them to the needs of the  user;&nbsp;(e) Freedom to make and distribute copies of  the software; and&nbsp;(f) Modification of the software and freedom  to distribute modifications of the new resulting software, under the same  license as the original software.</div>
<div></div>
<div>
<p>&nbsp;</p>
<p>Perhaps more interesting is the definition of an "open standard," a standard that:</p>
<p>(a) Is free for all to implement and use in  perpetuity, with no royalty or fee;</p>
<p>(b) Has no restrictions on the use of data  stored in the format;</p>
</div>
<div>
<p>(c) Has no restrictions on the creation of  software that stores, transmits, receives, or accesses data codified in such  way;</p>
<p>(d) Has a specification available for all to  read, in a human-readable format, written in commonly accepted technical  language;</p>
<p>(e) Is documented, so that anyone can write  software that can read and interpret the complete semantics of any data file  stored in the data format;</p>
<p>(f) If it allows extensions, ensures that all  extensions of the data format used by the state are themselves documented and  have the other characteristics of an open data format;</p>
<p>(g) Allows any file written in that format to  be identified as adhering or not adhering to the format; and</p>
<p>(h) If it includes any use of encryption or  other means of data obfuscation, provides that the encryption or obfuscation  algorithms are usable in a royalty-free, nondiscriminatory manner in perpetuity,  and are documented so that anyone in possession of the appropriate encryption  key or keys or other data necessary to recover the original data is able to  write software to access the data.</p>
</div>
<div>Open standards definitions are elusive -- you've got to admire the Granite State for trying.</div>
<div></div>
<div></div>
<div></div>
<div>The bill further mandates "principles of open government data" aimed at transparency and free availability of data.</div>
<div></div>
<div></div>
<div>On a personal note, I am always pleasantly surprised when anyone in government appears to be thinking about what is cost effective.</div>
<div></div>
<div></div>
<div></div>
<div>PS Thanks to Mark Radcliffe for the scoop on this.</div>
<div></div>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-14921414.xml</wfw:commentRss></item><item><title>Open Source in US Defense Acquisition</title><dc:creator>Heather Meeker</dc:creator><pubDate>Thu, 26 Jan 2012 22:49:06 +0000</pubDate><link>http://www.heathermeeker.com/news/2012/1/26/open-source-in-us-defense-acquisition.html</link><guid isPermaLink="false">457655:5143975:14746538</guid><description><![CDATA[<div>
<p>On Jan 12, 2012, the Department of Defense held a public meeting inviting comment on the use of open source software in defense contracting. &nbsp; Written comments were submitted by various organizations including the Aerospace Industries Association. &nbsp;<a href="http://www.acq.osd.mil/dpap/dars/docs/AIA_-_Public_Meeting_DFARS_-_Open_Source_Software.pdf">Those comments</a><span>&nbsp;lay out the questions posed by the&nbsp;<span>DoD&nbsp;</span>regarding risks that open source software includes proprietary software (i.e. is infringing), ability of contractors to get support for open source software, and whether the&nbsp;<span>DFARs</span>&nbsp;(Defense Federal Acquisition Regulations) should be revised to clarify the rights granted the government under licenses like&nbsp;<span>GPL</span>. &nbsp;The AIA's comments also raise the question of whether export restrictions are "additional restrictions" that conflict with&nbsp;<span>GPL</span>. &nbsp;</span><a href="http://www.acq.osd.mil/dpap/dars/docs/Craig_Bristol.pdf">Another set of comments</a><span>&nbsp;addressed the&nbsp;question&nbsp;of&nbsp;whether&nbsp;Apache 2.0,&nbsp;paragraph 9, which "provides&nbsp;that the licensee indemnifies the developer in certain circumstances,"&nbsp;conflicts with the&nbsp;<span>Antideficiency</span>&nbsp;Act (<span>ADA</span>) 31 USC 1341. &nbsp;The&nbsp;<span>ADA</span>&nbsp;</span>prevents the government from incurring of obligations in excess of appropriations&nbsp;or funds.&nbsp;</p>
</div>
<p>&nbsp;</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-14746538.xml</wfw:commentRss></item><item><title>Linux Coffee Roaster</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 24 Jan 2012 16:16:51 +0000</pubDate><link>http://www.heathermeeker.com/news/2012/1/24/linux-coffee-roaster.html</link><guid isPermaLink="false">457655:5143975:14712198</guid><description><![CDATA[<p>I don't know about you, but when I get up in the morning, I always think:&nbsp; the only thing that would make this cup of coffee better would be if it <a href="http://arkarthick.com/2012/01/18/linux-powered-coffee-roaster/">were made with open source software.</a>&nbsp; Until I decide to devote an entire computer to roasting coffee, open source caffeine will have to remain a dream for me.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-14712198.xml</wfw:commentRss></item><item><title>Mozilla 2.0 Published and Approved</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 03 Jan 2012 19:12:44 +0000</pubDate><link>http://www.heathermeeker.com/news/2012/1/3/mozilla-20-published-and-approved.html</link><guid isPermaLink="false">457655:5143975:14424186</guid><description><![CDATA[<p>Mozilla Public License 2.0 <a href="http://mpl.mozilla.org/2012/01/03/announcing-mpl-2-0/">has been released</a>, has been <a href="http://www.opensource.org/licenses/MPL-2.0">approved as an open source license</a>&nbsp; by the Open Source Initiative, and has been <a href="http://www.gnu.org/licenses/license-list.html#MPL-2.0">approved as a free software license</a> by FSF. &nbsp;</p>
<p>&nbsp;</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-14424186.xml</wfw:commentRss></item><item><title>Koha Trademark Dispute</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 06 Dec 2011 18:58:50 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/12/6/koha-trademark-dispute.html</link><guid isPermaLink="false">457655:5143975:14001323</guid><description><![CDATA[<p>An open source project in New Zealand is <a href="http://koha-community.org/update-2/">involved in a trademark dispute.</a> </p>
<p>If you want to see an example of the kind of reporting about open source legal matter that drives lawyers like me to distraction, take a look at <a href="http://www.stuff.co.nz/national/6016492/Small-library-fights-US-corporation-over-software-patent">this article</a>.  It describes the dispute as just about everything except what it is -- a trademark interference.  "A small New Zealand library is fighting to keep its trademark free software  from the clutches of a United States corporation."  It's actually a dispute about the trademark, not the software copyright.  "[A]n American company named LibLime has hijacked the system and wants to use it  for its own private client base."  Hijacked?  If it's open source, it's free to use and modify, though there may be a separate trademark issue.  Also the URL for the article calls it "Small-library-fights-US-corporation-over-software-patent" and there are no patents in sight.</p>
<p>But apparently the publicity worked, as the project, according to its own blog post linked above, got many donations to a legal fund, and also pro bono representation.  A deal is reportedly being brokered to assign the trademark to a non-profit representing the Koha community.</p>
<p> </p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-14001323.xml</wfw:commentRss></item><item><title>When is Open Source not Open Source?</title><dc:creator>Heather Meeker</dc:creator><pubDate>Mon, 24 Oct 2011 21:08:33 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/10/24/when-is-open-source-not-open-source.html</link><guid isPermaLink="false">457655:5143975:13443938</guid><description><![CDATA[<p><a href="http://www.networkworld.com/news/2011/101711-open-source-software-251834.html?hpg1=bn">A recent&nbsp;article in Network World</a> contained some interesting caveat emptors about marketing open source software.&nbsp; The first part of the article -- discussing whether open source is really free or secure -- is nothing new.&nbsp; But then, the article mentions this:&nbsp; "Some software vendors playing fast and loose with the rules have slapped an "open source" label on software that in fact turns out to be a "free to download and use" version of proprietary software that cannot be altered or distributed."</p>
<p>This raises an interesting potential legal issue that has not yet come to fruition.&nbsp; Key "trademarks" in the open source space such as "open source" and "Linux" are probably largely genericized, so it seems unlikely that claims will arise as to whether inaccurately calling a product these things is a trademark infringement.&nbsp; However, I have been surprised not to see a fraud or false advertising claim based on a vendor identifying software as "open source" when it is not.&nbsp;&nbsp; It's unclear what the damages might be if the software is <em>gratis</em> but not <em>libre</em>, but that has never stopped a class action plaintiff's lawyer, as far as I know.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-13443938.xml</wfw:commentRss></item><item><title>Meego Gone -- or at least reborn</title><dc:creator>Heather Meeker</dc:creator><pubDate>Sun, 02 Oct 2011 21:50:36 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/10/2/meego-gone-or-at-least-reborn.html</link><guid isPermaLink="false">457655:5143975:13056273</guid><description><![CDATA[<p>Intel has joined the Linux Foundation, and rebranded the Meego operating system as Tizen.&nbsp; Meego was an open source mobile platform that has foundered, after being created based on Intel's Moblin and Nokia's Maemo.&nbsp; The Tizen platform, "<span id="articleText"><a href="http://www.reuters.com/article/2011/09/28/us-linux-idUSTRE78R0O220110928"> an open-source, standards-based software  platform that supports multiple devices including smartphones, tablets,  smart TVs, netbooks and in-vehicle 'infotainment' systems</a>" that supports HTML5 </span>will be hosted by the Foundation and is supported by Samsung as well. Intel stated, &ldquo;Tizen builds upon the strengths of both LiMo and MeeGo, and Intel will  be working with our MeeGo partners to help them transition to Tizen."&nbsp;&nbsp; <a href="http://www.pcmag.com/article2/0,2817,2393830,00.asp#fbid=b1diAJXxHYR">Asus says it will continue to ship Meego systems</a>, and Nokia has just <a href="http://www.pcmag.com/article2/0,2817,2393646,00.asp#fbid=b1diAJXxHYR">recently released a Meego device</a>, N9.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-13056273.xml</wfw:commentRss></item><item><title>Quest -- Return of the Text Adventure</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 06 Sep 2011 14:37:33 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/9/6/quest-return-of-the-text-adventure.html</link><guid isPermaLink="false">457655:5143975:12747599</guid><description><![CDATA[<p>Get your affairs in order.&nbsp; <a href="http://www.textadventures.co.uk/quest/">An engine</a> for text adventure games called Quest has been released as open source.&nbsp; The <a href="http://www.gamepro.com/article/news/222664/open-source-quest-project-aims-to-reinvent-text-adventures-for-the-modern-web/">Zork adventure game</a> on PDP-11 pretty much destroyed my social life in 1980 -- though come to think of it, it was not healthy in the first place and may have never revived.&nbsp; And you would be correct if you observed that not everyone had a PDP-11 sitting around in the living room.&nbsp; We played it at work, after our project managers went home for the day.&nbsp; In fact, my project manager actually showed it to me; it was probably an evil plot to condition us to sleep under our desks.&nbsp; Now you can create your own spelunking adventures -- or whatever kind you want.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-12747599.xml</wfw:commentRss></item><item><title>S. Korean Mobile O/S Project Announced</title><dc:creator>Heather Meeker</dc:creator><pubDate>Tue, 23 Aug 2011 14:48:36 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/8/23/s-korean-mobile-os-project-announced.html</link><guid isPermaLink="false">457655:5143975:12600172</guid><description><![CDATA[<p>Spurred in part by Google's planned purchase of Motorola Mobility, the <a href="http://www.koreaherald.com/national/Detail.jsp?newsMLId=20110822000719">S. Korean government announced </a>plans to develop a new open source mobile O/S particularly geared toward Korean manufacturers and users.&nbsp; Samsung, the world&rsquo;s second-largest mobile phone maker, is the largest player in Korea.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-12600172.xml</wfw:commentRss></item><item><title>Ebay Buys Magneto</title><dc:creator>Heather Meeker</dc:creator><pubDate>Thu, 18 Aug 2011 13:59:10 +0000</pubDate><link>http://www.heathermeeker.com/news/2011/8/18/ebay-buys-magneto.html</link><guid isPermaLink="false">457655:5143975:12553788</guid><description><![CDATA[<p>Ebay today <a href="http://www.businessweek.com/ap/financialnews/D9P5UTK80.htm">closed the purchase of Magneto</a>, a company that makes open source ecommerce tools.&nbsp;&nbsp; EBay purchased a minority stake in the company in 2010.</p>]]></description><wfw:commentRss>http://www.heathermeeker.com/news/rss-comments-entry-12553788.xml</wfw:commentRss></item></channel></rss>
