git/list[1] front-page[2] threads[3] people[4] search[5] about
 

What's the best way to make my company migrate to Git?

From
DSDaniele Segato <daniele.bilug@gmail.com>
Date
May 21, 2010, 14:55 UTC
Message-ID
<AANLkTikwpjtJnR856CHr_O3856JoMrFBgOQGODXNBbeI@mail.gmail.com>
Hi,

I work as a Developer (mainly Java and web applications) and I'd like to introduce my company to the use of Git. I don't have much time to allocate on this matter, so the elapsed for applying any of your suggestion will probably go from weeks to months :)

If I manage to migrate I'll be only able to start using git with the new projects, I don't think that old project will be easily migrated to Git (unless not until it will be widely accepted and learned by everyone). There are, more or less, 30 developers working in different projects from junior to senior developers.

We use Subversion as versioning system.

The developers are used to work with Eclipse (an open source IDE) that happen to have a Subversion plugin and they all works on Windows platform. I'm the only one who work on a Linux box and use git-svn from command line as a front end to Subversion. I already know of (some of) the advantage of using git, but I'm also aware that it's not that easy to change other people mind on what they used for years. So I need to be really persuasive on the advantage of using it, and I think you can help me on this.

I think that to introduce git in my company I should at least go throw
this 5 points:
1. prepare a project management web application easy to use and
mantain (like github or gitorious for instance) on one of our intranet
servers.
2. achieve knowledge on the git-submodule and to handle binary files
versioning (mainly third party java libraries that are in every
project)
3. learn what I had to know to use Git on windows (i never did this),
and find some user friendly AND graphical tool to propose (i know
there is a Git-eclipse module but I don't know if it is considered
stable and/or full featured)
4. give my managers some reason to migrate/begin to use Git instead of
Subversion
5. do some "school" to other developers

I think there are many of you that went throw this before and I'd like to have some advice on the 5 point of the list above.

Can you also tell me if you think there is some risk in migrating and what kind of difficult I could encounter in the process? For example: like any company we have a proxy and a firewall.. For example: if i had to commit something working from home I connect to the Subversion via HTTPS and commit, with Git I should have ssh access which is something that I probably will not have.

I can summarize all this email with just this question: What's the best way to make my company migrate to Git?

thank you all for any advice.
Daniele
Next: Jakub Narebski
Message 1 of 27 in “What's the best way to make my company migrate to Git?”
  1. Daniele SegatoMay 21, 2010
  2. Jakub NarebskiMay 21, 2010
  3. Daniele SegatoMay 22, 2010
  4. Jakub NarebskiMay 22, 2010
  5. Joshua JensenMay 22, 2010
  6. Andrew SayersMay 22, 2010
  7. Daniele SegatoMay 22, 2010
  8. Andrew SayersMay 23, 2010
  9. Daniele SegatoMay 24, 2010
  10. Lin MacMay 23, 2010
  11. Andrew SayersMay 23, 2010
  12. Michael J GruberMay 25, 2010
  13. Andrew SayersMay 31, 2010
  14. Michael J GruberJun 1, 2010
  15. Daniele SegatoJun 1, 2010
  16. Alexander IljinJun 1, 2010
  17. Daniele SegatoJun 1, 2010
  18. Alexander IljinJun 1, 2010
  19. Erik Faye-LundJun 1, 2010
  20. Daniele SegatoJun 1, 2010
  21. Andrew SayersJun 1, 2010
  22. Andreas KreyJun 2, 2010
  23. Michael J GruberJun 2, 2010
  24. Andrew SayersJun 5, 2010
  25. Steven MichalskeJun 6, 2010
  26. Sylvain RabotJun 2, 2010
  27. Daniele SegatoMay 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.