Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Thomas Koch <thomas@koch.ro>
Reply-To: thomas@koch.ro
To: Paul Davis <paul.joseph.davis@gmail.com>
Subject: Re: Blog post on Gerrit (GIT review tool)
Date: Fri, 11 Feb 2011 08:20:12 +0100
User-Agent: KMail/1.13.5 (Linux/2.6.32-4-amd64; KDE/4.4.5; x86_64; ; )
Cc: infrastructure-dev@apache.org
References: <201102101044.54634.thomas@koch.ro>
 <AANLkTi=ns4ErqL2VrJSEKCP3=+5U1ZWbNJLkv9BWPNEC@mail.gmail.com>
 <AANLkTin5Vn0Frmw2u_+8dRYd+Kt4wAmwVRW-iTsS6OQK@mail.gmail.com>
In-Reply-To: <AANLkTin5Vn0Frmw2u_+8dRYd+Kt4wAmwVRW-iTsS6OQK@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201102110820.12795.thomas@koch.ro>

Paul Davis:
> > OTOH I don't think git can be used "much the same" as svn. I would
> > recommend any people that has not used git deeply to avoid comparing it
> > with subversion until they have used it deeply during, say, one year. By
> > using I
> 
> > mean at least:
> I was worried someone would take that comment wrong. I should've been
> more clear.
> 
> I meant to point out that it would be the same or similar from the
> point of view of the infrastructure team. As in, it'd be hosted by
> httpd, use mod_ldap for authentication, some various pieces of code to
> plug in ldap groups for authorization, etc. It'd be based on services
> for which there is already experience running.
> 
> This is opposed to something like Gerrit that would require multiple
> people on the infrastructure team to learn and care for a new service
> as well as require changes to processes like getting CLA's and such
> forth.
> 
> HTH,
> Paul Davis
So just because some people on infra should be avoided the burden to learn 
something new, some thousand developers should suffer from a suboptimal 
system?
And it's not much IMHO what needs to be learned. It's a well packaged, proven 
system with a big, active and maybe even helpful community.
And I also offered my help to set it up. I can also help in maintenance, if 
you really need it. I also already did set up a test instance (on request of 
Owen O'Malley) without any trouble.

It would just help to have just a little bit of communication going on. I've 
asked for a list of requirements on 2010/12/04 and even started a draft list 
to help out. However there wasn't any reaction to that.

Please note that the list of _TASKS_ on jira is not a list of requirements. 
Requirements come before you make tasks.

I know it's much more fun to sit down and hack on something. Communication is 
the hard part.

So you just formulated the first requirement: The infrastructure team 
shouldn't be required to learn anything new. Now questions could be:

- Who is the infrastructure team? I don't know.
- Do they agree with this requirement?
- Could somebody else join the infrastructure team who would like to work with 
something new?
- Could the GIT installation be administrated by another, dedicated GIT team?

Best regards,

Thomas Koch, http://www.koch.ro