Github vs Wiki

Github is popular in software, but it is not designed for hardware mainly because every single replication, unless it's part of core manufacturing - is effectively a fork. On memory issues alone, Github fails the basic requirement of documenting everything effectively outside of the main trunk.

Wikis are much more suited - because as databases, they can be reused easily.

Most importantly, the learning curve for Githib is prohibitive compared to the wiki, if public product development is desired.

Nonetheless, Github is useful for 3D CAD, electronic design, software, CAM files - while the remaining 16 in the Development_Spreadsheet_Template#Simple_Template are best served by wikis, and remaining 36 of 40 of the Development_Spreadsheet_Template#Extended_Development_Template are best served by wikis. This makes Github useful for 10-20% of OSE workflow. However, this does not include the Enterprise aspect - such that realistically - Github may be about 5-10% of the OSE workflow.

Pro

• ease of distribution
• version control methods allow for many feature
  • Recovery of lost versions
  • tracking history
• Ease of use
  • files are just dropped into a directory, and that is committed to the repository.
• Wiki's become fragmented - it is very difficult to track what is the latest version of a project.
  • GIT is self organizing in some ways. Wiki organization requires standard operating procedures and diligence.

Con

• Does not allow realtime document editability, which is done in Google Docs in wiki
• Does not use internal hypertext
• MicroSoft owns GitHub now.
• A CAD drawing and the BOM are not software code - it is hard to DIF and merge multiple commits from multiple people.
• the document needs to be brought down from google docs and now is a local spreadsheet file
  • Really wondering how we resolve merges on multiple commits. with wiki file history, there is a continuous genealogy of uploads.