Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Jonas Smedegaard]

Quoting Thomas Goirand (2015-09-09 09:20:51)
> On 09/08/2015 10:11 AM, Jonas Smedegaard wrote:
>> Quoting Thomas Goirand (2015-09-08 09:28:15)
>>> On 09/07/2015 08:42 PM, Jonas Smedegaard wrote:
> If you wish to drop the generation of fonts-roboto from the 
> fonts-android package, then good.

 I think the better approach is to keep the fonts-roboto package, have 
 your package exclude fonts, depend on the fonts-roboto package, and 
 symlink font files from there as needed.
>>>
>>> I don't think so. The fonts-roboto package currently only provides 
>>> .tff files, which are useless for the web. The sources aren't the 
>>> same.
>> 
>> What are the sources, then?
>
> git://github.com/choffmeister/roboto-fontface-bower.git

I do understand that above is the URL you intend to fetch the project 
from.  What I meant by my question is what is the source of the material 
you are fetching?  What is the source of WOFF and SVG files?

Or do you mean to tell me that WOFF and SVG files are _forks_ of the TTF 
files, developed independently onwards?  I find that highly unlikely.


> Do you think I should join the pkg-fonts group to maintain these 
> fonts under the group?

 We can always use more helping hands in the fonts team :-)

 But if your focus is on OpenStack then perhaps just coordinate with 
 the font team on tuning the fonts-roboto package to provide what is 
 needed for reuse with OpenStack - i.e. those web representations of 
 the font (CSS/Sass/Less sounds like OpenStack-specific glue so 
 probably makes best sense to package separately).
>>>
>>> They aren't OpenStack specific, it's just modern Javascript stuff, 
>>> which can be reused by any project.
>> 
>> Great - then suggest maintainers of the existing package to adopt 
>> those tiny files too.
>
> Well, we just talked about dropping the generation of fonts-roboto 
> from the old source package... Or am I missing something?

Yes, that is a suggestion you brought up, but which it seems neither 
Vasudev nor me agree with.

Looking at recent posts from Paul Wise on the fonts team list, it seems 
he also do not agree with packaging fonts known to have their actual 
source - even if our tools to rebuild from that canonical source is 
currently lacking in Debian.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Thomas Goirand]

On 09/08/2015 10:11 AM, Jonas Smedegaard wrote:
> Quoting Thomas Goirand (2015-09-08 09:28:15)
>> On 09/07/2015 08:42 PM, Jonas Smedegaard wrote:
 If you wish to drop the generation of fonts-roboto from the 
 fonts-android package, then good.
>>>
>>> I think the better approach is to keep the fonts-roboto package, have 
>>> your package exclude fonts, depend on the fonts-roboto package, and 
>>> symlink font files from there as needed.
>>
>> I don't think so. The fonts-roboto package currently only provides 
>> .tff files, which are useless for the web. The sources aren't the 
>> same.
> 
> What are the sources, then?

git://github.com/choffmeister/roboto-fontface-bower.git

 Do you think I should join the pkg-fonts group to maintain these 
 fonts under the group?
>>>
>>> We can always use more helping hands in the fonts team :-)
>>>
>>> But if your focus is on OpenStack then perhaps just coordinate with 
>>> the font team on tuning the fonts-roboto package to provide what is 
>>> needed for reuse with OpenStack - i.e. those web representations of 
>>> the font (CSS/Sass/Less sounds like OpenStack-specific glue so 
>>> probably makes best sense to package separately).
>>
>> They aren't OpenStack specific, it's just modern Javascript stuff, 
>> which can be reused by any project.
> 
> Great - then suggest maintainers of the existing package to adopt those 
> tiny files too.

Well, we just talked about dropping the generation of fonts-roboto from
the old source package... Or am I missing something?

Cheers,

Thomas

Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Jonas Smedegaard]

Quoting Thomas Goirand (2015-09-08 09:28:15)
> On 09/07/2015 08:42 PM, Jonas Smedegaard wrote:
>>> If you wish to drop the generation of fonts-roboto from the 
>>> fonts-android package, then good.
>>
>> I think the better approach is to keep the fonts-roboto package, have 
>> your package exclude fonts, depend on the fonts-roboto package, and 
>> symlink font files from there as needed.
>
> I don't think so. The fonts-roboto package currently only provides 
> .tff files, which are useless for the web. The sources aren't the 
> same.

What are the sources, then?


> Also, I don't think the FTP masters would like to have even more 
> binary packages and dependencies. If these can be avoided, it's best 
> for the Debian infrastructure, I heard.

It is not best for Debian to track actual upstreams as our upstream 
rather than redistributors.


