<?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: The Browser With No Name</title>
	<atom:link href="http://mike.kaply.com/2008/05/28/the-browser-with-no-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/</link>
	<description>Mozilla, money, microformats and more</description>
	<lastBuildDate>Thu, 17 May 2012 12:38:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: mconnor</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1025</link>
		<dc:creator>mconnor</dc:creator>
		<pubDate>Thu, 29 May 2008 20:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1025</guid>
		<description>Ironically enough, none of the &quot;free&quot; marks you&#039;re referring to are actually &quot;free&quot; in reality...

http://www.openoffice.org/about_us/summary.html

From the trademark section:

&quot;OpenOffice.org&quot; is trademarked and protected in the USA.

You also need to get permission to use their own logos/banners etc.  Even just to link to them from your blog with those images!

http://www.apache.org/foundation/licence-FAQ.html#Marks

&#039;Apache&#039;, &#039;Apache Software Foundation&#039;, the multicoloured feather, and the various Apache project names and logos are trademarks of The Apache Software Foundation, and are usable by others only with express permission from the ASF.

http://www.linuxmark.org/

Set up expressing to handle licensing the use of the Linux trademark owned by Linus Torvalds.  If you want to trademark &quot;Red Hat Linux&quot; you need to license the Linux trademark through LMI.</description>
		<content:encoded><![CDATA[<p>Ironically enough, none of the &#8220;free&#8221; marks you&#8217;re referring to are actually &#8220;free&#8221; in reality&#8230;</p>
<p><a href="http://www.openoffice.org/about_us/summary.html" rel="nofollow">http://www.openoffice.org/about_us/summary.html</a></p>
<p>From the trademark section:</p>
<p>&#8220;OpenOffice.org&#8221; is trademarked and protected in the USA.</p>
<p>You also need to get permission to use their own logos/banners etc.  Even just to link to them from your blog with those images!</p>
<p><a href="http://www.apache.org/foundation/licence-FAQ.html#Marks" rel="nofollow">http://www.apache.org/foundation/licence-FAQ.html#Marks</a></p>
<p>&#8216;Apache&#8217;, &#8216;Apache Software Foundation&#8217;, the multicoloured feather, and the various Apache project names and logos are trademarks of The Apache Software Foundation, and are usable by others only with express permission from the ASF.</p>
<p><a href="http://www.linuxmark.org/" rel="nofollow">http://www.linuxmark.org/</a></p>
<p>Set up expressing to handle licensing the use of the Linux trademark owned by Linus Torvalds.  If you want to trademark &#8220;Red Hat Linux&#8221; you need to license the Linux trademark through LMI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkaply</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1024</link>
		<dc:creator>mkaply</dc:creator>
		<pubDate>Thu, 29 May 2008 11:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1024</guid>
		<description>@Alfred:

That&#039;s not technically distribution per the MPL because we are redistributing it to other employees within our company. It is perfectly legitimate for a company to customize Firefox and distribute it to their employees.

The issue here is broad distribution.</description>
		<content:encoded><![CDATA[<p>@Alfred:</p>
<p>That&#8217;s not technically distribution per the MPL because we are redistributing it to other employees within our company. It is perfectly legitimate for a company to customize Firefox and distribute it to their employees.</p>
<p>The issue here is broad distribution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alfred Kayser</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1023</link>
		<dc:creator>Alfred Kayser</dc:creator>
		<pubDate>Thu, 29 May 2008 06:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1023</guid>
		<description>I have developed a specific theme for the IBM w3v8 theme (as used for the IBM Intranet).
As you know, within IBM Firefox is distributed with a IBM extension (to add some specific search agents and to add some specific logo&#039;s). So it is certainly possible to distribute the default Firefox together with a branded theme and an extension to add some company specific functionality.

Check: https://addons.mozilla.org/en-US/firefox/addon/6594</description>
		<content:encoded><![CDATA[<p>I have developed a specific theme for the IBM w3v8 theme (as used for the IBM Intranet).<br />
As you know, within IBM Firefox is distributed with a IBM extension (to add some specific search agents and to add some specific logo&#8217;s). So it is certainly possible to distribute the default Firefox together with a branded theme and an extension to add some company specific functionality.</p>
<p>Check: <a href="https://addons.mozilla.org/en-US/firefox/addon/6594" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/6594</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1022</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 29 May 2008 00:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1022</guid>
		<description>How bout this:
A company can put out a Firefox branded browser with custom theming and extensions (though no modifications to the core of the browser) as long as the theme and extensions all make it out of the sandbox on AMO.

Part of the idea (from what I remember) of not allowing others to have custom browsers that carry the Firefox name is so that they won&#039;t modify the core or include extensions that make the browser crap and thereby besmirch the Firefox name.
All the addons at AMO that are available to the public have been through a review process and the fact that we&#039;re providing them through our own secure site (integrated with our addons browser) we&#039;re giving them some seal of approval.
If we wanted to, I suppose we could invent another &quot;gold star&quot; seal of approval that keeps to even higher standards.  But the point is that we could make the approval process easy on ourselves and still ensure relative non-suckiness of branded browsers with these few simple rules.</description>
		<content:encoded><![CDATA[<p>How bout this:<br />
A company can put out a Firefox branded browser with custom theming and extensions (though no modifications to the core of the browser) as long as the theme and extensions all make it out of the sandbox on AMO.</p>
<p>Part of the idea (from what I remember) of not allowing others to have custom browsers that carry the Firefox name is so that they won&#8217;t modify the core or include extensions that make the browser crap and thereby besmirch the Firefox name.<br />
All the addons at AMO that are available to the public have been through a review process and the fact that we&#8217;re providing them through our own secure site (integrated with our addons browser) we&#8217;re giving them some seal of approval.<br />
If we wanted to, I suppose we could invent another &#8220;gold star&#8221; seal of approval that keeps to even higher standards.  But the point is that we could make the approval process easy on ourselves and still ensure relative non-suckiness of branded browsers with these few simple rules.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peng&#8217;s links for Wednesday, 28 May &#187; lolcat.us</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1021</link>
		<dc:creator>Peng&#8217;s links for Wednesday, 28 May &#187; lolcat.us</dc:creator>
		<pubDate>Wed, 28 May 2008 22:42:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1021</guid>
		<description>[...] Kaply/Planet Mozilla: The Browser With No Name. Sorry, this isn&#8217;t a take on the old America tune, but a problem when people want to put out [...]</description>
		<content:encoded><![CDATA[<p>[...] Kaply/Planet Mozilla: The Browser With No Name. Sorry, this isn&#8217;t a take on the old America tune, but a problem when people want to put out [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert O'Callahan</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1020</link>
		<dc:creator>Robert O'Callahan</dc:creator>
		<pubDate>Wed, 28 May 2008 21:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1020</guid>
		<description>&gt; I’ve long thought that having two distinct entities (MoFo and MoCo), each with different purposes, both starting
&gt; with “Mozilla” is confusing as hell.

Maybe, but it&#039;s standard practice. Things could be worse --- my wife worked for a Pittsburgh company called &quot;Compunetix&quot;, which had a sibling company called &quot;Compunetics&quot; :-).

Something no-one raised is the need for Mozilla to be able to shut down sites distributing Trojaned Firefox builds. I don&#039;t see how they can do that if they give up trademark protection for Firefox.

Seems to me that the best thing Mozilla can do is strengthen the Mozilla brand.

Rob</description>
		<content:encoded><![CDATA[<p>&gt; I’ve long thought that having two distinct entities (MoFo and MoCo), each with different purposes, both starting<br />
&gt; with “Mozilla” is confusing as hell.</p>
<p>Maybe, but it&#8217;s standard practice. Things could be worse &#8212; my wife worked for a Pittsburgh company called &#8220;Compunetix&#8221;, which had a sibling company called &#8220;Compunetics&#8221; <img src='http://mike.kaply.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> .</p>
<p>Something no-one raised is the need for Mozilla to be able to shut down sites distributing Trojaned Firefox builds. I don&#8217;t see how they can do that if they give up trademark protection for Firefox.</p>
<p>Seems to me that the best thing Mozilla can do is strengthen the Mozilla brand.</p>
<p>Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJ Cabrera</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1019</link>
		<dc:creator>PJ Cabrera</dc:creator>
		<pubDate>Wed, 28 May 2008 18:40:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1019</guid>
		<description>New! Improved! Disney Iceweasel!

What nonsense. I&#039;m totally with you, Mike.</description>
		<content:encoded><![CDATA[<p>New! Improved! Disney Iceweasel!</p>
<p>What nonsense. I&#8217;m totally with you, Mike.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkaply</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1018</link>
		<dc:creator>mkaply</dc:creator>
		<pubDate>Wed, 28 May 2008 16:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1018</guid>
		<description>@lilmatt:

From http://www.mozilla.org/foundation/trademarks/policy.html :

Those taking full advantage of the open-source nature of Mozilla&#039;s products and making significant functional changes may not redistribute the fruits of their labor under any Mozilla trademark. For example, it would be inappropriate for them to say &quot;based on Mozilla Firefox&quot;. Instead, in the interest of complete accuracy, they should describe their executables as &quot;based on Mozilla technology&quot;, or &quot;incorporating Mozilla source code.&quot;</description>
		<content:encoded><![CDATA[<p>@lilmatt:</p>
<p>From <a href="http://www.mozilla.org/foundation/trademarks/policy.html" rel="nofollow">http://www.mozilla.org/foundation/trademarks/policy.html</a> :</p>
<p>Those taking full advantage of the open-source nature of Mozilla&#8217;s products and making significant functional changes may not redistribute the fruits of their labor under any Mozilla trademark. For example, it would be inappropriate for them to say &#8220;based on Mozilla Firefox&#8221;. Instead, in the interest of complete accuracy, they should describe their executables as &#8220;based on Mozilla technology&#8221;, or &#8220;incorporating Mozilla source code.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lilmatt</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1017</link>
		<dc:creator>lilmatt</dc:creator>
		<pubDate>Wed, 28 May 2008 16:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1017</guid>
		<description>@mkaply:
I disagree about Apache.  Apache actually has significant confusion.  You say Apache and you&#039;re talking about code.  I assume you&#039;re talking about httpd, but you&#039;re not.  You&#039;re talking about Tomcat or Cocoon or Axis or ?.  In addition, the Apache Foundation is significantly less visible to the public eye than MoFo.  I don&#039;t even know who chairs the thing, and I&#039;d like to think I&#039;m fairly knowledgeable in this area.

Joe User doesn&#039;t know anything about the foundation that writes the webserver and other middleware that lets him get to his favourite website.  While it is true that the general population is still confused and still enter http:// addresses into the Google search box, Joe User still has a heck of a lot better chance of knowing (and caring) about who makes the software he just launched to get to his favourite website.  Making the connection between &quot;Mozilla&quot; and the &quot;Mozilla Foundation&quot; is indeed a stretch, but I&#039;d think it&#039;s more likely than him making the Apache connection.

Of course Flock gets crazy amounts of goodness from mentioning both Mozilla _and_ Firefox.  If they didn&#039;t, they wouldn&#039;t.  I know lots of Mozilla folks mutter obscenities under their breath whenever they read on TechCrunch &quot;Flock, the social web browser based on Firefox&quot;, but it does put &quot;Firefox&quot; in &quot;print&quot; one more time, and continues to burn that wordmark into people&#039;s brand consciousness.  Flock undoubtedly gets more out of being associated with Firefox than the reverse, but as long as Flock isn&#039;t known as something bad like &quot;the spyware browser&quot; the reverse association _is_ good for Firefox.

Also, I believe you _can_ say &quot;based on the same code as Firefox&quot;.  Flock does this today.  You just can&#039;t say &quot;Flock Firefox&quot; or something similarly goofy and misleading.  You can&#039;t use their trademark as part of your own.  IANAL though, so maybe I&#039;m wrong here.

Again, I am _not_ speaking for or on behalf of Flock, and I don&#039;t always agree with what they do.  They just pay my salary and I still get to work on Mozilla stuff.

@raccettura:
Unfortunately you can&#039;t realistically monetize an extension as a product (yet).  If I made an innovative and popular extension (think say, Firebug), but in order to pay the salaries of the devs who wrote it, the extension also changed the Google affiliate code in the search box, I suspect it wouldn&#039;t be looked upon too kindly.  If someone comes up with a good business model for extensions, I&#039;d love to hear it.</description>
		<content:encoded><![CDATA[<p>@mkaply:<br />
I disagree about Apache.  Apache actually has significant confusion.  You say Apache and you&#8217;re talking about code.  I assume you&#8217;re talking about httpd, but you&#8217;re not.  You&#8217;re talking about Tomcat or Cocoon or Axis or ?.  In addition, the Apache Foundation is significantly less visible to the public eye than MoFo.  I don&#8217;t even know who chairs the thing, and I&#8217;d like to think I&#8217;m fairly knowledgeable in this area.</p>
<p>Joe User doesn&#8217;t know anything about the foundation that writes the webserver and other middleware that lets him get to his favourite website.  While it is true that the general population is still confused and still enter http:// addresses into the Google search box, Joe User still has a heck of a lot better chance of knowing (and caring) about who makes the software he just launched to get to his favourite website.  Making the connection between &#8220;Mozilla&#8221; and the &#8220;Mozilla Foundation&#8221; is indeed a stretch, but I&#8217;d think it&#8217;s more likely than him making the Apache connection.</p>
<p>Of course Flock gets crazy amounts of goodness from mentioning both Mozilla _and_ Firefox.  If they didn&#8217;t, they wouldn&#8217;t.  I know lots of Mozilla folks mutter obscenities under their breath whenever they read on TechCrunch &#8220;Flock, the social web browser based on Firefox&#8221;, but it does put &#8220;Firefox&#8221; in &#8220;print&#8221; one more time, and continues to burn that wordmark into people&#8217;s brand consciousness.  Flock undoubtedly gets more out of being associated with Firefox than the reverse, but as long as Flock isn&#8217;t known as something bad like &#8220;the spyware browser&#8221; the reverse association _is_ good for Firefox.</p>
<p>Also, I believe you _can_ say &#8220;based on the same code as Firefox&#8221;.  Flock does this today.  You just can&#8217;t say &#8220;Flock Firefox&#8221; or something similarly goofy and misleading.  You can&#8217;t use their trademark as part of your own.  IANAL though, so maybe I&#8217;m wrong here.</p>
<p>Again, I am _not_ speaking for or on behalf of Flock, and I don&#8217;t always agree with what they do.  They just pay my salary and I still get to work on Mozilla stuff.</p>
<p>@raccettura:<br />
Unfortunately you can&#8217;t realistically monetize an extension as a product (yet).  If I made an innovative and popular extension (think say, Firebug), but in order to pay the salaries of the devs who wrote it, the extension also changed the Google affiliate code in the search box, I suspect it wouldn&#8217;t be looked upon too kindly.  If someone comes up with a good business model for extensions, I&#8217;d love to hear it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkaply</title>
		<link>http://mike.kaply.com/2008/05/28/the-browser-with-no-name/#comment-1016</link>
		<dc:creator>mkaply</dc:creator>
		<pubDate>Wed, 28 May 2008 16:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.kaply.com/weblog/?p=150#comment-1016</guid>
		<description>@Robert:

I assume you are referring to Netscape.

Netscape chose to &quot;over customize&quot; the browser. If they had just created a set of customizations on top of Firefox and not tried so hard to be a completely different browser, they might have succeeded. Especially if real Firefox code was what got updated behind the scenes.

Anytime you set yourself up where you have to go through a lot of effort to compile your own browser, set up your own update servers, etc., you&#039;re never going to be current.

And I agree with sticking to extensions/themes to update the browser.</description>
		<content:encoded><![CDATA[<p>@Robert:</p>
<p>I assume you are referring to Netscape.</p>
<p>Netscape chose to &#8220;over customize&#8221; the browser. If they had just created a set of customizations on top of Firefox and not tried so hard to be a completely different browser, they might have succeeded. Especially if real Firefox code was what got updated behind the scenes.</p>
<p>Anytime you set yourself up where you have to go through a lot of effort to compile your own browser, set up your own update servers, etc., you&#8217;re never going to be current.</p>
<p>And I agree with sticking to extensions/themes to update the browser.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  mike.kaply.com/2008/05/28/the-browser-with-no-name/feed/ ) in 0.35425 seconds, on May 21st, 2012 at 8:36 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 21st, 2012 at 9:36 am UTC -->
