Distribute a XUL Application using Firefox binary
<p>I'm going to release a XUL Application to my users. It's freeware (and maybe it will be opensource-ed later). Previously I used to package it with XULRunner and ship them all to the end user. Now I have to use <code>firefox -app /path/to/application.ini</code> instead.</p>

<p>However, these slight modifications are required:</p>

<ol>
<li><p>I'd like to remove all unnecessary files and directories. Including these directories: <code>browser, components, defaults, dictionaries, gmp-clearkey, icons, webapprt</code>, and almost all <code>.ini</code> files. This is to save memory (around 18MB).</p></li>
<li><p>I want to rename <code>firefox</code>, <code>firefox.app</code> and <code>firefox.exe</code> to something else. Also, I want to change (or remove) the default firefox icon.</p></li>
<li><p>On Mac, there is an extra step. I'd like to remove 32-bit code from <code>XUL</code> library, <a href="http://hints.macworld.com/article.php?story=20050810112422666" rel="nofollow">using <code>ditto</code> command</a>. This will save more than ~60Mb according to my tests. This is extremely useful as I don't want to have both 32-bit and 64-bit on the same bundle.</p></li>
</ol>

<p>Do these modifications require Mozilla's written permission?</p>

<p>There is some information on this page: <a href="https://www.mozilla.org/en-US/foundation/trademarks/policy/" rel="nofollow">Mozilla Trademark Policy</a>. However, I can't tell whether they require written permission or not.</p>

<p>I got this answer after contacting <code>trademarks AT Mozilla dot com</code>:</p>

<blockquote>
  <p>If you are shipping a modified version of Firefox, <strong>these steps are
  required</strong> :-) You may not brand it as Firefox in any way. As long as you
  make that change, <strong>you can make whatever other changes you want</strong>. That's a freedom given to you by the open source licenses; you don't need our
  permission.</p>
  
  <p>You will, of course, have to abide by the open source licenses governing
  our code, for example by telling your users where to get the source code
  of any MPLed code and Modifications. See:
  <a href="https://www.mozilla.org/MPL/2.0/FAQ/" rel="nofollow">https://www.mozilla.org/MPL/2.0/FAQ/</a></p>
</blockquote>

licensing trademark open-source-software