Re: [Pkg-fonts-devel] About the licensing of URW Garamond No. 8

2010-04-15 Thread Nicolas Spalinger
Walter Landry wrote:
> Nicolas Spalinger  wrote:
>> Paul Wise wrote:
>>> I'd strongly suggest to indicate a preference about which license you
>>> would like them to choose.
>>>
>>> I would personally suggest standard FLOSS licenses like BSD,
>>> MIT/Expat, ISC, GPL + font exception etc. If those aren't acceptable,
>>> the SIL OFL is a DFSG-compatible compromise between font foundry needs
>>> and free software principles.
>> Yes! Recommending a particular validated model and explaining how it
>> will benefit both upstream and downstream is much more effective in such
>> advocacy efforts.
>>
>> I recommend you take advantage of the campaign resources on
>> http://www.unifont.org/go_for_ofl/
>>
>> Considering how various key Libre Software communities have given their
>> support to the licensing model it seems like a good model to recommend
>> to URW. Various fonts in CTAN are under OFL as well.
> 
> Please do not recommend the OFL.  Legally requiring a name change is
> unfriendly and subject to abuse.  Not allowing a font to be sold by
> itself is a useless countermeasure.  It is GPL-incompatible to boot.
> As someone who just recently needed a GPL compatible font, it was
> quite annoying trying to find one.


Hi Walter,

There are obviously varying needs and preferences (prejudices?) along
the licensing spectrum but IMHO your reply is very reductive.

At the end of the day upstreams make up their own mind about how they
license their own creation but allow me to explain the reasoning of the
OFL model a bit more:

A name change mechanism has already been in use for a while for many of
the core fonts the distros have included in their main archive and use
by default (Dejavu or Liberation for example): the OFL simply makes that
mechanism generic, re-usable and understandable by actual upstream
authors of fonts and downstream modifiers. Similar ways of requiring a
derivative branch not to advertise itself as the upstream branch or the
trunk exist in other community-recognized licenses.

The BundlingWhenSelling clause has been researched, validated and
recognized as a useful nexus between the concerns of the actual
producers of font software and the free/libre software values. It is
social signalling that font designers want and that still satisfy the
DFSG. You may see it as useless from your perspective but many others
can guarantee you that various libre/open fonts would never have been
released by their authors without this clause.

For the GPL imcompatibility, fonts are much more useful aggregated to
rather than "merged" with existing software, possible incompatibility
with existing software licenses is not a problem. See
http://www.gnu.org/licenses/license-list.html#Fonts

You say you needed a "GPL-compatible font" but what does that mean? I
assume you needed a font to bundle with when distributing a piece of
software under GPL, right? OFL-ed fonts explicitely allow anyone to
bundle. (even with restricted software).  OTOH you probably want to
recommend an external open font instead by adding a package dependency.

BTW one of the goals we have in the Debian fonts team is to work to
reduce the big duplication of fonts in various packages in our archive:
there is no absolute need for every single piece of software to ship
with its very own set of fonts... Sometimes it does but from a Debian
perspective IMHO a dependency is much nicer. There is a lintian check
for this too.

I do agree that GPL-compatibility is great and very desirable but fonts
have a different set of requirements corresponding to their special
status and usage scenarios.

BTW when looking for fonts for your own use you may find the review that
we run weekly on the Debian fonts team useful:
http://pkg-fonts.alioth.debian.org/review/

> Also, I found this page
> 
>   http://openfontlibrary.org/wiki/Font_Licensing
> 
> which mentions
> 
>   Despite the problems, the base 35 PostScript fonts donated by URW++
>   to (originally) the Ghostscript project are licensed under the GPL,
>   with an exception similar to the font above.
> 
> But then I found this page
> 
>   http://www.advogato.org/person/raph/diary/257.html
> 
> which says
> 
>   By the way, URW did not donate these fonts under the GPL out of
>   their own hearts. Artifex paid good money for them, and donated them
>   out of a mix of self-interest and altruism.
> 
> So is may be easy to change the license to GPL, but you may want to
> talk to Artifex, not URW++.

TTBOMK previous attempts have not been successful, anybody is welcome to
try again.

Also IIRC GUST had derived a branch under LPPL. You may want to search
for that. I don't recall the exact details.

I'll simply point out that Raph Levien (whose diary you link to) has
chosen to release some of his own fonts under the OFL finding that the
model makes sense.

BTW have you read through the thread in -devel that he linked to?

>> Hopefully your advocacy efforts will benefit many people throughout the
>> communities. Thanks! Let us 

Re: [Pkg-fonts-devel] About the licensing of URW Garamond No. 8

2010-04-15 Thread Nicolas Spalinger
[...]

>> But then I found this page
>>
>>   http://www.advogato.org/person/raph/diary/257.html
>>
>> which says
>>
>>   By the way, URW did not donate these fonts under the GPL out of
>>   their own hearts. Artifex paid good money for them, and donated them
>>   out of a mix of self-interest and altruism.
>>
>> So is may be easy to change the license to GPL, but you may want to
>> talk to Artifex, not URW++.
> 
> TTBOMK previous attempts have not been successful, anybody is welcome to
> try again.
> 
> Also IIRC GUST had derived a branch under LPPL. You may want to search
> for that. I don't recall the exact details.

