Slashdot Mirror


IceWeasel — Why Closed Source Wins

engtech writes, "There's been some hype about the Debian fork of FireFox called IceWeasel. Politics aside, this is a bad idea because it fragments the user base, divides the focus, and opens the path for Microsoft and Internet Explorer 7 to regain marketshare."

77 of 551 comments (clear)

  1. Seamonkey by El_Muerte_TDS · · Score: 5, Insightful

    Just like how Firefox fragmented the Mozilla userbase?

    1. Re:Seamonkey by Anonymous Coward · · Score: 5, Funny

      Linux users talking about fragmentation? Never heard of that before. Anyway, I'm off to distrowatch to download my 643rd distro. See you guys later.

    2. Re:Seamonkey by rolfwind · · Score: 5, Insightful

      But Firefox is installable on a ton of platforms.

      Ice Weasel sounds like it will be only installable on Debian, perhaps Debian-descended platforms like Ubuntu. Of course, since it's open source, anyone can port it to other platforms, I suppose. But why bother, all Ice Weasel is, is Firefox devoid of any nonfree trademarked art. And any updates to Firefox will be bought to Iceweasel.

      But there are already other variations of Firefox, like Swiftfox. Firefox will be the main flavor for a long time.

      The only way a fracture in the community will happen is if the releases are not compatible with each other, but the projects don't sound like they will develop on their own, but always staying with the main branch of Firefox. They can't really afford not to.

    3. Re:Seamonkey by Firehed · · Score: 4, Interesting

      IceWeasel is only Firefox without the logos. The guys at Debian don't want anything that's not completely Free (as in speech), and Firefox's logos are copyrighted. Mozilla says you can't create a Firefox distro with the same title if it doesn't have the logos. So they changed the name.

      --
      How are sites slashdotted when nobody reads TFAs?
    4. Re:Seamonkey by Anonymous Coward · · Score: 5, Insightful
      How are sites slashdotted when nobody reads TFAs?

      It's not that nobody reads them. It's just that the intersection of (dotters who read the articles) and {dotters who post} is the empty set.

    5. Re:Seamonkey by djimi · · Score: 3, Insightful

      Interesting analogy, but I think it's a bit off. Text editors "create" text -- which all of them will see. There really isn't variation in the grand scheme of things. The differences are the keystrokes & interface that people like one way or another. On the other hand, a web browser is a content viewer, and the web is forever changing what we can and will see & hear. Text really isn't changing is it? Web "Compatibility" & standards of experience across platforms is the debate.

      --
      Vox et praetera nihil
    6. Re:Seamonkey by quanticle · · Score: 2, Insightful

      No, the analogy isn't off at all. As long as this "IceWeasel" or whatever uses the same Gecko rendering engine as Firefox, it'll be able to display all of the same things that Firefox does. Unless the Debian folk deliberately go and screw with the rendering engine or the plugin manager, IceWeasel will maintain perfect compatibility with Firefox.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    7. Re:Seamonkey by Fordiman · · Score: 2, Interesting

      Ah, correct me if I'm wrong, but IceWeasel is just Firefox with different branding, ne?

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    8. Re:Seamonkey by zsau · · Score: 4, Informative

      Actually, the Debian version of Firefox contains various patches which the Mozilla people aren't happy about (including security patches--Debian wants to keep versions in Debian/Stable secure, but Mozilla wants everyone to use the latest version). Iceweasel is a fork that doesn't intend to diverge very far from the original codebase, but a fork it is nonetheless.

      --
      Look out!
    9. Re:Seamonkey by Schraegstrichpunkt · · Score: 3, Insightful
      Port? Debian is Linux.

      This isn't the 1990s. The "Linux distros" are now quite different from each other, and often binary-incompatible in some ways. Granted, it's very easy to port software between them (if you have source code, which you usually do), but they are most definitely different OSes now.

      There are (or will soon be) more similarities between e.g. Debian GNU/Linux and Debian GNU/kFreeBSD than between Debian GNU/Linux and Mandriva Linux or Fedora Core.

    10. Re:Seamonkey by Arker · · Score: 4, Informative

      It's a little more than that. Debian maintains a stable branch, and when firefox (or any other app) releases a new version, debian stable sticks with the old one, but backports any security and stability work. This appears to be what the mozilla folks have a problem with - when they release a new version they want everyone to move to it. Debian just doesn't work that way though. They maintain their stable version independently, and do a damn good job of it - security work gets backported, but new features (statistically suspect to introduce new issues that won't be discovered or fixed for awhile) don't. Mozilla says they can't use the name and logo, so they're going to call it iceweasel now. But other than that, it's really a continuation of what they've *always* done with this and every other upstream package. You can call it a fork if you want, but if it's a fork it's a parrallel fork and it's not starting now, it's been going for many years.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    11. Re:Seamonkey by rahlquist · · Score: 2, Interesting

      ::feeding troll:: Yeah, youre right, and I can take the FF source and recode it to delete 30 meg of files from you disk for every page you pull up. And still use the logos! Oh wait no, I cant that would give FF a bad name and they are trying to protect their name. I guess since Debian is so much more 'free' I will just make my own distro that deletes itself and they wont care to protect their reputation.

      --
      Sick of stupidity? http://www.patentlystupid.com
  2. Err by republican+gourd · · Score: 5, Insightful

    Exactly *how*, is Microsoft going to capitalize on a fracture of Firefox... within *Debian*? This doesn't touch the userbase that is competing with IE etc whatsoever.

    1. Re:Err by westlake · · Score: 3, Insightful
      Exactly *how*, is Microsoft going to capitalize on a fracture of Firefox... within *Debian*?

      "Iceweasel" is a name chosen out of pure spite.

      What kind of message do you think this sends to the small business and enterprise markets about the maturity of the FOSS community?

  3. Missing the point... by roster238 · · Score: 5, Informative

    The point of open source software is to allow users the freedom to modify the code to meet their needs. If you restrict users to one single unmodified browser for the sake of unity then we have met the enemy and he is us.

    --
    I swear I didn't know it was loaded...
  4. My Thoughts on the Issue by AKAImBatman · · Score: 4, Insightful
    My first reaction to this entire situation is that, it's more complicated than it looks. On one hand, Mozilla doesn't want binaries being redistributed that they didn't build themselves. On the other hand, Debian wants to be able to handle source patches of their entire source tree. The result is that you get two competing ideals, both seemingly valid, creating this bit of a mess.

    After stepping back for a moment, however, I realized that the problem isn't as complex as it seems. In fact, I think it highlights something I've been saying for a while: Package systems under Linux are a broken concept.

    When I was working on the Linux Desktop Distribution of the Future article, I received quite a bit of criticism for calling the package management systems a major source of breakage. In the follow-up, I was forced to point out that complete system packaging creates a massive, monolithic code base:

    There is no way to fully test a package repository. Since every package modifies the base system, the only way to prove that a package will work is to test it against every possible package configuration available! In case you're wondering, the math for that is P * P, where P is the number of packages available. A mere 100 packages could potentially result in 10,000 available configurations! That's a lot of potential for breakage! Now consider that most distros today have thousands of packages under their care, and the number is not declining.

    Minor Correction: Reader Bradley Momberger has correctly pointed out that my math was a little screwy on this one. The correct forumla for the number of combinations is 2^P, which is actually quite a bit worse. 100 packages yields 1.26e30 possible combinations!


    What we're seeing here is a legal extension of that same problem. By integrating the software into the codebase, Debian is attempting to take legal responsibility for the software. Yet the software provider (Mozilla) is already handling that responsibiity, and does not wish to give it up. On any other operating system, the binaries would get bundled (or not at all, if they're too untrustworthy) as a self-contained application, and the software provider would be allowed to continue handling updates. End of story.

    In this case, Debian wants this software to be managed like all the other software they manage. Which means that taking responsibility becomes easier for them, rather than allowing the software producer to handle their own software. While this theoretically allows for a more cohesive system, that cohesiveness only goes as far as the packages checked into Debian's repository. Mozilla should be outside of that repository, but any software that's not in the repository is not well supported by the packaging system. Ergo, the process breaks down.

    That's just my thoughts, anyway. I'm sure many will disagree. Loudly. And rudely. Oh well. :P
    1. Re:My Thoughts on the Issue by Bruce+Perens · · Score: 2, Interesting
      I'm afraid that your point "it's not possible to fully test a package repository" is simplistic.

      It's not even theoretically possible to fully test an individual program in the time you would have to do so - the complexity limit is that low. This has spurred the development of functional programming, as the only programming paradigm that has a hope of mathematical verification in a reasonable amount of time, but that has not reached the point of practicality for most development.

      A package repository is a collection of programs, generally without much interaction between them except for dependencies. The fact that they are in a single repository does not increase their complication.

      Indeed, multiple repositories make the problem worse because the dependencies can get out of phase. The few things that you can test with a single repository, that all of the programs install correctly without missing dependencies and collission between packages, go out the window once there are multiple repositories. Just look at all of the problems people have installing packages in Red Hat or Fedora from an unofficial repository. Those things go out of phase with every release.

      The problem is that Firefox isn't even Open Source until you change the name, because they use trademark law to prohibit the distribution of modified versions. Obviously, they're going overboard, and should establish a trust relationship with the Debian packagers. This hasn't anything to do with repositories.

      Bruce

    2. Re:My Thoughts on the Issue by nine-times · · Score: 2, Insightful

      After stepping back for a moment, however, I realized that the problem isn't as complex as it seems. In fact, I think it highlights something I've been saying for a while: Package systems under Linux are a broken concept.

      Funny, but when I stepped back for a moment, I didn't see a problem anymore.

      It seems to me that there are people who like Firefox and see this as some kind of an attack from Debian people. There are people who like Debian and see this as Mozilla trying to inhibit their freedom. People get angry, and yadda yadda yadda, people start coming up with wild theories and yelling at each other on Slashdot.

      I'm not a developer. I try to keep current on what's going on, but I have no special insight. After reading the news on this, and trying to look at the big picture, I don't see why some people are freaking out. Am I missing something?

      As I understand it the Debian people wanted to do certain things with Firefox, and the Mozilla people said, "Well, you can't do that and still call it Firefox." And then the Debian people said, "Ok. We'll call it something else then." Both parties are satisfied. Who's hurt by this again?

      Ah... the open source community is "fragmented". Right. But this happens all the time. The Linux kernel is modified by different distributions. Some people use KDE, while some use Gnome. Some people use OOo for word processing, some use Abiword. Konquerer, Firefox, Epiphany, etc. Diversity is one of the strengths of open-source software. I'm glad. If Iceweasel ends up being very similar, most people won't know the difference. If it's very different, then people will use whichever is better for them. If Iceweasel becomes substantially better, then we can all benefit from the improvements.

      So what is the problem here again? Anyway, it's BAD if we all use the same browser. It encourages web developers to use browser specific hacks. It makes that single browser an easy target for malware writers. The best possible scenario isn't one open-source browser taking the place of IE, but that IE's market share gets divided up among many browsers. It doesn't matter which ones, so long as they're all standards-compliant so that web developers will be encouraged to write standard HTML/CSS.

  5. Ummm by bky1701 · · Score: 4, Insightful

    How does this make Debian users use IE?

  6. Paradox of Choice by Kelson · · Score: 3, Interesting

    The article brings up an interesting question: to what extent does having multiple choices "split the vote" (as the article put it)? Let's take two scenarios:

    1. Choose between IE and Firefox.
    2. Choose between IE, Firefox, Opera, IceWeasel, and Flock.

    Is someone more likely to choose IE in scenario 2 than scenario 1?

    Possibly yes, if the paradox of choice holds true. If the number of options paralyze your decision, you'll be more likely to stick with the status quo... which for Windows users means Internet Explorer."

    Should proponents of alternative browsers pick one to rally behind? If so, should it be Firefox? Would it be worth voting third-party (so to speak), but pooling resources to campaign for the lead challenger?

  7. Wrong by dedazo · · Score: 4, Interesting
    I might be mistaken here but the whole stupid "Iceweasel" thing is exclusive to Debian. The author's contention that this will "hurt" adoption of "open source" because choice is confusing to end users might by correct in some instances but would a Windows version of Iceweasel ever see the light of day? I don't think the Debian "you're not free enough for us" hacks will also create a "more free" port of Iceweasel that runs on Windows. I can't see that happening.

    No, the problem will be relegated to people who use Linux, and more specifically, Debian and derivatives (I guess). Issues with extensions and themes not working for whatever reasons and so on are possible, I suppose, but people who use Firefox on other platforms wouldn't even see Iceweasel at all.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  8. marketshare? by teslar · · Score: 5, Insightful
    and opens the path for Microsoft and Internet Explorer 7 to regain marketshare
    Pray, do tell me again, what exactly is the current marketshare of IE7 on debian?
  9. Re:Debian marketshare = ??? by joe+155 · · Score: 2, Insightful

    Indeed, this isn't even like all Linux users are being forced to move, it's still the default on Fedora and Ubuntu (I think)... Not only that but Debian, at least the last time I heard, wasn't going to create something completely different, they just wanted a different name and logos - I bet most of the code would be the same.

    --
    *''I can't believe it's not a hyperlink.''
  10. Not exactly related, but... by suparjerk · · Score: 5, Funny

    That is a disturbing logo.

    --
    I caught the Mountain Wumpus! He gave me his treasure chest ($100) to let him go free again.
  11. Re:it's bad either way by XanC · · Score: 5, Insightful

    Debian's goals are to quickly patch security problems, and to backport fixes to versions declared stable for the benefit of their users.

    Both these goals a) good, useful, helpful, and worthwhile, and b) in conflict with the wishes of the Mozilla Corporation.

    Perhaps Mozilla could give a little here, instead of Debian. Hmm?

  12. Firefox and Ubuntu by Rik+Sweeney · · Score: 3, Interesting

    I don't know what's happening with Firefox and Ubuntu, but I do know that if it does get replaced with IceWeasel, I'll either

    1. Download it from some 3rd party website
    2. Download the source, compile it, package it up and host it on my website

    And to be honest I'd encourage everyone else to do the same. I'm really not trying to troll, I just don't want to one day find a vulnerability or incompatibility in IceWeasel that's not in Firefox.

  13. Debian vs. Mozilla.COM by Bruce+Perens · · Score: 5, Interesting
    Unfortunately, the Firefox.com folks didn't leave Debian a choice. The current terms under which they distribute Firefox make it not Open Source at all as long as you call it "Firefox". The Mozilla.com folks are using trademark law to enforce that no versions of Firefox can be modified and still called "Firefox".

    Debian can't carry the browser in their distribution under the "Firefox" name if they are to have any ability to tune it for their distribution or to fix bugs before the Firefox team makes their own release.

    The software will be essentially identical to Firefox. I think we may see other distributions doing the same thing, as it's just not tenable for ANY distribution to contain software that it can't service.

    And then hopefully we'll see the Firefox team go back to the policy they negotiated with the Debian organization only a year ago, before their new .com folks took charge, which was that they would agree to trust some people to modify the code and not make a fuss about it.

    The author of the quoted piece is being absurd to say this is "Why closed-source wins". It's not about fragmenting the user base, it doesn't have much effect on the brand and won't be very visible to naive users. It's just turning an obnoxious trademark policy that is flagrantly in conflict with the purportedly Open Source nature of the product on its head.

    Bruce

    1. Re:Debian vs. Mozilla.COM by Anonymous Coward · · Score: 2, Informative

      http://www.debian.org/logos/

      Debian Official Use Logo License

      Copyright (c) 1999 Software in the Public Interest

            1. This logo may only be used if:
                          * the product it is used for is made using a documented procedure as published on www.debian.org (for example official CD-creation)
                          * official approval is given by Debian for its use in this purpose
            2. May be used if an official part of debian (decided using the rules in I) is part of the complete product, if it is made clear that only this part is officially approved
            3. We reserve the right to revoke a license for a product

      Permission has been given to use the official logo on clothing (shirts, hats, etc) as long as they are made by a Debian developer and not sold for profit.

    2. Re:Debian vs. Mozilla.COM by Natasha · · Score: 2, Informative

      I can understand the need to tune it or fix bugs, but it seems to go beyond that. On the fresh Ubuntu install I recently did, my Firefox has a fun "feature". If you move the mouse over a button, the button goes yellow and flat. And it doesn't change back when you move the mouse away. Hardly what I would describe as tuning or fixing. My first thought when I saw it was "stupid Firefox". My second thought was "It doesn't do that on Windows". Only after that did I think, "Oh, must be a Ubuntu change". Is that really the experience the Mozilla folks want people to have when they interact with the browser for the first time.

      I think the Mozilla folks should probably adjust the licensing terms on the artwork, but it does reflect badly on them when distros make changes that affect the user experience.

    3. Re:Debian vs. Mozilla.COM by Bruce+Perens · · Score: 3, Insightful
      Right, Mozilla.com not Firefox.com .

      Of course nobody likes the name. You're not supposed to. It's Firefox turned on its head. It's supposed to be annoying to the Firefox developers, to spur them to do something about this.

      Bruce

    4. Re:Debian vs. Mozilla.COM by Bruce+Perens · · Score: 4, Informative
      Dear AC, You quoted Debian's "official use" logo policy, but I think you missed the point. Debian publishes an "unofficial use" logo which allows consistent branding to be used by modified versions. And if you don't call your product "Official Debian", you can modify it.

      A lot of thought was put into that. It would be fine if there was an "Official Firefox" and "Firefox", similarly to the way Debian handles their trademark.

      Bruce

    5. Re:Debian vs. Mozilla.COM by Bruce+Perens · · Score: 2, Insightful
      It sounds like a bug. But you haven't checked if it's in a plugin or not. Surprisingly, you can still use the Firefox name and load a plugin that makes a total wreck of Firefox. That's hardly a consistent policy.

      If Ubuntu put a glaring bug in the code the Firefox folks have reason to complain. Just complain, not ban use of their name entirely. They should have an official and non-official use logo policy, as Debian has. That allows people to use consistent branding on modified versions.

      Bruce

    6. Re:Debian vs. Mozilla.COM by aconbere · · Score: 4, Funny

      Bruce -

      Supprisingly that option _IS_ available in firefox as a compile time switch. However (and the irony doesn't escape me here) Debian has patched firefox in such a way that this switch no longer works! Hurah!

      ~ Anders

    7. Re:Debian vs. Mozilla.COM by garutnivore · · Score: 2, Insightful

      That's only part of the problem. Even with the switch, you still can't call your built binary "Firefox" in any way shape or form if you make any modifications to it. I really fail to see how "deer park" and "bon echo" would be better names than replacing all of that crud with "IceWeasel".

    8. Re:Debian vs. Mozilla.COM by Anonymous Coward · · Score: 2, Funny

      It's supposed to be annoying to the Firefox developers, to spur them to do something about this.

      Brian: Brothers! Brothers! We should be struggling together!
      ???: We are! Ohh.
      Brian: We mustn't fight each other! Surely we should be united against the common enemy!
      Everyone: The Judean People's Front!!??

    9. Re:Debian vs. Mozilla.COM by Natasha · · Score: 2, Informative

      *doh* You're right. I didn't even think about plugins and sure enough, I've got a plugin that turns submit buttons yellow if the form is secure. Since that's the only issue I've found while using Firefox so I don't see what Mozilla could be complaining about.

    10. Re:Debian vs. Mozilla.COM by Bruce+Perens · · Score: 2, Informative
      Oh.

      Unfortunately, Bon Echo and Deer Park are version names. We need non-version-dependent stable branding that unifies modified versions and the official firefox into a consistent branding program. The Official Debian CD (really the only place Debian uses their official-use logo) and their unofficial-use logo seem to do this well.

      Thanks

      Bruce

    11. Re:Debian vs. Mozilla.COM by asuffield · · Score: 3, Insightful
      Debian wants to change the code-base of Firefox. Fine. allowed.


      I'm sorry, you lose. This is not allowed - unless you remove the firefox artwork and change the name, or submit to specific per-change licensing from Mozilla (which Debian's policies do not permit, for a number of practical and philosophical reasons). That is what Mozilla have said to Debian. If you do not agree with this, feel free to take up the issue with Mozilla, because Debian will presume them to be correct on any matters regarding what is and is not acceptable here.

      Debian wants to get a free ride


      This is not at all true. Debian has been saying to the Mozilla crew for a long time (since several years ago when this first came up): "we'll leave the name alone if you don't give us a reason to change it, but we'll change it if you want". Mozilla previously said "okay, leave it alone for now" but now they came back to Debian and said "you've got to change it now". At no point did Debian attempt to "get a free ride", they just did exactly what the Mozilla developers asked for.

      Im sure you will counter with: security patches after mozilla.org stops supporting $VER_NOW dont qualify. Only partially true: with IBM/RedHat/Novell supporting mozilla 1.4 long after .org dropped it


      This option has never been offered by Mozilla in respect of Debian's support for Firefox 1.0 (which is still having security fixes applied in Debian, and which is known to have users that are either unable or unwilling to upgrade).

      Let us recap with a statement from Mike Connor, speaking officially on behalf of Mozilla (on the subject of whether or not Debian can call the version it ships "Firefox"):

      At the time, we obviously
      weren't taking that part seriously. We are now, and we're saying its
      not ok.

  14. This doesn't hurt Firefox by Anonymous Coward · · Score: 2, Insightful

    It hurts Debian. They could simply have moved it to non-free, and many would have respected Debian for sticking to the letter of the DFSG. But instead, they chose this snarky little twist.

    What do I care, I use Ubuntu. Debian is becoming the new XFree86.

    1. Re:This doesn't hurt Firefox by Anonymous Coward · · Score: 3, Insightful

      They could simply have moved it to non-free

      No they couldn't. The objective of the Debian Project is to create the universal free operating system. The existance of the non-free branch is a minor evil, and there have been discussions not too long ago to remove it.

      What do I care, I use Ubuntu. Debian is becoming the new XFree86.

      You sir are an ignorant. Read the words of Mark Shuttleworth when he says that I'm of the opinion that Ubuntu could not exist without Debian . Debian is a much bigger and important project than you think.

      I'm appalled that people detests someone or something for standing up for their rights and their freedom, I don't understand why.

    2. Re:This doesn't hurt Firefox by Russ+Nelson · · Score: 2, Insightful

      There are two issues here. First is that Debian ships a modified Firefox, which of course isn't really Firefox, but they thought it was okay to call it Firefox.

      Second is that, were they to have been shipping Firefox, the Firefox trademark graphic (which comes in a file) is also copyrighted, and not licensed for modification. Debian says that trademarks must be modifiable because they might be usable in a different trademark field. This problem is solvable, as you say, either by putting it in non-free, or by getting Mozilla to put a copyright license on the graphic which allows people to use it in unrelated trademark fields.

      --
      Don't piss off The Angry Economist
  15. Stop marginalizing us! by bunions · · Score: 4, Funny

    I am a proud IE-on-Debian user and there are millions* like me!

    http://www.tatanka.com.br/ies4linux/page/Main_Page

    *0.00005 millions

    --
    there is no need to sign your posts. this isn't usenet. your username is right there above your post. stop it.
  16. Re:it's bad either way by perlchild · · Score: 2, Insightful

    I am quoting from memory, but here's the situation in a nutshell:
    That's been tried, the core of the issue was that Mozilla included non-free(as per Debian's DFSG) images along with Firefox, presenting Debian with the two following options:
    1) Not distributing Firefox
    2) Finding a way to distribute Firefox without the offending image

    They picked two, which caused the uproar, which caused the request from Mozilla not to use the Firefox name if the non-free images weren't there. Debian said "We'll fork and use a new name".

  17. Re:Debian marketshare = ??? by LWATCDR · · Score: 4, Funny

    Hey those what 10,000 debian desktop machines will really mess things up for Firefox.
    I am a Linux user but let us all get a grip. Firefox on Linux is a tiny blip... Firefox on windows is where what scares Microsoft.
    Even then Suse, Fedora, Gentoo, Ubuntu, and Linspire all use Firefox.
    So I would rate this news as two yawns and a stretch.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  18. Microsoft? So what? by jonnythan · · Score: 2, Interesting

    No one told me that Free Software was about beating Microsoft at all costs.

  19. Re:Missing the point... Yourself by Anonymous Coward · · Score: 5, Insightful

    The Mozilla Foundation doesn't have a problem with Debian modifying FireFox. What they have a problem with is Debian modifying FireFox fairly significantly, yet continuing to call the product "FireFox". FireFox(tm) is a specific codebase, maintained by the Mozilla Foundation. I think they have every right to ask Debian to rename their fork, so that end users are not confused, thinking that bugs in Iceweasel are general FireFox bugs (in some cases, they may be, in other cases, not).

    I don't see anything wrong with asking someone who forks your codebase to use a different name to avoid confusion. What's the problem with that?

    Plus, there is this thing about Trademark law. If you don't actively police it, you can lose the right to the mark.

  20. Do all 6 Debian users care ? by SnapperHead · · Score: 2, Insightful

    Yes, the subject is slightly misleading. I am a Debian user, soon to be former Debian user. Not because of this, this has nothing to do with me switching distros (again). I am moving away because if the slow as balls release cycles. Even after its released, you are already behind by 6 months to a year.

    I only used Debian for apt. It totally blows away yum. But, with the slow ass release cycles I can't take it much longer.

    I wish more Distros would base on Debian, rather then base on Red Hat. I really don't care for RPMs.

    --
    until (succeed) try { again(); }
    1. Re:Do all 6 Debian users care ? by asuffield · · Score: 2, Informative
      I am moving away because if the slow as balls release cycles.


      This is a feature. A slow release cycle is a benefit in many environments - a high-end teaching environment, for example, absolutely can not be deploying a functionality-changing upgrade more than once a year, because you'll screw over all the work currently in progress if you do it in the middle of the academic year. A lot of businesses also need to keep disruption to a minimum, which means infrequent upgrades - any high end sysadmin will tell you that "upgrade" is synonymous with "downtime and more trouble tickets than usual". A distribution which forces you to upgrade often in order to maintain support is entirely inappropriate in such an environment.

      You are obviously not the target audience. Please hurry up and use something else so that we don't have to listen to you gripe about it any more. If you're using the wrong tool for the job then that's your own fault. (Quite what job requires using only software that is less than 6 months old is unclear, but I'll just assume that you do have a reason and aren't simply crazy)
  21. Re:it's bad either way by Trifthen · · Score: 2, Interesting

    That's what I was wondering. We're talking about Debian here, easily the slowest releasing distribution in the Linux world. Are they saying they can't submit patches to the Mozilla foundation so Mozilla can check the fixes for bugs or come up with a better patch, because they can't wait that long? Sure, Firefox is open source, but what Debian is distributing is not Firefox. It's somewhat sad Debian had to react in a petulant manner and come up with a childish reactionary name like "IceWeasel." I seem to remember them forcing vendors to remove "Debian" from their name, too...

    --
    Read: Rabbit Rue - Free serial nove
  22. Politics? by subreality · · Score: 2, Insightful
    Politics aside, this is a bad idea because it fragments the user base, divides the focus, and opens the path for Microsoft and Internet Explorer 7 to regain marketshare.


    No, trying to fight those things IS politics. The Debian project has never been interested in fighting those kinds of battles. They don't care about market share. They have a single focus: Making the best possible distribution, which can absolutely, no questions asked, be used by anyone for any purpose.

    I for one am glad they put those principles first. I don't want compromises for the sake of market share.
  23. Distros are response to configuration problems. by Kadin2048 · · Score: 3, Interesting

    I agree with you.

    However, I'm not sure that people haven't at least realized some of the underlying concepts behind your point before. The complexity of packaging systems is what leads to specialization in distros.

    It's possible to take Debian and install packages on it, and make almost anything you want. A PVR machine, a digital audio workstation, a web server, a firewall, whatever. You can do it (and frankly, it probably works well in all of those roles, because they're fairly well-tested).

    But rather than doing that, lots of people who want a machine in a particular role, don't just get "Linux" and then install a lot of packages on it, but get a particular, preconfigured distribution that already has a lot of packages installed and tested, and uses that.

    The diversity of distros is basically an attempt to take the huge number of possible configurations possible with Linux and its ecosystem of packages, and produce a smaller number of well-tested configurations. So rather than building your own digital audio workstation, you get a digital-audio-workstaion distribution that already has everything rolled together. It's convenient, and it's less likely to have bugs.

    So while I think that the diversity of packages is a source of possible conflicts because of the huge number of possible configurations, I don't think it's a totally insurmountable problem.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  24. opens the path for Microsoft... by joebooty · · Score: 3, Insightful

    "...and opens the path for Microsoft and Internet Explorer 7 to regain marketshare."

    This is a worthless mindset. The goal should be to release a good product that end users appreciate. Competition will make both products better.

  25. Re:it's bad either way by Al+Dimond · · Score: 4, Insightful

    As I understand it Debian does contribute patches back to Mozilla. But Debian wants to backport security fixes to versions of Firefox that Moz. Foundation no longer supports. I'm pretty sure this is true.

    As I understand it Mozilla used to let them call these versions "Debian Firefox" but now they don't anymore. I'm not entirely sure this is quite right. Also there's a DFSG issue that I don't remember the details of.

    Mozilla Foundation doesn't have to "deal with" Iceweasel at all, except to respond to all of this publicity. This looks "big-picture bad" to some people but to Debian keeping the stable branch secure is more important than Firefox advocacy. In other words, the "small-picture" disagreements that made this happen are actually the big picture.

    For most users there's not much of a reason to use package management for a program like Firefox. It's frequently-updated and for most people frequently-used, and it has an auto-update system if you use the official binaries. People will usually want the updated version. For people that have a good reason to stick with a really old version, or who don't use the browser enough to keep it updated independently of other software Iceweasel gives them their security backports. And I can understand why MoFo wouldn't want their trademark applied to software that's maintained by Debian.

  26. Re:Computer Hippies are the Worst by TheRaven64 · · Score: 3, Informative

    You may only use the FireFox trademark if you do not apply patches to FireFox. The Debian team want to apply security fixes and bug fixes to their packaged version. They can either do this and not call it FireFox, or not do it. If you were a Debian user, which would you rather they did?

    --
    I am TheRaven on Soylent News
  27. Re:it's bad either way by Anonymous Coward · · Score: 4, Informative

    Debian releases are slow. Debian security patches are lightning fast.

  28. Polarising the argument by delire · · Score: 5, Insightful

    If it is to be renamed then why not do it with some reference to the reason. A name like FreeFox or similar would at least maintain symbolic connection to the parent while underscoring that it is a wholly non-proprietary distribution of that parent. 'IceWeasel' sounds directly antagonistic of FireFox itself. If FireFox is hot, then it's alternative must be cold. It itself reads as a childishly extremist 'reaction' to what should otherwise be understood as a wise and considered move, for real and sane reasons.

    The sheer lack of foresight amazes me. For years afterward we'll be hearing damaging myths that "FireFox doesn't install on Linux". Newbies coming into IRC to ask how to install FireFox will be pointed to what's later knows as the longest running $TOPIC in history. 'IceWeasel' just adds needless noise for all those millions considering switching to a Linux OS. FireFox is arguably the most important FOSS application for the desktop, if only because of it's notoriety. The name itself is larger than the software it represents. fscking with this reveals new depths of disregard for the adoption of Desktop Linux more generally.

    1. Re:Polarising the argument by krmt · · Score: 3, Informative

      Trademark law requires that the name be different enough to not cause confusion. As a result, FreeFox or FireFaux or any of the other similar ones might cause problems and just result in Debian having to rename it yet again.

      --

      "I may not have morals, but I have standards."

    2. Re:Polarising the argument by Mr.+Hankey · · Score: 2, Interesting

      How about (and I don't intend to sound flip here) WebBrowser? Just a thought, since IceWeasel lends a rather unprofessional sound to the distribution. Many apps could use a name more descriptive of what they do, and if you get the chance to rename them with the author's blessing it wouldn't hurt to make them less ambiguous. I don't use Debian myself, but if I did I'd be more likely to install WebBrowser than IceWeasel.

      --
      GPL: Free as in will
  29. Re:it's bad either way by phoenix.bam! · · Score: 3, Insightful

    Debian aims to offer support for version of software that are in it's stable distro. Firefox 1.0.7 I believe is still supported by debian stable, yet mozilla has long stopped supporting it. Debian needs to be able to maintain a patch set to keep unsupported version of firefox stable and Mozilla is unwilling to budge on trademark enforcement (and well they shouldn't.)

  30. Re:it's bad either way by Intron · · Score: 4, Informative

    Except that the Mozilla developers work on what they want to do, not what you want them to do. Take a look at bug 33654 - TEXTAREA incorrectly applying ROWS= and COLS=. This was reported in 2000 (yes, 6 years ago) and makes forms not line up properly. If you were to fix this, you couldn't technically distribute your fixed version, because the firefox license prohibits it. Hence, iceWeasel.

    --
    Intron: the portion of DNA which expresses nothing useful.
  31. Re:Unofficial by Tacvek · · Score: 2, Insightful
    They're fine with you calling it an "unofficial" build of Firefox.
    Do you have any evidence of this? Their Trademark licence seems to forbid use of unapproved patches without completely removing Firefox from the name.

    Please point to a policy document that says that builds with random patches may call themselves: "Unoffical Firefox".

    --
    Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
  32. Misunderstanding trademark law by Bruce+Perens · · Score: 4, Informative
    Plus, there is this thing about Trademark law. If you don't actively police it, you can lose the right to the mark.

    I hear this repeated a lot. It's not true. If you allow your mark to become generic you can lose your right to it. Firefox is not at risk of this happening. Google is. You can be selective about enforcement as long as you don't allow the mark to become generic.

    Debian has handled this problem, for years, by having an official-use and an un-official-use logo for their own distribution. This allows people to package the program with modifications and still use consistent branding.

    Bruce

    1. Re:Misunderstanding trademark law by Russ+Nelson · · Score: 2, Insightful

      I hear this repeated a lot. It's not true. If you allow your mark to become generic you can lose your right to it. Firefox is not at risk of this happening. Google is. You can be selective about enforcement as long as you don't allow the mark to become generic.

      I have never EVER heard a lawyer say this. On the other hand, I have heard lawyers say that to hold a trademark, you must control the quality of the goods described. But what do lawyers know about the subject?? After all, this is the same Bruce Perens who thought that you could transfer a trademark independent of the goods it describes. Yes, yes, I know, we all get smarter as we get older; on the other hand your track record of understanding of trademark law is not exemplary.

      --
      Don't piss off The Angry Economist
    2. Re:Misunderstanding trademark law by Bruce+Perens · · Score: 2, Informative
      Oh, gee, Russ. It might be helpful if you were to actually provide some evidence to refute what I said, instead of just abuse. I know you call yourself "the angry economist", but it really seems that you're just angry.

      Actually, I have this from Pixar's head attorney, Larry Sonsini, some years ago. At the time, we were considering how much we needed to enforce the "Renderman" mark.

      But I looked at 14 USC 1064 (3), which says you can lose your trademark if:

      (3) At any time if the registered mark becomes the generic name for the goods or services, or a portion thereof, for which it is registered, or is functional, or has been abandoned, or its registration was obtained fraudulently or contrary to the provisions of section 4 or of subsection (a), (b), or (c) of section 2 for a registration under this Act, or contrary to similar prohibitory provisions of such said prior Acts for a registration under such Acts, or if the registered mark is being used by, or with the permission of, the registrant so as to misrepresent the source of the goods or services on or in connection with which the mark is used.

      If the registered mark becomes the generic name for less than all of the goods or services for which it is registered, a petition to cancel the registration for only those goods or services may be filed.

      A registered mark shall not be deemed to be the generic name of goods or services solely because such mark is also used as a name of or to identify a unique product or service.

      The primary significance of the registered mark to the relevant public rather than purchaser motivation shall be the test for determining whether the registered mark has become the generic name of goods or services on or in connection with which it has been used.

      And then 45 USC 1127 (way down the page, not sure of the paragraph numbering)
      Abandonment of mark.

      A mark shall be deemed to be "abandoned" if either of the following occurs:

      (1) When its use has been discontinued with intent not to resume such use. Intent not to resume may be inferred from circumstances. Nonuse for 3 consecutive years shall be prima facie evidence of abandonment. "Use" of a mark means the bona fide use of such mark made in the ordinary course of trade, and not made merely to reserve a right in a mark.

      (2) When any course of conduct of the owner, including acts of omission as well as commission, causes the mark to become the generic name for the goods or services on or in connection with which it is used or otherwise to lose its significance as a mark. Purchaser motivation shall not be a test for determining abandonment under this paragraph.

      This was on the web for you to look up.

      Bruce

  33. Re:Missing the point... Yourself by Kelson · · Score: 2, Informative
    Plus, there is this thing about Trademark law. If you don't actively police it, you can lose the right to the mark.

    Of course, they can actively police it *and* grant permission to use it. That didn't work in this case, because the conditions Mozilla placed on that permission weren't acceptable to Debian.

    Also, I seem to recall something in the DFSG such that licenses *must* be transferable to derived products. I suspect Mozilla's trademark license would have been specific to Debian, and therefore not qualify for the DFSG.

  34. Re:So let's see if I got this right... by Anonymous Coward · · Score: 2, Informative

    You may want to hit yourself with the cluestick. It's not that they don't want the logo changed (they don't). It's that they don't want the logo or name used on anything that hasn't been vetted by Mozilla - so no security updates for you unless they come from Mozilla. This is particularly a problem if a distribution wants to support older versions of the program by backporting fixes rather than updating the package. Other distributions will have to deal with this problem too if Mozilla doesn't change their stance; Debian is just the first to face it.

  35. What the DFSG says by Bruce+Perens · · Score: 3, Informative
    DFSG #4 explicitly says that an Open Source license can require you to change the name if you modify the product.

    That said, a well-designed trademark policy (like Debian's) provides a mark that they explicitly recommend that you to use if you modify the product, which does not throw their own branding out the window. The Mozilla.com people simply haven't thought that through sufficiently.

    Bruce

  36. Re:it's bad either way by entrylevel · · Score: 2, Insightful

    There is a very good reason to install Firefox via your distribution's package management system. If another packages relies on the Gecko libraries to embed a web browser (examples: Eclipse, Listen), and you installed Firefox manually, you'll wind up with two copies installed.

    Actually, on Ubuntu you'll probably wind up with both Mozilla and Firefox installed (grr), but you see my point.

    --
    Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
  37. It is interesting how the dialogue has changed by Infonaut · · Score: 3, Insightful

    Just a few years ago we were talking about making sure Open Source software provided users alternatives to proprietary software. Forking has always been an issue, but the gestalt view seemed to be that ultimately even in a forking situation, the better software would "win" in the sense that it would continue to be developed. The focus was not on defeating proprietary software in the marketplace, but in making truly great software.

    Now it's 2006. Linux is a huge force in the IT world. Firefox has stolen marketshare from IE. These nibbles of success have changed the dialogue, and now marketing is as important if not more important than diversity. Choice is good and all, but getting computer users to make "the correct choice" is perhaps now the ultimate goal. Consumers may become confused by so many browser choices! Ah yes, let's not confuse them. Let's market and package Firefox so the choice will be clear.

    I understand the rationale for not forking Firefox. But that's a tactical issue in a small skirmish. The real war is about choice. I'm for it.

    --
    Read the EFF's Fair Use FAQ
  38. Of course... by Ayanami+Rei · · Score: 2, Insightful

    the binary and launch scripts still say "mozilla".

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  39. Parent Post is overrated ! by alexhs · · Score: 4, Informative

    Except trolls nobody seems to disagree with you in that thread (when I started writing this post), so i feel I need to explain why you arguments are bogus instead of modding you down.

    Since every package modifies the base system, the only way to prove that a package will work is to test it against every possible package configuration available!

    Each package is independant with others except with its own dependencies. Those dependencies happen to be linear : for P packages, nP total dependencies, with n an integer independant of the number of packages. It's the job of a Debian package maintainer to check the dependencies are fulfilled and working : each maintener just needs to check n dependencies. That's part of the job people are doing to move a new version of a package from sid (unstable) to testing. I will add that chain of dependencies are irrelevant : if A needs B and B needs C, maintainer of A checks his program working against B, while it's the duty of the maintainer of B to check his program works with C. The only cross-dependancies are for kernel-mode code, that is only drivers.

    In fact it's better than the windows "DLL hell", because the state of the system is known (for a Debian stable for exemple), while on MS Windows... Your program has been developped and tested for DirectX 8, will it work with DirectX 9 ? No way to know what the state of the user's system will be (and no developper includes DirectX as a static dependency, it isn't even possible). It's no wonder that most OSes are using repositories (Linux, BSD, QNX, BeOS with software wallet, that one being somewhat different IIRC).

    any software that's not in the repository is not well supported by the packaging system.

    You seem to ignore that there isn't a single central repository. Want Opera browser ? Just add http://deb.opera.com/opera/ in your repositories list, and you get the official binary matching your version of Debian, checked against it.

    If something is not clear, feel free to ask for details.

    --
    I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
  40. Not _Pure_ Spite. by nodrog · · Score: 2, Interesting

    It's at least partly based on a quotation from Matt Groening -

    "Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the iceweasels come"

    --
    Abort, Retry, Ignore?
  41. Every package is a fork by bhmit1 · · Score: 4, Insightful
    Ice Weasel sounds like it will be only installable on Debian, perhaps Debian-descended platforms like Ubuntu.
    With the exception of a few Debian native packages, everything in Debian is a fork that is designed to only be installed on a Debian or a derivative distribution. The source of a Debian package is the original source files and a diff (aka fork) of everything needed to make that software bug free, comply with the packaging standards, and work with other packages on the system. The only difference here from every other package is that Firefox doesn't want to allow Debian to distribute with the same name and logos if it's not released by them, and that's their right. The Debian developers will keep the changes to a minimum to reduce their work, so this will still be very similar to firefox, and I expect the developers to continue using updates from firefox and sending patches and bug reports, where appropriate, back to firefox. The whole thing would have been a lot easier if firefox just made some unofficial branding that could be applied to their product so that people know they are still using firefox that's been modified by a 3rd party vs the real firefox.
  42. Re:Unofficial by Enderandrew · · Score: 2, Interesting

    I'm curious how a simple statement of facts constitutes flamebait.

    Fact - most distros make changes to Firefox. They include unofficial patches and make changes.

    Fact - Linspire claims to make "hundreds" of changes to Firefox.

    Fact - Firefox says on their own website that if you change it, then just make it known that it isn't an unofficial build, and don't use the official branding artwork.

    Fact - When people don't share patches and fixes upstream, it hurts the overall quality of the project.

    How is any of this flame-bait?

    Sometimes I wonder why I bother posting here.

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
  43. Not entirely. by Almahtar · · Score: 2, Insightful

    I think what presents a threat to Microsoft is when the programs people use on Windows are available everywhere else. That allows for a seamless transition away from Windows and the entire Microsoft suite. So when users can't find their pretty fox-setting-the-world-on-fire-with-its-tail button, they don't feel as comfortable: it's just one more thing that's "different." What's more, not being geeks, they won't know that IceWeasel == Firefox. All it takes is one idiot saying "Iceweasel isn't as good as Firefox..." and tons will just believe them.

    Sending clear market signals and extensive branding are vital to success with the "unwashed masses." That's a big reason Microsoft's been winning for so long in the first place. I mean let's face it - it was NOT because they had the best product.

  44. Time to classify the word "fork" by deek · · Score: 3, Funny
    With such a wide discrepency in intentions between forked projects, it seems we need a new word to adequately describe things. Something that would describe forking a project, with the intent of keeping it close to the original project.

    Maybe something along these lines:

    • spoon - well after all, it's not really a fork.
    • spork - continuing on the theme of almost being a fork.
    • prong - I enjoy the idea of describing a project as "pronged".


    Any other suggestions? Any preference from the above? This clearly fills a need that I see in the community, so I shall leave it to the community to decide what they want.
  45. Re:What about Ubuntu? by arose · · Score: 2, Insightful

    Or they may not be sure what do yet--remember that Ubuntu is closely tied to Debian and adopts many of their changes. My prefered solution would be Epiphany in main as the default browser, Mozilla version of Firefox in restricted or multiverse and Iceweasel in universe.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.