Language Selection

English French German Italian Portuguese Spanish

Fox Wars: Debian vs. Mozilla

Filed under
Software

Would you believe that two open-source powers are battling over the Firefox Fox logo? Well, believe it.

Mozilla Corp. is insisting that when a Linux distributor includes its own variation of the popular web-browser, Firefox, with its operating system, it must pass any customized code by Mozilla before using its Firefox name or Fox logo.

This is pretty straightforward. Mozilla owns the trademark on the name and logo, so they need to protect it. The company also needs to make sure that when someone clicks on "Firefox," they're running Mozilla-approved Firefox. After all, if something goes wrong with Firefox, Mozilla's programmers want to know that something went wrong with their code rather than someone else's patch.

Debian doesn't see it this way.

Full Story.

Further from the mainstream

This seems to be another example of developers and others deciding that it's easier to beat Debian than join it. :waves:

It's hard work enough leaving the mainstream to use Linux and other open source software without leaving the open source mainstream.

Far out.

For seekers only

Imagine other open-source apps doing this

From the Mozilla Trademark Policy:

Quote:
Serious Modifications

Those taking full advantage of the open-source nature of Mozilla'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 "based on Mozilla Firefox". Instead, in the interest of complete accuracy, they should describe their executables as "based on Mozilla technology", or "incorporating Mozilla source code." They should also change the name of the executable so as to reduce the chance that a user of the modified software will be misled into believing it to be a native Mozilla product.

There are two problems Debian has with Firefox. First, its logo isn't free software as defined by the Debian Free Software Guidelines. So, it's shipped with a modified logo. Mozilla doesn't approve. They say, ship it with the original logo, or don't call it Firefox. Apparently, that's a "serious modification."

Second, Mozilla demands that Debian submit any and all patches made to the source provided by Mozilla for prior approval. Apparently, Debian's patches amount to more "serious modifications" (at least in the eyes of the Mozilla people).

Now, imagine that every open-source app made the same demands. Want to call it The GIMP? Use our new copyrighted logo and pass your patches through us. How about OpenOffice.org? AbiWord? Pan? You can see how there'd be a real mess if everyone took the same attitude that Mozilla's taking.

I'm not saying Mozilla doesn't have the right to defend its trademarks. However, it does seem to be taking a line that is definitely not in the spirit of the open source community here.

--
><)))°> Debian/Kanotix: http://kanotix.com

re: Imagine...

Yes, how dare the Mozilla Foundation after providing untold man-hours and real hard-dollars developing (and supporting) one of the more successful open-source projects declare that they want to keep QC in-house.

To top it off, they have the audacity to demand that their effort is marketed by having uniform branding.

Gosh, you'd think they were trying to present a professional and polished application to the world instead of the normal half-assed, eternally half-finished, ill-supported, ego-centric driven, garage band-esque app that the other 95% of the open source projects do.

Indeed, when your for-profit

Indeed, when your for-profit corporation's making millions of dollars in revenue based on the hard work of all those non-paid coders, it sure is important to protect that revenue-producing asset. What's a for-profit subsidiary (Mozilla, Corp.) of a non-profit organization (Mozilla Foundation) going to do with all that money, anyway? Why not hire some lawyers?

Seriously, I can understand Mozilla's position. I can understand Debian's position. Unfortunately, there doesn't seem to be much compromising going on. I'd prefer to see both parties work together to reach an amicable solution.

Ultimately, Firefox is open-source, so Debian can take the code and release it under another name. Despite what the Mozilla guy said, it's not like they change it a whole lot.

(By the way, if you're tired of being stuck with those crappy "95% of the open source projects," there is this other operating system called "Windows" you might be interested in.)
--
><)))°> Debian/Kanotix: http://kanotix.com

Why keep the patches?

I can see both arguments. The flaw in Debian's stand is that if Debian has genuine improvements to make, they should go upstream to Mozilla anyway.

Arguing about whether a logo is free software seems like a silly way to waste everyone's time.

For seekers only

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Thunderbolt 3 in Fedora 28

  • The state of Thunderbolt 3 in Fedora 28
    Fedora 28 is around the corner and I wanted to highlight what we did to make the Thunderbolt 3 experience as smooth as possible. Although this post focuses on Fedora 28 for what is currently packaged and shipping, all changes are of course available upstream and should hit other distributions in the future.
  • Thunderbolt 3 Support Is In Great Shape For Fedora 28
    Red Hat developers have managed to deliver on their goals around improving Thunderbolt support on the Linux desktop with the upcoming Fedora 28 distribution update. This has been part of their goal of having secure Thunderbolt support where users can authorize devices and/or restrict access to certain capabilities on a per-device basis, which is part of Red Hat's Bolt project and currently has UI elements for the GNOME desktop.

New Heptio Announcements

Android Leftovers

New Terminal App in Chome OS Hints at Upcoming Support for Linux Applications

According to a Reddit thread, a Chromebook user recently spotted a new Terminal app added to the app drawer when running on the latest Chrome OS Dev channel. Clicking the icon would apparently prompt the user to install the Terminal app, which requires about 200 MB of disk space. The installation prompt notes the fact that the Terminal app can be used to develop on your Chromebook. It also suggests that users will be able to run native apps and command-line tools seamlessly and securely. Considering the fact that Chrome OS is powered by the Linux kernel, this can only mean one thing. Read more