Why Github is Important for Book Publishing

Eric Hellman, Go To Hellman, Jan 26, 2015
Commentary by Stephen Downes
files/images/forks.png

Something like Github could be important for book publishing. But the documentation is needlessly opaque and the applications take you back to the days of typing commands in terminal windows. In addition to a diagram without lables we get explanations like the following: "Someone working on a project will first create a 'feature branch', a copy of the repository that adds a feature or fixes a bug. When the new feature has been tested and is working, the changes will be 'committed'. Each set of changes with be given an identifier and a message explaining what has been changed." Now if you don't already understand these concepts, these sentences will not help you. And this is the simple explanation (I read the official documentation and it's a long explanation of how it's different from Subversion). I've never found a clear and non-technical description of Git or GitHub (I believe they're separate things, but who knows?) nor an easy-to-use application. Just me? Maybe. But the difficulty of understanding Git makes me really sympathetic with people who have difficulty adapting to tech.

Views: 0 today, 139 total (since January 1, 2017).[Direct Link]