Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
145 lines (97 sloc) 6.81 KB
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
<html xmlns="" xml:lang="en" lang="en" id="mysite-com">
<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" />
<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"/>
<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="" />
<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>
<script type="text/javascript" src="js/lightbox.js"></script>
<div id="page">
<div id="header">
<h1><a href="" rel="home">Git Process for Publishers</a></h1>
<p class="tagline">
A guide to version tracking, revision, and collaboration for open-source writing.
<ul class="accessibility">
<li><a href="#navigation">Jump to Navigation</a></li>
<li><a href="#content">Jump to Content</a></li>
<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>
<div id="content">
<p>In this scenario, an exercise is presented that will help pull together the concepts discussed previously and allow for hands-on practice. This project will be most effective if a team of four is formed. For the purposes of this exercise, you will need to refer to previous documentation, for greater detail specific to github commands. </p>
<p>Although there is strong support for non-linear development within Git (through rapid branching and merging), this project follows a rather straightforward publishing process with a managing editor controlling the various stages of editorial development.</p>
<img src="media/img/timeline_1.png" alt="timeline_1" height="610" width="534" />
<div id="main">
<h4>Legend for Chart</h4>
<p><b>Step 1.</b> The scenario involves a linear publishing process whereby a team of four individuals are working independently to create an XHTML tagged text file that any writer could download and start writing within. A CSS template file also needs to be created so that none of the writers worry about the formatting of their content.</p>
<p>A managing editor will oversee the entire process, but will rely on the three writers to create the content and load into the Git repository within Github. The editor will then pull the content down once he/she approves of the version for others to access and further revise.</p>
<p>Three chapters need to be written by separate writers: 1) a marketing chapter with a purpose narrative on why writers should utilize the Git technology and their proposed workflow process; 2) a chapter on GitHub commands specific to the publishing industry; and, 3) a setting up Github (for the first steps in the process) which include basic navigational commands: push/pull, merge, revision history, etc.</p>
<p>As the chapters are written, marketing’s narrative is validated and the commands are practiced by the writers as they execute what they write. The writers and managing editor will ensure quality control is in place as they work through the process of creating this content for electronic publication.</p>
<p><b>Step 2</b>.
Each individual participating in this exercise should setup a Github account. Follow the instructions within the tutorial and access Github at Don’t forget to provide Git your name and email address so your future commits are associated with your name and email.</p>
<p>The project member selected to be the managing editor should create the Github repository. In addition to the tutorial within the documentation preceding this project, another reference is the Git Community Book: The open Git resource pulled together by the whole community, “Chapter 3: Basic Usage” for information on how to obtain a Git repository. </p>
<p>You can either clone a repository or initialize one. Don’t forget to review “git init” and “git clone” commands.</p>
<p><b>Step 3. </b>Once everyone has an account and a repository is in place. Each writer should begin researching and writing their topic. An XHTML tagged text file should be used by everyone within the project to ensure common format structure.</p>
<p>Each writer will need to commit their changes to the repository in at least two intervals: referred to as 1st Pass and 2nd Pass in the graphic accompanying these instructions.</p>
<p>Writers will either add a new file or stage an existing file and then commit (“git add” versus “git commit” commands). Refer to earlier documentation for instructions on how to Stage a file for a Commit.</p>
<div id="supporting">
<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>
<div id="footer">
<p class="copyright">
© 2010 by Gewgaws Lab. Some rights reserved. Content licensed under a
<a rel="license" href="">
Creative Commons Attribution-Share Alike 3.0 United States License
<a class="cc-badge" rel="license" href="">
<img alt="Creative Commons License" src="" />
<p class="project-information">
<a href="">Git for Writers repository</a>
hosted at <a href="">GitHub</a>. Learn <a href="participate.htm">how to
contribute</a> to Git for Writers.
<ul class="validators">
<li><a href="" title="Validate this page's XHTML">XHTML</a></li>
<li><a href="" title="Validate this page's CSS">CSS</a></li>