If you would like to switch from a legacy version control system like SVN to Git at your enterprise but do not know how to convince your manager, this presentation is for you! It will help you to clearly explain Git benefits over Subversion or another centralized system and will cover capabilities and pricing options of available enterprise solutions (Github and GitLab). Please feel free to fork and/or share!

1. Git at an Enterprise
Git vs Subversion
and
Enterprise Solutions

2. Git vs Subversion

3. DISTRIBUTED VS CENTRALIZED
Git is distributed, SVN is not
• Designed from the ground up to be fully distributed
• Git has multiple redundant repositories, not one
• You never lose code even if the server explodes
• Developers can work offline
• very important for distributed teams
• Developers work much faster (no latency)

4. BRANCHING AND WORKFLOW
Branches are first-class concepts in Git
• in SVN branches are based on folders structure
• Git branches are simpler and less resource
heavy than Subversion’s
• Git branches carry their entire history
• Git supports any type of workflow not only
Centralized one
• Git is much more suited for proper Versioning
and Release Process

5. GIT USABILITY
• High productively without network connection
• Most operations could be done offline
• Perform a diff;
• View file history;
• Commit changes;
• Merge branches;
• Obtain any other revision of a file;
• Switch branches.
• Makes most operations much faster since no network is involved
• Allows participation in projects without requiring permissions from project authorities, and
thus arguably better fosters culture of meritocracy instead of requiring “committer” status
• Allows private work, so users can use their revision control system even for early drafts
they do not want to publish
• Avoids relying on a single physical machine as a single point of failure.
• Still permits centralized control of the “release version” of the project

6. OTHER CONSIDERATIONS
• Git stores content as metadata, SVN stores just files
• Git's repos are much smaller than Subversions
• for example, Mozilla code is 30x smaller in Git
• Developers often have to use Git anyway to work with open-source
libraries
• Automatic line ending conversion (CRLF or LF)
• Git’s content integrity is better than SVN’s as it is based on based
SHA-1 checksums
• Used and loved by millions of developers
• developers’ satisfaction is important for productivity
• Fantastic enterprise grade solutions based on Git (see below)

7. VERDICT
Git is highly recommended

8. Enterprise Solutions
Github and Gitlab

9. GitHub
github.com on premises and on steroids

10. POWERFUL WORKFLOW
Branching and merging
• pull-requests
• discussion
• code changes preview
• tests result status

11. CODE REVIEW

12. SEARCH

13. ISSUE MANAGEMENT

14. WIKI

15. INTEGRATIONS

16. ENTERPRISE FEATURES

17. USED BY

18. PRICING AND DEPLOYMENT OPTIONS
Hosted (Github Enterprise)
• starts at $2,500 per 10-user seat pack per year.
• 5-10% discounts based on number of seats purchased.
• includes maintenance, upgrades, and technical support at no extra cost.
SaaS (github.com)
• Based on the number of private repositories:

19. GitLab
Enterprise grade open-source system

20. POWERFUL BRANCHING AND MERGING

21. ISSUE MANAGEMENT

22. ACTIVITY STREAM

23. WIKI

24. ENTERPRISE FEATURES
Git Hooks LDAP Group Sync
Branded Login Page
• LDAP group sync
• audit logs and multiple roles
• deeper AuthN and AuthZ integration
• fine-grained workflow management
• runs on your servers
• extra server management options

25. USED BY

26. PRICING AND DEPLOYMENT OPTIONS
Hosted (GitLab Enterprise)
SaaS (gitlab.com)
• Free
• unlimited private and public repositories
• unlimited private collaborators
• Premium
• same + next business day support
• $9.90 per user, per year in multiples of 20 users

27. RESOURCES
• http://blog.teamtreehouse.com/why-you-should-switch-
from-subversion-to-git
• http://www.codeforest.net/git-vs-svn
• https://github.com
• https://about.gitlab.com

28. Thank you!