Why we should drop Vault use git

use_git.md

Why Vault isn't good enough

single license and floater user

• who's got it checked out?
• who / what DR broke it?
• why did they do that?
• what were the specs?
• who tested it?
• no integration with IDE

business analysts, testers, and managers don't have access

their contributions to products/deployments:

• specs
• documentation
• validation scripts
• front ends

are typically lost after each release in:

• emails
• network drives
• share point

we need an common interface that is:

• free: no licencing, no servers
• intuitive: niave BAs and silly managers can use it
• integrated: jira, visual studio
• flexible: accomadates whatever workflow they concoct
• accessible: gives managers a much needed clue

no project management features

• no issue tracking
• no work flow release cycle (need for DR database)

deployments and agile stories aren't compatible

• agile storys are stored in a disintegrated access database

• tracked on 3 redundant white boards, outlook calendars but mostly emails

• deployments are managed on a different access database
• bugs/issues/maintaince are documented in emails + network drives + share point + post its

Why we should use git (not svn or subversion)

Industry Standard

Git has won

• Cerner
• Microsoft
• Google
• Apache
• Facebook
• Microsoft .NET Core
• Twitter

Git

• Free and standard
• Supports all workflows and deployment cycles
• Decentralized mean accesible

Why we should host git with github

• Free intuitive GUI

• Free mobile app

• Free Visual Studio and Jira integration

Free Online Hosting

• Google search for free
• Active Directory and GitHub user accounts
• Privacy and security
• Easy online access from home and VCH vms

Enterprise Quality and Standard

Free Support

Integrated

Compatible

Accessible

Team Foundation Server

As explained by Denodo consultant: there is a problematic file name length limit.

Subversion

It lost the vcs war.

• Jira/Visual Studio integration
• Centralized