GitHub LFS exists in a weird place for astronomy, where potential users are unlikely to hit the sweet spot of "too much data for plain GitHub, but not so much that LFS can't handle it."
The idea of including some kind of data infrastructure is good (see #443); including LFS is not the solution we're looking for.
Every account using Git Large File Storage receives 1 GiB of free storage and 1 GiB a month of free bandwidth. If the bandwidth and storage quotas are not enough, you can choose to purchase an additional quota for Git LFS.
If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth.
Hmm - it looks like this is actually not a feature anymore, but was still hanging out in the documentation. I'm proposing removal of this section as a part of #460
GitHub LFS exists in a weird place for astronomy, where potential users are unlikely to hit the sweet spot of "too much data for plain GitHub, but not so much that LFS can't handle it."
The idea of including some kind of data infrastructure is good (see #443); including LFS is not the solution we're looking for.
As an overview of caps, from the GitHub LFS docs:
And here: