Slashdot Mirror
IceWeasel — Why Closed Source Wins
engtech writes, "There's been some hype about the Debian fork of FireFox called IceWeasel. Politics aside, this is a bad idea because it fragments the user base, divides the focus, and opens the path for Microsoft and Internet Explorer 7 to regain marketshare."
The point of open source software is to allow users the freedom to modify the code to meet their needs. If you restrict users to one single unmodified browser for the sake of unity then we have met the enemy and he is us.
I swear I didn't know it was loaded...
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.
You may only use the FireFox trademark if you do not apply patches to FireFox. The Debian team want to apply security fixes and bug fixes to their packaged version. They can either do this and not call it FireFox, or not do it. If you were a Debian user, which would you rather they did?
I am TheRaven on Soylent News
The issue in trademark law not copyright law. Trademark law is a whole different animal. Unlike copyrights and patents, you can lose your trademark if you fail to defend it.
Debian releases are slow. Debian security patches are lightning fast.
I can understand the need to tune it or fix bugs, but it seems to go beyond that. On the fresh Ubuntu install I recently did, my Firefox has a fun "feature". If you move the mouse over a button, the button goes yellow and flat. And it doesn't change back when you move the mouse away. Hardly what I would describe as tuning or fixing. My first thought when I saw it was "stupid Firefox". My second thought was "It doesn't do that on Windows". Only after that did I think, "Oh, must be a Ubuntu change". Is that really the experience the Mozilla folks want people to have when they interact with the browser for the first time.
I think the Mozilla folks should probably adjust the licensing terms on the artwork, but it does reflect badly on them when distros make changes that affect the user experience.
A lot of thought was put into that. It would be fine if there was an "Official Firefox" and "Firefox", similarly to the way Debian handles their trademark.
Bruce
Bruce Perens.
Except that the Mozilla developers work on what they want to do, not what you want them to do. Take a look at bug 33654 - TEXTAREA incorrectly applying ROWS= and COLS=. This was reported in 2000 (yes, 6 years ago) and makes forms not line up properly. If you were to fix this, you couldn't technically distribute your fixed version, because the firefox license prohibits it. Hence, iceWeasel.
Intron: the portion of DNA which expresses nothing useful.
I hear this repeated a lot. It's not true. If you allow your mark to become generic you can lose your right to it. Firefox is not at risk of this happening. Google is. You can be selective about enforcement as long as you don't allow the mark to become generic.
Debian has handled this problem, for years, by having an official-use and an un-official-use logo for their own distribution. This allows people to package the program with modifications and still use consistent branding.
Bruce
Bruce Perens.
Of course, they can actively police it *and* grant permission to use it. That didn't work in this case, because the conditions Mozilla placed on that permission weren't acceptable to Debian.
Also, I seem to recall something in the DFSG such that licenses *must* be transferable to derived products. I suspect Mozilla's trademark license would have been specific to Debian, and therefore not qualify for the DFSG.
I only used Debian for apt. It totally blows away yum. But, with the slow ass release cycles I can't take it much longer.
Don't use the stable branch then, use testing or unstable. With only some care before upgrading (forget dist-upgrade) and using apt-listbugs you should be fine and using bleeding edge software (I upgraded to KDE 3.5.5 some days ago, and guess when it was released).
Debian has solutions for almost everything, you just have to learn.
You may want to hit yourself with the cluestick. It's not that they don't want the logo changed (they don't). It's that they don't want the logo or name used on anything that hasn't been vetted by Mozilla - so no security updates for you unless they come from Mozilla. This is particularly a problem if a distribution wants to support older versions of the program by backporting fixes rather than updating the package. Other distributions will have to deal with this problem too if Mozilla doesn't change their stance; Debian is just the first to face it.
That said, a well-designed trademark policy (like Debian's) provides a mark that they explicitly recommend that you to use if you modify the product, which does not throw their own branding out the window. The Mozilla.com people simply haven't thought that through sufficiently.
Bruce
Bruce Perens.
Trademark law requires that the name be different enough to not cause confusion. As a result, FreeFox or FireFaux or any of the other similar ones might cause problems and just result in Debian having to rename it yet again.
"I may not have morals, but I have standards."
Oh, wait!
1) I've made this "humping weasel" logo (see https://wiki.ubuntu.com/IceWeaselIcon ) and I'm not involved in the development of Debian, Ubuntu, Firefox or IceWeasel in any kind.
2) This logo is NOT the official logo of IceWeasel! It is still up for discussion what the logo will look like.
3) There is NO political statement intended. This logo was made "just for fun". It is based on the original, not animated and completely inoffensive logo of Mark Riedesel (see the wiki).
So, don't blame the people behind Debian, Ubuntu or IceWeasel. They are simply not involved in the creation of this "funny" logo. Blame me instead. Thanks.
Except trolls nobody seems to disagree with you in that thread (when I started writing this post), so i feel I need to explain why you arguments are bogus instead of modding you down.
Since every package modifies the base system, the only way to prove that a package will work is to test it against every possible package configuration available!
Each package is independant with others except with its own dependencies. Those dependencies happen to be linear : for P packages, nP total dependencies, with n an integer independant of the number of packages. It's the job of a Debian package maintainer to check the dependencies are fulfilled and working : each maintener just needs to check n dependencies. That's part of the job people are doing to move a new version of a package from sid (unstable) to testing. I will add that chain of dependencies are irrelevant : if A needs B and B needs C, maintainer of A checks his program working against B, while it's the duty of the maintainer of B to check his program works with C. The only cross-dependancies are for kernel-mode code, that is only drivers.
In fact it's better than the windows "DLL hell", because the state of the system is known (for a Debian stable for exemple), while on MS Windows... Your program has been developped and tested for DirectX 8, will it work with DirectX 9 ? No way to know what the state of the user's system will be (and no developper includes DirectX as a static dependency, it isn't even possible). It's no wonder that most OSes are using repositories (Linux, BSD, QNX, BeOS with software wallet, that one being somewhat different IIRC).
any software that's not in the repository is not well supported by the packaging system.
You seem to ignore that there isn't a single central repository. Want Opera browser ? Just add http://deb.opera.com/opera/ in your repositories list, and you get the official binary matching your version of Debian, checked against it.
If something is not clear, feel free to ask for details.
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
*doh* You're right. I didn't even think about plugins and sure enough, I've got a plugin that turns submit buttons yellow if the form is secure. Since that's the only issue I've found while using Firefox so I don't see what Mozilla could be complaining about.
Unfortunately, Bon Echo and Deer Park are version names. We need non-version-dependent stable branding that unifies modified versions and the official firefox into a consistent branding program. The Official Debian CD (really the only place Debian uses their official-use logo) and their unofficial-use logo seem to do this well.
Thanks
Bruce
Bruce Perens.
This is a feature. A slow release cycle is a benefit in many environments - a high-end teaching environment, for example, absolutely can not be deploying a functionality-changing upgrade more than once a year, because you'll screw over all the work currently in progress if you do it in the middle of the academic year. A lot of businesses also need to keep disruption to a minimum, which means infrequent upgrades - any high end sysadmin will tell you that "upgrade" is synonymous with "downtime and more trouble tickets than usual". A distribution which forces you to upgrade often in order to maintain support is entirely inappropriate in such an environment.
You are obviously not the target audience. Please hurry up and use something else so that we don't have to listen to you gripe about it any more. If you're using the wrong tool for the job then that's your own fault. (Quite what job requires using only software that is less than 6 months old is unclear, but I'll just assume that you do have a reason and aren't simply crazy)
Actually, the Debian version of Firefox contains various patches which the Mozilla people aren't happy about (including security patches--Debian wants to keep versions in Debian/Stable secure, but Mozilla wants everyone to use the latest version). Iceweasel is a fork that doesn't intend to diverge very far from the original codebase, but a fork it is nonetheless.
Look out!
It's a little more than that. Debian maintains a stable branch, and when firefox (or any other app) releases a new version, debian stable sticks with the old one, but backports any security and stability work. This appears to be what the mozilla folks have a problem with - when they release a new version they want everyone to move to it. Debian just doesn't work that way though. They maintain their stable version independently, and do a damn good job of it - security work gets backported, but new features (statistically suspect to introduce new issues that won't be discovered or fixed for awhile) don't. Mozilla says they can't use the name and logo, so they're going to call it iceweasel now. But other than that, it's really a continuation of what they've *always* done with this and every other upstream package. You can call it a fork if you want, but if it's a fork it's a parrallel fork and it's not starting now, it's been going for many years.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.