If you are working on project with a team of developers, then revision control is necessary, period. Even developers working solo on a project will find that using a revision control system provides many benefits. Revision control systems have been around for over a decade, but what makes Git attractive is that it's a DISTRIBUTED revision control system (DRCS), which allows it to keep track of revisions and allows many developers to work on a given project without necessarily being connected to a common network.
How does revision control work?
Revision control is the management of changes to the files of a development project. Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is "revision 2", and so on. Each revision is associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged.
How does a Distributed Revision Control System work?
Distributed revision control (DRCS) takes a peer-to-peer approach to revision control, as opposed to the client-server approach of centralized systems. Rather than a single, central repository on which clients synchronize, each peer's working copy of the codebase is a bona fide repository. Distributed revision control conducts synchronization by exchanging patches (sets of changes) from peer to peer.
What's the difference between Git and Github?
Git is a distributed revision control system with an emphasis on speed. Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server.
GitHub is a web-based hosting service for software development projects that use the Git revision control system. GitHub offers both commercial plans and free accounts for open source projects.
Does this meetup need any volunteers?
We currently have a presenter for this meetup, but are still looking for co-presenters with experience in the subject to assist, as well as volunteers to help with various aspects of the meeting (like signing attendees in and videotaping the presentation). The meetup will be presented by Chris Baril, who holds a Computer Science B.S. degree from the University of British Columbia and has been developing websites since the late 90s. For more information visit chrisbaril.com
Who should attend?
INTENDED AUDIENCE: Front-end and back-end developers
DIFFICULTY LEVEL: Beginner/Intermediate
Where should I start?