Hi,
The Debian fonts team got a request[1] to package OpenBaskerville for
Debian GNU/Linux (and therefore Ubuntu).
While looking at this request I found some issues with OpenBaskerville.
I am hoping you are able to rectify these issues:
Your git repository doesn't contain any tags apart from the initial
import tag. Please tag the 0.0.53 version and push it to github.
You aren't providing any source tarball, just a ZIP file with pre-built
fonts. For each release, please create a source tarball, containing the
generated FONTLOG.txt but not the generated fonts since in general
source tarballs do not contain VCS history or pre-built fonts.
You are dual-licensing the font under the GPLv3, but without the font
exception. I guess users who prefer the GPLv3 would also like to have
the font exception[2][3][4]. I strongly suggest that you relicense the
font to add the font exception since it means people will not get scared
that their documents could suddenly become GPLed if using the font.
The current git master of OpenBaskerville gives these fontlint warnings:
Validation OpenBaskerville ...Failed
Self Intersecting Glyph
Wrong Direction
Missing Points at Extrema
We would like to invite you to join the Debian Fonts Task Force to help
collaboratively maintain the Debian/Ubuntu packaging for OpenBaskerville
and for other fonts already in Debian.
Since you are an upstream you might like to read our guide[7] for
creating a Debian-friendly project, with links lots of guides to
creating distribution-friendly projects.
1. http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/2012-January/009332.html
2. http://en.wikipedia.org/wiki/GPL_font_exception
3. http://www.gnu.org/licenses/gpl-faq.html#FontException
4. http://www.fsf.org/blogs/licensing/20050425novalis
5. http://pkg-fonts.alioth.debian.org/
6. http://wiki.debian.org/UpstreamGuide
--
bye,
pabs
http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part