Mike Hommey wrote: "Some changes applied to the debian packages don't fall in the community edition authorized changes, and there's no way we want not to apply these."
If you're referring to the list of "permitted" changes in Community Editions on http://www.mozilla.org/foundation/trademarks/community-edition-policy.html I would really like to see what specifically you think would not be allowed. One of the permitted changes is "Porting the software to different operating systems" which would imply a degree of OS-integration (e.g. updates through apt-get vs. individual programs downloading updates for themselves). Also, it says below the list: "It is very important that Community Editions of Firefox and Thunderbird meet (or exceed) the quality level people have come to associate with Mozilla Firefox and Mozilla Thunderbird. We need to ensure this, but we don't want to get in people's way. So, we are taking an optimistic approach." I would like someone from Mozilla (Mike? :) and someone from Debian (Eric? :) to sit down and determine if there is actually anything stopping the Debian FF release from being called "Firefox Community Edition Debian" right now... If it can, problem solved :) If not, can the Mozilla CE Policy be altered slightly to accomodate Debian and/or can Debian move some of the changes into a separate package? Eric Dorland wrote: "If we call the package firefox, aren't we claiming that's what it is and hence infringing the mark? I'd certainly like to keep the package name unchanged, but also if it is left as firefox and the browser presents itself as "Foobar" might that not confuse users? If the CE idea actually has merit, changing the package to "firefox-community-edition-debian" or "firefox-ced" or some such (with an accompanying change in the description) shouldn't be too confusing to users; plus you could always have a metapackage "firefox" that installs the CE version. CK -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
