<?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"
	>
<channel>
	<title>Comments on: trademark and branding</title>
	<atom:link href="http://whacked.net/2008/01/23/trademark-and-branding/feed/" rel="self" type="application/rss+xml" />
	<link>http://whacked.net/2008/01/23/trademark-and-branding/</link>
	<description>thoughts on open spaces</description>
	<pubDate>Sat, 22 Nov 2008 05:29:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Asa Dotzler</title>
		<link>http://whacked.net/2008/01/23/trademark-and-branding/#comment-82435</link>
		<dc:creator>Asa Dotzler</dc:creator>
		<pubDate>Thu, 24 Jan 2008 01:25:42 +0000</pubDate>
		<guid isPermaLink="false">http://whacked.net/2008/01/23/trademark-and-branding/#comment-82435</guid>
		<description>&lt;p&gt;Stephen Lau, yep, exactly. That's one of the problems we faced with Debian. We were able to make specific agreements with folks like Ubuntu, but Debian was unwilling to make an agreement with us about what could and could not be changed in Firefox because they felt that they shouldn't be in a position to enforce that on their downstream customers (that's how it sounded to me, anyway.) &lt;/p&gt;

&lt;p&gt;Interestingly enough, Debian protects its own trademark to avoid just such a problem. They call it "a bug". &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A&lt;/li&gt;
&lt;/ul&gt;
</description>
		<content:encoded><![CDATA[<p>Stephen Lau, yep, exactly. That&#8217;s one of the problems we faced with Debian. We were able to make specific agreements with folks like Ubuntu, but Debian was unwilling to make an agreement with us about what could and could not be changed in Firefox because they felt that they shouldn&#8217;t be in a position to enforce that on their downstream customers (that&#8217;s how it sounded to me, anyway.) </p>

<p>Interestingly enough, Debian protects its own trademark to avoid just such a problem. They call it &#8220;a bug&#8221;. </p>

<ul>
<li>A</li>
</ul>]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Lau</title>
		<link>http://whacked.net/2008/01/23/trademark-and-branding/#comment-82433</link>
		<dc:creator>Stephen Lau</dc:creator>
		<pubDate>Thu, 24 Jan 2008 01:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://whacked.net/2008/01/23/trademark-and-branding/#comment-82433</guid>
		<description>&lt;p&gt;... but that becomes troublesome for any product that wants to prevent its brand from being potentially misused.  For instance, with free and unfettered/unrestricted license rights to use logo/branding, someone else could take a shell script that did "cat /dev/random &gt; /dev/sound" and put it in a script called "songbird" and give it the Songbird logo/icon, and that would be okay.&lt;/p&gt;

&lt;p&gt;(contrived example sure, but possible without &lt;em&gt;some&lt;/em&gt; sort of restriction on the right to use POTI/Songbird trademarks)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8230; but that becomes troublesome for any product that wants to prevent its brand from being potentially misused.  For instance, with free and unfettered/unrestricted license rights to use logo/branding, someone else could take a shell script that did &#8220;cat /dev/random > /dev/sound&#8221; and put it in a script called &#8220;songbird&#8221; and give it the Songbird logo/icon, and that would be okay.</p>

<p>(contrived example sure, but possible without <em>some</em> sort of restriction on the right to use POTI/Songbird trademarks)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Asa Dotzler</title>
		<link>http://whacked.net/2008/01/23/trademark-and-branding/#comment-82431</link>
		<dc:creator>Asa Dotzler</dc:creator>
		<pubDate>Thu, 24 Jan 2008 00:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://whacked.net/2008/01/23/trademark-and-branding/#comment-82431</guid>
		<description>&lt;p&gt;I suspect that Debian will have a problem with that. They want to be able to ensure that their downstream customers don't have any restrictions put on them about how they modify and re-distribute the software.  Your smoketests would probably constitute such a restriction.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I suspect that Debian will have a problem with that. They want to be able to ensure that their downstream customers don&#8217;t have any restrictions put on them about how they modify and re-distribute the software.  Your smoketests would probably constitute such a restriction.</p>]]></content:encoded>
	</item>
</channel>
</rss>
