Closed Bug 1261445 Opened 4 years ago Closed 4 years ago
Clarify license information for gsubtest font testing tools
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.57 Safari/537.36 Steps to reproduce: Downloading the gsubtest font testing files and trying to adapt them to use them in Chrome testing for font-variant-caps support. https://dxr.mozilla.org/mozilla-central/source/layout/reftests/fonts/gsubtest Actual results: Unclear what license the generator script, and what license the actual output font files are. Expected results: Please clarify whether the script is MPL, and whether the font file is SIL? Thanks!
Component: Untriaged → Layout: Text
Product: Firefox → Core
Similarly, could you please clarify the license of the test files in: https://dxr.mozilla.org/mozilla-central/source/layout/reftests/font-features/ as well?
Most or all of these files were added by John Daggett in bug 549861 and others.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yeah, the first batch were added in this commit (no bug number unfortunately, but it looks like John wrote the script): https://hg.mozilla.org/mozilla-central/rev/0788ea9dbee0 I think John might be inactive/less-active as a contributor currently (so I'm not sure he'll see the needinfo), but he was working full-time on Mozilla at the time of that commit (2012) so we can safely assume that commit should be considered MPL-licensed.
...or right, this test code is actually public domain, as khuey said in IRC, and as gerv's blog post made explicit here (since the commit that added them, linked in comment 3, was before 2014 which is the cutoff date that Gerv mentions): http://blog.gerv.net/2014/09/licensing-policy-change-tests-are-now-public-domain/
Thanks everyone for the quick help!
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
(Yeah, this test code is all public domain by default, per gerv's post -- since, even though it's from before 2014, it was contributed by John Daggett who was a Mozilla employee at the time.)
You need to log in before you can comment on or make changes to this bug.