- Open Source Ecology Germany (OSEG) is prototyping a zinc-air fuel-cell/battery whose design knowledge is only one-third documented in public wikis and git repos, with the rest trapped in paper notes and one engineer’s memory—highlighting the persistent documentation deficit in open-hardware projects.  
- Engineers in the channel argued that mechanical designers avoid git mainly because of cultural/educational barriers, not technical ones; they need GUI-driven “File → Commit” workflows rather than command-line tools.  
- FreeCAD and OpenSCAD are the mandated CAD packages inside OSEG; FreeCAD files are ZIP archives of text, so the ReZipDoc tool (https://github.com/hoijui/ReZipDoc) transparently compresses/uncompresses them on git check-in/out, while a companion PNG-inflate utility (https://github.com/rayrobdod/png-inflate/) makes binary PNGs delta-compressible via git’s “clean” and “smudge” filters.  
- The DIN 3105 open-hardware standard (gitlab.com/OSEGermany/OHS) is authored in Markdown but must be round-tripped through Word for DIN reviewers; outdated copies on Nextcloud caused confusion, underscoring the need for better cross-linking and CI-generated technical drawings and thumbnails.  
- A decentralized certification model for open hardware was proposed: anyone can become a certifier, and trust accrues through demonstrated quality, with the expectation that good community practice will eventually pressure industry adoption.  
- Bruno Postle’s 2003 draft suggests turning the entire filesystem into a version-control layer that auto-commits every change, providing “infinite undo” without explicit VCS use; selective rules would be required to avoid performance hits from indiscriminate commits.  
- Participants criticized the resource bloat of modern web-based editors (e.g., Atom using ~200 MB on disk and 500 MB RAM) and the trend of re-implementing features inside every application instead of leveraging higher-quality external tools like Inkscape or GIMP.