jonas at jones.dk
Tue Apr 4 07:54:05 UTC 2017
Quoting James GK (2017-03-31 17:50:47)
> >> Are you looking at https://github.com/googlei18n/noto-source or
> >> something else?
> >> My understanding, from the presentation of the maintainers at AtypI
> >> Warsaw, and from watching the project for a while, that they do
> >> have a working python-based toolchain that they are constantly
> >> refining via a continuous integration system.
> > Thanks for the pointers.
> > I have not yet looked closely - and when I do I might very likely
> > learn that upstream indeed uses purely Free tools in their workflow
> > - in which case the issue with fonts-noto is "only" the lack of
> > _packaging_ those tools. Which is a real issue.
> Hi, I joined this mailing list a couple of weeks ago very specifically
> in the hopes of helping with packaging for Noto and Roboto. Please let
> me know if there's anything that can be done better (reach out to me
> personally if that's more appropriate / this is too much noise for the
> whole list).
Thanks a lot. Great!
I generally¹ find it most appropriate to discuss here on the list.
Help identifying (i.e. filing as RFP or ITP bugreport), packaging and
maintaining said packages for tools used upstream is very helpful.
Latter parts involves knowledge on Debian packaging - so if new to
Debian you will need guidance from others at first - but anyone should
be able to do the initial part by following the short instructions at
To ease coordination among us here in the fonts team - if some do the
initial part and want others to do the latter - I recommend to create a
wiki page similar to https://wiki.debian.org/FreedomBox/LeavingTheCloud
- that should also be doable by anyone without intimate knowledge on
Most importantly we need packaged all tools used upstream for automated
build process when upstream releases fonts.
Ideally we additionally have packaged also any and all tools used in
other parts of upstream design process - be it interactive editing
tools, visualization tools for proof and/or promotion, continuous
integration scripts, etc. - even if we will not mimick upstream parts of
that for the specific font, the availability of such tools are obviously
helpful for anyone wanting to use Debian for upstream font design work.
> My understanding of your concern is admittedly low but I can say that
> all the dependencies of the Noto tools can be pulled down either
> directly from Github or from the Python package index. Any further
> improvements with packaging I'd be happy to help with.
Great. Please file RFP or ITP bugs for each of those dependencies, and
consider setup a wiki page to help us get an overview of how they relate
- to understand the urgency (or not) for each of them in order for
Debian to properly comply with our self-imposed rules.
¹ A classic antipattern is to discuss discretely to avoid being a
nuisance to others: As long as you are on-topic for a mailinglist you
are *not* a nuisance - all following the list are interested! Feel free
to contact me discretely - but then please explicitly mention why you
feel we need discretion, as each secrecy you impose on me is a burden: I
do want to respect your privacy and I do appreciate your confiding with
me, but ony when truly needed.
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
More information about the Pkg-fonts-devel