git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Bainbridge <david.bainbridge@gmail.com>
To: William Hall <will@gnatter.net>
Cc: git@vger.kernel.org
Subject: Re: SVN migration
Date: Sat, 3 Jul 2010 13:37:57 +0200	[thread overview]
Message-ID: <AANLkTimtGoNQe2-nA_Qn_qsZP2Iley9x6TU3Ht28Eg4t@mail.gmail.com> (raw)
In-Reply-To: <4C25D783.4070602@gnatter.net>

Hi William,

I have been following this thread with interest so I thought that I
would just throw in my thoughts!

While maintaining synchronization with Git is part of what is needed I
suspect that this will not entirely convince the management of your
company that Git is the way forward.

They probably see Svn as a safe repository ... The company's assets
(intellectual property) are on a central server that is backed up, and
the contents of that repository can be audited and so on. They may be
thinking about things like SOX compliance too.

So if you want them to accept Git as a replacement for svn then you
need to understand and address these concerns. This means that you
will have to have a conversation with them. To a large extent this a
people thing ... technical solutions won't necessary convince them.
They are running a company based on the knowledge and information they
own - and they want to make sure that it doesn't get lost, stolen,
corrupted, or whatever. And they are accountable to the shareholders
for this.

Also, you say that they have been using Svn for donkey's years, so
from a corporate perspective it probably does what they want and need.
Otherwise THEY would have decided to change it.

I am in a similar situation and while developers clearly want to use
gIt, the motivation from a corporate perspective is less clear and can
be perceived as introducing risk. So we are looking at the wya in
which repositories are set up, the topology of git repository
networks, use of Gitosis. Gitolite and Gitorious, and so on, to
provide some security in the corporate environment.

Every company will have a different view of this so there is no
'right' answer. A lot depends on the type of product you produce and
how long it will need to be supported. If you have products that need
to be supported for 10 years or more then promoting a tool that is 5
years old may also raise some eyebrows! You need to have the answers
ready :-)

Get it right and you will be seen as a hero who understands the
business. Get it wrong and you will consigned to the religious nerd
category who just wants to promote his favourite tool ... which I
would hope is not the case :-)

Good luck with this ... you are not alone!

Dave Bainbridge

  reply	other threads:[~2010-07-03 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 23:02 SVN migration William Hall
2010-06-17  0:41 ` Steven Michalske
2010-06-17 10:33   ` William Hall
2010-06-17 16:27     ` William Hall
2010-06-21 21:12       ` Joshua Shrader
2010-06-21 22:26         ` William Hall
2010-06-26 10:33 ` William Hall
2010-07-03 11:37   ` David Bainbridge [this message]
2010-07-04 17:55     ` William Hall
2010-07-04 22:01       ` David Bainbridge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimtGoNQe2-nA_Qn_qsZP2Iley9x6TU3Ht28Eg4t@mail.gmail.com \
    --to=david.bainbridge@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=will@gnatter.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).