Revision as of 20:57, 25 May 2018

Notes on OSE Directory Structure

In order to allow Git Clone of an entire directory, the directory must be right below the main directory like this - OpenSourceEcology/3D-Printer-OSE-Marlin
It would be nice to do OpenSourceEcology/3D-Printer/OSE-Marlin - but then OSE-Marlin is not a repository in itself - it's a part of a repository, and therefore can't take advantage of Githubs collaboration workflow (fork/merge/pull request, etc).
It is possible to set up a repo within a repo, but it is a pain to set up.
A repo looks like this - it has a Clone or Download button

Branch management, forks, pull requests, and merges can be done automatically with Github. OSE should use this capacity to manage hardware development projects with high complexity and many iterations.
STL viewing is available in GitHub since 2013 - [1]

@@ Line 2: / Line 2: @@
 =Notes on OSE Directory Structure=
 *In order to allow Git Clone of an entire directory, the directory must be right below the main directory like this - OpenSourceEcology/3D-Printer-OSE-Marlin
-*It would be nice to do OpenSourceEcology/3D-Printer/OSE-Marlin - but then OSE-Marlin would be a repo within a repo, which is a pain to set up.
+*It would be nice to do OpenSourceEcology/3D-Printer/OSE-Marlin - but then OSE-Marlin is not a repository in itself - it's a part of a repository, and therefore can't take advantage of Githubs collaboration workflow (fork/merge/pull request, etc).
-*A repo looks like this - it has a Clone or Download button -
+*It is possible to set up a repo within a repo, but it is a pain to set up.
+*A repo looks like this - it has a Clone or Download button
 [[File:repo.jpg|800px]]