>>> Do you think I should join the pkg-fonts group to maintain these 
>>> fonts under the group?
>>
>> We can always use more helping hands in the fonts team :-)
>>
>> But if your focus is on OpenStack then perhaps just coordinate with 
>> the font team on tuning the fonts-roboto package to provide what is 
>> needed for reuse with OpenStack - i.e. those web representations of 
>> the font (CSS/Sass/Less sounds like OpenStack-specific glue so 
>> probably makes best sense to package separately).
>
> They aren't OpenStack specific, it's just modern Javascript stuff, 
> which can be reused by any project.

Great - then suggest maintainers of the existing package to adopt those 
tiny files too.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Thomas Goirand]

On 09/07/2015 08:42 PM, Jonas Smedegaard wrote:
>> If you wish to drop the generation of fonts-roboto from the 
>> fonts-android package, then good.
> 
> I think the better approach is to keep the fonts-roboto package, have 
> your package exclude fonts, depend on the fonts-roboto package, and 
> symlink font files from there as needed.

I don't think so. The fonts-roboto package currently only provides .tff
files, which are useless for the web. The sources aren't the same.

Also, I don't think the FTP masters would like to have even more binary
packages and dependencies. If these can be avoided, it's best for the
Debian infrastructure, I heard.

>> Do you think I should join the pkg-fonts group to maintain these fonts 
>> under the group?
> 
> We can always use more helping hands in the fonts team :-)
> 
> But if your focus is on OpenStack then perhaps just coordinate with the 
> font team on tuning the fonts-roboto package to provide what is needed 
> for reuse with OpenStack - i.e. those web representations of the font 
> (CSS/Sass/Less sounds like OpenStack-specific glue so probably makes 
> best sense to package separately).

They aren't OpenStack specific, it's just modern Javascript stuff, which
can be reused by any project.

Cheers,

Thomas Goirand (zigo)

Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Vasudev Kamath]

Thomas Goirand  writes:

> On 09/08/2015 05:33 AM, Vasudev Kamath wrote:
>> Yeah, we already have couple of webfonts under pkg-fonts team, though
>> there is no strict policy yet we place them under /usr/share/fonts/type
>> where type can be ttf, otf, woff, svg eot, etc. And less/css/scss files
>> under /usr/share/fonts-package.
>
> That's what I've done in my package, indeed.
OK.
>
>> As an example you can have a look at fonts-font-awesome source, which is also
>> used by owncloud.
>
> Horizon also uses the fonts-font-awesome package, so it's nice to have
> such consistency indeed.
>
> Now, to move on, what's next action? Remove the fonts-roboto generation
> from the android fonts source? Or ... ? The thing is, I really *need*
> this webfont and the CSS, otherwise Horizon will be quite broken.

I'm not quite sure, as said earlier roboto-fontface-bower is not the
original roboto upstream so splitting it from the fonts-android doesn't
sound right.

OTOH to build fonts-roboto from actual upstream it needs a lot of work
as most of tools needed are not/not up-to-date in Debian.

May be for now it should be fine to ship fonts-roboto-fontface as not to
block the bringing of Horizon into Debian. May be once we have proper
fonts-roboto in proper shape in Debian we can generate required woff/svg
files and make roboto-fontface-bower only ship required less/css/scss
files.

Bug#798261: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font

[Jonas Smedegaard]

Hi Thomas,

Quoting Thomas Goirand (2015-09-07 19:53:16)
> On 09/07/2015 07:00 PM, Vasudev Kamath wrote:
>> We already have a fonts-roboto which is part of fonts-android
>> source. ¹. There was a discussion on pkg-fonts-devel IIRC previously to
>> split roboto fonts to its own package as code was moved to its own git
>> repository. Sorry but I don't exactly have the link to discussion, so
>> ccing fonts team.
>> 
>> I wonder if we can eliminate duplicate and have a single font. 
>> 
>> ¹ https://packages.debian.org/unstable/fonts-roboto

> That's not the same package. The one that I'm packaging has not only 
> the .ttf files, but also .eot, .svg, .woff and .woff2, plus .css, 
> .less and .scss files. All of these are needed for the web developers.

Seems the project you want to package only includes the Roboto font, but 
is not the canonical source of the font: Package description begins with 
"A simple package providing the Roboto fontface."


> If you wish to drop the generation of fonts-roboto from the 
> fonts-android package, then good.

I think the better approach is to keep the fonts-roboto package, have 
your package exclude fonts, depend on the fonts-roboto package, and 
symlink font files from there as needed.


> Do you think I should join the pkg-fonts group to maintain these fonts 
> under the group?

We can always use more helping hands in the fonts team :-)

But if your focus is on OpenStack then perhaps just coordinate with the 
font team on tuning the fonts-roboto package to provide what is needed 
for reuse with OpenStack - i.e. those web representations of the font 
(CSS/Sass/Less sounds like OpenStack-specific glue so probably makes 
best sense to package separately).


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature