why storing binary font files in the repo?

[anthrotype]

Hi,
I just stumbled on this project. Please excuse me if this has been discussed before already.
I was a bit surprised to see you are recommending to store the built TTF/OTF files inside the git repository along with the rest of the other source files, especially since this is being proposed as a "standard way to organize Open Source font project source files".
The font files are not "sources" but the result of building from the sources (e.g. UFO, .glyphs, etc.). Git is for version control of source files. It can't produce meaningful diffs for binary blobs, and their presence can cause merge conflicts, and makes the size of the repository become bigger and bigger.
Any binary built artifacts could be best stored using Github Releases, which reference the state of the source files with a precise git tag.
If one really wanted to store source files in binary format (e.g. photos) one would use things like https://git-lfs.github.com/. But fonts here are really not the sources, but the product.

[raphaelbastide]

Most visitors will first try to find the binaries in the repo by using directly the download button. But UFR is supposed to be a set of good practices so I agree with your comment. It can be even more clear for potential users to see a download link to the last release in the readme, and even more accessible than Github hidden download button.. This can be there by default. The downside is that this link will have to be adapted to non GitHub websites (e.g. Gitlab).