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

Source files #609

Open
wayne-shih opened this issue Nov 26, 2024 · 2 comments
Open

Source files #609

wayne-shih opened this issue Nov 26, 2024 · 2 comments

Comments

@wayne-shih
Copy link
Contributor

Hi there,

With the source files (ufo, glyphs, ...) removed from this repo earlier this year due to overall repo file sizes (#452, #554, #560)... It was hinted the source files will be uploaded as release artifacts (/assets) instead.

Doesn't seem like this practice was followed? Is there any plans for the source files to be released again and where would be the best place to discover them?

@NightFurySL2001
Copy link

NightFurySL2001 commented Dec 10, 2024

It would be helpful if the source files can be released to match Google Fonts requirements (https://googlefonts.github.io/gf-guide/production.html#scalable-font-production) and for modifications, especially given the bad design and multiple errors for SC in #612 and #613 .

@yanone
Copy link

yanone commented Feb 21, 2025

Hello.

Users of Google Fonts are also asking about Plex sources.

While I want to emphasize that IBM is under no obligation to follow the GF Guide (as linked above) to make sources available, and neither does the OFL license (sadly) require sources to be available, your own README does explicitly state open-sourcedness, which is currently false:
The IBM Plex typeface is an open-source project available for download and various uses following the Open Font License (OFL).

In the spirit of open-source software, I kindly ask to make the sources available in the repository again. If repository size is indeed a limiting factor, please consider breaking the repository apart into individual repositories, one for each family, as is the common habit. You may employ your own repository template to reduce friction in keeping dependencies up-to-date.

Thank you.

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

3 participants