Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Every family should have a known upstream repo #7121

Open
simoncozens opened this issue Dec 20, 2023 · 10 comments
Open

Every family should have a known upstream repo #7121

simoncozens opened this issue Dec 20, 2023 · 10 comments
Assignees
@simoncozens
Labels
I API / Website / Platform fonts.google.com related stuff I Request I Tools / workflow / repo
Milestone
2024 Q4

Comments

@simoncozens
Copy link
Collaborator

simoncozens commented Dec 20, 2023 •
edited
Loading

(I am using this issue as way to track and dump information.)

In order to (a) improve and update existing fonts to evolving QA standards, (b) test the fontc compiler, and (c) eventually remove binary artefacts from this repository (a very long term goal), we want to be able to rebuild every Google Fonts font from sources. And that means we need to know where the sources are! This is information we really should have anyway, but for some historical fonts, we don't.

Currently:

Out of 1382 google font families:
    721 (52%) have known and accessible upstreams
    263 appear to be based on the GFR

Out of 344 source files:

    Glyphs 2: 177 (51%)
    Glyphs 3: 126 (36%)
    designspace: 32 (9%)
    Missing Glyphs file: 4 (1%)
    Glyphs 3 package: 4 (1%)
    ufo: 1 (0%)

The fonts missing upstreams are:
@simoncozens simoncozens self-assigned this Dec 20, 2023
@davelab6
Copy link
Member

davelab6 commented Apr 3, 2024

@chrissimpkins and I are setting up the Q2 milestone with a full slate of issues, and I just discussed #7358 with @simoncozens and we agreed it would be fantastic if @eliheuer could take on the laborious legwork to make the tool Simon posted the output of above reach 100% :)

@simoncozens please unassign once the tool is part of gf-tools and ready for Eli to work with :)

@davelab6 davelab6 added this to the 2024 Q2 milestone Apr 3, 2024
@simoncozens
Copy link
Collaborator Author

The script to list known upstream status is found at https://github.com/simoncozens/gf-dashboard/blob/main/list-known-upstreams.py

@simoncozens
Copy link
Collaborator Author

Latest stats:

Out of 1657 google font families:
    1071 (64%) have known and accessible upstreams
    549 appear to be based on the GFR

Out of 646 source files:

    Glyphs 2: 282 (43%)
    Glyphs 3: 236 (36%)
    designspace: 94 (14%)
    Glyphs 3 package: 21 (3%)
    Missing Glyphs file: 11 (1%)
    ufo: 1 (0%)
    Glyphs 2 package: 1 (0%)

@chrissimpkins chrissimpkins modified the milestones: 2024 Q2, 2024 Q3 Jul 2, 2024
@chrissimpkins chrissimpkins removed the P2 label Jul 10, 2024
@miketheman miketheman mentioned this issue Aug 15, 2024
Open
@chrissimpkins chrissimpkins modified the milestones: 2024 Q3, 2024 Q4 Oct 3, 2024
@chrissimpkins
Copy link
Collaborator

@emmamarichal @vv-monsalve @m4rc1e I came across this tracker today following our discussion about upstream repository URLs

@davelab6
Copy link
Member

@cmyr and @rsheeter shared that

in the process of looking for fonts to use in testing I've come across a bunch of fonts in the collection for which we have repos that contain some source file, but no config.yaml. A list is here, if anyone is interested:

https://gist.github.com/cmyr/ed0fc3f6423273a97eca7335e96082f3

This is useful as we make progress on this, mostly next year

@n8willis
Copy link
Collaborator

How should designers update this info if they can? newscycle and dellarespira both have upstreams on Launchpad.net, for example. Old ones, which someday I do hope to revitalize, but for right now I'm just wondering how best to be helpful with that info.

@rsheeter
Copy link
Collaborator

How should designers update this info if they can?

We need a source stanza in the metadata file, for example https://github.com/google/fonts/blob/main/ofl/abeezee/METADATA.pb

In a perfect world that repository would have a gftools builder config, for example https://github.com/googlefonts/abeezee/blob/main/sources/config.yaml.

@rsheeter
Copy link
Collaborator

For context, ^ empowers our old/new compiler comparison. https://googlefonts.github.io/fontc_crater/ has results.

@n8willis
Copy link
Collaborator

For context, ^ empowers our old/new compiler comparison. https://googlefonts.github.io/fontc_crater/ has results.

At the risk of getting into spoiler territory, if it also sounds empowering to test things on SFD sources and with non-Git DVCSes, then I have some EXCITING NEWS....

@rsheeter
Copy link
Collaborator

SFD sources and with non-Git DVCSes

This is somehow my Halloween costume next year lol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@simoncozens simoncozens

Labels
I API / Website / Platform fonts.google.com related stuff I Request I Tools / workflow / repo
Projects
Google Fonts
Status: In Progress
Milestone
2024 Q4
Development

No branches or pull requests
6 participants
@simoncozens @davelab6 @n8willis @chrissimpkins @eliheuer @rsheeter