We provide pre-compiled Open Source binaries for Solaris, HP-UX, AIX, IRIX, Tru64 UNIX, and Redhat Linux. Our distribution is called the "Open Source Collection". We would like to include Mozilla Thunderbird in our distribution. Is it possible to do this with the enigmail extension as part of our binary package?
You would need to do this under the "Community Edition" rules of the Trademark Policy: http://www.mozilla.org/foundation/trademarks/policy.html which allow you to include any extensions available from http://update.mozilla.org. Enigmail is one such extension: https://addons.update.mozilla.org/extensions/moreinfo.php?application=thunderbird&id=71 Gerv
Ok, thanks. We'll do this. Even if we didn't include enigmail, our other changes fall under the "Community Editions" requirements. We'll make sure not to use the default Firefox/Thunderbird logos. Regarding the name of our Firefox or Thunderbird product, the "Community Editions" requirements state we must call it "Firefox Community Edition[blah]" and "Thunderbird Community Edition[blah]", respectively. When our customers install our binary packages, they use the generic name of the product. So, to install GNOME, they run: $ pkg-inst gnome and to install KDE, they run: $ pkg-inst kde Because of the Firefox/Thunderbird name requirement, they must use: $ pkg-inst firefox-community-edition[blah] This seems rather cumbersome. Can we use the terms "TWW Firefox" to identify Firefox, "TWW Thunderbird" to identify Thunderbird, and "TWW Mozilla" to identify the Mozilla Suite? Our customers would then install as follows: $ pkg-inst tww-firefox $ pkg-inst tww-thunderbird $ pkg-inst tww-mozilla Last is the name of the binary package to the package management system. In the case of our RPM packages for Redhat Linux, are the following names acceptable: TWWfirefox[version], TWWthunderbird[version], TWWmozilla[version]? On AIX, a "." must be placed after "TWW".
Those package names are fine. Gerv
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.