Core Dev Process
OSE's collaborative product development workflow for onsite participants involves an ability to document and share information digitally, while engaging in prototyping and digital fabrication.
A common workflow involves hand drawings inserted into Google Slides presentations, CAD designs in FreeCAD 101, and subsequent extraction of CNC torch table cut files or 3D print files using Cura. For CNC cut files, see Generating CNC Torch Table Cut Files. For 3D printing, use Lulzbot Cura Appimage, and upload code to the Universal Controller via the Arduino Environment software. We run all CNC machines with Marlin and RAMPS - up to dozens of axes of a screw machine based on the Universal Axis.
To collaborate, start a Work Log, get a FreeCAD Badge, and request a Time Log.
Learn how to embed Google Slides using the {{Subst:Embed}} template, or just embed manually. Use Presentation Template to start working docs on everything - assuming that you have a greater vision for your work. The key is to include the Edit link so you and others can edit, and to open permissions for open global editing in the Google Slides. Then use hyperlinks in your Work Log linking to other wiki pages, thereby augmenting your brain with the wiki as an organizing platform. Learn how to Embed YouTube and to use the Gallery feature of the wiki for creating Part Libraries. Learn basic editing with Kdenlive.
To organize all work, use the {{dev+|Project Name}} template - but substitute that into the wiki page by using {{subst:dev+|Project Name}}. Note the difference between these 2 routes by clicking edit. Then you're ready to become immortal. Understand that to collaborate seamlessly with a large, global team - you need to upload to the internet as soon as you have any file or picture: if it's not on the wiki on your log, it doesn't exist. To organize information, understand that the Taxonomy includes the 50 GVCS Machines, 500 Modules, and any other dev projects. The development follows a standard product development protocol (see OSPD) nomenclature, and we use Concurrent Engineering with the Second Toyota Paradox, which fits well with a swarm-based, Module-Based Design process with a lego-like Construction Set Approach - reified with Extreme Manufacturing.
Version history is an important topic. The wiki already has a built-in file version history, and our process is to 'upload new versions of a file' to build on prior work. External repositories may be used for files >1MB, which is the wiki limit.
Does this make sense?