Posts Tagged ‘source control’

Tortoise Git

Most of you probably already know TortoiseSVN and TortoiseCVS, the popular Windows Explorer extensions to Subversion and CVS source control servers.

It is now time for Tortoise Git. Compared to many other Git gui, I can tell Tortoise Git is ahead of the competition. You have access to all the day to day Git commands with a nice and intuitive user interface. Give it a try and, if you like it, please donate to the team!

You can download Tortoise Git from here http://code.google.com/p/tortoisegit/downloads/list

An image worth a thousand words … well, at least a dozen of words. Following are the commands exposed through the Tortoise Git explorer extension.

Manage Virtual Assistant Using Git

It is now easy as 1-2-3 to hire a Virtual Assistant to help you out with your software development projects. You don’t have to be a large corporation to work with these oversea companies. The key to success with impartition reside, as many will tell you, in two things.

First, your ability to clearly define the work to do. You will get through it with time and practice. Communication is most often very hard because of the distance and the language barrier.

Second, your ability to control the quality and the velocity of the code produced by the team and to merge it to the final product. For that task you can get help from technologies such as Git, a distributed source control application.

Git is a free & open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Branching and merging are very low cost compared to server based source control systems.

In the context of impartition, Git becomes very effective because there is no need for the developers to know about it. Here is the sequence I use to work with remote Virtual Assistants:

  1. Since branching in Git is very effective and low cost, you start by creating a branch for a specific developer.
  2. Checkout the user branch
  3. Zip the project and send it to the programmer.
  4. Repeat 1 to 3 for all programmers.
  5. Once a programmer send back a zip of the project, you can use Git to view and merge all changes made by this user.

This can only be done on a distributed source control application. If you have several developer for a longer period of time, you may want to take time to teach Git to them so they can send you patches to simplify the merge process.