Revision as of 15:28, 14 April 2018

Github - good article on how to work pull requiests and merges with open hardware. - [1]. Key is modularity, so only parts need modification. Changes can be verified by the project leader, or the leader can even request that pull requests must be accompanied by mailing the modified hardware to the leader - to save time. Mechanics of the pull/merge process for hardware need to be documented. Does someone simply submit a code patch (OpenSCAD or FreeCAD file)? How are diffs shown in STLs? Does Github already have that capacity? If not, it should be added.

Comments

Good comment in the article from practitioners - Thom Randolph - http://thomr.com/
Important study of how Git originated - definite lessons for OSE - [2]

@@ Line 1: / Line 1: @@
 *Github - good article on how to work pull requiests and merges with open hardware. - [https://hackaday.com/2018/02/27/can-open-source-hardware-be-like-open-source-software/#comments]. Key is modularity, so only parts need modification. Changes can be verified by the project leader, or the leader can even request that pull requests must be accompanied by mailing the modified hardware to the leader - to save time. Mechanics of the pull/merge process for hardware need to be documented. Does someone simply submit a code patch (OpenSCAD or FreeCAD file)? How are diffs shown in STLs? Does Github already have that capacity? If not, it should be added.
+=Comments=
+*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/
+*Important study of how Git originated - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]