Quelltext der Seite File Sharing and Workflow (Hardware)

The following are a few short notes related to file sharing and workflow.
While the workflow tools for software development are neatly realized and broadly used thanks to platforms like GitHub,
workflow tools for hardware projects, although in existence ([https://opentoolchain.org/ Open Toolchain Foundation]),
do not seem to be integrated in any platform ─at least not in the open-source environment─ that would allow their
combined use and a seamless bidirectional data flow between project developers/participants.
During the annual meeting of OSEG in 2023, a brief comment was made about the necessity of streammlining 
the platform for the CAB reviews as to make it more serious and userfriendly. I believe this could be a good
opportunity to also consider the topic of this wiki page.

===GitLab===
*als review Werkzeug, wenn alle die Information und die Dateien schon klassifiziert und aufgeräumt sind :)
*als workflow werkzeug für die reverse engineering/development Verfahren :/ <br>

For example in GitLab I cannot preview images in large tile format, meaning that I have to open the <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>

[https://wiki.opensourceecology.de/Git Git]

===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<br> functionality, associated software, and file accessibility depend on how the platform is configured<br> 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<br> a local server for internal use like in a company. There, permissions can be given on at least two<br> levels: view and download only; or view, download, move, delete, comment, discuss etc.<br> These permissions are independent from the user having his or her own account in the system. A link<br> suffices to get access.
*:- On the other hand, with an online provider like The Good Cloud, without registering an account, only<br> downloads and viewing are enabled and there are further restrictions added, namely a mandatory<br> expiry date for the shared link to the documents and a mandatory password to access it. <br>
: ''Advantageous tools provided by Nextcloud: Files can be commented and discussions can take<br> place in an associated chat.

: Example [https://use04.thegood.cloud/s/TMXkxFTSLZSpMno The Good Cloud]
: Pass. +P{Xer4Jzx

<span style="color:#fff; background:#ff1493"> Wann wird die OSEG Nextcloud verfügbar und was für einstellungen wären für so ein Projekt möglich? </span> <br>
https://cloud.opensourceecology.de/apps/forms/xiEwEFzwkXdHBqXz <br>
https://cloud.opensourceecology.de/login <br>

===wiki + Dropbox===



===general Wiki + Folder Directory Structure===
<gallery widths="300" heights="240" perrow="2>
Datei:Workflow basic.drawio.png|gerahmt|links|Possible workflow for the project
Datei:Workflow basic 00.drawio.png|gerahmt|
</gallery>
[https://drive.google.com/file/d/1BQj12XaIn2qolEnu3BOROZAffzfLsQdL/view?usp=sharing Workflow Description]<br>
[https://drive.google.com/file/d/1Cay-fRREcdA338_k9V3uRdXJ4bejwxBy/view?usp=sharing Workflow Folders]<br>
Open with: [https://app.diagrams.net/?src=about Diagrams.net]

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

{| class="wikitable"
|+ <big>'''Ordner A_Quellgrafiken Readme'''</big>
|-
|In diesem Ordner sollten alle Bilder und Zeichnungen hingelegt werden, die Information für die CAD-Konstruktion der Teile behalten.
Zum Beispiel:
*Fotos
*Fotos mit Abmessungen
*Skizzen

Für diese Dateien wird folgendes Namensformat benutzt werden:<br>
ME_'''Bezeichnung'''.jpg/.png/...

<big>''Weiteres...''</big> <br>
:Zu diesem Ordner ist der Zugang für Kollaborateuren zu "sehen und herunterladen" eingeschränkt. Keine Dateiänderung / Dateilöschung ist möglich.
|-
|+ <big>'''Ordner B_zur_Review Readme</big>
|-
|In diesem Ordner sollten alle 3D-Modelle und technische Zeichnungen hochgeladen werden, die von den im Ordner ''A_Quellgrafiken'' abgeleitet sind.
Zum Beispiel:
*3D-Modelle ohne technische Zeichnungen
*3D-Modelle mit technische Zeichnungen
*Alleinstehende technische Zeichnungen

Die Dateien müssen mit dem selben Format als in ''A_Quellgrafiken'' benannt werden. Hier ändert sich aber ihre '''Dateiendung:<br>
ME_Bezeichnung wie in original (Ordner A).'''FCStd/...


<big>''Weiteres...''</big> <br>
:Diese Dateien werden vor Ort und in einer 3D-Assembly überprüft, bevor sie zum Ordner ''D_endgültige_Version'' verschoben sind.
:Zu diesem Ordner ist der Zugang für Kollaborateuren zu ''sehen, herunter- und hochladen"'' eingeschränkt. Keine Dateiänderung / Dateilöschung ist möglich.
|}

===The OHO Approach===

==Useful Links==

[https://gitlab.opensourceecology.de/verein/koordination/dokumentation/tools-for-documentation#documentation-creation Werkzeuge für Dokumentation]