Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <20D2B90488A11941BF353395CDB446FB10EC15@001FSN2MPN1-012.001f.mgd2.msft.net>
References: 
 <CALJOYLF3LMjNwxzyYAKmPGu7Ky8x6tpOEvDPaQUoH3=PKrmpKw@mail.gmail.com>
 <6694E14A-C3DD-457B-B36A-D415D5AE7D86@mycosystems.co.uk>
 <CALhtWkfMTfbe5vfFt3wijvtZ0QSF26MXwCeFKaO3ieJa33hK+A@mail.gmail.com>
 <1339421465.75352.YahooMailNeo@web171502.mail.ir2.yahoo.com>
 <CALJOYLFzNcSm3S5KF2wCjgp0JE8LmW8pk2t=b1eYN1BCgSxVsw@mail.gmail.com>
 <CALhtWkchsCKy4g+G84rhGqJZGdvaEism31LJLZxpYAgNVn70fA@mail.gmail.com>
 <CALJOYLFfj-TuMXROLRp=Bg7wctK0q4e5kjgV+n=dgrFdCsGaVg@mail.gmail.com>
 <CALhtWkdFd8X8D5RjqFhzmfsE2U4uNj54XMp0bYeXnNQV5U_KDw@mail.gmail.com>
 <CALJOYLEpUdBEr3k1YAhRfTbb-gsuDmfSycBw60aywuLG9UxkgQ@mail.gmail.com>
 <20D2B90488A11941BF353395CDB446FB10EC15@001FSN2MPN1-012.001f.mgd2.msft.net>
From: Dan Haywood <dan@haywood-associates.co.uk>
Date: Tue, 12 Jun 2012 16:06:45 +0100
Message-ID: 
 <CALJOYLH1z7WfJwjC5Kya1ZAKymAbmAzg9HnZEnnjZnsOCHHdaw@mail.gmail.com>
Subject: Re: move to git?
To: isis-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1c6d4d703f504c247d1dd

--e89a8ff1c6d4d703f504c247d1dd
Content-Type: text/plain; charset=ISO-8859-1

Hi Jason,
>From your question, I'm guessing CVS is what you use internally?

Being blunt, I don't think moving to CVS is either feasible, nor desirable.
 SVN - which we are currently hosted on - was originally designed to be a
"better CVS"; and I think it's generally recognized that it succeeded.

GIT meanwhile, has become massively popular recently, and is exceptionally
good at encouraging contributions - witness the "fork me on github" banners
that one encounters everywhere.

The reason I'm suggesting we move to GIT, at least in some form, is that I
can see it'll make contributions easier, both for the project I'm starting
on, and more generally to help build the Isis community.  The fact that ASF
now supports GIT, at least in part, also lends credence to this... ASF is
all about building communities, after all.

But perhaps you have a different perspective?

Dan
~~~~~~~~~~

On 12 June 2012 15:44, Richardson, Jason - FSA, Kansas City, MO <
jason.richardson@kcc.usda.gov> wrote:

