Industrial Hemp Harvesting Machine (fiber)

I am going to add just a few notes here about the sharing of files and workflow to start with.
What motivates me to do this in the first place is the impression that, while the workflow tools
for software development are neatly realized and broadly used thanks to platforms like github,
the workflow tools for hardware projects, although they exist ([https://opentoolchain.org/ Open
Toolchain Foundation]), a platform that would allow a combined use of these tools and a seamless bidirectional data flow is
not quite there yet, or at least not in the open-source environment.

For example in gitlab I cannot preview images in large tile format, meaning that I have to open the
file in order to see what is inside. If I wanted to download this file I can not do it from the file
list but I also have to open the file or choose to download the whole "directory" which translates
into a high data volume and a higher associated use of energy for its traffic. The jargon used in
platforms like github makes things even less user-friendly since the average Joe (Otto Normalverbraucher)
or Jane whose contact with the digital world is limited to that of an user for practical purposes <be> (saving files or surfing the web) might find this jargon somewhat abstract. In my computer a folder
is a folder and I thing is not a wild guess to assert that most people associate a folder with some
type of container. In GitLab a folder is called a directory, I personally know that a directory is
equivalent to a folder because I learned to use DOS over 20 years ago otherwise the first idea that
comes to mind is a phone directory.

GitLab Terminology

one way folder (diode folders) for sharing raw information two way folders (with some restrictions e.g. deleting of files) for retrieving processed information at least three different access levels would be necessary admin/distributor --- contributor/developer --- user