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.

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

Hosting projects on Github: ban on storing font binaries #148

Open
m4rc1e opened this issue Oct 8, 2024 · 4 comments
Open

Hosting projects on Github: ban on storing font binaries #148

m4rc1e opened this issue Oct 8, 2024 · 4 comments

Comments

@m4rc1e
Copy link
Contributor

m4rc1e commented Oct 8, 2024

This topic comes up every year in discussions so it is worthy of an issue. It can be added to https://googlefonts.github.io/gf-guide/hosting#commits-manage-progress-and-track-changes

Several of us believe we shouldn't be storing font binaries in the repo for the following reasons:

  • The binaries may have been built from earlier commits or not the correct build chain
  • They take up a lot of space
  • They're not diffable.

Font binaries should be stored in tagged releases instead.

@davelab6
Copy link
Member

davelab6 commented Oct 8, 2024

@chrissimpkins wdyt

@rsheeter
Copy link
Contributor

rsheeter commented Oct 8, 2024

This seems consistent with the guiding principle to "treat fonts like software", provides a clear hook to build SBOMs, ... makes sense to me.

@vv-monsalve
Copy link
Contributor

Duplicated, see #43

@chrissimpkins
Copy link
Member

Agree with this. What needs to change in our tooling to support it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants