This document provides an overview of Git and GitHub for source control. It discusses the advantages of distributed version control with Git over centralized systems like SVN. Key points include that Git allows for fast local operations, supports multiple workflows, and enables cheap branching and merging. The document also provides examples of basic Git commands and demonstrates how to contribute to open source projects by forking repositories on GitHub and submitting pull requests.

1. Open Source Collaboration
with Git and GitHub
SaravanaMuthu Aka CF Mitrah.
Shamelessly copied slides from other
presentations.

2. Disclaimer
I am a hardcore ColdFusion Developer
I’m not a Git expert or pro 

3. No Source Control System =

4. This is also not source control...

5. Why you need it
•Your code will break (and you won't know why)
•Your hard drive will die
•Taking latest files from FTP is pain
Why you think you don't need it and are wrong
•I work alone (you will break your own code)
•My project is small
(projects grow – Facebook used to be 5 files)

6. Centralized

7. Centralized Version Control
• Traditional version control system
– Server with database
– Clients have a working version
• Examples
– CVS
– Subversion
– Visual Source Safe
• Challenges
– Multi-developer conflicts
– Client/server communication

8. Centralized Version Control :: Cons

9. Distributed Version Control

10. Distributed Version Control
• Authoritative server by
convention only
• Every working checkout
is a repository
• Get version control
even when detached
• Backups are trivial
• Other distributed
systems include
– Mercurial
– BitKeeper
– Darcs
– Bazaar

12. I'm an egoistical bastard, and I name
all my projects after myself.
First Linux, now git.
-Linus Torvalds

16. And Now

17. Git Advantages
• Resilience
– No one repository has more data than any other
• Speed
– Very fast operations compared to other VCS (I’m looking at you CVS
and Subversion)
• Space
– Compression can be done across repository not just per file
– Minimizes local size as well as push/pull data transfers
• Simplicity
– Object model is very simple
• Large user base with robust tools

18. 1. Fast

19. Local
2. Local

20. Distributed
3. Distributed

21. 3. Cheap Branching

22. Branching

23. Any Workflow
4.Many Workflows

24. Failboat.
It’s not perfect.

25. The downsides
• Complexity
• Windows FTL
• What's an IDE? (but see egit for Eclipse, plus
Vim and Emacs support, and GUIs)
• Still frequent releases
•Cygwin – build yourself
•Ubuntu – use Git PPA

26. The Staging Area

27. Integration Manager

28. Benevolent Dictator

29. Some Commands
• Getting a Repository
– git init
– git clone
• Commits
– git add
– git commit
• Getting information
– git help
– git status
– git diff
– git log
– git show

32. Now with git goodness as well

35. 1. Working on your own projects
2. Helping/ Contribute other OSS
projects

36. Create new repository

37. After created,
Everything you should know and do

38. Setting git before using github
• Generate SSH key in git ( Local )
• $ssh-keygen -t rsa -C "somkiat_spns@xxx.com"

39. Copy data in file id_rsa.pub to github

40. Manage data with github
• $ git config --global user.name "up1"
• $ git config --global user.email somkiat_spns@xxx.com
• $ git init
• $ touch README
• $ git add README
• $ git commit -m 'first commit'
• $ git remote add origin git@github.com:up1/----
hello_tarad.git
• $ git push -u origin master

41. Manage data with github ( demo )

42. Manage data with github (demo)

43. See result at github, Work !!

44. How to Contribute
1. Fork a repository at GitHub
2. Clone and connect your local repository
3. Write tests, implement functionality
4. Commit your local changes
5. Push your changes to your fork
6. Make a pull request
7. Profit!!

45. Very good series of blog posts by a CFML developer on Git
workflow to contribute to other open source projects.
http://www.silverwareconsulting.com/index.cfm/Git-Workflow

49. progit.org
http://git-scm.com