Looks like the following page on tug.org has more details:
http://www.tug.org/fonts/

Cheers,


-- 
Nicolas Spalinger, NRSI volunteer
Debian/Ubuntu font teams / OpenFontLibrary
http://planet.open-fonts.org


-- 
To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bc718ed.8020...@sil.org



Re: [Pkg-fonts-devel] About the licensing of URW Garamond No. 8

2010-04-15 Thread Walter Landry
Nicolas Spalinger  wrote:
> Hi Walter,
> 
> There are obviously varying needs and preferences (prejudices?) along
> the licensing spectrum but IMHO your reply is very reductive.
> 
> At the end of the day upstreams make up their own mind about how they
> license their own creation but allow me to explain the reasoning of the
> OFL model a bit more:

I understand that many font designers want to put in annoying license
terms.  I really do understand that.  In fact, there are many regular
software developers who want to put in annoying license terms for
their programs.  Debian does not encourage these annoying terms for
programs, and Debian should not encourage annoying terms for fonts
either.


> For the GPL imcompatibility, fonts are much more useful aggregated to
> rather than "merged" with existing software, possible incompatibility
> with existing software licenses is not a problem. See
> http://www.gnu.org/licenses/license-list.html#Fonts

I was using the rendered fonts as art.  In the US, rendered fonts are
not copyrightable (as far as I understand).  Elsewhere, the situation
is unclear.

> You say you needed a "GPL-compatible font" but what does that mean? I
> assume you needed a font to bundle with when distributing a piece of
> software under GPL, right? OFL-ed fonts explicitely allow anyone to
> bundle. (even with restricted software).  OTOH you probably want to
> recommend an external open font instead by adding a package dependency.

You have it backwards.  It is the GPL which does not allow
incorporating OFL-ed fonts.

> BTW one of the goals we have in the Debian fonts team is to work to
> reduce the big duplication of fonts in various packages in our archive:
> there is no absolute need for every single piece of software to ship
> with its very own set of fonts... Sometimes it does but from a Debian
> perspective IMHO a dependency is much nicer. There is a lintian check
> for this too.
> 
> I do agree that GPL-compatibility is great and very desirable but fonts
> have a different set of requirements corresponding to their special
> status and usage scenarios.

Somehow, everyone thinks that they are special and therefore they
deserve annoying license terms.  We had this debate on debian-legal
before with the LPPL.  I am sure we will have it again.  I still have
zero sympathy for this view.

> BTW when looking for fonts for your own use you may find the review that
> we run weekly on the Debian fonts team useful:
> http://pkg-fonts.alioth.debian.org/review/

Interesting.  Thank you.

>> Also, I found this page
>> 
>>   http://openfontlibrary.org/wiki/Font_Licensing
>> 
>> which mentions
>> 
>>   Despite the problems, the base 35 PostScript fonts donated by URW++
>>   to (originally) the Ghostscript project are licensed under the GPL,
>>   with an exception similar to the font above.
>> 
>> But then I found this page
>> 
>>   http://www.advogato.org/person/raph/diary/257.html
>> 
>> which says
>> 
>>   By the way, URW did not donate these fonts under the GPL out of
>>   their own hearts. Artifex paid good money for them, and donated them
>>   out of a mix of self-interest and altruism.
>> 
>> So is may be easy to change the license to GPL, but you may want to
>> talk to Artifex, not URW++.
> 
> TTBOMK previous attempts have not been successful, anybody is welcome to
> try again.
> 
> Also IIRC GUST had derived a branch under LPPL. You may want to search
> for that. I don't recall the exact details.
> 
> I'll simply point out that Raph Levien (whose diary you link to) has
> chosen to release some of his own fonts under the OFL finding that the
> model makes sense.
> 
> BTW have you read through the thread in -devel that he linked to?

I just did.  I am not sure what point you are trying to make, though.
Ian Zimmerman asked the same question I did:

  Ben> "How am I going to deal with it when someone changes my font to
  Ben> something ugly and it reflects poorly on my skills as a
  Ben> fontographer?"

  How is this at all different from the same question asked about
  program source code?

  In that context, it is part of the rationale for the Q license,
  AFAIK.  (Redistribution only as original source + patches).

(http://lists.debian.org/debian-devel/2002/08/msg00881.html)

I have not seen anyone in Debian suggest the Q license for the longest
time.  It would really suck if everyone used the Q license.

>>> Hopefully your advocacy efforts will benefit many people throughout the
>>> communities. Thanks! Let us know how it goes.
>>>
>>> BTW the font exception for the GPL still has a bunch of unsolved
>>> problems. I wouldn't recommend that.
>> 
>> What are these problems?  A quick search yielded nothing.
> 
> The fact that the exception may disappear downstream

Why is this a problem?

> and that as an end-user it's tricky to know if you can safely embedd
> or not without suddenly having to satisfy the GPL requirements for
> your whole document or not...

Maybe I am arguing with the wrong person