Industrial Hemp Harvesting Machine (fiber): Unterschied zwischen den Versionen

Neueste Überarbeitung vom 27. April 2023, 10:54 Uhr

File Sharing and Workflow (Hardware)

@@ Zeile 1: / Zeile 1: @@
-I am going to add just a few notes here about the sharing of files and workflow to start with. <br>
+[[File Sharing and Workflow (Hardware)]]
-What motivates me to do this in the first place is the impression that, while the workflow tools <br>
-for software development are neatly realized and broadly used thanks to platforms like github, <br>
-the workflow tools for hardware projects, although they exist ([https://opentoolchain.org/ Open Toolchain Foundation]),<br>
-a platform that would allow a combined use of these tools and a seamless bidirectional data flow is <br>
-not quite there yet, or at least not in the open-source environment. <br>
-For example in gitlab I cannot preview images in large tile format, meaning that I have to open the <br>
+===Evolution der Blücher===
-file in order to see what is inside. If I wanted to download this file I can not do it from the file <br>
+#[https://youtu.be/GBtD1irbsr8 Ein-Trommel Blücher Prototyp/Labormaschine] <br>
-list but I also have to open the file or choose to download the whole "directory" which translates <br>
+#[https://youtu.be/A4CAPZ7KAtM Zwei-Trommel Blücher 02 Prototyp] <br>
-into a high data volume and a higher associated use of energy for its traffic. Another way is the <br>
+#[https://youtu.be/J6jhyJNDN2A Zwei-Trommel Blücher 02 auf Traktor mit Rückfahreinrichtung] <br>
-cloning and pull-push request approach, but for that I need to install some software on my computer. <br>
+#[https://youtu.be/EgHOhyGH-ww Hanfernte Zwei-Trommel Blücher 02 auf Neuholland Fahrgestell und Fahrwerk] <br>
-The jargon used in platforms like github makes things even less user-friendly since the average Joe  <br>
-(Otto Normalverbraucher) or Jane whose contact with the digital world is limited to that of a user for<br>
-practical purposes (saving files or surfing the web) might find this jargon somewhat abstract. In my <br>
-computer a folder is a folder and I thing is not a wild guess to assert that most people associate a folder <br>
-with some type of container. In GitLab a folder is called a directory, I personally know that a directory <br>
-is equivalent to a folder because I learned to use DOS over 20 years ago otherwise the first idea that <br>
-comes to mind is a phone directory. <br>
-Although the use and functions of GitLab are very well documented like is the case of the [https://docs.gitlab.com/ee/topics/git/terminology.html GitLab Terminology] <br>
-here one needs to ask the following question: Who wants to participate in the making of a copy of a <br>
-harvesting machine? or Who wants to participate in the making of a personal Loom for woven textiles? or <br>
-Who wants to
-[[https://wiki.opensourceecology.de/Git]]
-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

Industrial Hemp Harvesting Machine (fiber): Unterschied zwischen den Versionen

Neueste Überarbeitung vom 27. April 2023, 10:54 Uhr

Evolution der Blücher

Navigationsmenü

Suche