Repository navigation
Source files #609
Description
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?
Metadata
Metadata
Assignees
Labels
No labels
Activity
NightFurySL2001 commentedon 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 commentedon 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.
BoldMonday commentedon Apr 7, 2025
AFAIK -- as external contractor I cannot speak for IBM -- repository size is indeed the problem here.
Splitting the family into separate repositories is a solution. But currently there are some package managers for IBM’s Carbon Design System that rely on this repository and rewiring that seems to be an issue. I don’t know when this will be solved.
mon-jai commentedon Apr 7, 2025
@BoldMonday It is okay to keep this repo intact. They could just release the source in a separate repo.
NightFurySL2001 commentedon Apr 8, 2025
@BoldMonday in the meantime, can the source files be shared by zipping the relevant source folder and attach in GitHub releases as stated before, while waiting for the repository size problem to resolve?
BoldMonday commentedon Apr 8, 2025
@NightFurySL2001 I don’t have the privileges to do that but can forward your suggestion.
NightFurySL2001 commentedon Apr 8, 2025
@BoldMonday That was actually what was promised by @tay1orjones in comment #554 (comment)
but was never implemented.
Palke commentedon Apr 23, 2025
Sources are now available under releases tab as artifacts. Enjoy!