Get Going with Git DVCS in a Day

Over the past several years, I've been mentoring developers at IBM, Aetna, CSG, Echostar, Comverse and other corporations on best practices and efficiencies in using Open Source Source Code Control systems such as Subversion. Now, I?m helping some of these same companies make the absolutely painless sea-change to the Git open source distributed version control system (DVCS). Git incentivizes individual developer contributions and innovation, and brings improved dynamics, agility, and efficiencies to the way teams interact with their product code.


Session Agenda

Sessions begin at 9AM and end at 5PM. Attendees must bring their own laptop.

Day 1

  • DISTRIBUTED
    • Subversion and its commercial counterparts are all centralized, but Git is distributed. Learn how this new class of source code control system is sending shock waves through the development world. Git adds the ability to do perform offline checkins, incre
  • AGILE TEAM DYNAMICS
    • The fast local branching and revising of history before publishing in Git goes hand in glove with a fully agile team or a team that just wishes they were more agile.
  • GITHUB, GITORIOUS
    • Two repository hosting solutions are interestingly an attraction to Git. Discover the amazing community features of GitHub and Gitorious and how they add muscle to the already powerful Git.
  • REPLICATION
    • Since every developer’s working copy of the source is an entire copy of the master repository, backups and replication require no thought or effort.
  • BISECT
    • If you know a range of checkins from which a test was working and when it stopped working, you can have Git do all the heavy lifting of running any command and thus iteratively testing every unique checkin and mechanically identifying the checkin that bro
  • PROGRESSIVE ROLLOUT
    • Git can be incrementally adopted with its strong round-trip support to existing Subversion repositories. Not having to switch the central repository from Subversion means the innovative members of a team can be the first adopters, allowing them to in turn
  • Requirements
    • A Mac OSX 10.4, Mac OSX 10.5, Windows XP or Windows Vista notebook.
  • Recommended
    • MacPorts preinstalled on Mac OSX or Cygwin preinstalled on Windows.