From: Daniele Segato <daniele.bilug@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's the best way to make my company migrate to Git?
Date: Sat, 22 May 2010 17:58:51 +0200 [thread overview]
Message-ID: <1274543931.21346.171.camel@Luffy> (raw)
In-Reply-To: <m34oi1s13e.fsf@localhost.localdomain>
Il giorno ven, 21/05/2010 alle 08.54 -0700, Jakub Narebski ha scritto:
> Daniele Segato <daniele.bilug@gmail.com> writes:
>
> [...]
> > 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.
>
> Note that while Gitorious (in Ruby), InDefero (in PHP), and Girocco
> (with gitweb, Perl + shell script, used by http://repo.or.cz) are open
> source, GitHub is not. There is GitHub:FI if you want [self] hosted
> GitHub-alike, but it is proprietary and it is not cheap.
>
> There is also Gerrit, a web based code review system, which runs in
> any standard Java servlet container.
Thanks for the list.
Yes I know GitHub isn't Open Source, and just for this reason it can't
be an option, but it's features are the one I'm looking for.
I never heard of some of the project you listed here, I'll give them a
try.
Did someone worked with some of them and have a review or an opinion
about them?
>
> [...]
> > 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.
>
> Actually with never Git you can push and pull via HTTP(S) natively,
> thanks to git-http-backend. With older Git you had to use HTTP as
> "dumb" protocol, using HTTPS + WebDAV to push (note that for "dumb"
> servers git-update-server-info must be run, e.g. via a hook).
Oh, that's interesting. I wasn't aware of this.
I'll go read some doc about this new feature, thanks.
Daniele
next prev parent reply other threads:[~2010-05-22 15:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:55 What's the best way to make my company migrate to Git? Daniele Segato
2010-05-21 15:54 ` Jakub Narebski
2010-05-22 15:58 ` Daniele Segato [this message]
2010-05-22 16:06 ` Jakub Narebski
2010-05-22 18:26 ` Joshua Jensen
2010-05-22 10:52 ` Andrew Sayers
2010-05-22 15:52 ` Daniele Segato
2010-05-23 14:52 ` Andrew Sayers
2010-05-24 17:37 ` Daniele Segato
2010-05-23 9:12 ` Lin Mac
2010-05-23 15:06 ` Andrew Sayers
2010-05-25 7:42 ` Michael J Gruber
2010-05-31 20:04 ` Andrew Sayers
2010-06-01 6:28 ` Michael J Gruber
2010-06-01 16:00 ` Daniele Segato
2010-06-01 16:14 ` Alexander Iljin
2010-06-01 17:16 ` Daniele Segato
2010-06-01 17:45 ` Alexander Iljin
2010-06-01 16:25 ` Erik Faye-Lund
2010-06-01 16:36 ` Daniele Segato
2010-06-01 21:12 ` Andrew Sayers
2010-06-02 5:19 ` Andreas Krey
2010-06-02 7:15 ` Michael J Gruber
2010-06-05 21:27 ` Andrew Sayers
2010-06-06 8:19 ` Steven Michalske
2010-06-02 16:01 ` Sylvain Rabot
[not found] ` <AANLkTilIihNTDPZ5NIKUzsPEZ2Gpusm-10FCBVifvNuw@mail.gmail.com>
2010-05-23 22:46 ` Daniele Segato
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1274543931.21346.171.camel@Luffy \
--to=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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.
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 NNTP newsgroup(s).