Bug#380294: msttcorefonts-tahoma?

2006-10-28 Thread Conrad Knauer

On 14 Oct 2006 Thijs Kinkhorst <[EMAIL PROTECTED]> wrote:

"My problem with this patch specifically is that it codes a special
exception for that font, and that the package for that font is more than
10 times (!) larger than the average sizes of the others."

Would it solve the problem to spin this off to a new package, say
msttcorefonts-tahoma, and have it recommended by msttcorefonts?

CK


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#354622: Using Firefox as the app name without official branding is still a trademark violation

2006-10-01 Thread Conrad Knauer

On 10/1/06, Eric Dorland <[EMAIL PROTECTED]> wrote:


> http://www.mozilla.org/foundation/trademarks/community-edition-policy.html
>
> One of the permitted changes is "Porting the software to different operating 
systems"

I'm not sure that's what that clause really means, but one easy
example is backported security fixes. Another is just regular bug
fixes that aren't in the official releases for whatever reason.


Personally I would say that Debian packages with extra security and
bug fixes would 'exceed the quality' of the official Mozilla packages
and thus be a good example of what Community Editions are about:


> "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."


CK


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#354622: Using Firefox as the app name without official branding is still a trademark violation

2006-09-28 Thread Conrad Knauer

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]



Bug#354622: Using Firefox as the app name without official branding is still a trademark violation

2006-09-27 Thread Conrad Knauer

Steve Langasek wrote: "it seems that ultimately, the only acceptable
solution to Debian would unfortunately be to stop using the firefox
name altogether.  So I'm hoping we can find a middle ground
somewhere."

As I understand it, the problem is that Mozilla wants Debian to stop
calling it Firefox unless they agree to license the trademark, but
Debian doesn't want to do that because it violates DFSG 8, that a
'license must not be specific to Debian'.

Well how about this: the Mozilla draft policy on its trademarks in
"Community Edition" versions
of its products is here:

http://www.mozilla.org/foundation/trademarks/community-edition-policy.html

and that applies to any group, not just Debian.  Could Debian rename
"Firefox" to "Firefox Community Edition"?  Since its just a draft
(version 0.8), could Mozilla perhaps make the community edition policy
more explicitly friendly to the DFSG in a future version?

e.g.: Could "Community Edition" be generally abbreviated within the
program or better yet, only explicitly mentioned in the "About
Firefox" window?  Could a Firefox name be allowed so long as it
included the term "Community Edition" somewhere in it, such as
"Firefox DFSG Community Edition" or "Firefox Debian Community
Edition"? :)

Apologies if someone somewhere has suggested this before; I use Ubuntu
and I am only now learning about this :)

Sincerely,
Conrad Knauer


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]