I'm relatively new to version control and for git itself (rather than github, which I've not used yet) I found this to be a really nice introduction/tutorial:
http://git-scm.com/book/en/Getting-Started
Dan
________________________________
From: CF-metadata [mailto:cf-metadata-bounces at cgd.ucar.edu] On Behalf Of John Graybeal
Sent: 01 October 2014 21:02
To: Chris Barker
Cc: CF Metadata List
Subject: Re: [CF-metadata] Proposals for Versioning ... and Github
Chris B, this was a terrific recap, and the NDP interactive cheatsheet was cool once I got the idea of clicking on something. <doh!> (The escape a git mess, step-by-step<
http://justinhileman.info/article/git-pretty/git-pretty.png> was also fun!) I recommend reading some other guide first before looking too long at those cheatsheet details though -- it's a bit obscure.
I liked "Introduction to distributed version control with git", by Mark Longair -- a good combination of explanations of how git is different, and some basic tutorials.
http://cleanercode.com/introduction-to-git-talk/introduction-to-git.pdf
Your point that conversational participation doesn't require git/github expertise is key. And for me, having the option to build that conversation around documented, 'in-line' changes to text is a big plus, from two angles:
-- exploring a single conceptual change across all the affected components at once, and
-- exploring the history of a part of the text, across all its past and proposed changes,
Doing either of these from a single, linked, browseable context, without having to find and compare document versions and email threads, is a big win.
John
On Oct 1, 2014, at 10:50, Chris Barker <chris.barker at noaa.gov<mailto:chris.barker at noaa.gov>> wrote:
On Tue, Sep 30, 2014 at 9:38 AM, Christopher Duncombe Rae - NOAA Affiliate <christopher.duncombe.rae at noaa.gov<mailto:christopher.duncombe.rae at noaa.gov>> wrote:
Yes, github provides opportunity for comment and questions through the issues and pull requests.
In short, an "issue" is much like a ticket in TRAC -- someone can start a new one, and then a discussion thread follows -- it can eventually be "resolved" one way or another.
a "pull request" is what you initiate when you have changed something in the repository (in this case, edited the document), and you want yur change to be incorporated into the main version. When one of these is initiated, the managers of the project can simply merge that change in -- unlikely -- or can start a thread of conversation about the changes -- usually leading to some editing and updated before the change is brought in -- or not.
The discussions of both issues and pull requests can be linked to email -- so that participants can reply to an email, and have their reply added to the discussion thread on gitHub.
Probably you want to start with the github bootcamp,
https://help.github.com/categories/54/articles.
This looks like a good start.
This also has links to other resources for git and github. If you are not too familiar with git, I have found the NDP interactive cheatsheet<
http://ndpsoftware.com/git-cheatsheet.html> an extremely valuable resource, although there are a lot of git tutorials and cheatsheets out there.
Note that in this case, one could participate in the process without knowing any thign about git at all -- particularly if you are mostly raising issues and participating in discussions initiated by others, and working on a project started by someone else.
So while git itself has a pretty difficult learning curve, that shouldn't be a barier to entry for this project.
-Chris (different Chris...)
Chris
On Tue, Sep 30, 2014 at 9:51 AM, Nan Galbraith <ngalbraith at whoi.edu<mailto:ngalbraith at whoi.edu>> wrote:
I agree, it's time for a webinar, unless we can manage a meeting,
preferably in the south of France. Following these threads is becoming
difficult.
I've had only a little experience with github; although I think trac has
worked really well for issues in CF-1, it does seem like the changes in
CF-2 will be so substantial that we'll need github, or something like it.
I'm hoping it provides the ability to ask questions and make comments - I
don't necessarily want to be editing the main document - and has an
email notification/interface built in.
If anyone can recommend a good github tutorial, please pass it along.
Thanks - Nan
On 9/23/14 5:16 PM, Signell, Richard wrote:
Jonathan,
I wonder if we might have a webinar to demonstrate/talk about the
concepts we envision here. We've done a lot of typing, but I get with
30 min together online I bet we could end up with consensus.
-Rich
--
*******************************************************
* Nan Galbraith (508) 289-2444<tel:%28508%29%20289-2444> *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 *
*******************************************************
_______________________________________________
CF-metadata mailing list
CF-metadata at cgd.ucar.edu<mailto:CF-metadata at cgd.ucar.edu>
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
--
--
=======================================================================
Dr. Christopher M. Duncombe Rae c<mailto:deirdre.byrne at noaa.gov>hristopher.duncombe.rae at noaa.gov<mailto:hristopher.duncombe.rae at noaa.gov>
Oceanographer / Data Scientist
IOOS/NOAA, Suite 1225, 1100 Wayne Avenue, Silver Spring, MD 20910, USA
Tel: +1-301-427-2450<tel:%2B1-301-427-2450> Fax: +1-301-427-2073<tel:%2B1-301-427-2073>
_______________________________________________
CF-metadata mailing list
CF-metadata at cgd.ucar.edu<mailto:CF-metadata at cgd.ucar.edu>
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov<mailto:Chris.Barker at noaa.gov>
_______________________________________________
CF-metadata mailing list
CF-metadata at cgd.ucar.edu<mailto:CF-metadata at cgd.ucar.edu>
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20141002/ca4b9e47/attachment-0001.html>
Received on Thu Oct 02 2014 - 02:47:37 BST
