Pull Requests in Open Source Hardware - Revision history

Marcin: /* Comments */

2018-04-14T16:10:38Z

Comments

← Older revision		Revision as of 16:10, 14 April 2018
Line 4:		Line 4:
	*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/		*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/
	*Important study of how Git originated - including the origin of the term git - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]		*Important study of how Git originated - including the origin of the term git - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]
	*Study the function of the patch (UNIX) program - https://en.wikipedia.org/wiki/Patch_(Unix). What is the equivalent of Diff-Patch for hardware? It is a program that works with FreeCAD to extract the Diff, then apply the Patch. What is the advantage of using Patch instead of making changes manually? It saves time over fixing lines of code, especially if there are many lines of code to be changed.		*Study the function of the patch (UNIX) program - https://en.wikipedia.org/wiki/Patch_(Unix). What is the equivalent of Diff-Patch for hardware? It is a program that works with FreeCAD to extract the Diff, then apply the Patch. What is the advantage of using Patch instead of making changes manually? It saves time over fixing lines of code, especially if there are many lines of code to be changed. But in hardware - currently the only way to apply a patch is to replace the old file with a new file - unless some new software is created that allows patches to be applied in different way.

	=Applications=		=Applications=
	*It may be worthwhile to use Github for CAD files and STL files.		*It may be worthwhile to use Github for CAD files and STL files.

Marcin: /* Comments */

2018-04-14T15:48:17Z

Comments

← Older revision		Revision as of 15:48, 14 April 2018
Line 4:		Line 4:
	*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/		*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/
	*Important study of how Git originated - including the origin of the term git - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]		*Important study of how Git originated - including the origin of the term git - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]
			*Study the function of the patch (UNIX) program - https://en.wikipedia.org/wiki/Patch_(Unix). What is the equivalent of Diff-Patch for hardware? It is a program that works with FreeCAD to extract the Diff, then apply the Patch. What is the advantage of using Patch instead of making changes manually? It saves time over fixing lines of code, especially if there are many lines of code to be changed.

			=Applications=
			*It may be worthwhile to use Github for CAD files and STL files.

Marcin: /* Comments */

2018-04-14T15:31:04Z

Comments

← Older revision		Revision as of 15:31, 14 April 2018
Line 3:		Line 3:
	=Comments=		=Comments=
	*Good comment in the article from practitioners - Thom Randolph - http://thomr.com/		*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]		*Important study of how Git originated - including the origin of the term git - definite lessons for OSE - [https://www.infoworld.com/article/2669670/operating-systems/after-controversy--torvalds-begins-work-on--git-.html]

Marcin at 15:28, 14 April 2018

2018-04-14T15:28:59Z

← Older revision		Revision as of 15:28, 14 April 2018
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.		*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]

Marcin: Created page with "*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/#c..."

2018-04-14T15:03:01Z

Created page with "*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/#c..."

New page

*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.