> Sorry to side track, but what about CVS?
>
>
>
> Jason Richardson
> National Payments Service (NPS) Technical Lead
> USDA/FSA/AFAO/SCADG
> (Administrative and Financial Applications Office)
> (Service Center Accounting & Debt Group)
> Office Ph: (816) 823-5296
> Cubicle:  3NW024
> NPS I.T. Matrix (JIRA)
> NPS Email Groups Listing
>
>
>
> -----Original Message-----
> From: Dan Haywood [mailto:dan@haywood-associates.co.uk]
> Sent: Tuesday, June 12, 2012 9:01 AM
> To: isis-dev@incubator.apache.org
> Subject: Re: move to git?
>
> do you know... is there any more detailed guidance from ASF anywhere on
> using svn as master with a git.apache.org clone?  I'm thinking this might
> be a good interim step.
>
> Thx
> Dan
>
>
> On 12 June 2012 14:23, Benson Margulies <bimargulies@gmail.com> wrote:
>
> > On Tue, Jun 12, 2012 at 9:12 AM, Dan Haywood
> > <dan@haywood-associates.co.uk> wrote:
> > > Hi Benson,
> > >
> > > am I right that the reverse direction would be using "git svn"?
> >
> > For a committer, yes. For someone just offering patches, it's
> > attaching them to JIRA, or emailing them to the list.
> >
> > There's a web page explaining how to clone a git.apache.org repo, and
> > then tweak it so that you can go on from there with git svn.
> >
> >
> > >
> > > Dan
> > >
> > >
> > > On 12 June 2012 14:06, Benson Margulies <bimargulies@gmail.com> wrote:
> > >
> > >> You can do that without moving. Ask infra to set up a
> > >> git.apache.org mirror of isis. Then he can clone that. The reverse
> > >> direction is not as convenient, but it's not awful.
> > >>
> > >>
> > >> On Tue, Jun 12, 2012 at 8:59 AM, Dan Haywood
> > >> <dan@haywood-associates.co.uk> wrote:
> > >> > On 11 June 2012 14:31, Mark Struberg <struberg@yahoo.de> wrote:
> > >> >
> > >> >> Hi!
> > >> >>
> > >> >> We use git in DeltaSpike. The question is how much benefit it
> > >> >> would
> > >> bring
> > >> >> for Isis.
> > >> >>
> > >> >
> > >> > I'm about to kick off a new project that is going to be using
> > >> > Isis,
> > with
> > >> > the resultant app also being licensed as open source.  We'll
> > >> > probably
> > be
> > >> > using github or similar for that.
> > >> >
> > >> > As a consequence of the project, there are likely to be a number
> > >> > of enhancements/fixes to Isis itself.  I was thinking that if
> > >> > Isis is
> > hosted
> > >> > on Git, then I can get the guy I'm working with sign an ICLA and
> > >> > thus
> > be
> > >> > able to "git pull" in any changes he might make on his clone of
> Isis.
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >>
> > >> >> Git is really nice for some use cases but not so nice for others.
> > E.g.
> > >> no
> > >> >> native line-ending conversion support, no binary support, etc
> > >> >>
> > >> >
> > >> > I think that there is reasonable support here.  I was going to
> > >> > mention core.autocrlf property, but a quick google also threw up
> > >> > the
> > >> .gitattributes
> > >> > file, see [1]
> > >> >
> > >> >
> > >> >
> > >> >>
> > >> >> I've written up a comparison here:
> > >> >>
> > >> >> http://wiki.apache.org/couchdb/SVNvsGIT
> > >> >> http://wiki.apache.org/couchdb/Git_At_Apache_Guide
> > >> >>
> > >> >>
> > >> > Thanks for this; read with interest.
> > >> >
> > >> >
> > >> >
> > >> >> It's quite some work and a few things like Jira commit tracking
> > >> >> still doesn't work.
> > >> >>
> > >> >>
> > >> >> LieGrue,
> > >> >> strub
> > >> >>
> > >> >>
> > >> > Thanks,
> > >> > Dan
> > >> >
> > >> > [1]
> > http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >>
> > >> >>
> > >> >> ----- Original Message -----
> > >> >> > From: Benson Margulies <bimargulies@gmail.com>
> > >> >> > To: isis-dev@incubator.apache.org
> > >> >> > Cc:
> > >> >> > Sent: Monday, June 11, 2012 3:13 PM
> > >> >> > Subject: Re: move to git?
> > >> >> >
> > >> >> > infra is supporting git. At last reading, there was a tax. If
> > >> >> > you
> > want
> > >> >> > to use git, you have to provide a volunteer to continue the
> > >> >> > infrastructure work. I haven't seen much lately. There are a
> > couple of
> > >> >> > example projects using git (couchdb?) you might want to sniff
> > around
> > >> >> > their situation.
> > >> >> >
> > >> >> > On Mon, Jun 11, 2012 at 8:37 AM, Mike Burton <
> > mikeb@mycosystems.co.uk
> > >> >
> > >> >> > wrote:
> > >> >> >>  1. +1
> > >> >> >>
> > >> >> >>  Best Regards
> > >> >> >>
> > >> >> >>  Mike Burton
> > >> >> >>  (Sent from my iPhone)
> > >> >> >>
> > >> >> >>
> > >> >> >>  On 11 Jun 2012, at 13:28, Dan Haywood <
> > dan@haywood-associates.co.uk
> > >> >
> > >> >> > wrote:
> > >> >> >>
> > >> >> >>>  Two questions:
> > >> >> >>>
> > >> >> >>>  1. for Isis developers ... how do you feel about moving
> > >> >> >>> Isis to
> > use
> > >> >> git
> > >> >> >>>  rather than svn?  I think it'd be worth considering,
> > >> >> >>> because
> > git is
> > >> >> >>>  generally considered easier to allow patches to be provided
> > ("pull
> > >> >> >>>  requests").
> > >> >> >>>
> > >> >> >>>  2. for mentors ... does anyone know what ASF's current
> > >> >> >>> support
> > is
> > >> >> > for git?
> > >> >> >>>  I can see there's git-wip-us.apache.org, and also clones
> > >> >> >>> over
> > on
> > >> >> >>>  github.org/apache.  Is anyone up to date on the status of
> > >> >> >>> ASF's
> > >> >> > support?
> > >> >> >>>
> > >> >> >>>  Thx
> > >> >> >>>  Dan
> > >> >> >
> > >> >>
> > >>
> >
>
>
>
>
> This electronic message contains information generated by the USDA solely
> for the intended recipients. Any unauthorized interception of this message
> or the use or disclosure of the information it contains may violate the law
> and subject the violator to civil or criminal penalties. If you believe you
> have received this message in error, please notify the sender and delete
> the email immediately.
>
>

--e89a8ff1c6d4d703f504c247d1dd--