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

Aktuelle Version vom 27. April 2023, 10:54 Uhr

File Sharing and Workflow (Hardware)

@@ Zeile 1: / Zeile 1: @@
-==File Sharing and Workflow==
+[[File Sharing and Workflow (Hardware)]]
-I am going to add a few short notes here about my thoughts related to file sharing and workflow to start with. <br>
-What motivates me to do this 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>
-===GitLab===
+===Evolution der Blücher===
-*als review Werkzeug, wenn alle die Information und die Dateien schon klassifiziert und aufgeräumt sind :)
+#[https://youtu.be/GBtD1irbsr8 Ein-Trommel Blücher Prototyp/Labormaschine] <br>
-*als workflow werkzeug für die reverse engineering/development Verfahren :/ <br>
+#[https://youtu.be/A4CAPZ7KAtM Zwei-Trommel Blücher 02 Prototyp] <br>
+#[https://youtu.be/J6jhyJNDN2A Zwei-Trommel Blücher 02 auf Traktor mit Rückfahreinrichtung] <br>
-For example in GitLab I cannot preview images in large tile format, meaning that I have to open the <br>
+#[https://youtu.be/EgHOhyGH-ww Hanfernte Zwei-Trommel Blücher 02 auf Neuholland Fahrgestell und Fahrwerk] <br>
-file in order to see what is inside. If I wanted to download this file I can not do it from the file <br>
-list but I also have to open the file or choose to download the whole "directory" which translates <br>
-into a high data volume and a higher associated use of energy for its traffic. Another way is the <br>
-cloning and pull-push request approach but for that, I need to install some software on my computer. <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 think 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 once used 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, for example, GitLab are very well documented as it is the case for the <br>
-[https://docs.gitlab.com/ee/topics/git/terminology.html GitLab Terminology]. Here one needs to pose the following question: Who wants to participate <br>
-in the making of a copy of a harvesting machine? or Who wants to participate in the making of a personal <br>
-Loom for woven textiles? or, in short, Who are the target users/collaborators for such a project? And yet, <br>
-despite the answer, the reality is that the whole process should be as easy as possible if I want to maximize <br>
-the participation level. A person whose interest is limited to the creation and formatting of text might find <br>
-the task of writing such text in a wiki just too daunting and might choose to walk away. <br>
-===wiki + Nextcloud===
-*A wiki is a very useful container to tip ideas into at the start of a project. A good starting <br>
-point that, later on, can be easily organized into a structural part of the project. The wiki <br>
-facilitates the organization and the search for specifics within a project and within itself <br>
-thanks to the use of links, embedded views and files, and other types of special formatting.<br>
-A properly formatted wiki can be a very user-friendly entry point to the project for all users <br>
-especially in combination with a text-poor file system.
-*Nextcloud provides quite a comfortable coworking environment although I have noticed that the
-functionality, associated software, and file accessibility depend on how the platform is configured by
-the party offering the service and the permissions given to the participants. For example, it seems
-that the configuration is most flexible when Nextcloud is being hosted in a local server for
-internal use like in a company. There, permissions can be given on at least two levels: view and
-download only, and view, download, move, delete, etc.
-===wiki + Dropbox===
-<gallery widths="300" heights="240" perrow="2>
-Datei:Workflow basic.drawio.png|gerahmt|links|Possible workflow for the project
-</gallery>
-===The OHO Approach===
-[https://wiki.opensourceecology.de/Git Git]
-[https://gitlab.opensourceecology.de/verein/koordination/dokumentation/tools-for-documentation#documentation-creation Werkzeuge für Dokumentation]
-one way folder (diode folders) for sharing raw information <br>
-two way folders (with some restrictions e.g. deleting of files) for retrieving processed information<br>
-at least three different access levels would be necessary<br>
-admin/distributor --- contributor/developer --- user

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

Aktuelle Version vom 27. April 2023, 10:54 Uhr

Evolution der Blücher

Navigationsmenü

Suche