The size of repository is almost 3 Gigabytes, making it very impractical to contribute offline.
I tried to clone this repository to contribute a fix, but ran out of space doing so.
This makes it more difficult for potential contributors (especially those contributing to multiple specs) to work with a local version (Git repositories are intended to be distributed), and takes more time & resources for the build pipelines to clone the repo and rebuild new versions fo the documents.
Would it be possible to host larger files somewhere else, and possibly amend / clean the history so that the repository as to facilitate cloning the specification to contribute?
The Examples/Video directory with several frames seems to be the biggest problem (722 mb).
The SolarPose demo models directory seems to be the other big culprit (345 mb).
It is likely that some of the huge size is also from the history, possibly as earlier revisions of these same files, or other huge files that were deleted but remain in the history.
I could possibly help shrinking this (as I have encountered, raised and corrected this issue in other OGC repositories before ;)), but it would require rewriting the history of the repository.
The size of repository is almost 3 Gigabytes, making it very impractical to contribute offline.
I tried to clone this repository to contribute a fix, but ran out of space doing so.
This makes it more difficult for potential contributors (especially those contributing to multiple specs) to work with a local version (Git repositories are intended to be distributed), and takes more time & resources for the build pipelines to clone the repo and rebuild new versions fo the documents.
Would it be possible to host larger files somewhere else, and possibly amend / clean the history so that the repository as to facilitate cloning the specification to contribute?
The Examples/Video directory with several frames seems to be the biggest problem (722 mb). The SolarPose demo models directory seems to be the other big culprit (345 mb). It is likely that some of the huge size is also from the history, possibly as earlier revisions of these same files, or other huge files that were deleted but remain in the history.
I could possibly help shrinking this (as I have encountered, raised and corrected this issue in other OGC repositories before ;)), but it would require rewriting the history of the repository.