Resuming project maintenance

amotl commented 9 months ago

Hi there,

this project was a bit dormant for some time, and now that some kind people are approaching us [^1], we think it is time to resume maintenance. Every kind of contribution will be much welcome.

With kind regards, Andreas.

[^1]: Getting HaniMandl out into the world

amotl commented 9 months ago

Over at @RolandRust's repository, we reached out to him, and invited him to the community forum. Thanks for joining!

https://github.com/RolandRust/HaniMandlWroom/issues/2

amotl commented 9 months ago

Problem

By adding hardware and design files, and images, the repository size became unbearably large.

Writing objects: 100% (78/78), 22.05 MiB | 1.23 MiB/s, done.

Improvement

The situation has been significantly improved now.

$ time git clone https://github.com/hiveeyes/hanimandl
Cloning into 'hanimandl'...
remote: Enumerating objects: 602, done.
remote: Counting objects: 100% (467/467), done.
remote: Compressing objects: 100% (245/245), done.
remote: Total 602 (delta 222), reused 453 (delta 214), pack-reused 135
Receiving objects: 100% (602/602), 673.36 KiB | 4.18 MiB/s, done.
Resolving deltas: 100% (311/311), done.

real    0m0.862s
user    0m0.098s
sys 0m0.098s

Breaking changes

To improve that, we had to rewrite project/repository history, in order to properly prune all huge artefacts from the repository and its history. We used bfg for the job.

bfg --delete-folders historic_copy-fb-group_imkerei-technik-eigenbau .
bfg --delete-folders parts-3d-printing .
bfg --delete-folders wiring-fritzing .
bfg --delete-files hani-mandl.bin .

This means you will need to destroy your clones, and fetch new ones.

Thanks for your understanding about this procedure. It had to happen at one day or another.

New location for hardware content

The folder layout has been improved, and the relevant content is now using a separate repository, called hanimandl-hardware.

hiveeyes / hanimandl