Slashdot Mirror


Mozilla vs Debian Analyzed

lisah writes "Linux.com has a behind the scenes look at the history of the ongoing debates between Debian and Mozilla that predate Debian's last release, Sarge. The article also reports the issue may have been laid to rest for good now that Debian tentatively plans on calling it "Iceweasel" but attorney Larry Rosen said this never should have been a debate in the first place. In addition, Mozilla has been prompted to clarify its position on the company's marketing blog."

414 comments

  1. Iceweasel? by Blakey+Rat · · Score: 4, Insightful

    Wow, what can you add to "Iceweasel?"

    Someone around here has a sig that says something like, "letting a programmer name your product is like making a marketer program it." Never before has it been demonstrated so clearly. (Well, to be fair, at least the browser isn't Gimped.)

    1. Re:Iceweasel? by kfg · · Score: 1, Funny

      Wow, what can you add to "Iceweasel?"

      I myself welcome our new Iceweasel on Wildebeest/Lucinda overlords.

      KFG

    2. Re:Iceweasel? by glittalogik · · Score: 2, Interesting

      Couldn't Mozilla just have an alternate version called FreeFox with a modified logo - still recognisably fox-like - and allow the hardcore anti-non-free distros (Debian, Ubuntu et al)to adopt that? How about DebianFox? There's internal capitalisation to appease to programmers' naming sensibilities, and everyone else would know what the hell they were talking about. Seriously, not that hard, guys.

    3. Re:Iceweasel? by BinaryOpty · · Score: 2, Interesting

      A better name would have been "Waterweasel," carrying over the alliteration Firefox has while being it's theoretical opposite still.

    4. Re:Iceweasel? by Kelson · · Score: 1
      I myself welcome our new Iceweasel on Wildebeest/Lucinda overlords.

      So you can now read syslogs in Lucinda Console, huh?

    5. Re:Iceweasel? by kfg · · Score: 1

      So you can now read syslogs in Lucinda Console [wikipedia.org], huh?

      Only on a fussy system.

      KFG

    6. Re:Iceweasel? by EricBoyd · · Score: 2, Insightful

      Dude, an even better name would have been "IceHound". A Hound is much more the "opposite" of fox than Weasel will ever be :-)

      --
      augment your senses: http://sensebridge.net/
    7. Re:Iceweasel? by Kelson · · Score: 4, Informative

      Mozilla has exactly that. There's a compile switch that lets you choose between an officially branded Firefox with the official name, icons and logos, or an unofficial version with the name of your choice and a generic icon.

      The "problem" was that Debian didn't want to use this switch and go the unofficial route. Instead, they wrote a patch that would mix-and-match the official name with the unofficial icons and logos. Mozilla, having consulted their lawyers, said "Wait, you can't do that! It has to be one way or the other." They went back and forth, and finally Debian settled on going all unofficial.

    8. Re:Iceweasel? by PygmySurfer · · Score: 1

      Why should Mozilla have to maintain two versions just because Debian wants to be difficult?

    9. Re:Iceweasel? by cammoblammo · · Score: 2, Funny

      Dude, do you know what alliteration is?

      --

      Cogito, ergo sig.

    10. Re:Iceweasel? by kbmccarty · · Score: 1

      Firefox remains the same, Debian's the one that doesn't come with Firefox. Why they didn't just move it to non-free is beyond me.

      The software is completely DFSG-free aside from the icons and trademark. What a waste it would be to move it to non-free just for the sake of these two easily removable things!

      There's a related argument (I know you didn't make it) that Debian could at least make Firefox available from non-free in parallel with IceWeasel in main. Unfortunately it would be a nightmare for the security team to have TWO slightly different versions of the browser in Etch, considering the monumental task it is just to support ONE.

      --
      - Kevin B. McCarty
    11. Re:Iceweasel? by telekon · · Score: 1
      Wow, what can you add to "Iceweasel?"


      Pfft. What can't you add to "Iceweasel?!"


      This being a corollary to:

      "What do ice weasels do?"

      "What don't they do!?!?"

      --

      To understand recursion, you must first understand recursion.

    12. Re:Iceweasel? by JourneyExpertApe · · Score: 2, Insightful

      You make it sound so easy. Have you ever tried compiling Firefox? It's like trying to build a car from parts with a one-page instruction manual. ;)

      --
      If you can read this sig, you're too close.
    13. Re:Iceweasel? by Fujisawa+Sensei · · Score: 0

      Compiling firefox is easy.

      emerge mozilla-firefox

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    14. Re:Iceweasel? by Fordiman · · Score: 1

      IceInu?

      c'mon. It has the alliteration, and it's more the direct opposite, re GPP.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    15. Re:Iceweasel? by thebluesgnr · · Score: 5, Informative

      Debian never wanted to go unofficial, they did so to comply with the DFSG. The Mozilla Foundation was aware that they were doing that, and they authorized Debian. Until recently, when the Mozilla Corporation changed their minds and filed a bug against Debian.

    16. Re:Iceweasel? by cortana · · Score: 1

      The package in non-free could just dpkg-divert the DFSG-free artwork out of the way, replacing it with the original Firefox artwork.

    17. Re:Iceweasel? by JourneyExpertApe · · Score: 1

      Try compiling it with MinGW.

      --
      If you can read this sig, you're too close.
    18. Re:Iceweasel? by Anonymous Coward · · Score: 0

      Yeah, what a waste. A much better solution is to use a name that no one else uses, and then explain to everyone that in Debian, Firefox is called "Iceweasel". Whatever. This is why for most people, Debian has been renamed to "Ubuntu".

    19. Re:Iceweasel? by Fyre2012 · · Score: 0

      why in the hell would you do that?

      I mean, we're talking about compiling it on Debian here, not Windows or Gentoo.

      --
      This is not the greatest .sig in the world, no. This is just a tribute.
    20. Re:Iceweasel? by bursch-X · · Score: 2, Insightful

      That's what I thought. OK, Debian wants to be all GPL and free (speech) and be completely religious about those issues, fine. But then they also say, we want to use Firefox with the Firefox name (we want to profit from Firefox' name value), but we also want to change it in ways that was not provided by the license (while using the Firefox name & logo).

      DUDES! If you want to use Firefox in the "Firefox" brandend incarnation, you abide to their rules. You're so anal about your own licensing being free only and GPL throughout, but when it comes to other licenses you suddenly want them all to bend over?

      Well fuck you Debian. If you want others to respect your licensing scheme and your decision to be all free and free only, then DO respect other license terms as well... geez.

      You just can't have the cake and eat it.

      --
      There are two rules for success:
      1. Never tell everything you know.
    21. Re:Iceweasel? by Anonymous Coward · · Score: 1, Funny

      Try translating it all by hand into binary.

      Up a hill.

      In the snow.

      Both ways.

    22. Re:Iceweasel? by foreverdisillusioned · · Score: 1

      Is it really that much dumber sounding than "Firefox"? Or "Mozilla" for that matter? "Weasel" is a somewhat negative (and funny) sounding word, but other than that the name is no worse than several dozen other software names I can think of off the top of my head. Practically every name sounds goofy when you first hear it. When the name "Wii" was leaked, people were foaming at the mouth, saying it the stupid name alone would doom the console. Now it elicits mild annoyance at worst, and most people have either embraced it or gotten so used to it that it doesn't matter anymore.

      I think that the underlying truth is if the underlying product is good enough then having a weird name really doesn't matter--in fact, if it's distinctive enough then it can actually be a good thing. That said, I think "weasel" might be a tad much--why not "Icebear" or some other single-syllable animal?

    23. Re:Iceweasel? by Jah-Wren+Ryel · · Score: 1

      Someone around here has a sig that says something like, "letting a programmer name your product is like making a marketer program it." Never before has it been demonstrated so clearly.

      I don't think you get it. They deliberately chose an obnoxious name.
      The same way that Apple renamed their internal project "Carl Sagan" to "BHA"
      for 'Butt-Head Astronomer' after he tried to sue them.

      --
      When information is power, privacy is freedom.
    24. Re:Iceweasel? by SirTalon42 · · Score: 4, Informative

      Previously the Mozilla Foundation said it was perfectly fine for Debian to release a patched version of Firefox and to keep the name, and to use the non-official artwork (the artwork that appears if you don't run make with the --enable-official-branding switch), but out of the blue the new Mozilla Corporation decided they don't want Debian to modify Firefox at ALL and be able to keep the name (unless they submit all patches to MC to have them 'approved' for their Debian's release, the problem with that is that when Debian backports security updates they wouldn't be able to release the fixed packages ASAP, they would have to wait around for the Mozilla Corporation to get around to checking it and letting them).

    25. Re:Iceweasel? by HiThere · · Score: 1

      That doesn't sound as good as IceWeasel.

      Mind you, the image is better, but IceWeasel has a certain sound. (Yes, I know what alliteration is, and assonance, too.)

      Gnuzilla, though, is just *strange*.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    26. Re:Iceweasel? by bluephone · · Score: 0, Troll

      Dude, it's fucking DEBIAN. It's not like anyone of consequence will ever use it. :)

      --
      jX [ Make everything as simple as possible, but no simpler. - Einstein ]
    27. Re:Iceweasel? by JackieBrown · · Score: 1

      I only use firefox in windows as well. I find konqueror to be making strides past firefox with every release.

    28. Re:Iceweasel? by JackieBrown · · Score: 2, Informative

      Why would mozilla maintain two versions? Debian is not asking Mozilla to maintain their browser.

      I don't think you understand the implications for Debian here.

      When Debian releases a stable version no upgrades may be allowed in, only security updates and those should not add new features.

      Now if you actually read the bug report that Mozilla filed, they are giving Debian 2 options

      1) Allow firefox to upgrade to newer versions which ruins Debian's very design of stable (plus hope other package developers don't start making the same demands.)
      or
      2) For every security patch that Debian want's to apply to the frozen version of firefox, they have to wait until someone from Mozilla signs off on the patch.

    29. Re:Iceweasel? by mr_zorg · · Score: 1
      Wow, what can you add to "Iceweasel?"
      I wouldn't be surprised if it was their marketing people that came up with that. Clearly it's a stab at Firefox. Hmm, what's the opposite of hot like fire? Cold like ice. What's the opposite of clever like a fox? Sneaky like a weasel? Fire-fox, ice-weasel. Get it?
    30. Re:Iceweasel? by Anonymous Coward · · Score: 0

      Direfox? Sea lion? Sea wolf?

    31. Re:Iceweasel? by Infernal+Device · · Score: 2, Funny

      I doubt you'll see any real innovation, since software engineering will be controlled by whomever has the most money to pass laws giving real teeth to infringements upon someone's software domain.

      A different (more realistic) side effect: a lot of Open/Libre code is written as an adjunct to paid programmer's work (ie., as a hobby). Get rid of patents, copyrights, etc., the paid work becomes worthless and along with it, programmers. Who then have to find other work which will most likely not afford them the luxury of time or money to write the Open/Libre code.

      --
      "My God...it's full of trolls!"
    32. Re:Iceweasel? by Simon+Garlick · · Score: 1

      There's this distribution called Ubuntu. Maybe you've heard of it?

    33. Re:Iceweasel? by civilizedINTENSITY · · Score: 1

      Firefox is the easy app to get people to switch to, though. Get them to try it for one single day, and going back to IE's work flow model is impossible. Maybe after IE redoes their UI it will just be a matter of security, which isn't nearly as sexy as just plain performing so much better. Even MBA students (ever a conservative crowd) stay switched, if you can get them to try it. Of course its hard to quantify UI design. I mean, hell, some people *prefer* a command line! ;-)

    34. Re:Iceweasel? by civilizedINTENSITY · · Score: 1

      Have to admit IceWeasel has a certain mental *tang* to it.

    35. Re:Iceweasel? by HeroreV · · Score: 1

      Seriously! They could have at least named it something cuter like "IceFerret". "Weasel" sounds evil and sneaky, not something I want on my computer.

    36. Re:Iceweasel? by MrNaz · · Score: 1

      Just wanted to let you know your post was NOT deserving of a -1 mod. I hope that comes up for meta-moderation for me, twice.

      --
      I hate printers.
    37. Re:Iceweasel? by jonasj · · Score: 2, Interesting

      Please stop differentiating between Mozilla Foundation and Mozilla Corporation like that to make it sound like MoFo are nice people and MoCo are evil. Mozilla Corporation is just a front they set up for legal and tax-related reasons. It's the exact same people running the project now as before.

      --
      You know, Microsoft's street address also says a lot about their mentality.
    38. Re:Iceweasel? by baptiste13 · · Score: 1

      > The "problem" was that Debian didn't want to use this switch and go the unofficial route.

      it's a little bit more complicated: the question had already been discussed one year ago, and the reason Debian didn't go unofficial then is that an agreement was reached with MoCo's Gervase Markham.

      Now, one year lated, and six months before Debian's target release, the MoCo's folks suddenly change their mind. My conclusion: the MoCo's folks are not to be trusted.

      For some reason, these facts have been underreported. The MoCo are better than Debian at public relations. That does not make their behaviour less wrong.

    39. Re:Iceweasel? by Ash+Vince · · Score: 2, Insightful

      Good on Debian for sticking to their guns, let's hope enough distributions have the balls to stick by their guns and start refusing to use the FireFox logo or icons in protest.

      Not sure why you say this. It seemed to me that the problem was that debian wanted to use firefox with all the firefox logos and artwork, but make some changes behind the scenes to the code. No I can understand firefox objecting to this, as if debian muck up their modifications it will reflect badly on the firefox brand, not debian.

      If you want to release firefox as part of your product (with modifications) then that is your right under the GPL providiing you also release it under the GPL. But you may not use the Logo's and artwork that come with firefox as you are no longer releasing firefox, you are releasing your bastardised version of firefox so need to label it as such. That way if you release complete crap it reflects badly on you, not the Mozilla corp.

      I love your comment about the capitalistic stuff, once upon a time I agreed with this. Then I got a job and joined the real world.
      What Mozilla are actually trying to do is protect their own public image, it has nothing to do with monopolies or market abuse of any kind.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    40. Re:Iceweasel? by Crayon+Kid · · Score: 1

      Most people don't have voluntary "work flow models" when it comes to computers or web browsing. They have Pavlov's dog reflexes, hardwired by years of use. They "know" where everything in their browser is and they use it as such, no matter how awkward.

      I'm afraid that you don't get non-computer-savvy people to switch by preaching. You change their browser, you import their bookmarks, you slap on a Windows XP theme and tell them to suck it. Of course they'll be better off in the long run, but don't expect them to recognize the difference.

      They simply don't have what it takes. They're cattle, and cattle don't thank you when you fix their barn.

      --
      i ate crayons when i was a kid and now i have two braincells and the blue ones taste nicer
    41. Re:Iceweasel? by ripcrd · · Score: 1

      Sounds a little like you are explaining the difference between good-touch and bad-touch in relation to software. Sorry, too many pedophiles in the news lately for my taste.

      --
      --Somewhere there is a village missing an idiot.
    42. Re:Iceweasel? by VJ42 · · Score: 1

      He hasn't been down modded on this post; he just has very bad Karma, look at his posting history, he seems to have been posting at -1 for some time.

      --
      If I have nothing to hide, you have no reason to search me
    43. Re:Iceweasel? by Blakey+Rat · · Score: 1

      Well, most other (successful) browsers have "exploration"-themed names. Netscape Navigator, Apple Safari, Internet Explorer. If they must use the ice theme, why not some kind of arctic exploration-related term? I don't know what it is, but there HAS to be a better name than "IceWeasel."

    44. Re:Iceweasel? by Anonymous Coward · · Score: 0

      It seemed to me that the problem was that debian wanted to use firefox with all the firefox logos and artwork, but make some changes behind the scenes to the code.

      You "seemed" wrong. The problem wasn't code, though that was brought up in the discussion.

      The problem was that a certain logo was copyrighted by the Mozilla Foundation in terms that made it impossible for Debian to redistribute freely. Debian used the unofficial-and-free logo that COULD be redistributed, and for over a year Mozilla was happy with that. Then Mozilla changed their mind and said that the Mozilla trademark had to go with the copyrighted logo afterall, and that put Debian into the position such that they realistically had no other choice but to drop the Mozilla trademark and call their version something else.

      The "code" part of the discussion involved additional terms that Mozilla Foundation would impose in order to retain access to the trademark. As a separate issue, those terms were onerous anyway and Debian couldn't accept them. However, this issue was still moot because the fundamental problem was that Mozilla wanted Debian to distribute a version of their browser that Debian could not in turn allow downstream distros to redistribute.

    45. Re:Iceweasel? by jdavidb · · Score: 1

      t reiterates my thought pattents - we should abolish copyrights, trademarks and patents and let true innovation happen. All else is a capitalistic way of trying to allow companies to build monopolies and control the market

      You are describing mercantilism, not capitalism. I oppose patents because I am a capitalist, and patents are a government granted monopoly, and thus an interference with pure capitalism.

    46. Re:Iceweasel? by bluephone · · Score: 1

      Tip: Never make a joke where Linux is the butt of it on Slashdot...

      --
      jX [ Make everything as simple as possible, but no simpler. - Einstein ]
    47. Re:Iceweasel? by MrNaz · · Score: 1

      I've said it before and I'll say it again: Karma's a bitch!

      --
      I hate printers.
    48. Re:Iceweasel? by jonasj · · Score: 1

      The Mozilla people didn't "suddenly change their mind". The agreement Debian reached with Gerv was a temporary, "until further notice" type agreement, and Debian was (or should have been) well aware back then that it was only a question of time before Mozilla would enforce their trademark policy.

      Read the bug report if you don't believe me.

      The people leading the Mozilla project today are veru much to be trusted :-)

      --
      You know, Microsoft's street address also says a lot about their mentality.
    49. Re:Iceweasel? by xenocide2 · · Score: 2, Interesting

      Actually, most of the changes revolved around removing the logo, since it's current owner is not releasing it under DFSG friendly policy. I guess Mozilla's corporate council woke up to what was happening and decided to tell em they can't cherry pick Firefox branding. Debian hasn't been using the firefox icon for a quite some time. Ultimately I think it hurts Firefox's brand a bit, and debian's user friendlyness as well. What Debian distributes is basically firefox. Their changes are typically either security backports to versions Mozilla doesn't support, the aforementioned logo patch, and I think they also take out the automatic check for updates, since they already provide a system wide tool for doing this (dkpg/apt-get), in a manner that doesn't rely on limited user accounts installing software. If I were Mozilla, these changes alone wouldn't be so bad, and I'd grant Debian an exception (and I believe I read that Mozilla's council was willing to do exactly that under some conditions), except for one problem:

      Debian isn't satisfied with an exception. Perhaps rightfully so. Several people have taken the liberty to capitalize on Debian's Free nature and modified and distributed Debian. To willfully package and distribute firefox as an exception would be placing a landmine for these people to step on inadvertantly. Digging through each and every package to verify that it is indeed safe to modify and redistribute is a task so large as to discourage people from ever attempting it legally. And given that Debian's existance owes to the fact that someone else gave them software freely redistributable and modifiable, it would be hypocritical not to reciprocate. So Debian naturally demands that they be able to offer the same rights that have been extended to them.

      This demand finds itself at odds with Mozilla's branding efforts. Mozilla worries about a number of possible modifications being negative and associated with firefox. Not in the "aids terrorists" way, but in the "adds spyware and makes people hate firefox" way. Even the community edition version is highly resistant to changes. But that doesn't mean Debian has to agree to help promote Firefox. Hence Debian's move to IceWeasel--a complete rebranding of firefox, one I hope who's aim is to minimize the changeset from firefox to only exactly what is required to allow free redistribution without landmines.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    50. Re:Iceweasel? by doom · · Score: 1
      Someone around here has a sig that says something like, "letting a programmer name your product is like making a marketer program it." Never before has it been demonstrated so clearly. (Well, to be fair, at least the browser isn't Gimped.)
      You're missing one or two points here. This is intentional nose-thumbing. The Debian team have reason to be annoyed at the Mozilla Corporation; and if they're so intent on protecting their good name, they can henceforth be known as "iceweasel".

      It is, by the way, not beyond the realm of possibility that MoCo will regret this move. At present they think of their main "market" as Windows users, but in another five years or so, most of their users may be on a linux distro derived from Debian such as Ubuntu.

      Oh, and by the way... if you ask marketers what the latest and greatest brands are of the modern era, they come up with things like "google" and "yahoo", and *surprise*: marketing people did not invent these names.

    51. Re:Iceweasel? by civilizedINTENSITY · · Score: 1

      Actually I have over a decade of experience supporting non-geeks. Your attitude towards people is disturbingly dark, because the fact is that people *do* recognize a difference. People can tell when something works better right away. Since most of what they do remains the same (clicking on a link is clicking on a link) the "hardwired" part doesn't change. Adblock and Flashblock, as well as tabbed browsing, make it work faster and smoother. Which is why they stay with Firefox. (I'm also not aware of even a single user that went with "a Windows XP theme", by the way. They seem to either not care, or playfully explore all kinds of weird themes.)

    52. Re:Iceweasel? by coredog64 · · Score: 1

      According to the Chilton manual for Firefox, "reinstallation is the reverse of disassembly".

    53. Re:Iceweasel? by Lord+Kestrel · · Score: 1

      Actually yes. It's a hell of lot easier now. It used to be a set of patches you applied to the Mozilla source tree.

    54. Re:Iceweasel? by Anonymous Coward · · Score: 0

      i suppose you'd go with some professional name like "Debian Web Browser"?

  2. Summary by Anonymous Coward · · Score: 5, Informative

    Summary, hopefully before anyone gets a chance to 'blame' Mozilla or 'blame' Debian over nothing:

    Debian don't want to include certain icons related to Firefox because the licensing of those graphics isn't consistent with the aims of their project.

    Mozilla say that's fine, as long as Debian don't call the package "Firefox".

    So Debian aren't going to call it Firefox.

    No villains, and everyone lives hapily ever after. The end.

    1. Re:Summary by Poltras · · Score: 2, Funny

      Say mommy, will they have many children?!?

    2. Re:Summary by snowgirl · · Score: 4, Insightful

      The article also states that Mozilla is expecting Debian to submit all modifications for review, and that if the modifications were not satisfactory, whether the code was in deep-freeze or not, that they would have to change the name.

      A lot of this comes down to "what's in a name"? Personally, I see Debian's position as more proper within the realm of the F/OSS community. If you toute your program as open source, yet say that if anyone makes any changes to the program that you do not approve of, that they cannot use your trademark, then that certainly doesn't sound "open" and "free" to me. Especially, if your source contains all of the trademark data in the code, and altering the content requires a great deal of work.

      When you come down to it, it's the same situation as I have with Windows XP. "Oh, of course you OWN the CD, you bought it. But you're only LICENSING the data on it." They hide all this un-free double plus ungood behind telling you that you're free to do whatever you want, so long as you don't screw with them.

      If a program is released as free/open source under the GPL, or BSD, or any license for that matter, but contains artwork inside of it that is restricted, then that's absurd, and retarded! I'm sorry that I have to take a Stallman approach to this issue, but it's stupid to have Copyleft and Trademark compete against each other...

      Let's all trade our freedom of IP expression for the shackles of another IP prison!

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    3. Re:Summary by jmv · · Score: 4, Insightful

      Debian don't want to include certain icons related to Firefox because the licensing of those graphics isn't consistent with the aims of their project. Mozilla say that's fine, as long as Debian don't call the package "Firefox".

      I think it's not that much about the logo as it is about other changes Debian makes.

      No villains, and everyone lives hapily ever after. The end.

      Sure, everyone is technically in their right. However, Mozilla is being very much of a pain in the ass. Can you imagine how life would be for distros if GNOME decided it doesn't get called GNOME unless it's the official GNOME release (no modifications)? And then KDE could do the same, along with X.Org, OpenOffice.org, ... So you would get a Linux distro (actually, it couldn't be called Linux) and you'd find all kinds of programs you never heard about, each of them being a "rebranded" version of the official package. Or alternatively, each Linux distro would need to ask each maintainer for the permission to apply each of their patch (i.e. for every cvs/svn commit during development!). I really hope all Linux distros drop Firefox (the name, not the software) and go with the same new name (IceWeasel?). Maybe that could even make Mozilla change their decision, although I'm not too optimistic. At least it would be a name all Linux users would recognise (Firefox? What's Firefox?).

    4. Re:Summary by snowgirl · · Score: 1

      I have to agree.

      Honestly, right now, we have Copyleft licenses, free licenses, open licenses, and Creative Commons licenses... but yet Mozilla while choosing to embrace one part of "free" denies freedom somewhere else? That doesn't make sense to me.

      We should have trademark usage license that chalks up to the same level as the Copyleft GPL, and Creative Commons. "You can use this trademark, and modify this trademark in such a way that it could be easily confused with this trademark, so long as you keep THAT trademark free under this same license."

      I think it's totally BRAINDEAD for a project to fork essentially only in name...

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    5. Re:Summary by Anonymous Coward · · Score: 0

      Do you know the difference between doesn't and don't?

      Doesn't == Does not
      Don't == Do not.

    6. Re:Summary by Mr.Ned · · Score: 1

      '''Debian don't want to include certain icons related to Firefox because the licensing of those graphics isn't consistent with the aims of their project.

      Mozilla say that's fine, as long as Debian don't call the package "Firefox".'''

      What's unfortunate is that two years ago the Mozilla Foundation told Debian they'd be fine as long as they didn't call it "Mozilla Firefox"; they sanctioned the change to "Debian Firefox", as referenced in one of the links from the article. Now the Mozilla Corporation (the new trademark holder) says that calling it "Debian Firefox" isn't good enough and they need to do away with the Firefox entirely.

    7. Re:Summary by Anonymous Coward · · Score: 0
      Do you know the difference between doesn't and don't?

      Yes I do. Debian do not want to include certain icons. One day you'll be ready for the advanced lessons; you'll learn about British English and you'll understand. Then again, maybe you won't.
    8. Re:Summary by Anonymous Coward · · Score: 0

      "Debian don't want to include certain icons related to Firefox because the licensing of those graphics isn't consistent with the aims of their project."

      The kicker: Debian includes certain icons related to Debian which are inconsistent with the aims of their project. :-)

      Doh!

    9. Re:Summary by mattgreen · · Score: 1

      You forgot the point about "IceWeasel" being too good a name to pass up!

    10. Re:Summary by mad.frog · · Score: 5, Interesting

      Can you imagine how life would be for distros if GNOME decided it doesn't get called GNOME unless it's the official GNOME release (no modifications)?

      Yes, I can imagine it.

      It would fucking ROCK.

      Being able to assume that "GNOME 2.10" really is "GNOME 2.10" everywhere, and not "GNOME 2.10 plus some stuff that I thought might cool and without the stuff I thought I didn't need"... well, it would make life a lot simpler for app developers.

    11. Re:Summary by sparkz · · Score: 2, Informative

      A lot of American corporate lawyers want to cause confusion between copyright and trademark law, by putting them both under the umbrella of "Intellectual Property", something which does not exist in law. Copyright and Trademarks are two entirely separate things. Even Stallman and the GPL doesn't get into Trademark issues. Mozilla have a right to put whatever restrictions they like on the use of their trademarks, whatever license the code is released under. Debian can call it IceWeasel (or even something less derogatory-sounding, if they so choose), but copyright and the MPL license mean that they can still use the code. The big issue here, is that confusion about copyright vs trademarks is the result of a deliberate ploy by corporate America to confuse the public about "Intellectual Property" (IP) and "IP Rights" (IPR).

      --
      Author, Shell Scripting : Expert Re
    12. Re:Summary by PygmySurfer · · Score: 5, Insightful

      What if the Firefox version released with Etch absolutely sucks? What if it crashes regularly, trashes the user's home directory, and eats small children? Are user's going to blame Debian, because of their patches? No, they're going to blame Mozilla and claim Firefox sucks. Word will spread, and people will be under the mistaken impression Firefox is an unstable child eating browser from Hell. If Debian makes their patches and renames it, people will only be under the impression Iceweasel sucks.

      I don't know what kind of patches Debian is applying, but they must not be trivial, if Mozilla wants to approve them before allowing distribution with their name and artwork.

      The Mozilla foundation laid all of this out a long time ago. Debian knew the terms when they began using Firefox. They're free to agree to the terms or not use it.

    13. Re:Summary by Mr.+Jaggers · · Score: 4, Interesting

      Nope, it's pretty clear from the article that that logos and associated graphics are the issue. Trademark use conditions require that they be included. The Debian Free Software Guidelines require that they not be included. Thus, Mozilla Corporation postures some, and also attaches other strings; like the patch review & description, tagged subversion branch, prior approval of build conditions themselves, and inclusion of said graphics.

      I agree with the rest of your statement, though, and I do think that this business is a big waste of developer time and effort. Now it is really more difficult to comply adequately, depending on the nature and volume of Debian's patches.

      If one were to invite prognostication from me, I'd say that this sort of response will grow, as Mozilla Corporation flexes it's muscle over trademark enforcement. I'd guess that Debian, Ubuntu, and any other distro striving to be truly free, will probably do something like perform conditions 1 and 3 anyway (publicly submit patches w/descriptions, as well as tag their divergent branch), will probably exert the GPL and use whatever build time configurations they think are best, and lastly, come up with their own artwork and graphics.

      That will further their goal of using & distributing free, high-quality software (without non-free strings attached to binary data included in the final product) to their users. My guess is that creative icon-ing will make this change remarkeably less noticeable to end users. After all, there is no reason that iceweasel (et. al.) couldn't use the same (or similar) versioning and advertise itself as being 'firefox compatible' as far as extensions & page rendering go. Not to mention, that I seriously doubt it would be a violation of trademark to install a 'firefox', or 'mozilla-firefox' symbolic link (in a very /etc/alternatives sort of way). In Debian and Ubuntu, it would be the 'sensible-browser', most likely. Folks could always still just go download the shell-archive installer from mozilla.org any time they want to and drop their own out-of-package-management version of the one true firefox.

      On the side of Mozilla Corp., they will either decide that this dilutes the brand, and just bend to unify everyone, or they won't care and will drop strictly-all-free sorts of GNU/Linux distributions, assuming that the market share they bring is minimal.

      And that will be that. Just my guess, anyway. If Mozilla Corp is smart, they'll exclude the user-agent string from trademark issues so that at least usage statistics will show a unified product, rather ruining firefox's growing usage statistics rank in a schism.

      --

      When I grow up, I want to have Christopher Walken hair.
    14. Re:Summary by PygmySurfer · · Score: 2, Insightful

      It sounds to me Mozilla isn't worried about them making modifications to the code, its the extent of the modifications ("grave concerns around the nature and quality of some of the changes the patchset contains" as they stated). They're concerned about the stability of Firefox, and rightly so. If the changes Debian makes impacts the stability of Firefox, its Mozilla and Firefox who're going to be blamed, not Debian.

    15. Re:Summary by jmv · · Score: 1

      If Mozilla Corp is smart, they'll exclude the user-agent string from trademark issues so that at least usage statistics will show a unified product, rather ruining firefox's growing usage statistics rank in a schism.

      That's an interesting one. Maybe it would be a way for Debian and the others to put pressure on Mozilla Corp. After all, using Firefox as the user-agent string would be claiming "I am an [official] Firefox browser", which Moz corp said they weren't allowed to do. So yes, I'd expect the usage statistics would drop a bit while Linux distros are making the switch.

    16. Re:Summary by Rydia · · Score: 2, Informative

      Just going into it basically, both trademarks and copyrights are powers assigned to congress by the same clause of the constitution (the copyright clause). The law dealing with the two is roughly parallel, using a lot of the same analyses and a large body of shared terms of art. Hell, I have 2 books sitting on my bookshelf right here specifically titled "Intellectual Property" which deal with copyrights and trademarks both, because they work rather similarly. This is how it's taught in law schools everywhere, to those who will actually end up dealing with the concepts and not going for cheap political points on websites.

      I can understand that you might not agree with the way a lot of companies use IP law, but that doesn't justify mischaracterizations and bending reality to fit your own preconcieved notions of what is and what isn't.

    17. Re:Summary by PygmySurfer · · Score: 1

      Honestly, right now, we have Copyleft licenses, free licenses, open licenses, and Creative Commons licenses... but yet Mozilla while choosing to embrace one part of "free" denies freedom somewhere else? That doesn't make sense to me.

      Mozilla has their own license. Why should they have to conform to the ideals of other licenses. Or should Mozilla not be free to choose their license? Maybe Microsoft and Adobe should have to adopt one of those licenses as well.

      We should have trademark usage license that chalks up to the same level as the Copyleft GPL, and Creative Commons. "You can use this trademark, and modify this trademark in such a way that it could be easily confused with this trademark, so long as you keep THAT trademark free under this same license."

      If Mozilla wanted you to use their trademark in such a way they could allow it - they've chosen not to. The Mozilla Firefox logo identifies Mozilla Firefox. When people see that logo, they think of a fast, stable, secure browser. Mozilla is worried Debian will distribute a browser that doesn't live up to those expectations.

      Trademark and Copyright are entirely different subjects, and should be treated as such.

    18. Re:Summary by jmv · · Score: 1

      I don't blame them for being concerned about the quality, but instead of making threats, they could simply have helped Debian in their process or try to talk them out of doing certain changes. What they're doing now is counter-productive. Debian users will still know it's Firefox underneath and will still blame Firefox. Depending on whether the Firefox actually accepts bug reports coming from Debian builds we'll have either:
      1) Same as before, they get blamed for all bugs, even those introduced by Debian
      2) They will lose the Debian bug reports, which means Debian will have to make the fixes themselves, making the two builds diverge further.
      I can't see any of these options being good for anyone.

    19. Re:Summary by telekon · · Score: 2, Funny

      Jesus. Does this mean we need to come up with some sort of corollary to GPL copylefting by using trademark law to un-trademark trademarks?

      And what do we call that? GiftMark?

      Copylefted, giftmarked... what's the opposite of patent? Suede?

      God, jokes about leather... that's a low, even for slashdot.

      --

      To understand recursion, you must first understand recursion.

    20. Re:Summary by LOTHAR,+of+the+Hill · · Score: 1

      So what are they going to call "GIMP"? It has a logo too? So do many other OSS projects. There's also one with a penguin, but I can't recall the name.

    21. Re:Summary by jmv · · Score: 1

      Mozilla has their own license. Why should they have to conform to the ideals of other licenses. Or should Mozilla not be free to choose their license? Maybe Microsoft and Adobe should have to adopt one of those licenses as well.

      Mozilla is free to choose their license. They could have made Firefox a proprietary browser (assuming they owned all the copyright) if they wanted to. They could have asked $1000/seat. We're not arguing the legality, but the fact that they're being a PITA for Linux distributions, who will have to change the name. Everyone has a right to be a PITA, everyone also has a right to complain about people who are a PITA.

    22. Re:Summary by jmv · · Score: 3, Insightful

      Yes, I can imagine it.
      It would fucking ROCK.
      Being able to assume that "GNOME 2.10" really is "GNOME 2.10" everywhere, and not "GNOME 2.10 plus some stuff that I thought might cool and without the stuff I thought I didn't need"... well, it would make life a lot simpler for app developers.


      You're getting it wrong here. It would mean that Debian would have "TROLL 2.10 plus some stuff that I thought might cool and without the stuff I thought I didn't need", and RedHat would have "EMONG 2.10 plus some stuff that I thought might cool and without the stuff I thought I didn't need" and so on. Distribution are *integrators*, they can't just ship everything unmodified (they'd all be the same otherwise). (Most) People want something polished where apps fit together and all.

    23. Re:Summary by PygmySurfer · · Score: 1

      One could argue the distributions are being the PITA, by not following the guidelines Mozilla asked them to. Indeed, they could have made a proprietary browser, and Debian wouldn't have Firefox at all.

    24. Re:Summary by Millenniumman · · Score: 2, Insightful
      If you toute your program as open source, yet say that if anyone makes any changes to the program that you do not approve of, that they cannot use your trademark, then that certainly doesn't sound "open" and "free" to me.

      No one will let you use their trademark. It reflects back on them. If anyone could call a product Firefox, and put all of the Firefox graphics on there, then they can do anything in Mozilla's name. Anything includes making spyware, a virus, or just plain bad software. That would cripple Mozilla's reputation. If I took some of your code, messed with it to make it destroy a linux installation when used, and released it as your software, would you like that?

      Maybe Debian should be allowed to use the name for small patches, but that would have to be a special accommodation.
      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    25. Re:Summary by dircha · · Score: 2, Informative

      Especially considering section 3.3 of the MPL already carries the standard "prominent notice of change" distribution requirement that seems to work well enough for almost every other free software project out there.

      Apparently this wasn't enough for the Mozilla project.

    26. Re:Summary by PygmySurfer · · Score: 1

      As far as I understand it, Mozilla have been helping Debian. Actually, the entire discussion has been about helping Debian to comply with Mozilla's terms. By bringing it to Debian's attention now they hope to resolve it before release. If Debian releases their modified Firefox, there's always the possibility of lawsuits or other such nastiness (IANAL, but I know trademarks can be lost if left undefended. I don't know if this situation would qualify, however). Even if there is no legal action, Mozilla would have to request the packages be removed, which would impact Debian users. Getting this resolved now greatly benefits the Debian community.

      I also think by requesting approval on the changes Debian is making would help as well. More eyes on the code would identify more bugs.

    27. Re:Summary by AvitarX · · Score: 1

      I sure hope not.

      The whole point of a (TM) is so you can control branding.

      If debian is making un-official patches I should be able to tell it is something different. That way Firefox can be the same everywhere and a patched version is something different.

      If you don't want a something to be a (TM) don't make it one, and then it is just copyrighted and can use the creative commons liscense.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    28. Re:Summary by jmv · · Score: 1

      One could argue the distributions are being the PITA, by not following the guidelines Mozilla asked them to.

      As the author of Speex, I demand that any distro who want to use the name Speex needs to display my picture as the boot screen. Oh, and I want then to bow before me and call me "Your Highness". If they choose not to comply with my guidelines, they're just being a PITA.

      [Note to distributions: This is a joke, please don't do that!]

    29. Re:Summary by dircha · · Score: 1

      One of the points raised by the Debian maintainers is that distribution integration often requires modification. Modification is done for reasons ranging from conformance to distribution semantics to library integration, in order to provide uniform function and a consistent user experience.

      I suspect, were you to take the time to understand the unique requirements and concerns of distribution maintainers, you would come to have a better appreciation of their concerns.

    30. Re:Summary by Stormwatch · · Score: 0, Offtopic

      Debian == a group == a single entity == does not want to include certain icons.

    31. Re:Summary by Fordiman · · Score: 1

      I know IP is a recent concept, but Copyright, Patents, Trademarks and Trade Secrets have been lumped together, in terms of how they're thought about, for years.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    32. Re:Summary by PygmySurfer · · Score: 1

      Except that's not what they're asking. Their demands are confined strictly to their program, not all of the software on your system.

      If you demanded that upon starting up Speex, it display your picture, that'd be perfectly valid. As for bowing down, I don't know. Are you going to pay airfare to fly everyone to your palace, or is that the users' problem? :)

      So long as they're lawful, any terms of use are valid. It's up to the users (distributors, etc). If they want to use the software, they'll agree to the terms.

    33. Re:Summary by xtronics · · Score: 1

      Not so fast. The issue is not really about the logo - it is the use of the logo 'trade-mark' to end run the GPL.

      Mozill does not want Debian to patch older versions of firefox mozilla no longer wants to support. They also do not want Debian from coming out with security patches before they do.

      The logo is the lever to force Debian to do things they don't like. Firefox is no longer Free (as in Freedom) software. To fit in with Mozilla Debian would have to scrap a Stable version and sit on Security patches while users get stung.

    34. Re:Summary by sparkz · · Score: 2, Informative
      trademarks and copyrights are powers assigned to congress by the same clause of the constitution (the copyright clause)

      That is not true. That is exactly the confusion (FUD) that I was referring to. Copyright and Trademark are entirely separate. "Intellectual Property" is a fiction, or - more accurately - a theoretical combination of (C) and (TM). In this instance, Mozilla aren't disputing (C), but are disputing (TM).

      If you want a full description, feel free to get yourself a lawyer ;-)

      This instance should make it obvious to you that (C) and (TM) are different issues; Mozilla are disputing Debian's rights over the Mozilla Trademark, not at all over the Copyright.

      I refer you back to my original point, that it is convenient for certain (particularly large, USAian and/or Multinational, as it happens) corporations to confuse copyright and trademark law into some mush of "Intellectual Property".

      The better the general public understand the difference, the better off society will be.

      I can understand that you might not agree with the way a lot of companies use IP law, but that doesn't justify mischaracterizations and bending reality to fit your own preconcieved notions of what is and what isn't.

      I am doing nothing of the kind. There is no "IP Law". You appear to have fallen victim to the myth that there is such a thing. An issue like this makes the difference between copyright and trademark quite clear, surely? What part of it do you not understand?

      --
      Author, Shell Scripting : Expert Re
    35. Re:Summary by Bing+Tsher+E · · Score: 1

      You're kidding. You think that without the portion of the Userbase that runs Mozilla on Debian, that Mozilla's usage statistics would plummet???

      (disclaimer- I run Mozilla (seamonkey) on NetBSD)

    36. Re:Summary by Anonymous Coward · · Score: 0
      One of the points raised by the Debian maintainers is that distribution integration often requires modification. Modification is done for reasons ranging from conformance to distribution semantics to library integration, in order to provide uniform function and a consistent user experience.
      And Mozilla made it clear that those sorts of modifications are fine, subject to review and approval. What's so hard about that? It's called cooperation, which Debian seems unwilling to do. The irony of course being that Debian would squeal like a stuck pig if anybody were to make changes to their distribution and try to distribute it as "Debian". The hypocracy is just overwhelming.
    37. Re:Summary by cswiger2005 · · Score: 1

      The Open Source Definition allows you to require that someone who modifies your program must call it by some other name, to avoid random people confusing the "official" version released by the original author with modified versions.

      This being said, you're pretty much right that it's a silly argument for both sides to get into...

      --
      "The human race's favorite method for being in control of the facts is to ignore them." -Celia Green
    38. Re:Summary by Sancho · · Score: 1

      Be aware that altering the content is not a great deal of work. Mozilla has provided a single switch which allows you to turn off all the Firefox branding. In this way, they make it quite easy to comply with their terms.

      If a program is released as free/open source under the GPL, or BSD, or any license for that matter, but contains artwork inside of it that is restricted, then that's absurd, and retarded! I'm sorry that I have to take a Stallman approach to this issue, but it's stupid to have Copyleft and Trademark compete against each other...

      I completely disagree with this, and here's why.

      What do we lose by not getting to use the trademarks? We still have the right to modify and redistribute. We still have the right to demand the source code if someone gives us a binary. What we do not have is the right to call our own modified software by the same name--and to me, that makes sense. If I patch the Linux kernel and redistribute it, I am no longer distributing Linux--I am instead distributing Linux with my own particular patches in it. If it's not from the original release, Iwant to know it , because that way I can more easily track down likely sources of any problems I have, and possibly realize that I need to try downloading the official source before spending hours troubleshooting.

    39. Re:Summary by coaxial · · Score: 1

      A lot of this comes down to "what's in a name"? Personally, I see Debian's position as more proper within the realm of the F/OSS community. If you toute your program as open source, yet say that if anyone makes any changes to the program that you do not approve of, that they cannot use your trademark, then that certainly doesn't sound "open" and "free" to me. Especially, if your source contains all of the trademark data in the code, and altering the content requires a great deal of work.

      Why would you want to prevent people from using the name after they make changes to your code? When it doesn't do what you want it to. I think I'll download "Ice Weasel", turn it into a spambot, and then redistribute it as "Ice Weasel 2.0." That's good stuff! Or since there isn't a trademark on "ice weasel" I can create a new monkey porn site named "Ice Weasel" and then sully the "good name" of Debian's Ice Weasel. Awesome!

      When you come down to it, it's the same situation as I have with Windows XP. "Oh, of course you OWN the CD, you bought it. But you're only LICENSING the data on it." They hide all this un-free double plus ungood behind telling you that you're free to do whatever you want, so long as you don't screw with them.

      No. No it's not. It comes down to "Don't put my name on your crappy changes." It's the same problem I have with the FDL. You publish a book, and release it under the FDL. I can then rip all the pages out of it, and replace them with illicit pornography. Congratulations. You're name is now attached to pornography.

    40. Re:Summary by Anonymous Coward · · Score: 0

      It's not just the fact that Mozilla has a log. It is that there are licensing restrictions attached to the use of that logo that are inconsistant with Debian's ideals. Apparently there are licensing restrictions attached to the name as well.

    41. Re:Summary by coaxial · · Score: 1

      I do think that this business is a big waste of developer time and effort.

      Which makes it the perfect for Debian developers.

      Now excuse me. Some of us have important work to do.

    42. Re:Summary by Sancho · · Score: 1

      You seem to be heavily oversimplifying things. It is certainly true that trademark and copyright have significant differences. However they also have some similarities (which you seem to be discounting when you say, "Copyright and Trademark are entirely separate.") The are separate in the sense that they aren't synonyms. They are separate in the sense that granting one does not immediately confer the rights of the other. But they are similar in that they are both vapid--there is nothing hard or real about them. They are both granted by the government and are given properties of physical property in an effort to otherwise control or limit their use by persons other than those to whom the government has granted the mark or right.

      Calling them (along with patents) "intellectual property" does have connotations that ownership of ideas can exist, so perhaps a better term would be 'intangible property'. Nevertheless, "intellectual property" is a fairly well established and accepted term to call the collective group of monopolies that the government grants to individuals and corporations regarding intangible ideas. Even dictionaries include the term.

      The better the general public understand the difference, the better off society will be.

      I agree with this, but that doesn't mean that there aren't similarities between the two terms.

    43. Re:Summary by jmv · · Score: 1

      You're kidding. You think that without the portion of the Userbase that runs Mozilla on Debian, that Mozilla's usage statistics would plummet???

      No, I said that if all Linux distros did remove the Firefox user agent string, then the statistics would drop (not plummet). Since everyone wouldn't update at the same time, it could also just make the Firefox usage numbers stagnate for quite a while (reducing the number of Linux users at the same rate as the increase in Windows users). While Linux only has about 5% (sounds right, but not sure what the exact numbers would be) of the market, that's where Firefox is the most dominant. So with Linux, they have 90% of 5%, whereas for Windows they might have 5% of 90%. Numbers are made up but should be within a factor of 2, you get the idea.

    44. Re:Summary by cdcarter · · Score: 1

      One day you'll be ready for the advanced lessons; you'll learn about British English and you'll understand He was using Debian with plural verb forms as a reference to the people of Debian, but not the enity of Debian. Microsoft are releasing a security patch. QED

      --
      "Love is like a trampoline, first it's like "SWEET!!" then it's like *BLAMM!*"
    45. Re:Summary by Sancho · · Score: 1

      will probably exert the GPL

      You're aware that Mozilla isn't licenced under the GPL, right? Or did you mean something else, which I misunderstood?

    46. Re:Summary by Anonymous Coward · · Score: 0

      The article also states that Mozilla is expecting Debian to submit all modifications for review, and that if the modifications were not satisfactory, whether the code was in deep-freeze or not, that they would have to change the name.

      It's not like Debian ships a new release every couple of months -- a situation where waiting for Mozilla code review would hold up releases. They ship releases VERY slowly, which leaves plenty of time for review. Unfortunately, the issues didn't come up until near the release this time.

    47. Re:Summary by Sancho · · Score: 1

      Ok, I jumped the gun, obviously. I didn't realize that Mozilla is /tri-licensed/

      How does that work exactly? Can the end-user decide which license to use?

    48. Re:Summary by jdavidb · · Score: 1

      Except the only people who are aware of IceWeasel's existence will be those who asked "How do I get Firefox on this machine," so if it crashes, they'll still spread the impression that Firefox sucks.

    49. Re:Summary by absoluteflatness · · Score: 1

      trademarks and copyrights are powers assigned to congress by the same clause of the constitution (the copyright clause)

      That is not true.

      Or, maybe it is.

      From Article 1, Section 8 of the Constitution: The Congress shall have power... To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.

      Sure seems like the same clause to me. Also, while there is no "IP Law", there are certainly laws that outline the current implementation of Congress' power to grant copyrights, which could collectively be called "IP law" (lowercase l).

    50. Re:Summary by Rydia · · Score: 1

      If you want a full description, feel free to get yourself a lawyer.

      Uh, done? I don't keep old casebooks on my shelf for the hell of it, you know.

      You are correct that this dispute is over Trademarks. That really has no relevance to our discussion, however. Your argument is that grouping copyrights and trademarks (and occassionally, though rarely) patents into an umbrella of "IP" is a scheme to confuse people. My point is that we lump them together both because the authority for both schemes lie in the same clause of the constitution, and (partially as an offshoot of this), the two schemes share many characteristics (although the terminology is sometimes different), and a lot of the analyses are quite similar. This is why the two are often taught concurrently, and why they are given an umbrella "subject."

      You didn't respond to any of these arguments, and managed to insult both my intelligence and education. Well done, sir.

    51. Re:Summary by Shads · · Score: 1

      *watches the attorneys frolic with each other in the pale light of the monitor glow*

      --
      Shadus
    52. Re:Summary by Stormwatch · · Score: 1

      Again:

      Microsoft == a company == a single entity == is releasing a security patch.

    53. Re:Summary by zcat_NZ · · Score: 1

      That clause covers copyright and patents. It comes nowhere close to trademarks.

      Trademark law is based on the idea that other people shouldn't impersonate me.

      If I've established a good reputation for myself other people have no right to pretend to be me, or pretend that their business is associated with mine by using a confusingly similar name or logo. Let them build their own reputation.

      --
      455fe10422ca29c4933f95052b792ab2
    54. Re:Summary by Peter+La+Casse · · Score: 1
      And Mozilla made it clear that those sorts of modifications are fine, subject to review and approval. What's so hard about that?

      Their review and approval process doesn't meet the DFSG, isn't fast enough to keep up with Debian (jinkies!) and doesn't cover older versions of the software that Debian has committed to supporting.

    55. Re:Summary by metamatic · · Score: 1

      Yes, the issue of companies using trademarks to lock up GPL software is one I think ought to be addressed in GPL v3. I wrote to RMS about it, and also posted my thoughts. I think it's a genuine risk.

      RMS himself doesn't have a problem with what Mozilla are doing, but I think that loophole is going to get widened if Mozilla get away with it.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    56. Re:Summary by BZ · · Score: 1

      > How does that work exactly? Can the end-user decide which license to use?

      Yes, exactly. See the actual license text at http://www.mozilla.org/MPL/boilerplate-1.1/mpl-tri -license-html -- it pretty much spells it out.

    57. Re:Summary by mr_matticus · · Score: 1

      They're not locking up any software. Debian was never discouraged from making modifications or releasing the product--Mozilla just didn't want Debian calling it "Mozilla Firefox" when they did so. Mozilla isn't using any loophole, and there's nothing to get away with here.

    58. Re:Summary by Literaphile · · Score: 1

      Since when do we take orders from anonymous cowards?

    59. Re:Summary by mr_matticus · · Score: 1

      That's still not true. Anyone who looks at browsing stats will still see the Firefox code base in all its iterations. Proponents will group them together, opponents will isolate Mozilla Firefox "official" to under-report usage. It's all politics, but rebranding doesn't actually affect the ACTUAL market shares of browers.

      This all raises an issue I've been involved with for years. Browsers shouldn't be identified (and weren't originally meant to be identified) based on their commercial product names, but based on the rendering engine. The point of user agents is to identify the software people are using and make your sites compatible accordingly, not to be the ammo of a market share war. That and all other uses of the information should be a secondary concern.

      User agents should be centered on MSIE, Gecko, KHTML, etc. Whether the user is using Mozilla Firefox, Camino, or Debian Iceweasel should have zero impact on the stats.

    60. Re:Summary by A+beautiful+mind · · Score: 0, Flamebait

      Yay! Finally someone has a viable plan to kill that abomination they call Gnome. You made my day dude!

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    61. Re:Summary by A+beautiful+mind · · Score: 1

      Yeah, well someone who used Firefox from 0.x, my empirical evidence disagrees.

      I've been using Firefox on Debian, Gentoo and Redhat besides the occasional MSWin usage. The only problem I ever had with Firefox is that it crashed occasionally (after days of usage or on select websites). The 0.x had beta problems, after all it was a beta level software at the time. 1.0.x worked the best for me so far, crashes has been the least frequent here. 1.5.x is a step back in that respect, on all distributions I'm using consistently! If that is so, crashes aren't due to debian's patchset...just a food for thought.

      Mozilla needs to get off their high horse. They are blaming problems that do exist within their code on other experienced programmers, unjustly in my opinion.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    62. Re:Summary by jmv · · Score: 1

      Well, next thing you know Mozilla Corp will claim that they can't guarantee that Debian didn't break the Gecko rendering engine, so Debian should be calling it something different.

    63. Re:Summary by mr_matticus · · Score: 1

      Not really, no. Gecko isn't a product unto itself; it's an underylying technology from which end products are based. Mozilla has no objection to modifications of either Gecko or Firefox. It has objections to people distributing whatever they want and calling it "Firefox." The only place you might conceivably run into trouble is if you wanted to call your browser "Gecko." Other than that, change whatever you want.

      Again, the problem isn't that Mozilla objects to anything Debian is doing. Quit trying to paint Mozilla as the bad guy--if your company released a modified Linux distro and called it Debian Sarge, you'd get a letter from Debian.

    64. Re:Summary by Anonymous Coward · · Score: 0
      As the author of Speex, I demand that any distro who want to use the name Speex needs to display my picture as the boot screen. Oh, and I want then to bow before me and call me "Your Highness". If they choose not to comply with my guidelines, they're just being a PITA.

      [Note to distributions: This is a joke, please don't do that!]
      So you won't have a problem at all if somebody derives a product from Speex and uses the Speex name and your lame logos to promote it then, right? Or are you just a hypocrite?
    65. Re:Summary by k8to · · Score: 0

      Yeah, and all the other open source projects like Apache and python and so forth take the same stance to protect their images too!

      Oh wait, no they don't. In fact, no other free software project has requirements like this, because it flies in the face of the whole idea of free software. So sure, being concerned about the image of your software is reasonable. And taking legal steps to prevent people from using the brand of your software when modifying it is reasonble. But it is contrary to free software, and thus represents a turn by the Mozilla Corp away from the whole idea of free software.

      Not that they can't do this, but given the licenses and so on they have chosen for the main body of their code, it makes one wonder if they really have any clue what they're doing.

      --
      -josh
    66. Re:Summary by Spliffster · · Score: 1
      ... If Mozilla Corp is smart, they'll exclude the user-agent string from trademark issues so that at least usage statistics will show a unified product, rather ruining firefox's growing usage statistics rank in a schism.
      from a technical point of view this is already the case. gecko is the name of the render engine and this is what all mozilla derived browsers should (and mostly) have in their UA strings along with a build date.

      For example:
      Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.0.7) Gecko/20060921b Ubuntu/dapper-security Firefox/1.5.0.7
    67. Re:Summary by jmv · · Score: 1

      Debian is a distro: a collection of software and you only use one at a time. Mozilla is an application and you usually include hundreds in an application. Just try to imagine what would happen if every single open-source project decided to have the same policy as Debian. Think that would work?

    68. Re:Summary by sparkz · · Score: 1

      There is some common ground, but I still contend that the major benefactor of the concept of "IP" is corporate America. Whether or not (see an earlier post in this thread) the same part of the US Constitution applies to (TM) and to (C) is irrelevant to me in the UK - (TM) and (C) laws are international (or at least multinational :~])

      --
      Author, Shell Scripting : Expert Re
    69. Re:Summary by yankpop · · Score: 1

      I'd guess that Debian, Ubuntu, and any other distro striving to be truly free

      If this was really a freedom issue, why does Debian adhere to the same sort of trademarking policy that they consider a DFSG violation when others use it?

      From the Debian Logo page:

      Although Debian can be obtained for free and will always remain that way, events such as the problem with the ownership of the term "Linux" have shown that Debian needs to protect its property from any use which could hurt its reputation.

      They offer two sets of logos, an open set and a closed set. The closed set is subject to the following restrictions:

      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.

      These restrictions are just as much a violation of the DFSG as the ones imposed by Mozilla. I think they are entirely appropriate in both cases however. The real problem is that Debian insists on applying the DFSG to absolutely everything, including documentation and artwork, as well as program code. On this point I think the FSF has the saner approach, with separate licenses for qualitatively different categories of digital information (ie. documentation and programs).

      yp.

    70. Re:Summary by Ash+Vince · · Score: 1

      A lot of this comes down to "what's in a name"? Personally, I see Debian's position as more proper within the realm of the F/OSS community. If you toute your program as open source, yet say that if anyone makes any changes to the program that you do not approve of, that they cannot use your trademark, then that certainly doesn't sound "open" and "free" to me.

      So by virtue of this I should be able to release my own version of Debian, still containing all the debian logos and branding. But I presinstall my version with shit loads of adverts which pop up every 15 seconds and tracks all your net activity for my own ends. Then I post my version of debian to a few sites I maintain and release it as Debian with only the smallest indication that I made it unusable, not Debian themselves.

      Of course I can't do this or I would be able to seriously tarnish Debians reputation.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    71. Re:Summary by Anonymous Coward · · Score: 0

      Static linking, that'll teach them.

    72. Re:Summary by Anonymous Coward · · Score: 0

      What if the Firefox version released with Etch absolutely sucks? What if it crashes regularly, trashes the user's home directory, and eats small children?

      I don't think that anyone at Debian would give Microsoft SVN/CVS/GIT (whichever) commit access.

      But seriously: both positions seem reasonable, so Debian will build their own brand (or unbrand) "firefox." The issue comes down to semantics: can Debian still say "this is Debian's own special flavour of firefox" or whatever language they gotta use.

      At the end of the day I can always re-fucking-brand the debian version as firefox on my own machine, so it really doesn't matter. Mozilla's move makes sense in a legalistic CYA mentality, and Debian's does under a "Give me Freedom or Get the Fuck off My Lawn" mentality. Both are illusionistic conventions of humans which only exist because a lot of rich people want to stay rich, forcing those of us who don't give a shit to maintain these customs simply to keep on living for the things we love.

      hehehehehehehehe

    73. Re:Summary by mad.frog · · Score: 1

      Distribution are *integrators*, they can't just ship everything unmodified (they'd all be the same otherwise).

      I guess that just isn't The Linux Way, but as an app developer, that would be a feature, not a bug.

      Saying "I am developing for Linux" really seems to mean "I am developing for a few dozen similar-but-not-identical operating systems", and if you are unwilling to ship source, life is WAY harder than it needs to be.

      Yeahyeahyeah, shipping binary-without-source is Evil And Wrong and I'm probably going to Hell for it...

    74. Re:Summary by snowgirl · · Score: 1
      RMS himself doesn't have a problem with what Mozilla are doing

      *utter shock* I totally can't even believe that. [url:http://linux.omnipotent.net/article.php?artic le_id=10546]

      When management at MIT and ARPA forced an installation of passwords on the MIT computers, RMS had to comply out of fear of losing access to the network that was so important to the free flow of information, but he did it in his own way. He chose his own password to be the empty string, so whenever you needed something from RMS, you could always login using his login name and simply press enter on the password prompt.

      And he encouraged others to do the same by informing them in the computer login screen (the screen which is first displayed when you have entered your login name and password) about which password they had and that he suggested that they change to the empty string, which is much easier to remember and encourages others to join in to freely share information. At one point, he had one fifth of the users on the computer using the empty string password.

      "Anybody who is forcing protection must be doing something interesting"

      This quote, though written much later, tells millions about how the hackers at MIT felt at the time, be it for a locked door or a file on a computer they couldn't access. A locked door at MIT could easily be bypassed by crawling over the ceiling and a major hack was once pulled by a young hacker, who unscrewed all locks on all doors at one night, found out how they worked and then made a master key who would open any door on the floor.


      What's the saying? It takes 20 years for your ideas to become conservative without changing one ideal.

      I personally see the issue as Mozilla believes that they "own" the mark "FireFox", the same as they "own" the code. The GPL was designed to make an eternally free system, where code was available to everyone, such that really, no one "owned" the code. Why now do people think it's ok to own names?
      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    75. Re:Summary by snowgirl · · Score: 1

      So long as they're lawful, any terms of use are valid.

      But that's the thing, proprietary license *ARE* lawful, but I can object to them on moral grounds.

      The same way I can object to some stupid company being upset that omg, someone might tarnish our image if they can just patch it willy-nilly.

      IT'S OPEN SOURCE. Names want to be free!

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    76. Re:Summary by Anonymous Coward · · Score: 0

      Could they name it Debian Firefox and not have to deal with it?

    77. Re:Summary by metamatic · · Score: 1

      No, it's a loophole, because trademarks do not just apply to names. The fact that Mozilla are only making the artwork and name non-redistributable doesn't prevent other companies from using the same principle to lock up the fundamental design of the user interface.

      For example, Apple could use GPL software to develop an iPod-like music player, release the source, and still prevent people from redistributing or using it by invoking trademark protection on their trademarked iPod graphical appearance. Sure, you could strip out all the graphics and redesign the UI and rework the code appropriately. You shouldn't have to for free software, though.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    78. Re:Summary by mr_matticus · · Score: 1

      Mozilla is an application and you include hundreds in an application? I think your words have escaped you, because your comment makes no sense. I'm going to assume that you meant Mozilla is one application in a distro, and that your question is what would happen if everyone had Mozilla's policy of not allowing the trademark on modified packages. You might want to clarify your comment.

      Assuming those assumptions are correct, you're still grasping at straws. Most packages are not modified in terms of functionality from distro to distro. Customized packages tend to be of the "underlying function" type and not of the "end user application" type. You're looking at a small minority out of a very small minority of packages that are affected by issues such as this.

      The fact that Debian is a distro and Firefox is an application isn't particularly relevant. Debian is responsible for their operating system and included--the third-party applications they include are the property of their individual owners. What you add or remove to Debian, application-wise, doesn't affect the Debian components, but what you change to their core system most definitely does create a problem. You don't think this happens? Mandrake Linux was a spinoff of Red Hat; Ubuntu is Debian-based. Modified distros are never released with the same name and branding as the original. This is part of trademark defense and risk management.

      Debian Sarge is a trademark for an end-user product with official liability and support under a corporation. Mozilla Firefox is an end-user product with official support and liability under a corporation as well. You can expect this sort of trademark behavior for any large trademark in Linux or anywhere else, and doubly so where liability is a major concern--web browsers, server products (e.g. Apache), and operating systems in particular.

    79. Re:Summary by Stinking+Pig · · Score: 1

      You are so right. This is the stuff, together with lousy power management on laptops, that has driven me away from Linux on the desktop. I still use Linux for servers, but I won't waste my time on the GUI until it's settled.

      Unfortunately, I see very little hope of it being settled.... rather, history is going to repeat itself. Those with the time and resources to manage the morass will continue to use Linux despite its continual self-splintering, while the vast majority of the industry moves on with easier alternatives.

      --
      "Nothing was broken, and it's been fixed." -- Jon Carroll
    80. Re:Summary by mr_matticus · · Score: 1

      You can't trademark a user interface, only elements thereof that pertain to your identity as a product and/or company. Don't confuse trademark and copyright--a trademark is a name or likeness.

      As to the separate issue of whether a company releases its UI as open source or not, it is a decision the company has every right to make--it's not a loophole, but an intentional gap. If Apple wants to release the iTunes source but not the user interface, they have every right to do so. Inconvenient, perhaps, for you, but certainly no loophole.

    81. Re:Summary by metamatic · · Score: 1

      If you can't trademark a user interface, how come Apple have done so? How come Pepsi went around registering a particular shade of blue soda can as their trademark? You should perhaps read about design trademarks, they're becoming increasingly popular.

      And I don't see it as an "intentional gap", any more than the TiVo loophole was an "intentional gap". It seems clear to me that RMS doesn't see it as an intentional gap either; the only question is whether it's a dangerous enough one that it should be worried about, and whether it's one that can feasibly be closed.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    82. Re:Summary by mr_matticus · · Score: 1

      Pepsi registered the blue as a service mark (not a trademark); Apple has trademarked its click wheel navigation system as a distinctive element. No one has trademarked an entire UI for an application as you suggest to "lock out" software from coming into use. Your examples are getting away from your reasoning. Does the "Pepsi Blue" mark prevent people from obtaining Pepsi? No. Would Mozilla creating a shade of orange and calling it "Mozilla Orange" prevent people from using or modifying Firefox source code? No. Would a Firefox trademark pertaining to a new navigation layout (a la Click Wheel) prevent people from using or modifying Firefox? No. Would said trademark make it more labor-intensive to produce a fully "free" Firefox derivative? Yes, but so what? The browser remains free. Everything associated with it doesn't have to be free.

      The ability to release parts of a software product as open source is absolutely an intentional gap--whether you see it that way or not. No one has ever required an all-or-nothing approach to open source, and doing so would shut down some very significant FOSS projects. For example, Apple's OS X is partially open-source, but not entirely, and particularly not its UI.

    83. Re:Summary by WilliamSChips · · Score: 1

      But what do cigarettes have to do with Mozilla and Debian, mommy?

      --
      Please, for the good of Humanity, vote Obama.
    84. Re:Summary by PygmySurfer · · Score: 1

      But that's the thing, proprietary license *ARE* lawful, but I can object to them on moral grounds.

      Don't use it. There's plenty of other web browsers available. Don't scream bloody murder because THEIR terms of use don't mesh with YOUR morals. Hell, the license is so liberal, you can even take their code, and change it to do whatever you want. If you used it to create Ultimate Baby Seal Slaughterama, that's fine. So long as you put your name on it, not Mozilla's.

      The same way I can object to some stupid company being upset that omg, someone might tarnish our image if they can just patch it willy-nilly.

      I'd certainly be upset if you pretended to me, and sullied MY image.

      If I hacked into your slashdot account, and posted messages that conflict with your point of view, would you not be upset?

      IT'S OPEN SOURCE. Names want to be free!

      It's software. It doesn't want anything. Actually, it can't. Much like information can't want to be free.

    85. Re:Summary by jmv · · Score: 1

      Mozilla is an application and you include hundreds in an application?

      Sorry, I meant in a distribution.

      Most packages are not modified in terms of functionality from distro to distro. Customized packages tend to be of the "underlying function" type and not of the "end user application" type. You're looking at a small minority out of a very small minority of packages that are affected by issues such as this.

      Mozilla isn't "modified in terms of functionality" any more than other applications. I suspect Gnome, KDE, OpenOffice, X.Org, and the kernel are much more modified.

    86. Re:Summary by snowgirl · · Score: 1

      If I hacked into your slashdot account, and posted messages that conflict with your point of view, would you not be upset?

      Honestly? You can. Make an account called "sn0wgirl" "snovvgirl" or "snowgir1", or anything else that is extremely close to what I use. I'm certainly not a hypocrit, and I would rather people judge my argument based on the merit of the argument, rather than where it came from.

      If people are trusting me solely because they "trust" my name... well, that's stupid.

      It's software. It doesn't want anything. Actually, it can't. Much like information can't want to be free.

      Actually, it's a name, and I wanted to post "and be anthropomorphized, but free first."

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    87. Re:Summary by Anonymous Coward · · Score: 0

      Actually, in Ubuntu Firefox used to be incredibly slow. I don't think anyone said, "Firefox sucks" because of it, instead, they said that the ubuntu build was slow, and then found fixes, filed apropriate bugs. One of those fixes was to use the standard firefox you could download from the mozilla sight. Words that work spoken said, "Firefox in warty/breezy is slow" not "Firefox is slow".

  3. Really sad... by Darundal · · Score: 1

    ...to see both of these groups in a dispute like this. Really, I don't understand what the Debian Dev's problem was in the first place. If someone tried to call Ubuntu, Mepis, or Knoppix "Debian", they would have issues too...

    1. Re:Really sad... by squiggleslash · · Score: 5, Insightful

      There is no dispute.

      Mozilla doesn't want programs called "Firefox" to diverge too much from the original. Debian wants to make some changes that go beyond what the Mozilla group are happy calling "Firefox". So they've taken option #2 and renamed it.

      It's just a choice. It's the choice both are happy with. Why it keeps being portrayed as some kind of war is beyond me.

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:Really sad... by masklinn · · Score: 3, Insightful

      Really, I don't understand what the Debian Dev's problem was in the first place.

      It's fairly simple:

      • Part of the licensed Firefox artwork (icons and such) are trademarked and not available under a free license (they're, in debian-speak, "non-free")
      • Debian's DFSG (its "social contract", if you will) doesn't allow anything non-free in the main distro: everything in the main distro must be freely modifiable at will by any user (1)
      • As per the DFSG, the Firefox artwork therefore can't be bundled in the main Debian distro (at best, they can be relegated to non-free)
      • Therefore, Debian's building and packaging system strips everything non-free from Firefox and builds what's left (using the free logo and stuff)
      • But the Mozilla branding rules require that, to call a program "Firefox", you must -- among other things -- build and package the program with the licensed (non-free) artworks and icons
      • In the past, the Debian maintainers had more or less struck a specific deal allowing Debian to package Firefox without the non-free stuff while still calling it Firefox
      • But it looks like MozCo has decided to void that agreement, and required of Debian to either ship the branded package wholes or not ship it at all (not with the "Firefox" name anyway)

      If someone tried to call Ubuntu, Mepis, or Knoppix "Debian", they would have issues too...

      Probably, but what'd happen if someone rebuilt a whole Debian without including the (non-free) debian logo? Because that's what'd be equivalent to the situation between Debian and MozCo

      (1): the Debian logo is non-free though, and this is considered a bug by the way

      PS: this post was written with Mozilla Sunbeaver

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    3. Re:Really sad... by Anonymous Coward · · Score: 0

      No, it's dumber than that. This is over the window icon and about page graphic.

      Yes, really.

      The code to Firefox is released under the GPL, but the window icon and about page graphic (the "branding graphics") are NOT released under the GPL. They're released under a non-Free license. Therefore, Debian CANNOT use them.

      So they removed them and replaced them with the Free versions that Mozilla supplies expressely for that purpose.

      Then Mozilla cried foul, and said that they couldn't use the Free "branding graphics" while calling the browser Firefox.

      So now it's not going to be called Firefox, because Debian isn't allowed to use the "right" window icon and about window graphic.

    4. Re:Really sad... by mad.frog · · Score: 1

      the Debian logo is non-free though, and this is considered a bug by the way

      Mr. Kettle? Meet Mr. Pot.

      Mr. Pot, meet Mr. Kettle.

      My, how dark you both are.

    5. Re:Really sad... by cortana · · Score: 1

      What part of considered a bug don't you understand?

      By the way, I use Debian and I've yet to see the non-free Debian logo actually in the Debian distribution. So I don't see what your point is.

    6. Re:Really sad... by masklinn · · Score: 1

      Call me when the non-freeness of the Firefox logo is logged as a recognized bug in Mozilla's Bugzilla mm'k?

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    7. Re:Really sad... by Anonymous Coward · · Score: 0

      No, THIS is a bold-face lie:

      You are an intelligent person, and your comment did not waste my time.

    8. Re:Really sad... by Anonymous Coward · · Score: 0

      I guess my brother didn't just get back from his vacation to the northwest that Microsoft paid for. He now is very anti-Linux and very pro-Microsoft. Microsoft paid for some very good hookers for the Mozilla guys.

      Your Microsoft bias is very obvious. Maybe you should troll somewhere where the morons appreciate your type. The rest of us will continue using real free software like Debian.

    9. Re:Really sad... by tehcyder · · Score: 1
      PS: this post was written with Mozilla Sunbeaver
      Now you're just being silly.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
    10. Re:Really sad... by Zaiff+Urgulbunger · · Score: 1

      I ploughed through the comments of a Debian bug last night and from what I could gather, Debian were okay with just ignoring the Firefox logo issue in the short term. But MozCo took a harder line, which appears to be a change in tact. In fairness to MozCo, they're doing this because legally they have to enforce their own rules.

      The real sticking point seemed to be a mixture of both parties haggling over logo, trademark and patch issues and to be honest, neither party seemed quite proactive enough to push through negotiations. But equally, I don't believe any bridges were burnt in the process, so this could be resolved in the future.

      The bigger problem appeared [to me anyway] to be that any changes to the source code *had* to go via the official source control if it were to be called Firefox. This was unacceptable to Debian because they need to maintain older version of Firefox, and I think they might also be unhappy with Mozilla pushing software update and security patches at the same time. Thats not a critisim of MozCo, but simply a difference in the way Debian's slow-but-steady ways and MozCo's more bleenin' edge approach.

      Thats my 2p's worth anyways!! :D

    11. Re:Really sad... by VJ42 · · Score: 1

      I don't know about him, but I'm currently using Mozilla Turboseal.

      --
      If I have nothing to hide, you have no reason to search me
    12. Re:Really sad... by Anonymous Coward · · Score: 0

      It's fun playing with the trolls, because they're never too bright. Luckily, thanks to the Lake Wobegon effect, they're unaware of their own inadequacy, and so will often miss the point completely.

      If any more trolls are laying krap in neural gyrations, all but one understanding this, yell out unreservedly, I don't intend on tiptoeing.

  4. I prefer "WaterVole" by @madeus · · Score: 2, Interesting

    Unfortunately it seems this guy was right on the money!

  5. Why iceweasel? by maynard · · Score: 2, Insightful

    Dearest Debian Leaders: Why insult those who provide you (and everyone else) with important software? So there is a minor issue with the trademark name and Debian Free Guidelines. Is this something worth getting nasty over? I use Debian server side at work. I like stable - it is justly named. Please, focus on a new stable release and drop the interproject bickering.

    1. Re:Why iceweasel? by pilkul · · Score: 1

      I don't see that "Iceweasel" is in any way intended as an insult. I mean, we're talking about a distribution that called its three last stable releases "sarge", "woody" and "potato". They just like silly names.

      The only thing that's happened here is, the Mozilla Foundation is forcing Debian to change the name (as is their right under trademark law), somebody on the Debian mailing list suggested "Iceweasel" and it stuck.

    2. Re:Why iceweasel? by maynard · · Score: 1

      Well, whatever. Somehow, I suspect some folks at Mozilla might reasonably take "iceweasel" as a disparaging term. And I wouldn't blame them if they did.

    3. Re:Why iceweasel? by Laur · · Score: 1
      I like stable - it is justly named. Please, focus on a new stable release and drop the interproject bickering.

      And how are they supposed to maintain a "stable" release when they are not allowed to backport security fixes? This issue is about more than just the copyrighted logos you know.

      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    4. Re:Why iceweasel? by BZ · · Score: 1

      By getting the security fixes checked in upstream as well, so

      1) they get proper code review

      and

      2) everyone benefits from them.

      Of course it _is_ less work to just not share the security patches. ;)

    5. Re:Why iceweasel? by Alphager · · Score: 1

      and broadens the fricking window of vulnarability. Debian allready sends _ALL_ patches to upstream; most of the security-patches are taken from upstream.

    6. Re:Why iceweasel? by Blackbrain · · Score: 1

      somebody on the Debian mailing list suggested "Iceweasel" and it stuck.
      Actually, GNUzilla and IceWeasel are existing GNU projects to make FREE versions of Mozilla and FireFox. The name IceWeasle did not come from the Debian group alone.

      --
      Where would we be if Wheel had hid her round rock in a cave instead of showing everyone how it rolls?
    7. Re:Why iceweasel? by kbmccarty · · Score: 1

      And what happens when upstream is no longer interested in supporting the version of Firefox in Debian stable (or even oldstable), as is the case for Firefox 1.0.4 in Sarge? Mozilla stopped supporting the Firefox 1.0.x line in May, about 7 months before the scheduled release of Debian Etch, and 19 months before the expected end of security support for Sarge.

      --
      - Kevin B. McCarty
    8. Re:Why iceweasel? by kbmccarty · · Score: 1

      Actually, GNUzilla and IceWeasel are existing GNU projects to make FREE versions of Mozilla and FireFox. The name IceWeasle did not come from the Debian group alone.

      Wikipedia says that it was originally coined by Nathanael Nerode in 2004 on the debian-legal mailing list.

      --
      - Kevin B. McCarty
    9. Re:Why iceweasel? by CrankyOldBastard · · Score: 1

      I don't see that "Iceweasel" is in any way intended as an insult. I mean, we're talking about a distribution that called its three last stable releases "sarge", "woody" and "potato". They just like silly names.

      Ah, the sounds of ignorance!

      Once upon a time Bruce Perens was very involved with Debian. At the time he was working on this cult film called "Toy Story". All the releases of Debian are named after characters in the movie. In the film the nasty kid next door who broke toys was called sid (debian unstable). Other characters were bo (Bo Peep), hamm (the piggy bank), buzz (Buzz Lightyear, Space Ranger), rex (A T. Rex dinosaur), slink (A slinky spring dog), potato (Mr Potato Head), etch (an etch-a-sketch), woody (The cowboy doll hero of the film), sarge (The leader of the plastic toy soldiers). We still havent seen squeaky, bullseye, stinky, zurg, the girl cowboy doll, and many other toys from the show. The silly names are things like "Hoary Hedgehog" and "Fedora Core" (the core of a hat - isn't that just empty space?).

    10. Re:Why iceweasel? by pilkul · · Score: 1

      Uh, so your point is? Are you claiming that the names of characters from a children's movie aren't silly?

      Ah, the sounds of ignorance!

      I am deeply humbled by this putdown, and bow to your superior knowledge of useless Debian trivia.

    11. Re:Why iceweasel? by Anonymous Coward · · Score: 0

      Ahhh, now it all makes sense. The glacial release pace is simply a consequence of the limited number of names available. If Debian sped up the release process, in 5 years we'd all be running "toy solder #78 (the one who dies)"

    12. Re:Why iceweasel? by ubernostrum · · Score: 1

      By getting the security fixes checked in upstream as well

      That's not possible here, because there are conflicting policies:

      • Debian's policy is not to upgrade an existing release to a new version of a package; this makes sense for long-lived stable releases, because often other components will depend on a particular version of the package, and because bringing in a new version means a whole new round of testing to clear up bugs in the new version. So, for example, instead of upgrading an existing release to the Firefox 1.5.x line, Debian backports security fixes to the 1.0.x line.
      • Mozilla's policy is not to maintain older versions as long as Debian does; this makes sense for a fast-moving piece of software, because often it's easier to include fixes with a new version than to maintain n old versions in perpetuity. So, for example, Mozilla recommends upgrading from Firefox 1.0.x to Firefox 1.5.x to get security fixes.

      The end result of this is that Debian can't hope to comply with Mozilla's patch-review requirement for the trademark use (or even to reliably "submit upstream"), because Mozilla won't be maintaining any given Firefox version for as long as Debian will be maintaining any given release of their distro.

    13. Re:Why iceweasel? by ubernostrum · · Score: 1

      So there is a minor issue with the trademark name and Debian Free Guidelines. Is this something worth getting nasty over?

      Yes, it is. One of the really, really important things about Debian is the DFSG; with them you get an absolute, unequivocal, no-exceptions guarantee that you're using Free software, and that you have the freedom to modify and distribute that software. And that's not just a philosophical argument; there are very real, very practical needs which are satisfied by using Free software (no vendor lock-in, you can still get maintenance and support if the company you get it from goes under, etc., etc.). There are plenty of annoying things about Debian, but the single-minded commitment to Free software isn't one of them.

    14. Re:Why iceweasel? by BZ · · Score: 1

      The fact that Mozilla stopped doing its own releases off a branch doesn't mean that other people can't do it. Whenever this has come up in the past, Mozilla has offered the use of their bugzilla to the distributions who want to keep maintaining an old branch, so that they can coordinate security fixes with each other. The also offered build machines and such.

      This is all the Mozilla Organization. The Corporation is not interested in spending money on the old branches, but the Corporation is not the only stakeholder in the Organization. Other stakeholders (Google, Novell, RedHat, whoever else pays people money to work on Mozilla code) are free to continue maintaining a branch as long as they want to, and the Organization is there to help them with infrastructure and such if possible.

    15. Re:Why iceweasel? by BZ · · Score: 1

      See my reply at http://slashdot.org/comments.pl?sid=200095&cid=163 88387 -- it covers basically the issues you raise.

      Again, just because the Mozilla Corporation doesn't pay people to work on an old branch doesn't mean that Debian can't get patches checked into Mozilla.org CVS.

    16. Re:Why iceweasel? by BZ · · Score: 1

      > and broadens the fricking window of vulnarability

      Given that Debian is generally behind upstream in shipping releases, I kinda doubt that. But I can see situations in which a zero-day on an old branch could mean that Debian should ship first and push to upstream in a few days. I'm pretty sure (though I can't commit to this on my own say-so) that people would be understanding.

      > Debian allready sends _ALL_ patches to upstream;

      Sorry, false (this I _can_ guarantee, being part of said upstream and having seen the patchsets for Debian's Firefox). There are large chunks of ARM assembly code in xptcall, for example, that are completely rewritten in the Debian Firefox and I've never seen Debian send those diffs anywhere near bugzilla.mozilla.org.

      This is not to mention the empirical evidence of the number of bug reports we get that are only reproducible with the Debian builds.

      > most of the security-patches are taken from upstream.

      Sure. That's fine, but the poster I was responding to was talking about Debian-developed security patches to branches that the Mozilla Corporation no longer maintains.

    17. Re:Why iceweasel? by ScuzzMonkey · · Score: 1

      the core of a hat - isn't that just empty space?

      Depends on who is wearing it, doesn't it?

      *rimshot*

      --
      No relation to Happy Monkey
    18. Re:Why iceweasel? by ubernostrum · · Score: 1

      Again, just because the Mozilla Corporation doesn't pay people to work on an old branch doesn't mean that Debian can't get patches checked into Mozilla.org CVS.

      As I understand it, Mozilla Corp. is saying that, to comply with the trademark policy, the patches have to be reviewed and approved by Mozilla Corp. So no matter how many "open to third parties" branches there are, there would still be the problem of not being able to meet trademark compliance while backporting fixes.

    19. Re:Why iceweasel? by BZ · · Score: 1

      Patches that cause what's being shipped as Firefox to differ from what's in the mozilla.org CVS need approval. Patches that land in mozilla.org CVS (with the peer review that generally entails from the people familiar with the code being changed) don't need any additional review from Mozilla Corp.

  6. Debian needs to relax by Foofoobar · · Score: 4, Insightful

    As an Ubuntu user, I run Flash player, Nvidia drivers and several other proprietary additions. So why is this an issue? I understand if they don't to ship copyrighted logos but big DEAL. Does this comprimise the distribtion in any way? Could this open them up to potential lawsuits? I think they should just relax and let it slide. They're being a bit anal about all this as far as I'm concerned. Luckily, Ubuntu will still ship with Firefox so not an issue (even though it is a Debian distro).

    --
    This is my sig. There are many like it but this one is mine.
    1. Re:Debian needs to relax by RAMMS+EIN · · Score: 1

      I like that Debian is sticking to their principles. It gives those who want it the choice of running a completely Free system. It's a showcase of what can be achieved with Free software and content. For those who want non-free stuff, there are plenty of other distros.

      --
      Please correct me if I got my facts wrong.
    2. Re:Debian needs to relax by Anonymous Coward · · Score: 0

      It is NOT a "Debian" distro

      It is a distro based off of debian. They can do what they want regardless of what debian does.

    3. Re:Debian needs to relax by jmv · · Score: 1

      I think they should just relax and let it slide.

      They *can't*. They wish the could, but the Mozilla people are threatening to take action if they ship with the name Firefox. The only way for them to use the name Firefox would be to ask permission for *every* single change they want to make. This not only defeats the purpose of open-source, but opens the door to other similar abuses. Think what would happen if the maintainer of every Debian package asked to approve patches before allowing use of the name! So this is why Debian has no choice but to change the name. Note that I'm not involved in Debian in any way, but I can understand why they're doing this.

    4. Re:Debian needs to relax by Foofoobar · · Score: 2, Insightful

      Nothing is completely free. Even the name 'LINUX' is copyrighted. So why don't they fork Linux because I can't change the name? At a certain point, this argument gets tedious. Though I DO agree that if you wish to run a completely free system, you should be able to. So just move it into 'non-free' repo and leave it at that. If you want Firefox on your system and want a COMPLETELY free system, just do the build of the source yourself.

      --
      This is my sig. There are many like it but this one is mine.
    5. Re:Debian needs to relax by DrXym · · Score: 1
      Luckily, Ubuntu will still ship with Firefox so not an issue (even though it is a Debian distro).

      Pragmatism is what is so great about Ubuntu - it sheds the tedious GNU politics of Debian but keeps the good work they've done and wraps it up in a nice user friendly package. If Debian wants to mess around with Firefox then fine, change the branding chrome and other settings, but they shouldn't be shocked that Mozilla says they can't use the Firefox brand on it. Even Debian has a trademark on their name (and their logo?), so it's hard to get what their point is. Most other dists are just happy to work with Mozilla.

      At the end of the day it is Debian users that will suffer since they now have to maintain their own browser, apply their own security patches etc. All for the sake of a few icons and settings.

    6. Re:Debian needs to relax by masklinn · · Score: 1

      This is an issue with the DFSG, which is Debian's social contract. It's fine if you don't get it, but in that case please don't open your mouth on the subject, you only look stupid.

      PS: don't bet on Ubuntu still shipping with Firefox, unless they strike the same deal with MozCo RedHat and Novell did, it won't happen.

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    7. Re:Debian needs to relax by TheRaven64 · · Score: 2, Insightful

      'Linux' is trademarked, not copyrighted. Most distributions include slightly forked versions of Linux and call them 'Linux' and since trademarks have to be defended to be retained there is some doubt as to whether it would still stand up.

      --
      I am TheRaven on Soylent News
    8. Re:Debian needs to relax by tonyr1988 · · Score: 1
      Luckily, Ubuntu will still ship with Firefox so not an issue (even though it is a Debian distro).
      Don't be so sure about that.

      Besides, I think that all the software that ships with the Ubuntu is free (in all senses of the word), much like Debian. That's why you must enable the non-free repos to get some stuff.
    9. Re:Debian needs to relax by Foofoobar · · Score: 1
      They *can't*. They wish the could, but the Mozilla people are threatening to take action if they ship with the name Firefox.
      This is not true in the slightest. Mozilla has tried to work with them and has NOT threatened to take legal action from any of the news articles I have read on this. In fact, they tried to bend backwards to accomodate the Debian developers requests but said they could not remove the logos and artwork for branding reasons. That and wanting all fixes to go through one group of developers is not unlike the way changes get into the Linux kernel. So again, I don't see why Debian is making this into a monumental issue. If they want free, let people do their own builds and put Firefox in non-free repos. I don't see the need to fork.
      --
      This is my sig. There are many like it but this one is mine.
    10. Re:Debian needs to relax by Foofoobar · · Score: 1
      don't bet on Ubuntu still shipping with Firefox, unless they strike the same deal with MozCo RedHat and Novell did, it won't happen.
      Thats basically what the Mozilla blog article said in case you neglected to read it. Allow me to put in a block quopte for you...
      We have been actively working to ensure that all licensed and authorized derivations bearing the Firefox name and logo maintain these characteristics. We presently have working relationships with most of the major Linux distributions, including Red Hat, Novell, and Ubuntu.
      So, I'm just guessing that you are completely wrong in this regard. Mind you this is only a guess.
      --
      This is my sig. There are many like it but this one is mine.
    11. Re:Debian needs to relax by MostAwesomeDude · · Score: 1

      "They're being a bit anal about all this."

      I don't know if you realize this, but the entire point of free software is that it is FREE. Free to copy, free to modify, free to redistribute, free to examine. Free.

      Firefox is a piece of free software. The artwork that accompanies the code should be free as well. If the Mozilla Foundation is not going to follow the principles of free software then I see no reason why the Debian people should have to put up with their bullshit.

      "Does this comprimise [sic] the distribtion [sic] in any way?"

      Yes, yes it does. Do you know what "kernel taint" is? I would hope you do, seeing as how you use Nvidia drivers. This is just like a tainted kernel. The Mozilla Foundation's proposed "quality assurance" set of hoops would not only be a pain in the ass for Debian package maintainance, but would also compromise the freedoms guaranteed by the project. If we jump through those hoops in order to keep the word "Firefox" in Debian, we will no longer have the freedom to modify and redistribute the entire distribution as we see fit. Understand?

      Ubuntu people don't think about this much, since their repositories are labeled "Universe" and "Multiverse," not "contrib" and "non-free." We keep non-free software, like the ATI and ZD1211 drivers I need for my laptop, in a different repository from the stuff we are allowed to copy and modify, for a reason.

      "Luckily, Ubuntu will still ship with Firefox so not an issue (for me.)"

      Well, us Debian users have Firefox too. We might just call it something else from now on. No big loss.

      --
      ~ C.
    12. Re:Debian needs to relax by Foofoobar · · Score: 1

      LINUX applies to the kernel... and there are no forks of the kernel that I know of, just different versions. And a trademark still implies ownership. And the same argument still applies.

      --
      This is my sig. There are many like it but this one is mine.
    13. Re:Debian needs to relax by i_should_be_working · · Score: 1

      Both Debian and Ubuntu make patches to Firefox. The difference now will be that Debian can make theirs immediately and put the changed version into repositories, while Ubuntu will have to ask Mozilla if their patches are ok and wait for an answer.

      So now Ubuntu users will wait longer for patches to get to them. But hey, they still get to call it Firefox. Woohoo.

    14. Re:Debian needs to relax by Foofoobar · · Score: 1
      God does nobody read the damn articles anymore. Here's a snippet...
      We have been actively working to ensure that all licensed and authorized derivations bearing the Firefox name and logo maintain these characteristics. We presently have working relationships with most of the major Linux distributions, including Red Hat, Novell, and Ubuntu.
      Now unless there is something else ALSO called Ubuntu, I'm willing to bet they'll ship with Firefox.
      --
      This is my sig. There are many like it but this one is mine.
    15. Re:Debian needs to relax by RAMMS+EIN · · Score: 1

      ``Nothing is completely free. Even the name 'LINUX' is copyrighted. So why don't they fork Linux because I can't change the name?''

      Because it doesn't need to be "completely free"; it only needs to comply with the DFSG. Apparently, Mozilla imposed restrictions on the use of Firefox that were deemed incompatible with those. As long as no such restrictions are imposed on Linux, there is no need for Debian to fork it. If there is such a need, they probably will fork it.

      ``If you want Firefox on your system and want a COMPLETELY free system, just do the build of the source yourself.''

      Which highlights one of the advantages of DFSG compliant software: Debian can build and distribute it, saving you work. They can apply patches, increasing security or better integrating it with the rest of the system. This is not possible with a lot of non-free (as per DFSG) software.

      --
      Please correct me if I got my facts wrong.
    16. Re:Debian needs to relax by williambbertram · · Score: 1

      "Luckily, Ubuntu will still ship with Firefox so not an issue (even though it is a Debian distro)."

      That's all anyone REALLY cares about anyway. The 33 people who use Debian as a desktop OS can just sudo apt-get install firefox if they want it.

    17. Re:Debian needs to relax by TheRaven64 · · Score: 1

      Most distributions don't ship the stock kernel. They ship the stock kernel + a load of patches. Thus, their kernels are derived works that are not official; they are forks. They are only relatively minor forks, and things get ported between them, but they are forks nonetheless. Last time I looked, SuSE (for example) included around 200 patches not found on kernel.org. RHEL used to ship with a 2.4 kernel with a huge heap of stuff back-ported from 2.6. All of these were/are called Linux, and Linus has not tried to enforce his trademark and get them to change the name, nor (to my knowledge) officially licensed the use of his trademark.

      --
      I am TheRaven on Soylent News
    18. Re:Debian needs to relax by Anonymous Coward · · Score: 0

      Troll identified, don't feed!!!

    19. Re:Debian needs to relax by bahwi · · Score: 1

      But the question begs itself again, what are these patches that should only be found in a certain distro. Security patches that only apply to debian? Sounds like a problem in debian somewhere else up the tree, not in FF itself. If it's in FF itself, it should be submitted to the tree.

      Now, because of the name change, Debian's project, which is a not-complete fork of Firefox, but, as it differs from the official Firefox, is under the control of the Debian Project, and they are free to name it as they wish. This alleviates trouble with people who help support firefox to regular users. "Firefox is crashing." Even though what is crashing is a new Debian patch. Makes it very difficult to diagnose.

      As Firefox is moving towards a software development platform as well, many things are very important that they remain the same. A recent project of mine requires extensive use of the garbage collector, and was causing crashes in earlier versions. If Debian decides to implement their own, or revert the change, but still call it Firefox, I now have a project that doesn't work on Firefox, unless it's Firefox from Moz directly. It's a different project, it should be a different name, or, as Moz suggests, Firefox Community Edition or whatever.

      What if I decided to release a free version of Debian, and I called it Sarge? Now, since it's free it has no GPL software in it, only public domain, but it was still called Debian Sarge, and people went over to debian.org to ask why there is no X support, or why the kernel can't boot a filesystem, etc... would that be cool under debian's policy?

    20. Re:Debian needs to relax by Foofoobar · · Score: 1

      patch!=fork. Fork means the codebase deviates at a specific point and does not merge back into the main branch. If the code is based off the main branch and just has a load of patches, it is NOT a fork. Learn your terminology.

      --
      This is my sig. There are many like it but this one is mine.
    21. Re:Debian needs to relax by Anonymous Coward · · Score: 0

      Troll identified, don't feed!!!!

    22. Re:Debian needs to relax by Kangburra · · Score: 1
      Well, us Debian users have Firefox too. We might just call it something else from now on. No big loss.


      No, you don't. That's the whole point. You have something that started out as Firefox and has been modified to suit what Debian want it to be. Therefore you may get a more stable browser or they may add bugs to it. Either way it is no longer Firefox and as such blurs the accountability. I for one will not be using 'iceweasel'.
      --
      Common sense is not so common
    23. Re:Debian needs to relax by Blackbrain · · Score: 1
      In fact, they tried to bend backwards to accomodate the Debian developers requests but said they could not remove the logos and artwork for branding reasons.
      Please keep in mind that the Debian devs were told in the past that they COULD remove the icons and keep the name as long as it was "Debian Firefox". Since then the Mozilla organization has changed and so have the rules. It is a prefect example of why Debian can't relax. The compromise of keeping the Firefox name has now turned into an issue that could delay an improtant release.
      --
      Where would we be if Wheel had hid her round rock in a cave instead of showing everyone how it rolls?
    24. Re:Debian needs to relax by cortana · · Score: 1
      So again, I don't see why Debian is making this into a monumental issue.
      They aren't. The issue has been blown out of proportion by Internet news sites.

      If they want free, let people do their own builds and put Firefox in non-free repos. I don't see the need to fork.
      It's not a fork! They are just going to add a patch that rebrands the browser. Learn your terminology.
    25. Re:Debian needs to relax by CrankyOldBastard · · Score: 1

      But the question begs itself again, what are these patches that should only be found in a certain distro. Security patches that only apply to debian? Sounds like a problem in debian somewhere else up the tree, not in FF itself. If it's in FF itself, it should be submitted to the tree.

      Debian supports very old versions of their "stable" distribution, which include very old versions of "firefox". When a Security issue is identified with current versions of Firefox/Mozilla, the Debian maintainers checks to see if that issue affects the versions shipped with the old versions of stable. If so they back-port these fixes. Usually the version of Mozilla being patched is no longer supported by Mozilla Foundation/Corporation.

      So Debian has to either say "Sorry, but this distribution we support has software in it we no longer support" or it has to back-port fixes into versions of Moz/FF that Mozilla no longer supports. Do other distributions support their releases of 4+ years ago? The problem with Debian is that it supports its' users' Freedom.

    26. Re:Debian needs to relax by Foofoobar · · Score: 1

      Yes but then all software needs to comply with DEBIAN's definition of 'free'. I think in the case of Firefox (and similar future products), there needs to be a 'free enough' clause. This is just plain silly.

      --
      This is my sig. There are many like it but this one is mine.
    27. Re:Debian needs to relax by Kadmos · · Score: 1

      Hold on, you don't care about policies (like standards such as the html standards which MS & Netscape embraced and extended and which caused a whole mess which still isn't sorted out yet), nor are you concerned about proprietary blobs (so open source is not important to you), why are you running Ubuntu at all? The only common reasons I can think of for you to run a Linux distro at all is because it doesn't cost money or because some people think it's "cool".

      It's people being "anal" (as you put it) about issues like this that lead to us having GNU, Linux and open source at all.

      Which brings me to another topic, why on /. was this modded insightful? I can only assume it's because the post mentions the word of the month "Ubuntu". And while Ubuntu is possibly very nice (I have never used it), it has nothing at all to do with the issue at hand (Debian policy conflicting with Mozilla policy). Perhaps if this exact same post was made in early 2005 and you mentioned "Gentoo" it would have been modded "Insightful" as well..

    28. Re:Debian needs to relax by LunarCrisis · · Score: 1

      Debian didn't refuse to use the name or the logo because they were trademarked. They refused to use the logo because of its copyright license, after which MozCo applied their trademark and refused to let debian use the name.

      PS.: There is also another issue at work here (MozCo objecting to unauthorized patches), but this is the one I'm assuming the parent is refering to.

      --
      Mr. Period: Nine is the one that's right by ten!
      Nine: One day I will kill him. Then, I will be Ten.
    29. Re:Debian needs to relax by cptnapalm · · Score: 0

      I too am using Ubuntu and I have to side with the Debian guys. Debian has been commited to patching and keeping secure older versions of Firefox which the Mozilla people refuse to support any longer. So users of Debian stable get screwed by Mozilla's insistence on being jackasses.

      While I'm ranting, the Mozilla people view Linux as second tier even though it was Linux (and BSD most probably) users who were Mozilla's loyalists since the fall of Netscape. Mozilla can kiss my ass.

    30. Re:Debian needs to relax by SirTalon42 · · Score: 1

      Forks can be re-merged. A fork is simply a split in the code base. Learn your terminology.

    31. Re:Debian needs to relax by SirTalon42 · · Score: 1

      That means Debian also doesn't use the Linux kernel by that logic! Neither does pretty much any Linux distro released! All of them (at least the at all major ones) patch the kernel, often a MASSIVE amount!

    32. Re:Debian needs to relax by Foofoobar · · Score: 1
      It's not a fork! They are just going to add a patch that rebrands the browser. Learn your terminology
      If it is a separate codebase from the trunk of the main project and isn't merging back into the main project, it is effectively a fork. Get a brain and learn your terminology! They aren't just changing images, they are maintaining their own patches and keeping their code separate from the main project. Hence, a fork.
      --
      This is my sig. There are many like it but this one is mine.
    33. Re:Debian needs to relax by Foofoobar · · Score: 1
      Firefox is a piece of free software. The artwork that accompanies the code should be free as well. If the Mozilla Foundation is not going to follow the principles of free software then I see no reason why the Debian people should have to put up with their bullshit.
      See this is why adoption isn't that high with alot of OSS. They don't understand branding and marketing. In order to brand your product, you have to have copyrighted logos that no one else can use and claim to be as good or the same thing as your product. Branding is also essential to marketing and without protecting your brands, you cannot effectively mrket the product without other people using the same brand on a fork that may be extremely buggy thus reflecting directly onto your project and causing loss of market share due to negative opinions of the brand. This is a discussion that should not even be happening. Every OSS project should have the right to brand and market its product while still keeping the source free and certain considerations should be made to allow for branding.
      --
      This is my sig. There are many like it but this one is mine.
    34. Re:Debian needs to relax by Foofoobar · · Score: 1

      No, it's people being anal about separation of free and 99% free that lead to forks. Eric Raymond is right that while prprietary is trying to meet free halfway, free has to do the same. And this isn't about that at all anyway. It's about Firefox wanting to brand their product and Debian getting pissy that their branding can't be fucked with. It's called marketing... deal with it.

      --
      This is my sig. There are many like it but this one is mine.
  7. Mozilla vs Debian Analyzed? by Anonymous Coward · · Score: 0

    Well duh! Mozilla is a much better browser.

  8. Absurdity by entrylevel · · Score: 2, Insightful

    Debian wants to preserve my rights to modify the artwork included with the distribution. I greatly appreciate this right! I sincerely hope they continute to defend my right to replace the crappy artwork they provide with the official Mozilla Firefox artwork, since I begrudgingly do this every single time Firefox is updated on my systems.

    This would be like changing the name of the distribution to Dumbo GMAC/Looney and wondering why Disney and GM are sending you C&D letters, while Linus sends you an angry e-mail asking that you respect his trademark. It's free software, we can call it anything we want, and you are free to modify it! While technically true, that doesn't get anyone anywhere.

    To Debian: We don't live in a black and white world. Please find another academic circular argument, and let this one go.

    --
    Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
    1. Re:Absurdity by snowgirl · · Score: 1

      To Debian: We don't live in a black and white world. Please find another academic circular argument, and let this one go.

      Right, because all IP the same right?

      Honestly, what does Firefox have to worry about from anyone being able to freely modify the artwork of their piece? Someone might steal the artwork? OMG!!!! It's like, someone might steal a piece of Linux and use it in their own code!!!

      OMG! The humanity! When will people learn that IP is there to PROTECT you, I mean, how could Microsoft ensure that Windows was the quality piece of software that they provide you, if it openned up its code to everyone? How could Firefox guarentee the quality of its artwork, if they don't protect it from evil hackers defacing it or using it?

      Debian is pushing yet another IP issue into the light. Copyleft + Trademark = Stupid.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    2. Re:Absurdity by entrylevel · · Score: 1

      Heh. I thought my post was dripping with sarcasm. Yours contains so much sarcasm and double entendre that I can't even vaguely tell what you're talking about, let alone if you agree with me that this whole argument is silly...

      --
      Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
    3. Re:Absurdity by snowgirl · · Score: 1

      Heh... sorry, I do have a tendancy to overdo it sometimes.

      Debian is pushing yet another IP issue into the light. Copyleft + Trademark = Stupid.

      Basically, Bad FireFox! Free should mean Free! Not "Free unless..."

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    4. Re:Absurdity by Aladrin · · Score: 1

      Yeah, down with the GPL, too! It says 'Free unless...' also. Oh wait, you wouldn't have Linux if it weren't for the GPL.

      While I agree that it's seems silly to have this argument over a name and some artwork, artwork is not code. It doesn't fall under the GPL. The code is still totally free. It's the art and name that aren't. If you had a project called XYZ, and someone wanted to take your work and distribute it, but change things in it... Would you still want them calling it 'XYZ'? No, you'd want to make sure people knew it wasn't the official distribution, and that the other person was responsible for maintaining the changes. That is what's happening here.

      Debian has not been told 'you cannot distribute Firefox'. They've been told 'You can distribute it under a different license, if you agree to our terms.' There's nothing new there. That's done ALL the time.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    5. Re:Absurdity by DragonWriter · · Score: 1
      Basically, Bad FireFox! Free should mean Free!


      I dunno. Copyright and trademarks are different domains. Copyright gives control as a method of increasing value to the creator, trademark gives control largely to prevent deception of consumers. Just because Firefox is opensource doesn't mean anyone should be able to release whatever they want and call it Firefox. While "Iceweasel" is the kind of edge case that provokes debate over who is right or wrong, I think this is pretty clear if you consider extreme cases: for instance, should Microsoft be allowed release a version of Internet Explorer bundled with a default theme that looks like Firefox's default theme called, say, "Firefox 3.0" as a notionally "alternative" browser to IE 7.0 in Windows Vista? I think clearly not. There is a very good case, I think, for strong trademarks in free/open source/copyleft software.

    6. Re:Absurdity by Anomolous+Cowturd · · Score: 1

      Well the copyright license on the logos distributed with the firefox source is NON-FREE. So it's a copyright issue.

      --
      Software patents delenda est.
    7. Re:Absurdity by PygmySurfer · · Score: 1

      how could Microsoft ensure that Windows was the quality piece of software that they provide you, if it openned up its code to everyone?

      Microsoft doesn't keep its source code closed for stability reasons, they do it to maintain a competitive advantage.

      How could Firefox guarentee the quality of its artwork, if they don't protect it from evil hackers defacing it or using it?

      Firefox isn't trying to guarantee the quality of its artwork, they're protecting their brand.

      Debian is pushing yet another IP issue into the light. Copyleft + Trademark = Stupid.

      Debian isn't pushing anything into light. There's no issue. Copyrights and Trademarks are two separate things, and should be dealt with as such.

    8. Re:Absurdity by obi · · Score: 1

      What if Linus said - you must use the exact Vanilla upstream linux kernel without patches I haven't vetted, or else you don't get to call it "Linux"? Because that's what Mozilla is doing.

      Guess what: Linus has a trademark, and yet there still are widely diverging kernels for totally different purposes kept in completely different trees by different companies/people - yet they're all called Linux.

      Mozilla decides that they're the ones that should have the final say over what patches are "ok" - even if they say stuff like: "don't patch your stable distro with firefox 1.0 for security fixes. upgrade your old, stable distro to firefox 1.5 instead, even if that means breaking users' expectations of 'stable distro' and breaking some programs in the process".

      That would also mean that derivative Debian distros (there's more than just Ubuntu) can't rely on the fact that they're free to use and change anything in the distro for their own purposes; They'd have to deal with Mozilla too, instead of just relying on Debian.

    9. Re:Absurdity by dircha · · Score: 1

      "Academic circular argument"? Changing the name to Dumo GMAC/Looney? I don't think you even understand what you are talking about.

      What is it to you if a group of volunteers want to produce a GNU/Linux distribution that is compliant with their own ideological values? That's right: volunteers. And they didn't ask for your opinion. Yours was quite unsolicited.

      When was the last time you contributed to the Debian project?

      I thought so.

      And I might add, I fail to see why the distribution requirements in section 3.3 of the MPL requiring prominent notice that the original work has been modified, shouldn't be enough for the Mozilla project. Most open source licenses have similar clauses, and these clauses appear to be good enough for most other projects.

      I say good on Debian. It's better that they not waste their resources to promote a proprietary, commercial brand like Firefox.

      I've never run a system I've been happier with than a Debian GNU/Linux stable release. Keep up the great work folks.

    10. Re:Absurdity by Chrono11901 · · Score: 0

      Mozilla is only protecting their products credibility.

      A worst case scenario: MS takes the FF source code, "patches" it to run 10X worst then IE then includes it with windows. Now when people go to use "FireFox" it will become apparent to them that IE is far superior.

      Debian wants to modify the source code and doesn't want to need mozilla's approval... Just like if it was MS... Their is no one to stop them from tarnishing FireFox's name.

    11. Re:Absurdity by entrylevel · · Score: 1

      Whoa, slow down there.

      I love Debian, especially the Ubuntu flavor. I've been been using Linux on and off for 5 years. My day job as a .NET programmer does not afford me the kind of time I would have liked to learn, but I'm progressing better now that I no longer use WinXP at home (unless via mono, wine, or VMware;).

      I am sincere about free software ideals. I am extremely grateful to have tens of thousands of free software packages at my fingertips, and yearn to see my own software in that list one day. I am currently adding DAAP client and server support to the Listen media player.

      I personally lean towards MIT, but license zealots need not apply... If my software one day winds up tangled in a petty argument such as this, it would be time to don negotiating hat and come to the table willing to make a concesion or two. Debian and Mozilla Corp. appear unwilling to do concede anything.

      I also believe that Mozilla is building a brand based on those exact same ideals. Building a sucessful (trademarked) brand is hard work, and legally requires Mozilla Corp. to defend that trademark. I think the Mozilla brand is as worthwhile as Debian to the open source world.

      We want to succeed, don't we? If yes, we must play by the rules, even if we don't like them. Most importantly, we must get along.

      My problem with this silliness is that it pollutes the Firefox brand and further fractures free software in general.

      I could truly care less that I feel the need to run a script to get the "official" Firefox icons, or if I must download an extension so it can be called "Firefox". That said, "Iceweasel" is at least contrary if not condescending.

      My first post was sarcasm, here is my unsolicited opinion: Use the official icon. Call it Firefox. And fuck Mozilla "approving" the patches you use with your own distribution. Make the Firefox package "Suggest" extension(s) that allows you to change the name and icon.

      --
      Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
    12. Re:Absurdity by snowgirl · · Score: 1

      Copyrights and Trademarks are two separate things, and should be dealt with as such.

      Oh, so sorry, for a second here, I thought we were talking about FREE software. Why do people think it's ok to own a name, and exert that control over other people?

      If you want the official FireFox, you download it straight from Mozilla. The second I get a copy of FireFox from ANYONE, I have no idea if that FireFox is the original or not.

      They're not "protecting" anything, they're "owning" a name.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    13. Re:Absurdity by snowgirl · · Score: 1

      Yeah, down with the GPL, too! It says 'Free unless...' also.

      The issue with the GPL is that GPL say "free unless not free". Basically, it uses existing laws to force people to respect the freedom of others.

      The issue here I have with this trademark stuff is that names should be free, too. Anyone who wants to own their name is silly, and stuck in an out-moded way of doing things.

      It's the art and name that aren't. If you had a project called XYZ, and someone wanted to take your work and distribute it, but change things in it... Would you still want them calling it 'XYZ'?

      Actually, this very thing happened to me. I've worked on PearPC, there were a few developers that released compiled "PearPC" binaries that included patches that we NEVER would accept into the source tree. Did we yell at them for distributing something that we would never call PearPC? No, we in fact told them that it was fine to patch up their binaries and distribute them, in fact, some people liked those patches, but they would never be mainstream patches, and included in the vanilla code.

      Take another group of peoplem, they made a product called CherryOS, they didn't use our name, and in fact, denied that they had ever used our code. Honestly, we wouldn't have had a problem if they had even decided to call it PearPC and sell it for $50 a piece with their changes intact, all we *EVER* wanted from MXS was an acknowlegment that they were using our code. Heck, if they had called it "PearPC", the lineage would have been directly apparent.

      Names should be free the same as code, and information.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    14. Re:Absurdity by doom · · Score: 1
      I'm having a little trouble following the logic of your posting here, so these comments may or may not apply to what you're saying:
      • People I respect like the BSD license (which is much like the MIT as I remember it) better than the GPL, but historically BSD licensed projects really have run into problems, notably the great unix wars of the 80s that ended up with Microsoft the winner. BSD licensed code is prone to proprietary forks, which subdivide the community even more so than this name change. The GPL was an extremely clever social hack to try to prevent this sort of problem.
      • You make an interesting point that Mozilla Corp may have been legally overreaching in claiming right of approval of code patches. At the very least, if that's legal under the MPL, I would think it should no longer be regarded as an Open Source/Free Software license.
    15. Re:Absurdity by obi · · Score: 1

      Well, there's a lot of patches out there that destabilize the Linux kernel, but somehow Linus doesn't feel threatened. If MS did that, I'm willing to bet people would actually recognize it as the FUD it is.

      Yes, it can happen that Mozilla's name might get tarnished a little bit by something someone else did. Some people might not be able to differentiate between that someone else and Mozilla.

      But I'm willing to bet that Mozilla going after distro's like that is probably going to cause more bad blood than the potential, hypothetical tarnishing they might receive.

  9. Iceweasel? by nuzak · · Score: 3, Insightful

    Firefox remains the same, Debian's the one that doesn't come with Firefox. Why they didn't just move it to non-free is beyond me.

    Oh well, Ubuntu already has things worked out with Firefox, so no naming games going on there. Debian should note well that sometimes downstreams do take over when the parent project became too onerous to work with. No one is too big for this to happen.

    --
    Done with slashdot, done with nerds, getting a life.
  10. Ubuntu status and IceWeasel Icon by Kelson · · Score: 2, Interesting

    cbeard's post suggests that Ubuntu has made a similar agreement with Mozilla as the agreements that Red Hat and Novell have (which is why you'll see a full branded Firefox in SuSE and Fedora). But Ubuntu folks are working on an IceWeasel icon.

    Anyone know what's up with Ubuntu? Are they going to pull official Firefox releases, or are they going to pull IceWeasel straight from Debian?

    1. Re:Ubuntu status and IceWeasel Icon by Hyram+Graff · · Score: 1
      But Ubuntu folks are working on an IceWeasel icon.

      Bah, you have to login to the forum to see the picture. Is this hosted somewhere where I don't have to login to see it?

      --
      0*0
      00*
      ***
    2. Re:Ubuntu status and IceWeasel Icon by Constantine+Evans · · Score: 1

      The forum does not reflect the development of Ubuntu - there are hardly any developers there, and many forumgoers are just users with strong opinions. Such places are where most of the bickering about the issues has been going on - it isn't really considered a large argument elsewhere.

      The last post on the developers' mailing list by an authoritative person (Matt Zimmerman) stated that Ubuntu was discussing a resolution of the issue with Mozilla.

    3. Re:Ubuntu status and IceWeasel Icon by towsonu2003 · · Score: 1
      Anyone know what's up with Ubuntu?
      they are still debating that. see the ubuntu-devel archives for the discussion (which is pretty boring). https://lists.ubuntu.com/archives/ubuntu-devel/200 6-October/021522.html
  11. Fuck 'em both. by Anonymous Coward · · Score: 0

    Frankly, I've had enough of this nonsense. I want to use software from developers who care about developing, rather than getting into petty arguments over the naming of certain pieces of software. That's why I've decided to boycott both Debian and Mozilla.

    What I've done is switch my desktop systems over to FreeBSD. FreeBSD offers many of the same features as Debian, but without the bullshit. Personally, I find its packaging and ports systems far more flexible than Debian's APT. And from my brief viewings of its kernel and userland source code, it appears far better-written than Linux.

    Likewise, I have also ditched Mozilla. I now use Konqueror as my web browser. Aside from missing a few handy extensions, it triumphs over Firefox in every other way. It's faster, and it uses much less memory. It has better CSS support. It has better Java integration.

    Debian and Mozilla really need to cut out this nonsense. The more they bicker, the more they fall behind projects like Konqueror and FreeBSD.

    1. Re:Fuck 'em both. by eloki · · Score: 1
      Debian and Mozilla really need to cut out this nonsense. The more they bicker, the more they fall behind projects like Konqueror and FreeBSD.
      Hahaha... that anyone could seriously assert this is amazing. In no way does the discussion of marketing folks and license purists stop other people from doing their normal development work. Do you seriously think the apt maintainer (for example) falls behind due to the Firefox maintainer having to rename the package? Of course not. The same applies to Mozilla too. They're not formal companies, just amorphous mobs of people where everyone individually decides to work on the things they want to work on.
    2. Re:Fuck 'em both. by AVee · · Score: 1

      I'd choose to boycot the project wich has a 'head of marketing and product strategy' if I were you...

      Indeed, the kind of people that put out crap like "This is how brands and trademarks are being managed in the world today" and "to protect consumers and the reputation of our products".

      Please, cut the crap and just ship it named iceweasel, I for one trust Debian far more when it comes to putting out rock solid software then some Mozilla(tm) Corp.

  12. Iceweasel? Boring! by Anonymous Coward · · Score: 0

    It should be called "Firevixen".

  13. Why not TurboRabbitChaser? or FoxOnFire? by RobiOne · · Score: 1

    It seems there's a bit much of the "fine" syndrome. Can't we play nice? Guess not, because one side said Fine, and the other FINE, and we end up with IceWeasel? WTF?

    There's so much respect in the air..

    How about people realizing the problem and finding a solution that will keep the name from changing yet again. Or just leave it out in non-free and have a meta package take care of it..

    Debian could also switch to Kmeleon as it's less memory hungry.

    --
    -- Robi
    1. Re:Why not TurboRabbitChaser? or FoxOnFire? by Kelson · · Score: 1
      Debian could also switch to Kmeleon as it's less memory hungry.

      I assume you mean Galeon or Epiphany. (Hmm, does Debian ship with WINE?)

    2. Re:Why not TurboRabbitChaser? or FoxOnFire? by RobiOne · · Score: 1

      Yes, I mean another Gecko based browser. You're correct as Kmeleon is win32 only.

      --
      -- Robi
    3. Re:Why not TurboRabbitChaser? or FoxOnFire? by eloki · · Score: 1
      Debian could also switch to Kmeleon as it's less memory hungry.
      They can't "switch" to anything, they already ship lots of browsers. Debian uses GNOME by default, so Epiphany might well be installed by default anyway and not Firefox (haven't done a fresh install for a while). If that's the case, then this just makes it a bit harder for users to specifically find Firefox (probably an apt-cache search will still find it, but the package would be called "iceweweasel" instead).
  14. The problem is at Moz's end by jmorris42 · · Score: 4, Informative

    Debian really had zero options here folks. Moz Corp's new policy is simple. "Nobody releases a browser called Firefox except us or those who allow us absolute control over their releases. Period, zero exceptions." So far RedHat, SUSE and Ubuntu have agreed to cede control over ALL modifications, including prior approval of security patches to Moz Corp. Obviously Debian couldn't, wouldn't and shouldn't have done anything of the sort. Thus IceWeasel comes to Debian.

    I already made the change earlier in the year. Done right FF plugins still work so no big deal.

    --
    Democrat delenda est
    1. Re:The problem is at Moz's end by Ranx · · Score: 1

      Have you ever tried to change Debian and release it as Debian?

      No?

      I thought so.

      Debian also has restrictions if you want to use the official logo:
      http://www.debian.org/logos/

      --

      Me
    2. Re:The problem is at Moz's end by suv4x4 · · Score: 1

      Debian really had zero options here folks. Moz Corp's new policy is simple. "Nobody releases a browser called Firefox except us or those who allow us absolute control over their releases. Period, zero exceptions." So far RedHat, SUSE and Ubuntu have agreed to cede control over ALL modifications, including prior approval of security patches to Moz Corp. Obviously Debian couldn't, wouldn't and shouldn't have done anything of the sort. Thus IceWeasel comes to Debian.

      I hope they're only trying to be funny and not calling it IceWeasel. It's lame attitude on their end.

      Why not call it Debian Internet Explorer and be done with it.

    3. Re:The problem is at Moz's end by Anonymous Coward · · Score: 0

      "Nobody releases a browser called Firefox except us or those who allow us absolute control over their releases. Period, zero exceptions."

      Ummmm.... no? "Nobody releases a browser called Firefox that uses a different (read: "globe") icon because both the icon and the Firefox name represent our brand. Nobody should keep their own CVS repositories of changes that never get contributed back upstream, release shoddy binaries of our product, strip out part of our brand image from a release and still call it 'Firefox'."

    4. Re:The problem is at Moz's end by IamTheRealMike · · Score: 1

      Their other option was to stop patching the hell out of Firefox and do what every other distro does - get with the program. They chose to rename it entirely which may be in compliance with the artwork parts of the DFSG but is also, to my mind, absurd.

    5. Re:The problem is at Moz's end by ClamIAm · · Score: 1

      Their other option was to stop patching the hell out of Firefox and do what every other distro does - get with the program.

      Um yeah, because this is the whole point of Free Software: don't ever improve software, just follow what the original author tells you to do.

    6. Re:The problem is at Moz's end by noahm · · Score: 2, Insightful
      Their other option was to stop patching the hell out of Firefox and do what every other distro does - get with the program.

      Get with the program? Are you serious? Should we not patch Linux either? How 'bout X?

      You should read Matthew Garrett's recent blog entry about why it's a good thing (for the Mozilla Corp, Debian, and the user community at large) for Debian (or anybody else) to be allowed to distribute patches. http://mjg59.livejournal.com/68112.html

      Also, you should probably read this post to the Fedora devel list that shows that Mozilla's trademark policies are a real problem not just for Debian but for other distributors as well.

      noah

    7. Re:The problem is at Moz's end by jesterzog · · Score: 1

      Their other option was to stop patching the hell out of Firefox and do what every other distro does - get with the program.

      Because "getting with the program", as you put it, means they can't patch the code as they want to without relying on a third party.

      A distribution is a collection of software that's configured to work together, and often it's vouched for by the distro maintainers. Debian's serious about stability in its official releases, and given that it also has an obligation to assure its users that the browser is stable and secure to run on their system, I have absolutely no problem with Debian wanting to patch the hell out of Firefox, if that's what they decide is necessary.

      I'm confused about why the Debian maintainers decided to try and use the Firefox name in the first place when they're not supposed to, but if they now need to rename it to maintain the quality of Debian, good on them.

    8. Re:The problem is at Moz's end by SanityInAnarchy · · Score: 2, Insightful
      So far RedHat, SUSE and Ubuntu have agreed to cede control over ALL modifications, including prior approval of security patches to Moz Corp. Obviously Debian couldn't, wouldn't and shouldn't have done anything of the sort.

      Here's the problem: Suppose Mozilla were to give Debian full control, Debian patches the hell out of it, and people say "Firefox sucks! It crashes all the time on Debian!" Now, suppose Debian gave Mozilla full control, Mozilla doesn't allow Debian-specific patches required to make it work properly, so people say "Debian sucks! Firefox crashes all the time on it, but not on Ubuntu!"

      Both of them have legitimate complaints.

      I already made the change earlier in the year. Done right FF plugins still work so no big deal.

      One big deal: A newbie coming over from Windows looking for FF plus plugins/extensions won't find it, and won't have a clue that IceWeasel is really Firefox. They should've at least attempted to make it clear that it's still Firefox, it's just Debian-specific.

      I'd have to go with tradition here. Distros get to release derivative versions, and still call them by the original name. In return, distros do the best to make everything play nice, and generally will listen to reasonable requests -- for instance, Gentoo removed the ebuild that built Cedega (then WineX) from the CVS, because although it was technically legal (they allow CVS access, but charge for prebuilt packages), it made it just as easy, if not easier, for Gentoo users to use the free (CVS) version than to subscribe.

      Distros have to keep in mind that users will just go and get upstream by themselves if the distro gets it wrong, or they'll switch to another distro that gets it right. Upstream has to keep in mind that if they refuse to cooperate with distros, they won't get distributed, so they should at least make an attempt to play nice with distros and other packages.

      In this case, neither is willing to allow full control, and both are paranoid that the other side will tarnish their good name. Because of this mutual stubbornness, both sides lose out. I will likely never prefer Debian over Ubuntu again, and not just for this reason.

      --
      Don't thank God, thank a doctor!
    9. Re:The problem is at Moz's end by Anonymous Coward · · Score: 0

      "So far RedHat, SUSE and Ubuntu have agreed to cede control over ALL modifications"

      And thank god, too. Have you actually benchmarked the Debian/Ubuntu package of Firefox against the official release?

    10. Re:The problem is at Moz's end by doom · · Score: 1
      jesterzog wrote:
      I'm confused about why the Debian maintainers decided to try and use the Firefox name in the first place when they're not supposed to,
      Apparently they had an agreement (unofficial or otherwise) that what they were doing was okay with the Mozilla guys. Getting fussy about trademarks is a new thing with the Mozilla Corporation.

  15. Community Edition by Noksagt · · Score: 2, Interesting

    Mozilla people have stated that the Community Edition Policy (listed as draft) is still valid. In the Debian bug on this issue, some Debian devs are considering it. A lot of the Mozilla marketing people seem to be unaware of it & didn't list it as an option.

    This policy seems to be a good fit--Debian MUST NOT include the image which is under a non-DFSG copyright to conform to this policy (they don't want to and currently don't include it, but the NEW "standard trademark policy" is that it must be used if the Firefox name is used). And they must rename it "Firefox Community Edition, Debian." This seems preferable to Ice Weasel for both the majority of Debian users and Mozilla's image. OpenBSD already follows this policy, as do others. If the CEP is ever dropped, there will be many more distros who will be forced to switch to "Ice Weasel."

    1. Re:Community Edition by Constantine+Evans · · Score: 1

      Mike Conner specifically ruled out Debian's version being a Community Edition. It wasn't listed as an option because Mozilla didn't consider it an option for Debian.

    2. Re:Community Edition by NereusRen · · Score: 1
      Ah, thanks for explaining the name that GoboLinux is using for their Firefox now... I was curious if they had come up with it on their own or if it was a standard.

      However, there's a problem with that for Debian: They need to have control over future security patches, so they can maintain their Stable distribution for a long time without having to wait on someone else who might or might not allow them to do any patching. Lets have a look-see on the very page you linked:

      The following changes are permitted within Community Editions:

              * Change certain preference settings
              * Change the default start page
              * Change both the structure and the contents of the default bookmarks and personal toolbar
              * Change the default search engine and other search engines in the search engine pulldown box
              * Include extensions that are also available through updates.mozilla.org
              * Include plugins, provided they can legally do so
              * Porting the software to different operating systems
              * Custom builds created using options to configure

      Nope, nothing about patching for security (or any other reason besides porting). By omission, it means you are *not* allowed to apply any unauthorized patches and still refer to it as Firefox, whether or not you use the "Community Edition" moniker. If I understand Debian's objection well enough, this is a deal-breaker for "Community Edition."
  16. It going to go down the wire and then be settled by LiquidCoooled · · Score: 1

    Its free advertising for both of them.

    I for one didn't know a new debian was due out, did you?
    I know theres a new firefox due but not everyone does.

    Or am I being too cynical?

    --
    liqbase :: faster than paper
  17. PLEASE MOD PARENT UP!!! by hummassa · · Score: 0, Redundant
    AC:
    Summary, hopefully before anyone gets a chance to 'blame' Mozilla or 'blame' Debian over nothing:

    Debian don't want to include certain icons related to Firefox because the licensing of those graphics isn't consistent with the aims of their project.

    Mozilla say that's fine, as long as Debian don't call the package "Firefox".

    So Debian aren't going to call it Firefox.

    No villains, and everyone lives hapily ever after. The end.
    'nuff said.
    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  18. No one got nasty by Anonymous Coward · · Score: 0

    They aren't bickering. Debian has policies in place and if they start making exceptions they have to make them for everyone. Thankfully they didn't make exceptions.

    This was the correct thing to do under the circumstances. It doesn't really change anything except artwork and the name.

    Just like they don't include Netscape because it's a branded version of the Mozilla based engines, firefox too is a branded version with non-free branding.

    If enough people don't like this, they can create their own debian based distribution and come up with their own rules.

    1. Re:No one got nasty by Kelson · · Score: 1
      Debian has policies in place and if they start making exceptions they have to make them for everyone.

      Why? What would obligate Debian to make even one more exception, never mind exceptions for everyone who asks them?

      That's a slippery slope argument -- a logical fallacy.

      At most, it would encourage others to ask for exceptions, but Debian would be free to keep refusing them.

      Debian making an exception to the DFSG for Mozilla would no more obligate them to let other groups bypass the policy than Ubuntu's exception for Firefox from their no-new-versions security policy obligates Ubuntu to ship new versions of other software instead of backporting patches.

      Besides, if they let everyone do it, it wouldn't be an exception, would it?

    2. Re:No one got nasty by Anonymous Coward · · Score: 0

      But why should they make an exception for Firefox? Having a browser called "Firefox" rather than the same browser called "Iceweasel" is just not important enough to compromise your principals for.

    3. Re:No one got nasty by Kelson · · Score: 1

      I didn't say they should make that exception -- just that "If I make an exception for you, I'll have to make an exception for everyone" is utter B.S.

    4. Re:No one got nasty by Anonymous Coward · · Score: 0

      If they were to make an exception for Mozilla, I'd expect them to come up with a damn good reason why. Any reason why I could think of, could easily apply to any number of other projects. If they then refused to make similar exceptions for those other projects, that simply wouldn't be fair. So yes. If they granted an exception to Mozilla, they would have to grant everyone an exception to be fair. If they chose not to be fair, then I'd lose a lot of respect for them.

  19. IceWeasel Icon - Direct Link by Kelson · · Score: 3, Informative

    Sorry, looks like I picked the wrong tab to paste in there. This IceWeaselIcon wiki page has several drafts.

    1. Re:IceWeasel Icon - Direct Link by morgandelra · · Score: 1

      http://mik.unpackable.org/humping_iceweasel.gif/

      Oh jeebus, thats gotta be the best one

    2. Re:IceWeasel Icon - Direct Link by vadim_t · · Score: 1

      Darn, I was about to post exactly that.

      Here goes another vote for the humping ice weasel.

    3. Re:IceWeasel Icon - Direct Link by jmorris42 · · Score: 1

      > http://mik.unpackable.org/humping_iceweasel.gif/

      > Oh jeebus, thats gotta be the best one

      How about instead of humping the earth/internet? have it humping a submissive little red/orange fox... flames optional.

      If ya really want to mess with Moz Corp's head.

      --
      Democrat delenda est
  20. Matt Groening - Love is ... by khasim · · Score: 5, Informative

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

    - Matt Groening

    Simpsons, Futurama, Life in Hell

    1. Re:Matt Groening - Love is ... by Blakey+Rat · · Score: 1

      Yes, ok, but it's still a fucking stupid name for a web browser.

    2. Re:Matt Groening - Love is ... by BorgCopyeditor · · Score: 3, Interesting
      Thank you for bringing out what I've been thinking since I heard that this was what they were calling it!

      ...except you forgot to add that this quote was meant to express Nietzsche's take on love, and not in some mythical book called "Life in Hell"--which was a late revision of multiple sources, not entirely unlike the Bible or the U.S. Constitution in that regard--but in "Love is Hell," which preceded the other "...is Hell" books. Special +1 Informatives for anyone who can list the other philosophers whose theories of life were discussed on this same page of "Love is Hell." (I can't actually remember, but I think one was Kierkegaard.)

      --
      Shop as usual. And avoid panic buying.
    3. Re:Matt Groening - Love is ... by Infonaut · · Score: 1

      Hah! That takes me back, alright. One of my favorite Groening creations. I've alwasy thought his Life in Hell drawings are fun, but the writing has always been the best part. I mean, can't you just picture the ice weasels, their sharp little teeth glistening in the frigid night? Brr!

      And now, life imitates art yet again...

      Maybe, if we're lucky, IE 7 will be renamed MWM, after "Mistakes were made," another of my favorite Groeningisms.

      --
      Read the EFF's Fair Use FAQ
    4. Re:Matt Groening - Love is ... by God'sDuck · · Score: 1

      that's....that's the point. they're being pains in the arse to be mean to MozCo for drawing a line in the sand. it's like naming it PoopyheadFox.

  21. Re:It is a BIG Deal by mpapet · · Score: 3, Interesting

    What you fail to understand is the liabilities involved in letting another organization use a proprietary logo.

    If the unauthorized use of logos were not prosecuted by a company I could do lots of fun things. For example, I could repackage the gimp, throw photoshop's splash image in it and call it photoshopper. Maybe the name of my company would be AdobeHut too. Better still, I'll put a "circle R" next to all of it and make it look official.

    If Adobe doesn't throw every last lawyer at me, then lots of other people could do it. The courts would see it as essentially public domain. Meanwhile, I can drag Adobe into court for using my logo. Crazy right?

    Both parties are doing the right thing here. I doubt it really consumed very much time/energy on the part of the project as these kinds of details must be addressed and that's about it.

    Stories like this tend to make a figurative fire where there is none.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  22. what's the insult? by hummassa · · Score: 1

    seriously, fire + fox ("elemental thingy" + animal) is similar to ice + weasel (ok, ice is not one of the four elements or elementals, but...)...
    nobody got nasty. DFSG does not permit the release of the logo with firefox, mozilla does not permit the browser to be called firefox w/o the logo.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
    1. Re:what's the insult? by Anonymous Coward · · Score: 0

      They should have called it WaterOtter.

  23. Shades of GPL3? by Fujisawa+Sensei · · Score: 3, Interesting

    Looks like Debian is getting burned by its own arrogance.

    The GPL-3 allows the copywrite holder to place certain restrictions on the licensee's use of the software, for instance no military/weapons use (don't like your stuff being used; Freedom's a biach isn't it). Restrictions on what parts of the code the use may or may not change; requiring links to download the source be maintained.

    Now they being hit, once again, by restrictions the copywrite holders are placing on the distribution: if you distribute software that we own the copywrite to, you must maintain our branding. Sounds reasonable, the application is called Firefox and the logos and branding are part of the application; after all the copywrite holder does have the right to say what's part of application, (certain exceptions may apply in the case of illegal monopolies, and fraudlent activities). The usage restrictions also don't seem out of line with Debain's official logo usage.

    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.

    Looks like the Mozilla Foundation is pretty much in line with the Debian usage here.

    So the Debian developers are free to change the code however they want, but they can't call it Firefox and they can't use the Firefox logos.

    --
    If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    1. Re:Shades of GPL3? by jmv · · Score: 1

      Looks like the Mozilla Foundation is pretty much in line with the Debian usage here.

      There's a difference here, one is an application and the other is a distribution. People who modify Debian usually *want* to turn it into a very different product. That's what Ubuntu did. For Firefox, people want it to be the same except for some minor (hopefully invisible) patches. Or are you saying all other software maintainers do the same as Mozilla and ask people to use a different name?

    2. Re:Shades of GPL3? by Grepdashv · · Score: 1

      For the first time I feel like an old fart reading this thread. The lack of understanding evidenced in posts like the parents is quite astounding. It is like listening to a group of high school girls talk about menopause.

    3. Re:Shades of GPL3? by cortana · · Score: 1

      Why would you want to use the Official Use logo in a DDD?

    4. Re:Shades of GPL3? by Ramses0 · · Score: 1
      Hrm:

      Debian Open Use Logo License

      Copyright (c) 1999 Software in the Public Interest
      This logo or a modified version may be used by anyone to refer to the Debian project, but does not indicate endorsement by the project.
      ...where is the mozilla/firefox "open use logo license"? I support Debian in all its idiosyncratic glory because they have the guts and the freedom to really take a stand. It's not DFSG-free? It's not in Debian (the official debian, anyway). If that means FireFox => IceWeasel, life is good, because I can modify and redistribute IceWeasel while I can't modify and redistribute FireFox. And that's probably a good thing too, because if Mr. Malware could make "FireFox 9.0 + PopupInfestation" and convince people to download it, then that'd be bad for people who get fooled by that and there wouldn't be a thing Mozilla foundation could do about it.

      --Robert

      --Robert
    5. Re:Shades of GPL3? by coaxial · · Score: 1

      Looks like the Mozilla Foundation is pretty much in line with the Debian usage here.

      I'm sure there's now that you've brought this to their attention, there's going to be CVS check in that removes all references to debian and its logos in debian. Debian is known for making political changes without concern to their consequences. ("Let's remove all the HOWTOs because they're not "free" enough!")

      God I hate Debian.

    6. Re:Shades of GPL3? by glwtta · · Score: 1

      Copyright.

      Copyright, copyright, copy-bleeding-right!

      It's a right, not a verb.

      --
      sic transit gloria mundi
    7. Re:Shades of GPL3? by dondelelcaro · · Score: 1

      The difference is that Debian doesn't ever distribute the Official Use Logo in main. [It's even more doubtful that anyone would know what the official use logo is anyway, unless they already were a serious Debian user or recently visited the logo page.] (And really, no one in Debian is arguing with Mozilla's right to enforce their trademarks. We'd rather they didn't, but it's their decision to make. Once they've made it, Debian doesn't have a choice. We have to change.)

      --
      http://www.donarmstrong.com
    8. Re:Shades of GPL3? by A+beautiful+mind · · Score: 1

      Unfortunately I have to agree.

      How can GP miss the fact that Debian has an official logo they don't EXPECT anyone to use anywhere, besides themselves, and a freely distributable/usable Debian logo to be used anywhere the users want.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    9. Re:Shades of GPL3? by Cyclops · · Score: 1
      The GPL-3 allows the copywrite holder to place certain restrictions on the licensee's use of the software, for instance no military/weapons use (don't like your stuff being used; Freedom's a biach isn't it).
      That statement is a lie. Back it up if you don't agree with me.

      1. There isn't a GPL3 YET
      2. The GPL3 DRAFT doesn't add any restrction on USE


      I would moderate you, but there isn't a "-5 Liar" choice, so I decided to refute your statement instead.
    10. Re:Shades of GPL3? by Pastis · · Score: 1

      Why? Matthew Garret says it best:

      http://mjg59.livejournal.com/68112.html

    11. Re:Shades of GPL3? by Anonymous Coward · · Score: 0

      Shh. Don't tell the OP. It's a good method of distinguishing the idiots from those with something useful to say.

    12. Re:Shades of GPL3? by Fujisawa+Sensei · · Score: 1
      2. The GPL3 DRAFT doesn't add any restrction on USE

      Since you obviously have the current draft you need to reread Section 7b Item 4 and Item 6 before calling people a liar, those sections to allow for the usage provisions.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    13. Re:Shades of GPL3? by Fujisawa+Sensei · · Score: 1
      where is the mozilla/firefox "open use logo license"?

      Why do they need to provide one? Your change, your responsibility.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    14. Re:Shades of GPL3? by Cyclops · · Score: 1
      I'm baffled. Where do you read user restrictions?
      4) terms that require, if a modified version of the material they cover is a work intended to interact with users through a computer network, that those users be able to obtain copies of the Corresponding Source of the work through the same network session; or
      and
      6) terms that are precisely equivalent in type and extent to a requirement expressly stated in this License, or that deny permission for activities that are clearly not permitted, expressly or otherwise, by this License.


      There are ZERO restrictions for the user of said software. Distribution of copies is not USE...
    15. Re:Shades of GPL3? by Fujisawa+Sensei · · Score: 1

      4) if I USE your software to build my website, I'm a user of your software.

      6) "terms ... or deny permission for activities that are not clearly permitted, expressly or otherwise" Means that I can add a clause the regulate activities , which include distribution AND usage expressly or otherwise basically means the copywrite holder had add pretty much any additional restrictions for activities that are not enumerated in the rest of the license.
      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    16. Re:Shades of GPL3? by Cyclops · · Score: 1

      You only read it that way because you do not have the objective clear in your head.

      The objective is user freedomm not the freedom to do all you want with the software including removing freedoms.

      The objective is to make a closed circle around the 4 freedoms:
      0. to run the software for any purpose
      1. to study and adapt the software (source code availability is a requirement)
      2. to distribute copies
      3. to distribute modified copies (source code availability is a requirement)

      If you keep in mind that the objective is to have those freedoms and that they can't ever be lost, then you will read the text properly.

      As long as you think in "open source" just because "open source", and that Freedom is something software (not the users) needs (which is absurd since software doesn't have needs or feelings), or that you think that making proprietary versions is "noble"... you're always going to nitpick such weird stuff.

      Of course this doesn't mean the text can't be made clearer. I suggest you make suggestions rather than bitch (that is, don't imitate Linus, be better than him).

    17. Re:Shades of GPL3? by Fujisawa+Sensei · · Score: 1

      If your read a license agreement with a pre-conceived idea, you're in trouble.

      You should never put something in a license or agree to a license that you don't want somebody else's lawyer holding up in court.

      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    18. Re:Shades of GPL3? by Cyclops · · Score: 1
      If your read a license agreement with a pre-conceived idea, you're in trouble.
      Wrong. That's why there's a preamble to almost every law. To set the spirit of the words written below.
  24. Appropriate summary by Anonymous Coward · · Score: 1, Funny

    I just minimized my browser and noticed the following heading on my taskbar:

    Mozilla vs Debian Anal

    Sounds like it sums everything up right there.

  25. I for one by Britz · · Score: 1

    welcome our new Iceweasel overlords!

    What's the big deal with the name? Anyone that needs to recognize it mostly just clicks on the internet icon (thingy). Anyone else can just look and will find it. Besides, I never liked the sound of the Firefox name anyways. Iceweasel sounds so much cooler (literally, as a matter of fact).

  26. It's all about the trademark by QuantumG · · Score: 3, Insightful

    He says that Mozilla's stance on protecting its branding elements is no different than that of any other company that wants to ensure a high-quality user experience.

    Yeah, so? That's the problem. You're not supposed to be like any other company. You're supposed to care about freedom.

    --
    How we know is more important than what we know.
    1. Re:It's all about the trademark by topham · · Score: 1


      Trademark law requires you protect you're trademark, if the images are part of the trademark then you cannot use them modified without negatively effecting your trademark.

    2. Re:It's all about the trademark by crayz · · Score: 1

      Freedom to take code Mozilla Foundation has verified lives up to their standards for quality, stability, and user-experience, change it in ways Mozilla doesn't approve of, and then re-release the altered application, giving it the same name? That's not freedom, it's wanting to have your cake and eat it too

    3. Re:It's all about the trademark by MadMidnightBomber · · Score: 1

      He says that Mozilla's stance on protecting its branding elements is no different than that of any other company that wants to ensure a high-quality user experience.

      And I bet a lot of Windows newbies are accidentally sucking down the Debian packages and saying "Hey, this doesn't work! FIREFOX SUCKS!"

      If you're running Debian, you expect to get Debian's customised packages. Sheesh.

      --
      "It doesn't cost enough, and it makes too much sense."
  27. Don't forget firebird by Mustang+Matt · · Score: 1

    This isn't the first situation regarding naming and Mozilla Foundation. (Although, completely different.)
    Firefox was once called Firebird but renamed due to the "other" firebird which was a db.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  28. Iceweasel by Gabesword · · Score: 2, Insightful

    I applaud Debian for sticking to what they believe. I, for one, will be taking the free Debian artwork and name and replacing the standard Firefox logo and name on my distro(s) of choice. I think Debian should have a contest for a new Iceweasel logo every bit as snazzy as the Firefox logo.

    1. Re:Iceweasel by remembertomorrow · · Score: 1

      Not Debian, but close enough: https://wiki.ubuntu.com/IceWeaselIcon

      --
      Registered Linux user #421033
    2. Re:Iceweasel by Spasmodeus · · Score: 1

      That's the way to stick it to The Man!

      Show the world -- or at least anybody who happens to look at your monitor -- that you ain't gonna be oppressed by no proprietary icons!

    3. Re:Iceweasel by Hakubi_Washu · · Score: 1

      Man, I'd really like http://mik.unpackable.org/humping_iceweasel.gif on my browser (maybe as the "I'm working"-Icon?) :-D

  29. So can I use the name "Debian" freely, then? by mad.frog · · Score: 2, Interesting

    If Debian is as "totally free" as they claim, then presumably I could make my own distro and call it "Debian" too. (Or, hell, I could make a TOTALLY UNRELATED piece of software and call it "Debian"... the name is free, right?)

    1. Re:So can I use the name "Debian" freely, then? by kilgortrout · · Score: 3, Funny

      The Debian Common Core Alliance(DCCA) was already slapped down by the Debian Project for the unauthorized use of "Debian" in the DCCA's name. Oh, the irony!!

    2. Re:So can I use the name "Debian" freely, then? by ElleyKitten · · Score: 1
      If Debian is as "totally free" as they claim, then presumably I could make my own distro and call it "Debian" too. (Or, hell, I could make a TOTALLY UNRELATED piece of software and call it "Debian"... the name is free, right?)
      On Ubuntu, I've installed XMMS, and for some reason it came with a skin that says "DEBIAN" in big letters, with the Debian logo. In fact, it doesn't actually say XMMS on it anywhere. I guess if I was stupid, and hadn't typed apt-get install xmms to get it, I might think it was called Debian, since that's the only name I see. Do I see Debian bitching at XMMS and/or Ubuntu? No. Ok, maybe they don't know about it, but when you make open source programs, you just gotta let some things slide. I mean, why would you license your program to be modified by anyone if you don't actually want people to mod it?
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    3. Re:So can I use the name "Debian" freely, then? by tehcyder · · Score: 1
      If Debian is as "totally free" as they claim, then presumably I could make my own distro and call it "Debian" too. (Or, hell, I could make a TOTALLY UNRELATED piece of software and call it "Debian"... the name is free, right?)
      I renamed the "start" button on my Windows machine at work "Debian" and have a picture of a penguin as my wallpaper. Does this count?
      --
      To have a right to do a thing is not at all the same as to be right in doing it
  30. Firebird, Phoenix, DCC... by Kelson · · Score: 3, Informative

    Yep. Mozilla has been on both sides -- they had to rename Phoenix to Firebird, then Firebird to Firefox.

    And Debian's been on both sides, too, when they forced the DCC to drop "Debian" (originally it was the "Debian Common Core Alliance.")

  31. VLAD FARTED by Anonymous Coward · · Score: 0

    lol lockwood the wallpaper is falling off of the walls and all the plants died

  32. Issue is larger than Debian, its about the GPL by ubuwalker31 · · Score: 1, Interesting

    This issue is larger than Debian. This is really about the GPL. If you downloaded the source code for Firefox, you'll find around 18 text files labeled 'license' in the source code and not one reference to the GPL. There are only references to the MPL. While the Mozilla website claims that it is "tri-licensed" under the GPL, I have found no evidence in the current source code that backs up that claim.

    In fact, Mozilla has modified the text of the MPL, which now has a new preamble which states "You are not granted rights or licenses to the trademarks of the Mozilla Foundation or any party, including without limitation the Firefox name or logo." This is a new modification to the MPL and is not reflected in the version of the license available on the Mozilla website. Furthermore, this version of the license has not been analysed by the GNU project, and might not be compatable with the GPL.

    It is a RED HERRING to argue that trademark and copyright law offer a distinction in this case. If you release source code that contains image files which are licensed under the GPL, they are licensed under the GPL. If you release it under them under a tri-license, then they are tri-licensed. If you pick and choose which parts of your source code are GPL or MPL, then, well, you have a problem with compliance.

    This is a serious LEGAL issue, not a moral issue. IMHO, all distros which are distributed under the GPL should stop using the MPL until they consult legal counsel!

    1. Re:Issue is larger than Debian, its about the GPL by Alphager · · Score: 1

      images don'fall under the GPL. The GPL only talks about source-code (see GPL paragraph 1). This basically is a dispute over GPL paragraph 2 a: if i apply my own pathes to Firefox, does 2 a allow me to still call it Firefox?

    2. Re:Issue is larger than Debian, its about the GPL by cortana · · Score: 1

      FYI, the tri-licensing issue is bug #330295 and is fixed in Firefox's trunk and whatever branch Firefox 2.0 is being built from.

      http://weblogs.mozillazine.org/gerv/archives/2006/ 03/relicensing_complete.html

    3. Re:Issue is larger than Debian, its about the GPL by Myen · · Score: 1

      http://www.mozilla.org/MPL/boilerplate-1.1/mpl-tri -license-txt other versions

      See the last paragraph starting with "Alternatively". LXR query for the text... And it's this option to use GPL/LGPL instead that makes the license "compatible". As far as I can tell, MPL itself really isn't for the distros, it's the option to use GPL instead (which the distros exercise) that make it possible.

    4. Re:Issue is larger than Debian, its about the GPL by ubuwalker31 · · Score: 0

      Well, the GPL doesn't really define what "source code" clearly.

      "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."

      Does this include images? I think that there is a strong argument that it does. Otherwise, GUIs, which contain images along with code, could just be distributed under a non-GPL license, right? Correct me if I'm wrong.

  33. Re:It is a BIG Deal by m-wielgo · · Score: 1

    Definitely. This is something we're currently discussing in my Intellectual Property course at my university. We're covering various cases, including the "Amen Break", the use of the word "Google" in terms of searching the internet (and not particularly using Google search engine), DVD Jon's DeCSS, and other issues that constitue "fair use" and infringment of copyrights, trademarks, patents and trade secrets.

    I never thought a legal class would be so interesting, but it really is. It's greatly helped in understanding these cases, and I'd recommend anybody who hasn't taken such a class, to enroll in one in the coming semesters.

  34. Re:It is a BIG Deal by Rydia · · Score: 1

    Amen. Every programmer should take at least a course in IP law. Maybe then I'd be able to spend less time explaining things to people whose education about IP law is a combinations of "what they want it to be" and talking points from RMS.

  35. Re:It is a BIG Deal by Anomolous+Cowturd · · Score: 1

    Makes one wonder if this whole "Intellectual Property (tm)" thing is worth the bother.

    --
    Software patents delenda est.
  36. As a sort-of-almost-not-quite-yet sdk by bahwi · · Score: 4, Insightful

    Firefox is becoming more of a software dev platform. Recently, in an app I did, we had a prob with Firefox's GC for xml objects causing it to crash. An upgrade fixed it(at first a beta ver of FF/XulRunner) and now it's in the stable branches.

    Now, pretend for a minute Debian had Firefox with that name and the regular icons. But they decided, for whatever reason, to roll back or use their own GC patch for the problem we had.

    So, my app wouldn't work on Firefox, but would work on Firefox? Specifically, not on Debian FF but in the rest of the world? Any idea how inane this is? Firefox is trying to protect a brand of quality, if debian introduces a new bug into their browser, should Moz provide support? Should other people provide support in IRC, newsgroups, etc.. ?

    What if I modified python to not use if anymore but use wellmaybeiwillonlyif instead, but released it, called it Python, same version, etc... should I be allowed to do so? Could I then say that python from python.org is not compatible with Python from python.org, which I should then call the unofficial branch?

    Yeah, it's silly, but if I'm an OS, that's a lot of implementations of it that no longer support "if".

    1. Re:As a sort-of-almost-not-quite-yet sdk by Vexorian · · Score: 1

      I personally don't think mozilla really distrust debian as much as they distrust companies outside (those not exactly whitehat developing companies that would love to make their own "Firefox") It is just that they shouldn't have any exception, letting Debian do it would make it harder to enforce against other cases.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    2. Re:As a sort-of-almost-not-quite-yet sdk by jmv · · Score: 1

      So only the distributions that ship exactly Linus' kernel can be called Linux? Only the PC vendors that ship Windows *totally unmodified* from the MS CD can say they ship Windows?

    3. Re:As a sort-of-almost-not-quite-yet sdk by prockcore · · Score: 1
      Only the PC vendors that ship Windows *totally unmodified* from the MS CD can say they ship Windows?


      I'd be all for that... if anything, to stop PC vendors from adding all sorts of shit to the default image.
    4. Re:As a sort-of-almost-not-quite-yet sdk by k8to · · Score: 1

      You can do that with python. You can do that with most free software programs.

      The only major restriction is if you are somehow demonstratably willfully creating confusion and damaging the reputation of a project whose name is trademarked, you are in trouble. Most projects don't have registered trademarks and even your silly modification above would not qualify as malfaesance.

      So yes, Mozilla is a special case.

      --
      -josh
    5. Re:As a sort-of-almost-not-quite-yet sdk by Just+Some+Guy · · Score: 1
      What if I modified python to not use if anymore but use wellmaybeiwillonlyif instead, but released it, called it Python, same version, etc... should I be allowed to do so? Could I then say that python from python.org is not compatible with Python from python.org, which I should then call the unofficial branch?

      I agree. Only binaries compiled directly from official sources should be allowed in. Starting immediately, I'll use only "pure" versions of GCC to make sure that I don't accidentally come to rely on any of the Debian bugfixes. I'll also use only the kernel.org kernel instead of the patched one Debian ships. Yep, from now on I'll boycott all fixes not supplied directly by the author, because I want to be justly crippled with the same problems everyone else faces.

      Honestly, I don't understand your position. As others have pointed out, major systems besides Firefox seem to work under this arrangement (or do you really think OpenOffice and KDE are less complex?) without major disasters, so what's so special about this one particular web browser?

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:As a sort-of-almost-not-quite-yet sdk by Stinking+Pig · · Score: 1

      Sort of the way that Mandriva ships a broken Perl but keeps on calling it Perl...

      --
      "Nothing was broken, and it's been fixed." -- Jon Carroll
  37. Oh good grief Mozilla guys! by sbaker · · Score: 2, Insightful

    Oh good grief Mozilla guys!

    Look - FireFox is OpenSourced - right? So for chrissakes let them
    do what they want with it - that is THE ENTIRE POINT!!! If the
    Debian guys (who are not exactly complete Klutzes at this stuff)
    mess up, you say "Hey the Debian guys screwed up - come download
    the real one from the usual places."

    Geez - just make it happen and get over it.

    --
    www.sjbaker.org
    1. Re:Oh good grief Mozilla guys! by SirTalon42 · · Score: 1

      The Mozilla Corporation wants more control. Thats what this is all about.

  38. IceWeasel and gentoo linux by pizzach · · Score: 1

    Please, tell me there will be a new use extention in gentoo for this! I must have the icon!

    --
    Once you start despising the jerks, you become one.
  39. When Firefox ceases to be Firefox... by 9mind · · Score: 5, Insightful
    1) Debian doesn't want to use the offical patch system (i.e wait on Firefox's update approval process, etc.)
    2) a user on a Debian system not knowing this goes to Mozilla IRC with a Firefox problem (this has already happened)
    3) No one can solve the Bug... only to find it is an unofficial patch made or nto made by Debian
    4) User complains that Firefox sucks because its not the same across systems
    5) Brand is tarnished
    6) Rinse. Repeat.

    If you don't want to follow the guidelines, and follow your own way of doing things... change the name, or risk damaging the whole projects reputation. If I know Firefox works a certain way, I go to a new system and something doesn't work quite right, well guess what I'm not going to be happy. It's starts with the logo... but where does it end?

    1. Re:When Firefox ceases to be Firefox... by Myen · · Score: 1

      Yeah, as somebody who randomly hangs out on irc://irc.mozilla.org/firefox ... We try to support everyone, but sometimes we just get really confused by patched builds.

      For example, https://launchpad.net/distros/ubuntu/+source/firef ox/+bug/33840 - this is Debian (and from there Ubuntu) specific and doesn't happen with Firefox builds from mozilla.com (on the same system).

    2. Re:When Firefox ceases to be Firefox... by Vexorian · · Score: 1

      As an end user, I found mozilla's firefox package to be much more convenient than the one included by ubuntu and I could use sudo firefox to use auto update which made it actually work instead of Being forced to use an outdated version which - I knew- had security issues, ubuntu developers seriously take their time to update the firefox package.

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    3. Re:When Firefox ceases to be Firefox... by jmv · · Score: 1

      2) So (just for my information), Mozilla is totally uninterested in bugs I encounter on my machine?
      4) So there's less difference between the Windows and the Linux versions of Mozilla as there is between the official and the unofficial Linux versions?

    4. Re:When Firefox ceases to be Firefox... by Anonymous Coward · · Score: 0
      2) So (just for my information), Mozilla is totally uninterested in bugs I encounter on my machine?
      4) So there's less difference between the Windows and the Linux versions of Mozilla as there is between the official and the unofficial Linux versions?
      You still don't seem to grasp the point. Mozilla won't know how different the official and the unofficial Linux versions are, since it didn't create the unofficial versions. They can't be expected to support what they didn't create. If there are differences between the Linux and Windows versions, they know what is in those products and they can support them. Do you have any experience whatsoever in the area of software development or support? You sure don't sound like it.
    5. Re:When Firefox ceases to be Firefox... by snowgirl · · Score: 1

      Do you have any experience whatsoever in the area of software development or support?

      Well, I don't know about the author of Speex, but I know I do. I've worked on a significant product that had a number of "rogue patches" that we would not service. Our first response to anyone with a problem is "did you run this from a build in the current CVS, or are you using someone else's code?" Essentially, diagnosing where the version came from in the first place is paramount. Just because the Mozilla IRC people forgot to ask a simple question of "Where did you get your version of Firefox from?" doesn't mean that everyone is incapable of diagnosing a bug correctly.

      The person would have said "Debian", next thing to do is know if Debian made any changes to the FireFox code. Because if you're assuming that the bug is in the code you're working on, that someone else shipped, well that's just silly. Obtain their code, and diagnose the problem from there.

      In an IRC channel that I frequent, I like to tease people sometimes with seemingly odd and random support questions, that are actually very simple if you ask the right question. Like, "Well, when I type notepad c:\autoexec.bat, it doesn't work." First question: "What OS are you running this on?" Answer: "Linux" Resolution: "Uh... that just won't work."

      Using trademarks as a chilling effect on patching open source is stupid. "It's not a chilling effect!" I hear. Well, that's total malarky! FireFox is telling them if they want to have FireFox like all the other distros, then they have to follow MOZILLA'S rules, but it's open source! So, now instead, you have people install Debian and say, "WTF is IceWeasel?" and then wonder why there isn't any support for it. Then if there is support for something that breaks in FireFox, they can't find it with "firefox stupid problem that crashes my webpage", no, they have to know that IceWeasel is FireFox, but Debian can't even SAY that it's 99% FireFox, because Mozilla won't let them.

      So, either you do things according to our unacceptable way, or you harass the people who use your product... your choice. Yeah right, rather you're stuck with a Horned Dilemma, and no way out.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
  40. you are correct by Anonymous Coward · · Score: 0

    "but the fact that they're being a PITA for Linux distributions,"..this is correct! Want to know why? It is because quite clearly mozilla firefox is a WINDOWS product. Yes, they release for other OSes, but primarily it is a windows dominated organization, intended for windows users, for a windows market. They are mozilla corporation, in this for the long haul to make money at this, and being a windows product is the path they have chosen, linux and mac are secondary issues they are sort of reluctantly stuck with because they needed the exposure to overcome their defects and lack of use early on. To be frank, it has been a colossal fake-out.

    Open source needs a true, different alternative, an open source GPL licensed browser intended solely for open source operating systems. Firefox is not leading people to open source operating systems in any statistically significant numbers, it is helping to keep people cemented to windows and helping to insure that microsoft maintains desktop and commercial dominance.

  41. Iceweasel? by SwashbucklingCowboy · · Score: 2, Insightful

    That's extremely childish.

  42. Re:It is a BIG Deal by dircha · · Score: 1

    Indeed. This is, i thought, why the MPL contains a clause (like the GPL) which requires prominent notice of modification as a condition to distribution of modifications.

    Linus doesn't need to enforce the Linux trademark to prevent distribution of modified versions. The relative unity of Linux stems from quality and leadership, not from legal wrangling.

  43. What about Linux? by Kwesadilo · · Score: 1
    Personally, I see Debian's position as more proper within the realm of the F/OSS community. If you toute your program as open source, yet say that if anyone makes any changes to the program that you do not approve of, that they cannot use your trademark, then that certainly doesn't sound "open" and "free" to me. Especially, if your source contains all of the trademark data in the code, and altering the content requires a great deal of work.

    I'm pretty sure that "Linux" is a trademarked. See the Linux Trademark Institute. IANAL, so I wasn't exactly sure what was going on there, but it looks like you have to get a license to use "the mark" (man, that's creepy). It would appear that there are also some legal considerations when using images of Tux, the Linux penguin. Once again, I didn't really have the knowledge required to understand the details.

    Just FYI...

    --
    This space reserved for administrative use.
    1. Re:What about Linux? by SirTalon42 · · Score: 2, Insightful

      Linux is a registered trademark of Linus Torvalds, though hes never told Debian, Fedora Project, Ubuntu, Gentoo, RedHat, Linspire, Xandros, SuSE, that they couldn't ship a patched kernel and still call it Linux (pretty much every Linux distro adds patches to the kernel they ship).

  44. Jesus Fucking Christ by BeeBeard · · Score: 1, Flamebait
    I'm posting anonymously because I don't feel like being polite to you. The levels of arrogance and ignorance you just displayed is all the evidence I need to forgo niceties. I read your post and it was like reading the ramblings of a fucking crazy person.

    First you claim this:

    A lot of American corporate lawyers want to cause confusion between copyright and trademark law, by putting them both under the umbrella of "Intellectual Property", something which does not exist in law.


    This just gets funnier every time I read it. I guess my first reaction was "Who the fuck are you?" That you would claim that IP doesn't exist is laughable. If you read the article you'll notice that it includes quotes from Larry Rosen, a well-known IP lawyer. Please email Mr. Rosen to tell him that his profession doesn't exist.

    You go on:

    Copyright and Trademarks are two entirely separate things.


    I would like to introduce you to Jim. Jim here is Associate Manager of the Department of No Fucking Shit, Sherlock. Interestingly, do you know who originally confused the two? Fucking Debian is who--some asshole coder who thought he knew more about the law than lawyers decided it would be reasonable to confuse the two, and Debian's petty "stance" was borne.

    Mozilla have a right to put whatever restrictions they like on the use of their trademarks, whatever license the code is released under.


    This is a truthful but completely meaningless statement. Jim would like to talk to you about it.

    Debian can call it IceWeasel (or even something less derogatory-sounding, if they so choose), but copyright and the MPL license mean that they can still use the code.


    More meaningless filler that anybody who's been reading Slashdot for the last few weeks could have written. Jim is not pleased.

    Then you wrote this glistening turd:

    The big issue here, is that confusion about copyright vs trademarks is the result of a deliberate ploy by corporate America to confuse the public about "Intellectual Property" (IP) and "IP Rights" (IPR)


    You made this all bold and everything, presumably because you thought it was important to do so. But I'm just stunned--your ignorance and failure is so astounding. Here's a shocker for you: the fucking "public" have no say or interest in this whatsoever, certainly not enough to even have "confusion" about copyrights vs. trademarks. It's a firm distinction that exists in the law (you know, in the field you think doesn't exist), and I daresay the distinction exists in the minds of this public you pretend to care so much about.

    Perform this simple fucking test: Ask somebody of average intelligence over 40 years old which they think is copyrighted and which they think is trademarked, the Nike Swoosh or the contents of the newest Grisham novel?

    So here's you, you pretended to have your thumb to the pulse of the "people" (whoever these fucking non-Debian dimwits might be) and claimed that there's some kind of fucking conspiracy afoot by Corporate America--and by Corporate America I think you mean companies who would dare diminish themselves and insult their customers by actually charging for their products. Oh exclamation point!

    Again, where did this confusion occur, the one you think Corporate America created to confuse people who don't exist about what goes down in a field of law you think doesn't exist? It started in the mind of a non-lawyer coder who decided to start some shit with Mozilla because he didn't like the fact that Mozilla wanted to approve sloppy Debian patches before they went out.

    Leave it to a Slashdot poster to pretend to know more about the law than fucking lawyers.
  45. IceWeasel has a better logo by Anonymous Coward · · Score: 0

    I for one welcome our Icy Weasel overlords.

    And the iceweasel logo is soo much cooler than the firefox logo.

  46. Re:It is a BIG Deal by Omnifarious · · Score: 1

    Hmm... I'm reasonably well educated about copyrights, patents and trademarks, and I've never found anything RMS has said about them to be at variance with what I knew. In particular his writings on copyright are excellent and factual, and his opinions are clearly stated and well supported.

    He doesn't in enough detail about the finer points of patent law though, and he should, because many of those finer points strongly indicate that patents no longer serve the purpose for which they were originally intended.

    Of all the various bodies of law bundled under the term 'intellectual property' (a truly horrible term IMHO) trademark law is the kind I find least objectionable and is the least abused. Most of the abuses of trademark law I've seen have been to try to silence public debate by taking over domain names and such.

  47. Captain Anonymous! by Anonymous Coward · · Score: 0

    I'm posting anonymously because I don't feel like being polite to you.

    ahahahahahahahahahaaaaaa

    It's OK, I've done the same thing before myself. I guess after taking the time typing that 3 part novel you forgot to click that anonymous ticker? Put your flame suit on buddy!

    1. Re:Captain Anonymous! by Anonymous Coward · · Score: 0

      I guess after taking the time typing that 3 part novel you forgot to click that anonymous ticker? Put your flame suit on buddy!

      I doubt he will get flamed. He probably would have received more flamage if he had posted AC because then someone might think he was doing something new. But a review of his posting history shows he's got a real big stick up his ass about his big fancy job as an ip lawyer and likes to let everyone know about it - like this randomly off-topic disclosure. Like he did in this thread's post, he seems to violently agree with people about the important stuff and then take them to task for minor and rather trite differences. Sad thing is, he's usually right about the big picture, but just too angry to let a minor detail go unflamed. Beebeard really needs to find his boodaself.

  48. Establish another good common name by Chuck+Chunder · · Score: 1

    Debian, Ubuntu, Redhat etc should get a few people round a table and establish a decent (ie not iceweasel) name they can all use and promote.

    If the main problem with not using "Firefox" is that the new name won't be recognisable then the solution is to make the new name recogniseable.

    Interestingly this could devalue the "Firefox" name more than freer licencing of the trademark. If a competing name is established and used by most distributors (and maybe packaged for Windows too) then it may be the start of the new name overtaking "Firefox" in peoples minds.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:Establish another good common name by Anonymous Coward · · Score: 0

      "Debian, Ubuntu, Redhat etc should get a few people round a table and establish a decent (ie not iceweasel) name they can all use and promote."

      They already have. Everyone except Debian have got round a table and established a decent name. It's called Firefox and they're all using and promoting it except Debian.

  49. In other news..... by Anonymous Coward · · Score: 0

    I am releasing Debian 6.0 as soon as the find and replace finishes......

  50. FireHound by jrobinson5 · · Score: 0

    Then all of the "The dog is on fire" jokes on Slashdot would be true.

  51. Call me slow... by crasher35 · · Score: 1

    Wow. I just got that... Fire Fox... Ice Weasel. Yeah, it took me a while :/

    --

    I don't like to sit. Sitting is for people who like to sit.

  52. But the Court has been kind by BeeBeard · · Score: 1

    I'm sorry that I have to take a Stallman approach to this issue, but it's stupid to have Copyleft and Trademark compete against each other...

    As punishment, you have been sentenced to having to wear eyeglasses, shorts and a false beard while you give speeches about free software for six (6) months.

  53. Imagine the mess ... by Anonymous Coward · · Score: 0

    Can you imagine the mess it would be if every FOSS project that have a trademark insisted on every Linux distributions getting their patches and build options approved before they where allowed to distribute the software ?

    This is a slippery slope, and I have no sympathy for Mozilla in this debate. I care absolutely zero about Mozilla branding and trademark protection, but I care a lot about the convenience of running an OS that is complete, functional and well-integrated out-of-the-box.

  54. GPL3 is not a Free Software license? Really? by Kaseijin · · Score: 1
    The GPL-3 allows the copywrite holder to place certain restrictions on the licensee's use of the software, for instance no military/weapons use

    This would make GPL3 non-free by the FSF's own definition, which requires the freedom to run the program for any purpose. Please support your claim with text from the current GPL3 discussion draft.

  55. HAH! That's brilliant! by deek · · Score: 2, Interesting

    ... IceWeasel! What a great name. I laughed my arse off when I saw this.

      Now this is one reason why I love open source software so much. They have fun with their naming. It makes using an OS so much more interesting. Much better than using those staid commercial systems. IceWeasel has to rate up there with replacing "more" with "less", or naming a vi clone as "Elvis".

  56. defeats the entire purpose of free software by Trepidity · · Score: 1

    The purpose of free software is to permit anyone to modify it and redistribute their modified versions. The Mozilla Corporation is essentially trying to use their trademark to strongarm people into treating Firefox as proprietary software, in which you may not distribute modified versions without permission of the owner. Debian wisely refused to agree to such a restriction, and insists on distributing it as free software that they are free to change as they see fit.

    Now whether any particular changes are good or not is something we can have a technical argument over, but the fundamental issues---that downstream distributors should have the right to modify free software and redistribute their modified versions---is so central to free software that the concept makes no sense without it.

  57. Too many syllables, "IceVole" perhaps? by Anomalyst · · Score: 1

    Too many syllables, "IceVole" perhaps?

    --
    There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
  58. As a debian user... by Shads · · Score: 1

    ... since the early days of linux, I can honestly say, debian has done somethings that make me cringe and as soon as I read the post here I went "oh here we go again." Then I read the story... cripes, gg mozilla for being a bunch of fucktards. This is why involving lawyers when not necessary is a *bad* thing. Someone's getting paid somewhere for this one and money says its an attorney. The vast majority of developers on both sides are wanting to beat their heads off the desk about now.

    --
    Shadus
    1. Re:As a debian user... by jonasj · · Score: 1

      Not sure if you're trolling or mean it, it appears that Mozilla's developers, not lawyers, want this, as they are sick and tired of getting bug reports sent to them that turns out to be introduced by Debian's patches.

      --
      You know, Microsoft's street address also says a lot about their mentality.
  59. Mozilla vs Debian Analyzed by Anonymous Coward · · Score: 0

    While I don't have much sympathy with the Political Correctness Debian attitude over this I have even less for what I see coming from Mozilla Corp.

    Apart from issuing phrases that sound as though they are coming from a certain (too) well-known software company in the North-West US ("preserving the user experience") they are getting on their high horse at a time when their product seems to be trying hard to corner the title of "World's buggiest web browser". I think they should be expending their effort on identifying whoever was responsible for the buggy code, getting them off the project and then re-writing the affected parts instead of worrying about this sort of issue.

  60. A revelation by petrus4 · · Score: 2, Interesting

    From Merriam-Webster:-

    Main Entry: contrary
    Pronunciation: 'kän-"trer-E, -"tre-rE, 4 often k&n-'trer-E
    Function: adjective
    1 : being so different as to be at opposite extremes : OPPOSITE (come to the contrary conclusion) (went off in contrary directions); also : being opposite to or in conflict with each other (contrary viewpoints)
    2 : being not in conformity with what is usual or expected (actions contrary to company policy) (contrary evidence)
    3 : UNFAVORABLE -- used of wind or weather
    4 : temperamentally unwilling to accept control or advice
    - contrarily /-"trer-&-lE, -'trer-/ adverb
    - contrariness /-"trer-E-n&s, -'trer-/ noun

    Without simply being derogatory, I've realised that when I think of Debian, the above word is what has customarily come to mind. It's nothing I can concretely put my finger on, but I've always felt that there was an aura of perversity about the project...a sense that the Debian developers change things from the upstream norm purely because they can, and not because they've necessarily put thought into whether or not it'd actually be a good idea. Not only that, I can also remember going into the Debian IRC channel on Freenode once. It reminded me very strongly of the account of the Mad Hatter's tea party from Alice in Wonderland. They honestly came across as some of the weirdest and most unhinged individuals I've encountered. I've been using IRC for 12 years, and have known some very bizarre types online...so that is saying a lot.

    I'm not claiming that that is definitely what is happening here...I don't know, and the referenced article is sufficiently vague that I feel as though I still haven't got a better idea after having read it. What I am definitely saying however is that from what I've seen, these kinds of issues coming up is entirely consistent with Debian culturally. It's also one of the reasons why I've stayed far away from the distribution; that, their degree of formality with "policy", (are they a FOSS project, or a sovereign government?!) and their degree of open sympathy with Stallman/the FSF. I think I also resent the fact that I've read about them being referred to as the only "successful" non-commercial distribution, when due in part to the reasons listed above, there are others that I feel are at least as worthy of that designation as Debian is, if not moreso. Debian might be bigger, sure...but size alone does not necessarily equal success in my own mind.

    That's not to say that there haven't been good things to come from the project, at least in a secondary sense. (Knoppix and Ubuntu come to mind, which are both Debian spinoffs) The point is that it's a long way from perfect...and things like this debacle are evidence to support that assertion.

  61. you are wrong by jizmonkey · · Score: 2, Informative
    The parent said, "If you want a full description, feel free to get yourself a lawyer."

    To which you said, "Uh, done? I don't keep old casebooks on my shelf for the hell of it, you know."

    On Slashdot, you are my favorite kind of lawyer. In real life, my least favorite. You are smug, lording it over other people, and 100% wrong.

    If you think that the trademark law is enabled by the copyright and patent clause of the US Constitution, you might want to read the 1879 Trademark Cases. They are Supreme Court cases, so they should be in the old casebooks on your shelf. To wit, the federal trademark laws stem from the commerce clause, not the patent and copyright clause, precisely because the patent and copyright clause says nothing about trademark. This is the opposite of what you said.

    Thus, your argument that the word "IP" has some kind of constitutional meaning is void.

    I sure hope you don't fancy yourself an "IP lawyer."

    --
    With great power comes great fan noise.
    1. Re:you are wrong by Rydia · · Score: 1

      So I'm smug for responding to someone belittling me by saying that he's wrong? Or is that just a rule you have for lawyers? He made a rude assumption about what I knew, and a very rude remark about my intelligence. I was moderately rude in reply. How horrid.

      I'm glad, however, that you know what you talking about, because that creates a real discussion.

      The first trademark enabling acts used the copyright clause. Later, the Supreme Court decided (in the trademark cases, as you've noted), that the copyright clause did not support trademark. The problem with just saying "ah, well, it's commerce clause now" is that the tools with which we analyze trademarks, and the mechanisms by which they are recognized and enforced were designed under copyright clause rationale. When the Court swatted it down, the government changed the law facially (and in some ways mechanically) to bring it in line with a commerce clause justification. Most of how we work with trademarks, however, remained the same. The significant changes for justification under the commerce clause is that it runs into the annoying "interstate" problems, and has difficulties with its consumer-confusion rationale under a clause that is quite clearly not meant to entertain the idea.

      In the end analysis, we have a producer-centered regime (unlike the more consumer-centered analyses that arise under the commerce clause) which grants protections similar in concept and mechanisms but different in practice to copyrights. In fact (as I mentioned), despite the different justifications, copyrights and trademarks have much more in common than copyrights and patents do (whose analyses and justifications are both rooted in the copyright clause).

      I apologize if I was overly simplistic or misspoke about the topic. Perhaps in the spirit of forgiveness I can ignore the fact that my argument had nothing to do with constitutional meaning of a phrase, simply an explanation of why that phrase has arisen, couched in a historical, constitutional analysis.

      Or, we could just run around insulting each other and using bold like it proves our point. I'm down for whatever.

    2. Re:you are wrong by tehcyder · · Score: 1
      I sure hope you don't fancy yourself an "IP lawyer."
      If a large law firm has an "Intellectual Property" division and they employ you as a lawyer, then you are an "IP lawyer." And, yes, they will know the difference between a Trademark and a Copyright.

      In the UK, there is no legal entity called "a group of companies" so does that mean that I can't be XYZ's "group finance director"?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  62. Pffft by BeeBeard · · Score: 1

    Hey buddy, I wouldn't expect you to take the time, but if you read the parent to the post you linked to, you'll notice that the parent identified himself as a Jew, and I also did in my reply as an honest effort to establish common ground. Mentioning I was an attorney in the same breath was self-deprecating because of the old cliche (as in "oh a Jewish attorney, gosh how original). Plus, I'm not an IP lawyer--just a random asshole attorney who has done some IP work. And I stress some. IP law is like the end-all, be-all boutique thing to be doing. Frankly I'd like to do more. But there are certainly more knowledgeable, experienced people out there than I am.

    Oh and to slam me based on my posting history? What is that? I come up with my fair share of good comments that contribute to the overriding discussion or at least brighten someone's day, so where's the harm in that?

    If I'm right in general but in my replies fucking pounce on the most trivial of misstatements like it's the end of the world if they're not pointed out, then I apologize. It's how I spend my days and I'm not the best at separating work from play. Plus, in case you haven't noticed, that seems to be par for the course as far as /. postings go. Someone will say something meaningful, and then a veritable herd of posters will call him/her out with this "oh actually that one insignificant thing is not the case..." nonsense. So don't act like I'm some kind of oddity simply because I can couple good arguments with an insane, irrational impatience for dissent. At least the stick doesn't bother me much as long as I use enough KY. Later.

  63. Debian didn't invent IceWeasel by mackyrae · · Score: 1

    I'm pretty sure GNU did it, seeing as it is downloadable from gnu.org and it goes with GNUzilla.

    --
    look! it's a bird, it's a plane, it's....a girl? yes, a girl browsing Slashdot on Linux
  64. Re:It is a BIG Deal by SirTalon42 · · Score: 2, Insightful

    Actually the Linux kernel is forked all the time, and is generally changed far more than any distro changes Firefox. Most every single Linux distro out there doesn't ship the vanilla Linux kernel as released by Linus. Debian, Fedora, RHEL, Gentoo, SuSE, Mandrake, Ubuntu, Knoppix, Linspire, etc all ship modified (sometimes VERY modified, on an old version of RHEL when they were still using 2.4, they back ported LOADS of patches from 2.6) versions of the Linux kernel.

  65. Oh yeah one more thing by BeeBeard · · Score: 1

    I also find it funny that you posted as a coward and linked to the one post I've made in like the last 2 months where I'm just really discussing something instead of making a point about it. It is fun to just talk to people about certain subjects, you know? To exchange information in that fashion? They say something I wasn't aware of and I respond in kind.

    Now if you'll excuse me, I have lawyer alcohol to consume while I watch a lawyer baseball lawyer game.

  66. simple solution! by sdnoob · · Score: 1

    why not quit screwing around with the names and artwork of mozilla packages and just put the "real" thing, including name & artwork, in a new "supported, non-free" repository...

    there are enough dsfg-compliant alternatives (epiphany, evolution, K-whatever, etc) out there to include in the regular "main" repository.

    problem solved!

  67. Re:When Linux ceases to be Linux... by SirTalon42 · · Score: 1

    1) Debian doesn't want to use the offical patch system (i.e wait on Linux's update approval process, etc.)
      2) a user on a Debian system not knowing this goes to Linux IRC with a Linux problem (this has already happened)
      3) No one can solve the Bug... only to find it is an unofficial patch made or nto made by Debian
      4) User complains that Linux sucks because its not the same across systems
      5) Brand is tarnished
      6) Rinse. Repeat.
      If you don't want to follow the guidelines, and follow your own way of doing things... change the name, or risk damaging the whole projects reputation. If I know Linux works a certain way, I go to a new system and something doesn't work quite right, well guess what I'm not going to be happy. It's starts with the logo... but where does it end?

    It's fine when the Linux kernel is modified and distributed, as well as Gnome and KDE, but not Firefox once the Mozilla Corporation notices (it was fine with the Mozilla Foundation previously). Also Mozilla often doesn't support the version of Firefox that ships with Debian stable anymore (so Debian HAS TO either back port security updates, leave the users with an unsecure system, or break stable by making major updates).

  68. assinine by BenLutgens · · Score: 1

    this is completely assinine. don't these people have anything better to do?

    Are they going to rename every package in the pools? Just add the bastard to non-free if you're that farking worried about it.

    flippin debian, too much politics, not enough releasing.

    --
    "If you love someone, set them free. If they come home, set them on fire." - George Carlin
    1. Re:assinine by doom · · Score: 1
      flippin debian, too much politics, not enough releasing.
      One more time: it's the Mozilla Corporation that suddenly decided to get fussy about this. They also then suddenly required changes in the way Debian handles it's patches. You want Debian to ship faster, and also deal with additional proceedural hassles, and accomodate changes like this (somehow) at the last minute?

  69. Where? by Noksagt · · Score: 1

    Can you point me to where he made this remark?

    The only comment he made was here, where he said it was meant for porting to other Operating Systems (as opposed to distributions). But other Linux distros follow this policy & other Mozilla people have agreed that it could be appropriate.

  70. The Real Issue Here by mr_matticus · · Score: 1

    I don't see a material difference between Mozilla and Debian with regard to the concept of "F/OSS." Firefox is fully open source, and there's no hypocrisy involved in their decision--it's not an open source vs. not-so-open source debate as you've framed it.

    It's a trademark and marketing/liability issue. If you modify Firefox for your own use, that's fine. You can even redistribute your modified Firefox. What you can't do is market your modified product *AS* Mozilla Firefox, because while it's based on the same source, it is NOT the same end product as the one vended as the "official" Mozilla Firefox.

    They could have tried to call the product Debian Firefox, which addresses the ownership/liability concerns put forth by Mozilla's lawyers, but then it becomes a trademark dispute. Firefox is a trademarked name for a web browser product (material goods, albeit digital) produced and supported by Mozilla. Therefore, using the name "Firefox" requires the approval of the owner of said trademark. In order to grant that approval, Mozilla wanted to see and approve all modifications--that way, they could point out problems and put out notice to modifications they do not support or endorse. Debian philosophically disagrees with that sort of vetting, and opted to rename the product.

    The whole debate has nothing to do with how "open" either company is. Imagine you, an independent company, made substantial modifications to a shipping version of Debian and put it back on the Internet for distribution, but you still called your product "Debian." Would Debian say, "please continue using our trademarks on your unofficial, non-Debian product"? You bet your ass they wouldn't.

  71. Re:It is a BIG Deal by A+beautiful+mind · · Score: 1

    Yeah. Shoddy distributors messing up the pristine and just perfect linux kernel! How dare they mess up the WORD OF GOSPEL from Linus's git repository itself!

    You say they are patching it to make it better? You're saying that Linus and LKML's opinion encourages this behaviour? Nevermind...

    On the other hand, shoddy distributors messing up the pristine and just perfect Firefox browser! How dare they mess up the WORD OF GOSPEL from the Mozilla corp.'s cvs repository itself!

    See the direction I'm going into?

    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
  72. Won't work. by SanityInAnarchy · · Score: 1

    The only possible way this could work is if you managed to sell it to a completely separate group of users. Maybe if you managed to convince them all that it was iNet or iWeb, the shiny new plastic browser from Apple, or maybe if you had a killer app for it, but seriously, I don't see a Firefox derivative replacing Firefox unless the name is moderately similar and the app is measurably better.

    Just remember how much time and money it took for Firefox to completely eclipse both Mozilla and Netscape. And Firefox was measurably better than both -- at least, by the time it was actually named Firefox.

    --
    Don't thank God, thank a doctor!
    1. Re:Won't work. by Chuck+Chunder · · Score: 1

      That is true to a degree. However the situation on Linux is a bit different from Windows and in many ways you do have a "seperate group of users".

      While Firefox markets directly to Windows users on Linux most people surely get their browser from their distribution rather than from Mozilla. If distributions did re-name it then the new name would get a reasonable amount of penetration automatically.

      Windows is a different prospect of course and frankly I'd think it would probably be a waste of time to spend any real effort trying to push an alternately named browser there.

      --
      Boffoonery - downloadable Comedy Benefit for Bletchley Park
    2. Re:Won't work. by SanityInAnarchy · · Score: 1

      This only makes sense because Firefox is the default browser of many distros. What about a KDE-based distro that defaulted to Konqueror?

      Most current Linux users would accept the new name with hardly a comment. It would, however, be yet another bad thing for marketing Linux to Windows users. It's no wonder Ubuntu caved.

      --
      Don't thank God, thank a doctor!
  73. I hope they use the standard browser by slack_prad · · Score: 1

    This bug clearly shows why Debian/Ubuntu shouldn't muck with the browser's source code. I wonder what additional functionality they add besides disabling the 'Check for updates' button.
    And of course security updates. It would benefit everyone if they just send patches upstream.

    https://launchpad.net/distros/ubuntu/+source/firef ox/+bug/64844
    I hope ubuntu sticks with the vanilla browser.

    --
    Sent from my desktop computer
  74. thunderbird by flanderz · · Score: 0

    Is thunderbird affected by this or does it's artwork have a different license?

  75. Matthew Garrett on the situation by alfino · · Score: 2, Informative
    --
    echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
  76. Fairfix! [Re:Iceweasel?] by jetxee · · Score: 1
    I think the best name would be "Fairfix".

    It is different enough to make Mozilla happy and similar enough to confuse users ;) Also it connotates with the better firefox than the old one.

  77. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  78. IceWeasel beats FireFox usage stats by end of 2007 by wmaster · · Score: 2, Insightful

    That's something very likely to happen. The real power of free and open source software always was and is what happens with forks. After all, that's how evolution works. An IceWeasel (and no, I did not vote for this name) being an improved, faster and even more secure browser than it's parent can easily be adopted not just by other Linux distributions, but also by MacOS (and even Windows!) users. It always begins with compatibility problems (incompatible code, license or personalities) and often creates the better software product. Let's support it and help make it strong. I vote for a full fork and substantial improvement. I would also invite all MozDevs to join IceWeasel, where a real free and open source browser will be done without "corporate governance". Greetings, Chris

    --
    "An operating system must operate."
  79. Epiphany by TobascoKid · · Score: 1

    It's been a few years since I last tried Epiphany, but I remember that it kinda sucked. The developers took GNOME's "users are idiots who need to be protected from themselves" philosophy way too far and made the software almost useless - for example, they redid bookmarks in such a way as to make them unusable for anyone with more than a trivial number of bookmarks (they didn't even call them bookmarks anymore). I seem to remember that there was a previous Gecko based gnome browser (I think it was called Galeon), which was less brain dead, but I think that project was dropped for epiphany (as epiphany was more in keeping with "protecting users from themselves").

    --
    At some point, somewhere, the entire internet will be found to be illegal.
  80. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1

    What on earth are you talking about? What debian is shipping is just firefox minus branding plus debian-specific patches. Why would anyone else have an interest in adopting that?

    Your idea about a full fork shows a complete lack of understanding about how the Mozilla project works. Why would you want to fork Gecko or XULRunner just because of disagreements over a front-end that makes up 10% of the code, tops? Because that's all Firefox is. At least learn the basics about Mozilla before calling for a fork of it, otherwise you won't get far.

    And for your "corporate governance" argument... Mozilla Corp. is just a subsidiary(sp?) the Mozilla Foundation created for administrative purposes. GNOME has the GNOME Foundation, Apache has the Apache Software Foundation, Python has the Python Software Foundation, GNU has the FSF. Are you calling for a fork of those projects too, to rid them of their evil governing entities?

    --
    You know, Microsoft's street address also says a lot about their mentality.
  81. All about the Merch by erroneous · · Score: 1

    Anyone else think this has nothing to do with Software - Free, Open or Whatever - and everything to do with Mozilla's ability to sell branded Merchandise?

    They should just open the Firefox Restaurant and be done with it.

    --
    erroneous: look me up in a dictionary
  82. Marketing ??? by Anonymous Coward · · Score: 0

    "Mozilla has been prompted to clarify its position on the company's
    marketing blog."

    Marketing blog ??

    Marketing ?????

    Tells me everything I need to know about this subject.

    Marketing = scum and/or slime

  83. Re:HAH! That's brilliant! by tehcyder · · Score: 1
    IceWeasel! What a great name. I laughed my arse off when I saw this
    Absolutely, I'd pay good money for any program called IceWeasel, even if it was a monochrome MS-DOS bookkeeping tutorial, just to have the box on my desk.
    --
    To have a right to do a thing is not at all the same as to be right in doing it
  84. NOT KNOWN AT THIS ADDRESS by Ginger+Unicorn · · Score: 1

    Your letter seems to have been delivered to slashdot by mistake. Please check the address you have for the "Debian Leaders"

    --
    (1.21 gigawatts) / (88 miles per hour) = 30 757 874 newtons
  85. Completely Stupid by scorpius13 · · Score: 1

    Mozilla says its guidelines are clear: the use of the Firefox name is permitted only if accompanied by its logo, icons, and other artwork.

    FINE. Ive been a debian user for many years - giving people permission to change the logo and mess with it is like changing my name on programs that I write. Leave my name on it and leave the logo ALONE.

    Firefox is already opensource - what more do you want - to now change the logo?!? What the hell would be the point of that?? Demands and decisions like this are what will drive debian into the ground.

    You will be wasting time and effort reworking the browser and coming up with your own.

    why not spend this time trying to get the next release out sooner than worrying about logos?!?!?

    Debian people: Stop being so stupid

    ~Daviddutch1964

    1. Re:Completely Stupid by doom · · Score: 1
      scorpius13 wrote:
      Mozilla says its guidelines are clear: the use of the Firefox name is permitted only if accompanied by its logo, icons, and other artwork.
      And Mozilla Corp is changing the deal that they had with the Debian group, and changing it in a hurry without much warning.

      FINE. Ive been a debian user for many years - giving people permission to change the logo and mess with it is like changing my name on programs that I write. Leave my name on it and leave the logo ALONE.
      And guess what? Now Firefox won't have the logo or the name on it. That was a great move on MoCo's part wasn't it?

      why not spend this time trying to get the next release out sooner than worrying about logos?!?!?
      It was Mozilla's Corporations decision to suddenly start worrying about logos. They also then suddenly started worrying about patch policies. And you think Debian has the problems here?
    2. Re:Completely Stupid by Anonymous Coward · · Score: 0

      I do NOT care at all about this political crap. Just give me my debian and a the browser. Arguing over logos - how rediculous.

  86. In plain English... by flyingfsck · · Score: 1

    The Debian developers are lazy and FOS. Moz caught them out and now the Debian devs are all surly and in a huff about it. Figures.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  87. Re:IceWeasel beats FireFox usage stats by end of 2 by wmaster · · Score: 1

    Your idea about a full fork shows a complete lack of understanding about how the Mozilla project works. Why would you want to fork Gecko or XULRunner just because of disagreements over a front-end that makes up 10% of the code, tops? Because that's all Firefox is. At least learn the basics about Mozilla before calling for a fork of it, otherwise you won't get far. I hope you are aware of the fact that FF itself started with a fork. Why would anybody? Well, the Debian community is always willing and ready to go the extra mile needed to protect the freedom of their users. Cdrecord was recently forked for very similar reasons - incompatible licenses (see wodim). You should also understand that Debian is not an unimportant hidden club of crazy extremist communists, probably time to learn something about it's organisation, size and abilities instead of teaching me Mozilla project structures. And for your "corporate governance" argument... Mozilla Corp. is just a subsidiary(sp?) the Mozilla Foundation created for administrative purposes.Obviously you did not understand - and I did not understand you. What do you mean by "just a subsidiary"? Does that mean Mozilla Corp. is "less corporate" because it's owned by a foundation? That's a faith it shares with some of the biggest corporations existing today, so the argument is interesting. Greetings, Chris

    --
    "An operating system must operate."
  88. Moooo! by Anonymous Coward · · Score: 0

    They're cattle, and cattle don't thank you when you fix their barn.

    Mooo. Moooo-moo! Muoooh; mooooooh! MuMuMooo!

    Translation: This is an insult to cattle everywhere; we proclaim a catt-wa against you and we know where you live!

  89. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1

    I hope you are aware of the fact that FF itself started with a fork.

    Just of the front-end. When you said you'd like a "full fork" I took it to mean the whole Mozilla codebase, Gecko and all. I may have misunderstood you.

    the Debian community is always willing and ready to go the extra mile needed to protect the freedom of their users.

    Yes, and they have always been, but I disagree with this move. I value software freedom highly -- when I ordered a ThinkPad last week, I chose a model with an Intel GMA 950 instead of one with an ATI chip, in spite of the lower screen resolution I'll get, just to avoid having to run a non-free driver -- but for me, software freedom is about code, not graphics.

    You should also understand that Debian is not an unimportant hidden club of crazy extremist communists, probably time to learn something about it's organisation, size and abilities instead of teaching me Mozilla project structures.

    I am well aware of that. I don't know on what you base your assumption that I'm not. I like Debian for both ideological and technical reasons.

    Does that mean Mozilla Corp. is "less corporate" because it's owned by a foundation?

    My point was that Mozilla Corp. is, in essence, just a legal entity set up by the Mozilla project for administrative purposes, similar to what the GNOME Foundation is for GNOME, and the other examples I listed. I just don't understand why you think that being incorporated makes Mozilla's legal entity more inherently evil than for example the GNOME Foundation.

    --
    You know, Microsoft's street address also says a lot about their mentality.
  90. Re:IceWeasel beats FireFox usage stats by end of 2 by doom · · Score: 1
    jonasj wrote:
    but for me, software freedom is about code, not graphics.
    I'm glad you weren't in charge of writing the Bill of Rights, the first ammedment would look a lot different.

    On another front: how do you feel about patch policies? This apparently started out as a trademarked graphic problem, and then MoCo decided to expand it, and demand rights of approval of every Debian patch.

    What would happen if every open source software group demanded that the Debian Security team seek their approval on every move they make?

  91. Re:IceWeasel beats FireFox usage stats by end of 2 by doom · · Score: 1
    My point was that Mozilla Corp. is, in essence, just a legal entity set up by the Mozilla project for administrative purposes, similar to what the GNOME Foundation is for GNOME, and the other examples I listed. I just don't understand why you think that being incorporated makes Mozilla's legal entity more inherently evil than for example the GNOME Foundation. The Mozilla Corp has changed the deal they had going with Debian twice during this dispute. They're behaving in a capricious and high-handed way, that the Mozilla group did not. It's at least a teneable hypothesis that there's something dangerous about using a "Corporation" like this -- it's not just a legal entity, it's a culture that's grown up around this type of entity.

    You understand there may be no difference between a "Corporation" and a "Foundation" but it's name, but the name difference alone could create different behavior, by attracting different people and/or encouraging different attitudes.

  92. Re:IceWeasel beats FireFox usage stats by end of 2 by wmaster · · Score: 1

    I just don't understand why you think that being incorporated makes Mozilla's legal entity more inherently evil than for example the GNOME Foundation.

    What would be the reason to build two different legal entities instead of just one? Mozilla runs the Foundation AND the Corp., while most other projects stick with a foundation only. Have a closer look at who/where is in charge and legally entitled to decide, and have also a very close look at who owns the shares, and how they might be distributed in the future. Such examination of Mozilla's legal framework will help you to answer your question.

    And despite the ridiculous logo/trademark discussion - did you recognize that Mozilla is the only bigger "free & open source" project with GNU/GPL licensed products requesting patch reviews/control and legitimize this with "trademark protection"? That's actually an ugly abuse of the GPL - if not an illegal step.

    Greetings, Chris

    --
    "An operating system must operate."
  93. Why don't we have "Internet" buttons? by doom · · Score: 1
    Britz wrote:
    Anyone that needs to recognize it mostly just clicks on the internet icon (thingy). Anyone else can just look and will find it.
    Do you know of any Linux distros that actually put an "Internet" icon on the desktop? I haven't seen this in my recent installations of Kubuntu and Knoppix. It would seem like a no-brainer as far as "useability" goes: make it easy for people to find the web browser, you know?

    Oddly enough, Mac OSX doesn't seem to do this either... I was helping a computer illiterate person with her new Mac laptop recently. She couldn't figure out how to launch a web browser. There's a band of gigantic flashy graphics going across the screen, but if any of those launch a browser, I couldn't find it. I had to go browsing around on the hard drive, and when I saw "safari" I recognized that as a web browser, but there's no way a total beginner would know that. And that's the famed Easy To Use macintosh, no less.

  94. What I want to know by Anonymous Coward · · Score: 0
    Is can I take the Debian patches, and artwork and create a Windows version of Ice Weasel? That way, it will be simpler to provide support for my friends who still use windows.

    Ok now, click on the Ice Weasel icon...

  95. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1

    What would be the reason to build two different legal entities instead of just one?

    That question was answered very well in the /. story about the Corporation's launch: "Don't let the word "commercial" scare you, the new Mozilla Corporation (as it has been dubbed) will be owned 100% by the Mozilla Foundation. The change is mostly a legal/tax thing to avoid the problems of pursuing revenue-generating avenues while remaining a non-profit. There will be no change to the development process and end-users won't notice much difference either.". They are generating a lot of money, mostly from Google, and being a corporation makes it easier to manage those funds for the good of the whole Mozilla project.

    Have a closer look at who/where is in charge and legally entitled to decide, and have also a very close look at who owns the shares, and how they might be distributed in the future. Such examination of Mozilla's legal framework will help you to answer your question.

    Now I'm beginning to suspect that you are simply trolling. The Mozilla Corporation is owned 100% by the Mozilla Foundation, and there is no way that is going to change. It's basically the same people overseeing the project as it has been ever since Netscape freed their source code. People like Mitchell Baker, Brendan Eich and Frank Hecker, to name a few.

    And despite the ridiculous logo/trademark discussion - did you recognize that Mozilla is the only bigger "free & open source" project with GNU/GPL licensed products requesting patch reviews/control and legitimize this with "trademark protection"? That's actually an ugly abuse of the GPL - if not an illegal step.

    Okay, now I'm almost *convinced* that you're trolling. You can download the source tarball for the latest firefox from ftp.mozilla.org and change WHATEVER YOU WANT it redistribute it HOWEVER YOU WANT. The source you download is already configured not to use the --enable-official-branding switch. Mozilla only requests patch review when you enable that switch, something that you specifically, intentionally need to do to switch on the official branding. The suggestion that there could be something illegal about that is absurd.

    --
    You know, Microsoft's street address also says a lot about their mentality.
  96. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1
    I have no idea what the first amendment is about. Not every person in the world is american, you know...

    how do you feel about patch policies? This apparently started out as a trademarked graphic problem, and then MoCo decided to expand it, and demand rights of approval of every Debian patch.

    Sorry, but you're wrong. The patch approval thing was there from the start. Read the bug. From the initial description: "calling the browser Firefox requires the same approvals as are required for using the logo and other artwork".

    What would happen if every open source software group demanded that the Debian Security team seek their approval on every move they make?


    You need to understand that "Firefox" is a brand which ordinary end users are starting to recognize. Most packages in debian are not. Look, when a security issue comes up in an old version of Firefox which is no longer supported by mozilla, why can't debian just work with upstream to produce one fix which all distros can take advantage of, and which can be checked into mozilla.org CVS? Just because MoCo no longer pays people to work on a specific branch doesn't mean Debian or others can't get patches checked in. This has happened in the past where Sun or IBM (IIRC) took over old branches that were abandoned by Mozilla.
    --
    You know, Microsoft's street address also says a lot about their mentality.
  97. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1
    The Mozilla Corp has changed the deal they had going with Debian twice during this dispute.


    As I just wrote in my reply to your other post, no, they have not; the issue you mentioned was brought up in the initial bug description.

    They're behaving in a capricious and high-handed way, that the Mozilla group did not.


    But this *is* the "Mozilla group". It's still the *same people* who are in control!

    It's at least a teneable hypothesis that there's something dangerous about using a "Corporation" like this -- it's not just a legal entity, it's a culture that's grown up around this type of entity.

    You understand there may be no difference between a "Corporation" and a "Foundation" but it's name, but the name difference alone could create different behavior, by attracting different people and/or encouraging different attitudes.


    I find this speculation kind of paranoid...
    --
    You know, Microsoft's street address also says a lot about their mentality.
  98. Mod parent up by Anonymous Coward · · Score: 0

    I just want to say kudos on a well worded summary of the situation. There are a lot of people here that don't seem to understand what exactly is happening. I hope they read your post.

  99. Re:IceWeasel beats FireFox usage stats by end of 2 by doom · · Score: 1
    jonasj wrote:
    doom wrote:
    how do you feel about patch policies? This apparently started out as a trademarked graphic problem, and then MoCo decided to expand it, and demand rights of approval of every Debian patch.
    Sorry, but you're wrong. The patch approval thing was there from the start. Read the bug [debian.org]. From the initial description: "calling the browser Firefox requires the same approvals as are required for using the logo and other artwork".
    I'm sorry, but I don't think you can read very well.

    Bug #354622, posted 27 Feb 2006, says that the previously agreed on compromise (using the name without the logos) is no good anymore. (Try re-reading the very sentence you quoted).

    Bug #354622, posted 20 Sep 2006, then includes the requirement: "All changes the distributor wishes to make to the source code must be provided as discrete patches, along with a description of why the change is required"

    What would happen if every open source software group demanded that the Debian Security team seek their approval on every move they make?
    You need to understand that "Firefox" is a brand which ordinary end users are starting to recognize.
    Okay. I'm turning on the understanding... Hm. Nothing is changing in my worldview. Perhaps I understood this already.

    Most packages in debian are not.
    Ah, I get it. Firefox is hot and Debian needs to bend over and kiss their toes.

    Look, when a security issue comes up in an old version of Firefox which is no longer supported by mozilla, why can't debian just work with upstream to produce one fix which all distros can take advantage of, and which can be checked into mozilla.org CVS?
    • I would be very surprised if they don't kick patches back upstream.
    • Debian maintains Firefox code long after Mozilla has abandoned it.
    • The idea of letting a vulnerability sit in "stable" while waiting for bureacratic approval from upstream does not sit well.
    Just because MoCo no longer pays people to work on a specific branch doesn't mean Debian or others can't get patches checked in. This has happened in the past where Sun or IBM (IIRC) took over old branches that were abandoned by Mozilla.
    Presuming this is all correct, it doesn't change the problem: Seeking prior approval before they get to patch their own distro...

  100. Re:IceWeasel beats FireFox usage stats by end of 2 by jonasj · · Score: 1
    You try re-reading that sentence. "calling the browser Firefox requires the same approvals as are required for using the logo and other artwork"; "the same approvals" being that Mozilla Corp. needs to agree to each patch. Mike Connor made that very clear in his first followup comment too: "To my knowledge, each patchset that deviates from what we ship should be run by whoever is doing licensing approvals". The argument that the Mozilla people are changing the rules all the time and therefore cannot be trusted still doesn't hold.

    Ah, I get it. Firefox is hot and Debian needs to bend over and kiss their toes.
    Please re-read what I was replying to. You asked "What would happen if every open source software group demanded that the Debian Security team seek their approval on every move they make?". I was explaining why that won't ever happen, showing that your point was irrelevant.

    The idea of letting a vulnerability sit in "stable" while waiting for bureacratic approval from upstream does not sit well.
    Please read what BZ wrote here.

    Presuming this is all correct, it doesn't change the problem: Seeking prior approval before they get to patch their own distro...
    Those are the rules if you want to ship something you call "Firefox", and I don't see a problem with that.
    --
    You know, Microsoft's street address also says a lot about their mentality.
  101. Hello, strawman by Kaseijin · · Score: 1
    4) if I USE your software to build my website, I'm a user of your software.

    The users are the ones interacting with the software. If this section is relevant, you're modifying and publicly performing it.

    6) "terms ... or deny permission for activities that are not clearly permitted, expressly or otherwise"

    The draft reads "clearly not permitted"; "not clearly permitted" is your own invention.