Font Awesome (http://fontawesome.io/) is now used by https://drupal.org/project/fontawesome, where its license page mention as below:

Font Awesome is fully open source and is GPL compatible. You can use it for commercial projects, open source projects, or really just about whatever you want.

On the other hand, my new project twbs_fontawesome.make would like to download it from official site with latest version manually.

May someone give a hand for adding the following Regex into whitelist?

^http://fontawesome\.io/assets/.+$

Comments

kreynen’s picture

Status: Needs review » Postponed (maintainer needs more info)

Despite what the developers behind font-awesome say, SIL OFL 1.1 is NOT GPL compatible. It can be packaged with GPL, but that is not the same as GPL compatible.

I responded to https://github.com/FortAwesome/Font-Awesome/issues/1124

The OFL issue doesn't even get solved with #1449452: Give installation profiles/distributions GPLv3+ license as option for packaged downloads and would likely require a specific exception.

hswong3i’s picture

@kreynen: thank you for your prompt reply and let's see if Font Awesome able to modify their license as OFL + GPLv2+FE, if so it should be suitable for our current GPLv2 ONLY policy on drupal.org (but for sure that this take time...)

hswong3i’s picture

Status: Postponed (maintainer needs more info) » Needs review

Thanks for WordPress which may give us some hints for solving font licensing issue (http://make.wordpress.org/themes/guidelines/guidelines-resources/):

The GNU Foundation and the Fedora Project maintain lists of acceptable licenses for use with GPL (see also: this list).

Which highlight GNU Foundation link as reference (http://www.gnu.org/licenses/license-list.html#Fonts):

SIL Open Font License 1.1: The Open Font License (including its original release, version 1.0) is a free copyleft license for fonts. Its only unusual requirement is that fonts be distributed with some computer program, rather than alone. Since a simple Hello World program will satisfy the requirement, it is harmless. Neither we nor SIL recommend the use of this license for anything other than fonts.

And also highlight Fedora Project link as reference (http://fedoraproject.org/wiki/Legal_considerations_for_fonts#Approved_fo...):

Preferred License: Nowadays, to avoid the license proliferation mess which is just as problematic in the free/libre/open ecosystem as in the software one, the Fedora project joins other free/libre/open actors, and recommends new font projects choose the OFL, and existing projects consider relicensing.

Long story short, I would like to recommend approve following font licenses to be included into drupal.org as reference as that of WordPress:

  • Arphic Public License (Arphic)
  • Baekmuk License (Baekmuk)
  • Bitstream Vera License (Bitstream Vera)
  • GNU GPL (with font exception) (GPL)
  • GUST e-Foundry Font License/LaTeX Project Public License (LPPL)
  • IPA Font License (IPA)
  • Liberation Font License (Liberation)
  • LaTeX Project Public License (LPPL)
  • mplus Font License (mplus)
  • ParaType Font License (PTFL)
  • SIL Open Font License (OFL)
  • STIX Fonts User License (STIX)
  • Ubuntu Font License (UFL)
  • Wadalab Fonts License (Wadalab)
  • XANO Mincho Font License (XANO)

Any idea?

kreynen’s picture

Status: Needs review » Postponed (maintainer needs more info)

PLEASE don't post the same information on every related issue. This whitelist request will not be approved until OFL licenses are allowed since they are not GPL compatible. If there is a change on #2139273: Allow GPL Friendly Font Licenses, we'll approve the request. Until then this will remain postponed.

avpaderno’s picture

Assigned: hswong3i » Unassigned
Status: Postponed (maintainer needs more info) » Postponed
kreynen’s picture

We are making another push for the DA to change the Drupal.org git policy. Please take a few minutes and add comment supporting #2919135: Update /git-repository-usage-policy to allow "GPL friendly" licensed non-code assets.

gabriel.nunez’s picture

Any workaround for this issue? Thanks for the answer!

kreynen’s picture

Status: Postponed » Fixed

@gabriel.nunez Great timing. The Drupal.org Git Policy was recently updated by the DA to allow for GPL friendly licenses for non-code assets like fonts. I've added https://www.drupal.org/node/2930279

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.