Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Fetching contributors…

Cannot retrieve contributors at this time

143 lines (96 sloc) 5.658 kB
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" id="mysite-com">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Git Process for Publishers</title>
<link rel="stylesheet" type="text/css" media="screen, print" href="css/reset.css" />
<link rel="stylesheet" type="text/css" media="screen" href="css/screen.css" />
<!--[if lte IE 7>
<link rel="stylesheet" type="text/css" media="screen" href="css/screen-ie.css" />
<![endif]-->
<link rel="stylesheet" type="text/css" media="print" href="css/print.css" />
<link rel="stylesheet" href="css/screen.css" type="text/css" media="screen" title="style" charset="utf-8"/>
<!--REMOVE COMMENT TAGS TO USE FACEBOOK SHARE METADATA:-->
<!--
<meta name="title" content="Match this with the content of the title tag above." />
<meta name="description" content="A short description of this page." />
<link rel="image_src" href="http://example.com/media/share/thumbnail.jpg" />
-->
<!--REMOVE COMMENT TAGS TO USE FAVICON LINKS:-->
<!--
<link rel="icon" href="" type="image/png" />
<link rel="shortcut icon" href="" type="image/png" />
-->
<script type="text/javascript" src="js/mootools/mootools-core.js"></script>
<script type="text/javascript" src="js/site.js"></script>
</head>
<body>
<div id="page">
<div id="header">
<h1><a href="http://gewga.ws/git-for-writers/" rel="home">Git Process for Publishers</a></h1>
<p class="tagline">
A guide to version tracking, revision, and collaboration for open-source writing.
</p>
<ul class="accessibility">
<li><a href="#navigation">Jump to Navigation</a></li>
<li><a href="#content">Jump to Content</a></li>
</ul>
</div>
<ul id="sub-navigation">
<li><a href="process.htm">Start</a></li>
<li><a href="process2.htm">Edit</a></li>
<li><a href="process3.htm">Produce</a></li>
</ul>
<div id="content">
<br>
<br>
<img src="media/img/timeline_2.png" alt="timeline_2" height="591" width="513" />
<div id="main">
<h4>Legend for Chart</h4>
<p><b>Step 4.</b>
The managing editor will also need to look out for Pull requests from each of the writers after they have Pushed changes to the fork of the project. Recall that changes are Pushed from the working repository to the master repository by the writers.</p>
<p>It is up to the managing editor to Pull the changes from all the writers into the master repository and review any messages accompanying these requests.</p>
<p>Writers may also find that they want to Push experimental content to fellow writers on an arbitrary branch in order to share content prior to making Pull requests of the managing editor. (Recall: “git pull” and “git push” commands.)</p>
<p>Writers: remember to type in a message with your Pull request.</p>
<p><b>Step 5.</b>
The managing editor will need to review all the files. The command “git log” will allow him or her to see the list of changes to the project.</p>
<p>First time Pull requests will need to be fetched with the “git remote add” command. Afterwards, the managing editor need only fetch again.</p>
<p>Decisions will need to be made whether to merge the changed done. Don’t forget to use the “$ git checkout master” command.</p>
<p>Also, the managing editor at this stage should be opening the “index.htm” file in a web browser to view how the content is displaying. Edits to the XHTML and CSS files may need to be made at this stage to save time later.</p>
<p><b>Step 6.</b>
The chapters will now be ready for a “2nd Pass” review and revisions. Each writer will need to Fork the latest repository to their Github account.</p>
<p>Practice with the “git log” command to show lists of commits and thus review the history of the changes.</p>
<p>Each writer will repeat steps described above as they review their current chapter, along with edits made from other writers and the managing editor. The “2nd Pass” of this project involves much more than simply revising your chapter. Indeed, it involves working on your chapter along with the chapters others have submitted. Writers will continually need to Push their content and then make Pull requests of the managing editor.</p>
</div>
<div id="supporting">
</div>
</div>
<ul id="navigation">
<li><a href="index.htm">Home</a></li>
<li><a href="resources.htm">Resources</a></li>
<li><a href="process.htm">Process</a></li>
<li><a href="about.htm">About</a></li>
</ul>
<div id="footer">
<p class="copyright">
© 2010 by Gewgaws Lab. Some rights reserved. Content licensed under a
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/">
Creative Commons Attribution-Share Alike 3.0 United States License
</a>.
<a class="cc-badge" rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/">
<img alt="Creative Commons License" src="http://i.creativecommons.org/l/by-sa/3.0/us/88x31.png" />
</a>
</p>
<p class="project-information">
<a href="http://github.com/gewgaws/git-for-writers">Git for Writers repository</a>
hosted at <a href="http://github.com">GitHub</a>. Learn <a href="participate.htm">how to
contribute</a> to Git for Writers.
</p>
<ul class="validators">
<li><a href="http://validator.w3.org/check?uri=referer" title="Validate this page's XHTML">XHTML</a></li>
<li><a href="http://jigsaw.w3.org/css-validator/check/referer" title="Validate this page's CSS">CSS</a></li>
</ul>
</div>
</div>
</body>
</html>
Jump to Line
Something went wrong with that request. Please try again.