Would anyone be opposed to doing this? I think you can apply to do this via
Apache, no? It would be nice to make git the first class citizen of
choice... forcing developers to use svn to work with pig is just another
barrier, imho. I thought this had been bandied about on Twitter and the
like, but not sure if it's been discussed seriously on the listserv.

Would love y'all's opinions on the matter
Jon

Please, yes.

Russell Jurney http://datasyndrome.com

On Mar 20, 2012, at 11:22 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:

> Would anyone be opposed to doing this? I think you can apply to do this via
> Apache, no? It would be nice to make git the first class citizen of
> choice... forcing developers to use svn to work with pig is just another
> barrier, imho. I thought this had been bandied about on Twitter and the
> like, but not sure if it's been discussed seriously on the listserv.
>
> Would love y'all's opinions on the matter
> Jon

AFAIK Apache still does not support git as a primary repository.  You can use the git mirror, which Pig does.  If this has changed (or when it does), I'm +0 on changing, by which I mean I don't care which we use.

Alan.

On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:

> Would anyone be opposed to doing this? I think you can apply to do this via
> Apache, no? It would be nice to make git the first class citizen of
> choice... forcing developers to use svn to work with pig is just another
> barrier, imho. I thought this had been bandied about on Twitter and the
> like, but not sure if it's been discussed seriously on the listserv.
>
> Would love y'all's opinions on the matter
> Jon

I think this changed, and you are now allowed.  Looking for the tweets.

Russell Jurney http://datasyndrome.com

On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]> wrote:

> AFAIK Apache still does not support git as a primary repository.  You can use the git mirror, which Pig does.  If this has changed (or when it does), I'm +0 on changing, by which I mean I don't care which we use.
>
> Alan.
>
> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>
>> Would anyone be opposed to doing this? I think you can apply to do this via
>> Apache, no? It would be nice to make git the first class citizen of
>> choice... forcing developers to use svn to work with pig is just another
>> barrier, imho. I thought this had been bandied about on Twitter and the
>> like, but not sure if it's been discussed seriously on the listserv.
>>
>> Would love y'all's opinions on the matter
>> Jon
>

I think this is the tweet (lacking the entire discussion tree that we had
re git) where I was pointing out that some incubator projects were using
git.

https://twitter.com/#!/billgraham/status/174744199407738880
On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
<[EMAIL PROTECTED]>wrote:

> I think this changed, and you are now allowed.  Looking for the tweets.
>
> Russell Jurney http://datasyndrome.com
>
> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]> wrote:
>
> > AFAIK Apache still does not support git as a primary repository.  You
> can use the git mirror, which Pig does.  If this has changed (or when it
> does), I'm +0 on changing, by which I mean I don't care which we use.
> >
> > Alan.
> >
> > On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >
> >> Would anyone be opposed to doing this? I think you can apply to do this
> via
> >> Apache, no? It would be nice to make git the first class citizen of
> >> choice... forcing developers to use svn to work with pig is just another
> >> barrier, imho. I thought this had been bandied about on Twitter and the
> >> like, but not sure if it's been discussed seriously on the listserv.
> >>
> >> Would love y'all's opinions on the matter
> >> Jon
> >
>

--
*Note that I'm no longer using my Yahoo! email address. Please email me at
[EMAIL PROTECTED] going forward.*

What do we have to do to be the first real project that uses git?
Let's do that. Or, let's just sink svn to github.

It will propel the project forward.

Russell Jurney
twitter.com/rjurney
[EMAIL PROTECTED]
datasyndrome.com

On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:

> I think this is the tweet (lacking the entire discussion tree that we had
> re git) where I was pointing out that some incubator projects were using
> git.
>
> https://twitter.com/#!/billgraham/status/174744199407738880
>
>
> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> <[EMAIL PROTECTED]>wrote:
>
>> I think this changed, and you are now allowed.  Looking for the tweets.
>>
>> Russell Jurney http://datasyndrome.com
>>
>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>
>>> AFAIK Apache still does not support git as a primary repository.  You
>> can use the git mirror, which Pig does.  If this has changed (or when it
>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>
>>> Alan.
>>>
>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>
>>>> Would anyone be opposed to doing this? I think you can apply to do this
>> via
>>>> Apache, no? It would be nice to make git the first class citizen of
>>>> choice... forcing developers to use svn to work with pig is just another
>>>> barrier, imho. I thought this had been bandied about on Twitter and the
>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>
>>>> Would love y'all's opinions on the matter
>>>> Jon
>>>
>>
>
>
>
> --
> *Note that I'm no longer using my Yahoo! email address. Please email me at
> [EMAIL PROTECTED] going forward.*

All that's left is for someone to volunteer to do the work.

On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]> wrote:

> What do we have to do to be the first real project that uses git?
> Let's do that. Or, let's just sink svn to github.
>
> It will propel the project forward.
>
> Russell Jurney
> twitter.com/rjurney
> [EMAIL PROTECTED]
> datasyndrome.com
>
> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>
>> I think this is the tweet (lacking the entire discussion tree that we had
>> re git) where I was pointing out that some incubator projects were using
>> git.
>>
>> https://twitter.com/#!/billgraham/status/174744199407738880
>>
>>
>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>> <[EMAIL PROTECTED]>wrote:
>>
>>> I think this changed, and you are now allowed.  Looking for the tweets.
>>>
>>> Russell Jurney http://datasyndrome.com
>>>
>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>>
>>>> AFAIK Apache still does not support git as a primary repository.  You
>>> can use the git mirror, which Pig does.  If this has changed (or when it
>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>
>>>> Alan.
>>>>
>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>
>>>>> Would anyone be opposed to doing this? I think you can apply to do this
>>> via
>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>> choice... forcing developers to use svn to work with pig is just another
>>>>> barrier, imho. I thought this had been bandied about on Twitter and the
>>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>>
>>>>> Would love y'all's opinions on the matter
>>>>> Jon
>>>>
>>>
>>
>>
>>
>> --
>> *Note that I'm no longer using my Yahoo! email address. Please email me at
>> [EMAIL PROTECTED] going forward.*

What's the work?

Russell Jurney http://datasyndrome.com

On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> All that's left is for someone to volunteer to do the work.
>
> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]> wrote:
>
>> What do we have to do to be the first real project that uses git?
>> Let's do that. Or, let's just sink svn to github.
>>
>> It will propel the project forward.
>>
>> Russell Jurney
>> twitter.com/rjurney
>> [EMAIL PROTECTED]
>> datasyndrome.com
>>
>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>>
>>> I think this is the tweet (lacking the entire discussion tree that we had
>>> re git) where I was pointing out that some incubator projects were using
>>> git.
>>>
>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>
>>>
>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>> <[EMAIL PROTECTED]>wrote:
>>>
>>>> I think this changed, and you are now allowed.  Looking for the tweets.
>>>>
>>>> Russell Jurney http://datasyndrome.com
>>>>
>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> AFAIK Apache still does not support git as a primary repository.  You
>>>> can use the git mirror, which Pig does.  If this has changed (or when it
>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>>
>>>>> Alan.
>>>>>
>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>>
>>>>>> Would anyone be opposed to doing this? I think you can apply to do this
>>>> via
>>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>>> choice... forcing developers to use svn to work with pig is just another
>>>>>> barrier, imho. I thought this had been bandied about on Twitter and the
>>>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>>>
>>>>>> Would love y'all's opinions on the matter
>>>>>> Jon
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> *Note that I'm no longer using my Yahoo! email address. Please email me at
>>> [EMAIL PROTECTED] going forward.*

Answering that question is the first part of the answer to that question.
#recursion

D

On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:

> What's the work?
>
> Russell Jurney http://datasyndrome.com
>
> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
> > All that's left is for someone to volunteer to do the work.
> >
> > On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
> wrote:
> >
> >> What do we have to do to be the first real project that uses git?
> >> Let's do that. Or, let's just sink svn to github.
> >>
> >> It will propel the project forward.
> >>
> >> Russell Jurney
> >> twitter.com/rjurney
> >> [EMAIL PROTECTED]
> >> datasyndrome.com
> >>
> >> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
> >>
> >>> I think this is the tweet (lacking the entire discussion tree that we
> had
> >>> re git) where I was pointing out that some incubator projects were
> using
> >>> git.
> >>>
> >>> https://twitter.com/#!/billgraham/status/174744199407738880
> >>>
> >>>
> >>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >>> <[EMAIL PROTECTED]>wrote:
> >>>
> >>>> I think this changed, and you are now allowed.  Looking for the
> tweets.
> >>>>
> >>>> Russell Jurney http://datasyndrome.com
> >>>>
> >>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
> wrote:
> >>>>
> >>>>> AFAIK Apache still does not support git as a primary repository.  You
> >>>> can use the git mirror, which Pig does.  If this has changed (or when
> it
> >>>> does), I'm +0 on changing, by which I mean I don't care which we use.
> >>>>>
> >>>>> Alan.
> >>>>>
> >>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >>>>>
> >>>>>> Would anyone be opposed to doing this? I think you can apply to do
> this
> >>>> via
> >>>>>> Apache, no? It would be nice to make git the first class citizen of
> >>>>>> choice... forcing developers to use svn to work with pig is just
> another
> >>>>>> barrier, imho. I thought this had been bandied about on Twitter and
> the
> >>>>>> like, but not sure if it's been discussed seriously on the listserv.
> >>>>>>
> >>>>>> Would love y'all's opinions on the matter
> >>>>>> Jon
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> *Note that I'm no longer using my Yahoo! email address. Please email
> me at
> >>> [EMAIL PROTECTED] going forward.*
>

Let's start using github and publish to svn during releases.

Russell Jurney http://datasyndrome.com

On Mar 21, 2012, at 10:20 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> Answering that question is the first part of the answer to that question.
> #recursion
>
> D
>
> On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:
>
>> What's the work?
>>
>> Russell Jurney http://datasyndrome.com
>>
>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>>
>>> All that's left is for someone to volunteer to do the work.
>>>
>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>> wrote:
>>>
>>>> What do we have to do to be the first real project that uses git?
>>>> Let's do that. Or, let's just sink svn to github.
>>>>
>>>> It will propel the project forward.
>>>>
>>>> Russell Jurney
>>>> twitter.com/rjurney
>>>> [EMAIL PROTECTED]
>>>> datasyndrome.com
>>>>
>>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> I think this is the tweet (lacking the entire discussion tree that we
>> had
>>>>> re git) where I was pointing out that some incubator projects were
>> using
>>>>> git.
>>>>>
>>>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>>>
>>>>>
>>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>
>>>>>> I think this changed, and you are now allowed.  Looking for the
>> tweets.
>>>>>>
>>>>>> Russell Jurney http://datasyndrome.com
>>>>>>
>>>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>> wrote:
>>>>>>
>>>>>>> AFAIK Apache still does not support git as a primary repository.  You
>>>>>> can use the git mirror, which Pig does.  If this has changed (or when
>> it
>>>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>>>>
>>>>>>> Alan.
>>>>>>>
>>>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>>>>
>>>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>> this
>>>>>> via
>>>>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>>>>> choice... forcing developers to use svn to work with pig is just
>> another
>>>>>>>> barrier, imho. I thought this had been bandied about on Twitter and
>> the
>>>>>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>>>>>
>>>>>>>> Would love y'all's opinions on the matter
>>>>>>>> Jon
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Note that I'm no longer using my Yahoo! email address. Please email
>> me at
>>>>> [EMAIL PROTECTED] going forward.*
>>

Start here: http://www.apache.org/dev/git.html

I don't think having an out of date svn repo is a good idea, since that's
where newcomers will check.

D

On Wed, Mar 21, 2012 at 10:30 PM, Russell Jurney
<[EMAIL PROTECTED]>wrote:

> Let's start using github and publish to svn during releases.
>
> Russell Jurney http://datasyndrome.com
>
> On Mar 21, 2012, at 10:20 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
> > Answering that question is the first part of the answer to that question.
> > #recursion
> >
> > D
> >
> > On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney <
> [EMAIL PROTECTED]>wrote:
> >
> >> What's the work?
> >>
> >> Russell Jurney http://datasyndrome.com
> >>
> >> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >>
> >>> All that's left is for someone to volunteer to do the work.
> >>>
> >>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
> >> wrote:
> >>>
> >>>> What do we have to do to be the first real project that uses git?
> >>>> Let's do that. Or, let's just sink svn to github.
> >>>>
> >>>> It will propel the project forward.
> >>>>
> >>>> Russell Jurney
> >>>> twitter.com/rjurney
> >>>> [EMAIL PROTECTED]
> >>>> datasyndrome.com
> >>>>
> >>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
> wrote:
> >>>>
> >>>>> I think this is the tweet (lacking the entire discussion tree that we
> >> had
> >>>>> re git) where I was pointing out that some incubator projects were
> >> using
> >>>>> git.
> >>>>>
> >>>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >>>>>
> >>>>>
> >>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >>>>> <[EMAIL PROTECTED]>wrote:
> >>>>>
> >>>>>> I think this changed, and you are now allowed.  Looking for the
> >> tweets.
> >>>>>>
> >>>>>> Russell Jurney http://datasyndrome.com
> >>>>>>
> >>>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
> >> wrote:
> >>>>>>
> >>>>>>> AFAIK Apache still does not support git as a primary repository.
>  You
> >>>>>> can use the git mirror, which Pig does.  If this has changed (or
> when
> >> it
> >>>>>> does), I'm +0 on changing, by which I mean I don't care which we
> use.
> >>>>>>>
> >>>>>>> Alan.
> >>>>>>>
> >>>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >>>>>>>
> >>>>>>>> Would anyone be opposed to doing this? I think you can apply to do
> >> this
> >>>>>> via
> >>>>>>>> Apache, no? It would be nice to make git the first class citizen
> of
> >>>>>>>> choice... forcing developers to use svn to work with pig is just
> >> another
> >>>>>>>> barrier, imho. I thought this had been bandied about on Twitter
> and
> >> the
> >>>>>>>> like, but not sure if it's been discussed seriously on the
> listserv.
> >>>>>>>>
> >>>>>>>> Would love y'all's opinions on the matter
> >>>>>>>> Jon
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> *Note that I'm no longer using my Yahoo! email address. Please email
> >> me at
> >>>>> [EMAIL PROTECTED] going forward.*
> >>
>

(With my member and PMC hat on) No, that's a violation of Apache policy.  Apache code is hosted on Apache sites, not on github.  If we want to use git we have to sell Apache on letting us use it through their infrastructure, not by moving the code somewhere else.

Alan.

On Mar 21, 2012, at 10:30 PM, Russell Jurney wrote:

> Let's start using github and publish to svn during releases.
>
> Russell Jurney http://datasyndrome.com
>
> On Mar 21, 2012, at 10:20 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> Answering that question is the first part of the answer to that question.
>> #recursion
>>
>> D
>>
>> On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:
>>
>>> What's the work?
>>>
>>> Russell Jurney http://datasyndrome.com
>>>
>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>>>
>>>> All that's left is for someone to volunteer to do the work.
>>>>
>>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>>> What do we have to do to be the first real project that uses git?
>>>>> Let's do that. Or, let's just sink svn to github.
>>>>>
>>>>> It will propel the project forward.
>>>>>
>>>>> Russell Jurney
>>>>> twitter.com/rjurney
>>>>> [EMAIL PROTECTED]
>>>>> datasyndrome.com
>>>>>
>>>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> I think this is the tweet (lacking the entire discussion tree that we
>>> had
>>>>>> re git) where I was pointing out that some incubator projects were
>>> using
>>>>>> git.
>>>>>>
>>>>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>>>>
>>>>>>
>>>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>
>>>>>>> I think this changed, and you are now allowed.  Looking for the
>>> tweets.
>>>>>>>
>>>>>>> Russell Jurney http://datasyndrome.com
>>>>>>>
>>>>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>>> wrote:
>>>>>>>
>>>>>>>> AFAIK Apache still does not support git as a primary repository.  You
>>>>>>> can use the git mirror, which Pig does.  If this has changed (or when
>>> it
>>>>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>>>>>
>>>>>>>> Alan.
>>>>>>>>
>>>>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>>>>>
>>>>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>>> this
>>>>>>> via
>>>>>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>>>>>> choice... forcing developers to use svn to work with pig is just
>>> another
>>>>>>>>> barrier, imho. I thought this had been bandied about on Twitter and
>>> the
>>>>>>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>>>>>>
>>>>>>>>> Would love y'all's opinions on the matter
>>>>>>>>> Jon
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Note that I'm no longer using my Yahoo! email address. Please email
>>> me at
>>>>>> [EMAIL PROTECTED] going forward.*
>>>

Viva el Chancho!

Russell Jurney http://datasyndrome.com

On Mar 21, 2012, at 11:10 PM, Alan Gates <[EMAIL PROTECTED]> wrote:

> (With my member and PMC hat on) No, that's a violation of Apache policy.  Apache code is hosted on Apache sites, not on github.  If we want to use git we have to sell Apache on letting us use it through their infrastructure, not by moving the code somewhere else.
>
> Alan.
>
> On Mar 21, 2012, at 10:30 PM, Russell Jurney wrote:
>
>> Let's start using github and publish to svn during releases.
>>
>> Russell Jurney http://datasyndrome.com
>>
>> On Mar 21, 2012, at 10:20 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>>
>>> Answering that question is the first part of the answer to that question.
>>> #recursion
>>>
>>> D
>>>
>>> On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:
>>>
>>>> What's the work?
>>>>
>>>> Russell Jurney http://datasyndrome.com
>>>>
>>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> All that's left is for someone to volunteer to do the work.
>>>>>
>>>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>
>>>>>> What do we have to do to be the first real project that uses git?
>>>>>> Let's do that. Or, let's just sink svn to github.
>>>>>>
>>>>>> It will propel the project forward.
>>>>>>
>>>>>> Russell Jurney
>>>>>> twitter.com/rjurney
>>>>>> [EMAIL PROTECTED]
>>>>>> datasyndrome.com
>>>>>>
>>>>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>> I think this is the tweet (lacking the entire discussion tree that we
>>>> had
>>>>>>> re git) where I was pointing out that some incubator projects were
>>>> using
>>>>>>> git.
>>>>>>>
>>>>>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>
>>>>>>>> I think this changed, and you are now allowed.  Looking for the
>>>> tweets.
>>>>>>>>
>>>>>>>> Russell Jurney http://datasyndrome.com
>>>>>>>>
>>>>>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>>>
>>>>>>>>> AFAIK Apache still does not support git as a primary repository.  You
>>>>>>>> can use the git mirror, which Pig does.  If this has changed (or when
>>>> it
>>>>>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>>>>>>
>>>>>>>>> Alan.
>>>>>>>>>
>>>>>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>>>>>>
>>>>>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>>>> this
>>>>>>>> via
>>>>>>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>>>>>>> choice... forcing developers to use svn to work with pig is just
>>>> another
>>>>>>>>>> barrier, imho. I thought this had been bandied about on Twitter and
>>>> the
>>>>>>>>>> like, but not sure if it's been discussed seriously on the listserv.
>>>>>>>>>>
>>>>>>>>>> Would love y'all's opinions on the matter
>>>>>>>>>> Jon
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Note that I'm no longer using my Yahoo! email address. Please email
>>>> me at
>>>>>>> [EMAIL PROTECTED] going forward.*
>>>>
>

Am 22.03.12 06:30, schrieb Russell Jurney:
> Let's start using github and publish to svn during releases.

+1

Apache is currently doing a trial with git as the primary repo using the
CouchDB project.  Other projects may be able to volunteer to join the
trial, I'm not sure.

see http://git-wip-us.apache.org/

I suggest that if you are interested in this join the apache
infrastructure-dev list.

On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:

>What's the work?
>
>Russell Jurney http://datasyndrome.com
>
>On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> All that's left is for someone to volunteer to do the work.
>>
>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>>wrote:
>>
>>> What do we have to do to be the first real project that uses git?
>>> Let's do that. Or, let's just sink svn to github.
>>>
>>> It will propel the project forward.
>>>
>>> Russell Jurney
>>> twitter.com/rjurney
>>> [EMAIL PROTECTED]
>>> datasyndrome.com
>>>
>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>>>
>>>> I think this is the tweet (lacking the entire discussion tree that we
>>>>had
>>>> re git) where I was pointing out that some incubator projects were
>>>>using
>>>> git.
>>>>
>>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>>
>>>>
>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>>> <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> I think this changed, and you are now allowed.  Looking for the
>>>>>tweets.
>>>>>
>>>>> Russell Jurney http://datasyndrome.com
>>>>>
>>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>>>>>wrote:
>>>>>
>>>>>> AFAIK Apache still does not support git as a primary repository.
>>>>>>You
>>>>> can use the git mirror, which Pig does.  If this has changed (or
>>>>>when it
>>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>>>>>>
>>>>>> Alan.
>>>>>>
>>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>>>>>
>>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>>>>>>>this
>>>>> via
>>>>>>> Apache, no? It would be nice to make git the first class citizen of
>>>>>>> choice... forcing developers to use svn to work with pig is just
>>>>>>>another
>>>>>>> barrier, imho. I thought this had been bandied about on Twitter
>>>>>>>and the
>>>>>>> like, but not sure if it's been discussed seriously on the
>>>>>>>listserv.
>>>>>>>
>>>>>>> Would love y'all's opinions on the matter
>>>>>>> Jon
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Note that I'm no longer using my Yahoo! email address. Please email
>>>>me at
>>>> [EMAIL PROTECTED] going forward.*

On 3/20/12 11:22 PM, "Jonathan Coveney" <[EMAIL PROTECTED]> wrote:

>forcing developers to use svn to work with pig is just another
>barrier, imho.

Some might say forcing developers to use git to work with pig is just
another
barrier.
Many people don't know how to use git well (or at all), many people don't
know how to use svn well (or at all).

If people don't know git or svn, they are going to have to learn one or the
other if they want to work with open source projects. It might as well be
git, since that's where things are going.

2012/3/22 Scott Carey <[EMAIL PROTECTED]>

> Apache is currently doing a trial with git as the primary repo using the
> CouchDB project.  Other projects may be able to volunteer to join the
> trial, I'm not sure.
>
> see http://git-wip-us.apache.org/
>
> I suggest that if you are interested in this join the apache
> infrastructure-dev list.
>
>
>
> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>
> >What's the work?
> >
> >Russell Jurney http://datasyndrome.com
> >
> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >
> >> All that's left is for someone to volunteer to do the work.
> >>
> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
> >>wrote:
> >>
> >>> What do we have to do to be the first real project that uses git?
> >>> Let's do that. Or, let's just sink svn to github.
> >>>
> >>> It will propel the project forward.
> >>>
> >>> Russell Jurney
> >>> twitter.com/rjurney
> >>> [EMAIL PROTECTED]
> >>> datasyndrome.com
> >>>
> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I think this is the tweet (lacking the entire discussion tree that we
> >>>>had
> >>>> re git) where I was pointing out that some incubator projects were
> >>>>using
> >>>> git.
> >>>>
> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >>>>
> >>>>
> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >>>> <[EMAIL PROTECTED]>wrote:
> >>>>
> >>>>> I think this changed, and you are now allowed.  Looking for the
> >>>>>tweets.
> >>>>>
> >>>>> Russell Jurney http://datasyndrome.com
> >>>>>
> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
> >>>>>wrote:
> >>>>>
> >>>>>> AFAIK Apache still does not support git as a primary repository.
> >>>>>>You
> >>>>> can use the git mirror, which Pig does.  If this has changed (or
> >>>>>when it
> >>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
> >>>>>>
> >>>>>> Alan.
> >>>>>>
> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >>>>>>
> >>>>>>> Would anyone be opposed to doing this? I think you can apply to do
> >>>>>>>this
> >>>>> via
> >>>>>>> Apache, no? It would be nice to make git the first class citizen of
> >>>>>>> choice... forcing developers to use svn to work with pig is just
> >>>>>>>another
> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
> >>>>>>>and the
> >>>>>>> like, but not sure if it's been discussed seriously on the
> >>>>>>>listserv.
> >>>>>>>
> >>>>>>> Would love y'all's opinions on the matter
> >>>>>>> Jon
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> *Note that I'm no longer using my Yahoo! email address. Please email
> >>>>me at
> >>>> [EMAIL PROTECTED] going forward.*
>
>

This can be done in the future but I don't see there is an urgent need
for that. I'd rather wait for Apache to standardize the process and we
can easily follow and switch, rather than become the first several to
try and solve the infrastructure problem.

Daniel

On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:
> If people don't know git or svn, they are going to have to learn one or the
> other if they want to work with open source projects. It might as well be
> git, since that's where things are going.
>
> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>
>> Apache is currently doing a trial with git as the primary repo using the
>> CouchDB project.  Other projects may be able to volunteer to join the
>> trial, I'm not sure.
>>
>> see http://git-wip-us.apache.org/
>>
>> I suggest that if you are interested in this join the apache
>> infrastructure-dev list.
>>
>>
>>
>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>>
>> >What's the work?
>> >
>> >Russell Jurney http://datasyndrome.com
>> >
>> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>> >
>> >> All that's left is for someone to volunteer to do the work.
>> >>
>> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>> >>wrote:
>> >>
>> >>> What do we have to do to be the first real project that uses git?
>> >>> Let's do that. Or, let's just sink svn to github.
>> >>>
>> >>> It will propel the project forward.
>> >>>
>> >>> Russell Jurney
>> >>> twitter.com/rjurney
>> >>> [EMAIL PROTECTED]
>> >>> datasyndrome.com
>> >>>
>> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
>> >>>
>> >>>> I think this is the tweet (lacking the entire discussion tree that we
>> >>>>had
>> >>>> re git) where I was pointing out that some incubator projects were
>> >>>>using
>> >>>> git.
>> >>>>
>> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
>> >>>>
>> >>>>
>> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>> >>>> <[EMAIL PROTECTED]>wrote:
>> >>>>
>> >>>>> I think this changed, and you are now allowed.  Looking for the
>> >>>>>tweets.
>> >>>>>
>> >>>>> Russell Jurney http://datasyndrome.com
>> >>>>>
>> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>> >>>>>wrote:
>> >>>>>
>> >>>>>> AFAIK Apache still does not support git as a primary repository.
>> >>>>>>You
>> >>>>> can use the git mirror, which Pig does.  If this has changed (or
>> >>>>>when it
>> >>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
>> >>>>>>
>> >>>>>> Alan.
>> >>>>>>
>> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>> >>>>>>
>> >>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>> >>>>>>>this
>> >>>>> via
>> >>>>>>> Apache, no? It would be nice to make git the first class citizen of
>> >>>>>>> choice... forcing developers to use svn to work with pig is just
>> >>>>>>>another
>> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
>> >>>>>>>and the
>> >>>>>>> like, but not sure if it's been discussed seriously on the
>> >>>>>>>listserv.
>> >>>>>>>
>> >>>>>>> Would love y'all's opinions on the matter
>> >>>>>>> Jon
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> *Note that I'm no longer using my Yahoo! email address. Please email
>> >>>>me at
>> >>>> [EMAIL PROTECTED] going forward.*
>>
>>

Thanks, Scott.  Can a committer plz join that list with me and we can hash
this out?

On Thu, Mar 22, 2012 at 10:40 AM, Scott Carey <[EMAIL PROTECTED]>wrote:

> Apache is currently doing a trial with git as the primary repo using the
> CouchDB project.  Other projects may be able to volunteer to join the
> trial, I'm not sure.
>
> see http://git-wip-us.apache.org/
>
> I suggest that if you are interested in this join the apache
> infrastructure-dev list.
>
>
>
> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>
> >What's the work?
> >
> >Russell Jurney http://datasyndrome.com
> >
> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >
> >> All that's left is for someone to volunteer to do the work.
> >>
> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
> >>wrote:
> >>
> >>> What do we have to do to be the first real project that uses git?
> >>> Let's do that. Or, let's just sink svn to github.
> >>>
> >>> It will propel the project forward.
> >>>
> >>> Russell Jurney
> >>> twitter.com/rjurney
> >>> [EMAIL PROTECTED]
> >>> datasyndrome.com
> >>>
> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I think this is the tweet (lacking the entire discussion tree that we
> >>>>had
> >>>> re git) where I was pointing out that some incubator projects were
> >>>>using
> >>>> git.
> >>>>
> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >>>>
> >>>>
> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >>>> <[EMAIL PROTECTED]>wrote:
> >>>>
> >>>>> I think this changed, and you are now allowed.  Looking for the
> >>>>>tweets.
> >>>>>
> >>>>> Russell Jurney http://datasyndrome.com
> >>>>>
> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
> >>>>>wrote:
> >>>>>
> >>>>>> AFAIK Apache still does not support git as a primary repository.
> >>>>>>You
> >>>>> can use the git mirror, which Pig does.  If this has changed (or
> >>>>>when it
> >>>>> does), I'm +0 on changing, by which I mean I don't care which we use.
> >>>>>>
> >>>>>> Alan.
> >>>>>>
> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >>>>>>
> >>>>>>> Would anyone be opposed to doing this? I think you can apply to do
> >>>>>>>this
> >>>>> via
> >>>>>>> Apache, no? It would be nice to make git the first class citizen of
> >>>>>>> choice... forcing developers to use svn to work with pig is just
> >>>>>>>another
> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
> >>>>>>>and the
> >>>>>>> like, but not sure if it's been discussed seriously on the
> >>>>>>>listserv.
> >>>>>>>
> >>>>>>> Would love y'all's opinions on the matter
> >>>>>>> Jon
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> *Note that I'm no longer using my Yahoo! email address. Please email
> >>>>me at
> >>>> [EMAIL PROTECTED] going forward.*
>
>
--
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

Uhhh how do you even get on the infrastructure-dev list?  Can't find
link/instructions.  Feeling dumb.

On Thu, Mar 22, 2012 at 2:02 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:

> Thanks, Scott.  Can a committer plz join that list with me and we can hash
> this out?
>
>
> On Thu, Mar 22, 2012 at 10:40 AM, Scott Carey <[EMAIL PROTECTED]>wrote:
>
>> Apache is currently doing a trial with git as the primary repo using the
>> CouchDB project.  Other projects may be able to volunteer to join the
>> trial, I'm not sure.
>>
>> see http://git-wip-us.apache.org/
>>
>> I suggest that if you are interested in this join the apache
>> infrastructure-dev list.
>>
>>
>>
>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>>
>> >What's the work?
>> >
>> >Russell Jurney http://datasyndrome.com
>> >
>> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>> >
>> >> All that's left is for someone to volunteer to do the work.
>> >>
>> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>> >>wrote:
>> >>
>> >>> What do we have to do to be the first real project that uses git?
>> >>> Let's do that. Or, let's just sink svn to github.
>> >>>
>> >>> It will propel the project forward.
>> >>>
>> >>> Russell Jurney
>> >>> twitter.com/rjurney
>> >>> [EMAIL PROTECTED]
>> >>> datasyndrome.com
>> >>>
>> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
>> wrote:
>> >>>
>> >>>> I think this is the tweet (lacking the entire discussion tree that we
>> >>>>had
>> >>>> re git) where I was pointing out that some incubator projects were
>> >>>>using
>> >>>> git.
>> >>>>
>> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
>> >>>>
>> >>>>
>> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>> >>>> <[EMAIL PROTECTED]>wrote:
>> >>>>
>> >>>>> I think this changed, and you are now allowed.  Looking for the
>> >>>>>tweets.
>> >>>>>
>> >>>>> Russell Jurney http://datasyndrome.com
>> >>>>>
>> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>> >>>>>wrote:
>> >>>>>
>> >>>>>> AFAIK Apache still does not support git as a primary repository.
>> >>>>>>You
>> >>>>> can use the git mirror, which Pig does.  If this has changed (or
>> >>>>>when it
>> >>>>> does), I'm +0 on changing, by which I mean I don't care which we
>> use.
>> >>>>>>
>> >>>>>> Alan.
>> >>>>>>
>> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>> >>>>>>
>> >>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>> >>>>>>>this
>> >>>>> via
>> >>>>>>> Apache, no? It would be nice to make git the first class citizen
>> of
>> >>>>>>> choice... forcing developers to use svn to work with pig is just
>> >>>>>>>another
>> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
>> >>>>>>>and the
>> >>>>>>> like, but not sure if it's been discussed seriously on the
>> >>>>>>>listserv.
>> >>>>>>>
>> >>>>>>> Would love y'all's opinions on the matter
>> >>>>>>> Jon
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> *Note that I'm no longer using my Yahoo! email address. Please email
>> >>>>me at
>> >>>> [EMAIL PROTECTED] going forward.*
>>
>>
>
>
> --
> Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.
> com
>

--
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

[EMAIL PROTECTED]

On Thu, Mar 22, 2012 at 2:06 PM, Russell Jurney
<[EMAIL PROTECTED]> wrote:
> Uhhh how do you even get on the infrastructure-dev list?  Can't find
> link/instructions.  Feeling dumb.
>
> On Thu, Mar 22, 2012 at 2:02 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:
>
>> Thanks, Scott.  Can a committer plz join that list with me and we can hash
>> this out?
>>
>>
>> On Thu, Mar 22, 2012 at 10:40 AM, Scott Carey <[EMAIL PROTECTED]>wrote:
>>
>>> Apache is currently doing a trial with git as the primary repo using the
>>> CouchDB project.  Other projects may be able to volunteer to join the
>>> trial, I'm not sure.
>>>
>>> see http://git-wip-us.apache.org/
>>>
>>> I suggest that if you are interested in this join the apache
>>> infrastructure-dev list.
>>>
>>>
>>>
>>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>>>
>>> >What's the work?
>>> >
>>> >Russell Jurney http://datasyndrome.com
>>> >
>>> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>>> >
>>> >> All that's left is for someone to volunteer to do the work.
>>> >>
>>> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <[EMAIL PROTECTED]>
>>> >>wrote:
>>> >>
>>> >>> What do we have to do to be the first real project that uses git?
>>> >>> Let's do that. Or, let's just sink svn to github.
>>> >>>
>>> >>> It will propel the project forward.
>>> >>>
>>> >>> Russell Jurney
>>> >>> twitter.com/rjurney
>>> >>> [EMAIL PROTECTED]
>>> >>> datasyndrome.com
>>> >>>
>>> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
>>> wrote:
>>> >>>
>>> >>>> I think this is the tweet (lacking the entire discussion tree that we
>>> >>>>had
>>> >>>> re git) where I was pointing out that some incubator projects were
>>> >>>>using
>>> >>>> git.
>>> >>>>
>>> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>> >>>>
>>> >>>>
>>> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>> >>>> <[EMAIL PROTECTED]>wrote:
>>> >>>>
>>> >>>>> I think this changed, and you are now allowed.  Looking for the
>>> >>>>>tweets.
>>> >>>>>
>>> >>>>> Russell Jurney http://datasyndrome.com
>>> >>>>>
>>> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>>> >>>>>wrote:
>>> >>>>>
>>> >>>>>> AFAIK Apache still does not support git as a primary repository.
>>> >>>>>>You
>>> >>>>> can use the git mirror, which Pig does.  If this has changed (or
>>> >>>>>when it
>>> >>>>> does), I'm +0 on changing, by which I mean I don't care which we
>>> use.
>>> >>>>>>
>>> >>>>>> Alan.
>>> >>>>>>
>>> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>>> >>>>>>
>>> >>>>>>> Would anyone be opposed to doing this? I think you can apply to do
>>> >>>>>>>this
>>> >>>>> via
>>> >>>>>>> Apache, no? It would be nice to make git the first class citizen
>>> of
>>> >>>>>>> choice... forcing developers to use svn to work with pig is just
>>> >>>>>>>another
>>> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
>>> >>>>>>>and the
>>> >>>>>>> like, but not sure if it's been discussed seriously on the
>>> >>>>>>>listserv.
>>> >>>>>>>
>>> >>>>>>> Would love y'all's opinions on the matter
>>> >>>>>>> Jon
>>> >>>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> *Note that I'm no longer using my Yahoo! email address. Please email
>>> >>>>me at
>>> >>>> [EMAIL PROTECTED] going forward.*
>>>
>>>
>>
>>
>> --
>> Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.
>> com
>>
>
>
>
> --
> Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

If there is already a trial going, the project would benefit from switching
to git, as we could then (I think?) accept pull requests on github.  Maybe
not, I'm not familiar with integrating multiple gits.  Barrier of entry for
contributing would then drop dramatically, making happy for all.

On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:

> This can be done in the future but I don't see there is an urgent need
> for that. I'd rather wait for Apache to standardize the process and we
> can easily follow and switch, rather than become the first several to
> try and solve the infrastructure problem.
>
> Daniel
>
> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> wrote:
> > If people don't know git or svn, they are going to have to learn one or
> the
> > other if they want to work with open source projects. It might as well be
> > git, since that's where things are going.
> >
> > 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >
> >> Apache is currently doing a trial with git as the primary repo using the
> >> CouchDB project.  Other projects may be able to volunteer to join the
> >> trial, I'm not sure.
> >>
> >> see http://git-wip-us.apache.org/
> >>
> >> I suggest that if you are interested in this join the apache
> >> infrastructure-dev list.
> >>
> >>
> >>
> >> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
> >>
> >> >What's the work?
> >> >
> >> >Russell Jurney http://datasyndrome.com
> >> >
> >> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> wrote:
> >> >
> >> >> All that's left is for someone to volunteer to do the work.
> >> >>
> >> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
> [EMAIL PROTECTED]>
> >> >>wrote:
> >> >>
> >> >>> What do we have to do to be the first real project that uses git?
> >> >>> Let's do that. Or, let's just sink svn to github.
> >> >>>
> >> >>> It will propel the project forward.
> >> >>>
> >> >>> Russell Jurney
> >> >>> twitter.com/rjurney
> >> >>> [EMAIL PROTECTED]
> >> >>> datasyndrome.com
> >> >>>
> >> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
> wrote:
> >> >>>
> >> >>>> I think this is the tweet (lacking the entire discussion tree that
> we
> >> >>>>had
> >> >>>> re git) where I was pointing out that some incubator projects were
> >> >>>>using
> >> >>>> git.
> >> >>>>
> >> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >> >>>>
> >> >>>>
> >> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >> >>>> <[EMAIL PROTECTED]>wrote:
> >> >>>>
> >> >>>>> I think this changed, and you are now allowed.  Looking for the
> >> >>>>>tweets.
> >> >>>>>
> >> >>>>> Russell Jurney http://datasyndrome.com
> >> >>>>>
> >> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
> >> >>>>>wrote:
> >> >>>>>
> >> >>>>>> AFAIK Apache still does not support git as a primary repository.
> >> >>>>>>You
> >> >>>>> can use the git mirror, which Pig does.  If this has changed (or
> >> >>>>>when it
> >> >>>>> does), I'm +0 on changing, by which I mean I don't care which we
> use.
> >> >>>>>>
> >> >>>>>> Alan.
> >> >>>>>>
> >> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
> >> >>>>>>
> >> >>>>>>> Would anyone be opposed to doing this? I think you can apply to
> do
> >> >>>>>>>this
> >> >>>>> via
> >> >>>>>>> Apache, no? It would be nice to make git the first class
> citizen of
> >> >>>>>>> choice... forcing developers to use svn to work with pig is just
> >> >>>>>>>another
> >> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter
> >> >>>>>>>and the
> >> >>>>>>> like, but not sure if it's been discussed seriously on the
> >> >>>>>>>listserv.
> >> >>>>>>>
> >> >>>>>>> Would love y'all's opinions on the matter
> >> >>>>>>> Jon
> >> >>>>>>
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> *Note that I'm no longer using my Yahoo! email address. Please
> email
> >> >>>>me at
> >> >>>> [EMAIL PROTECTED] going forward.*

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

There is downside for switching now:
* Lose Jira integration
* Lose review board integration
* Lose code search integration

It would be more beneficial if we get more Apache infrastructure
support before we switch.

On Thu, Mar 22, 2012 at 2:08 PM, Russell Jurney
<[EMAIL PROTECTED]> wrote:
> If there is already a trial going, the project would benefit from switching
> to git, as we could then (I think?) accept pull requests on github.  Maybe
> not, I'm not familiar with integrating multiple gits.  Barrier of entry for
> contributing would then drop dramatically, making happy for all.
>
> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:
>
>> This can be done in the future but I don't see there is an urgent need
>> for that. I'd rather wait for Apache to standardize the process and we
>> can easily follow and switch, rather than become the first several to
>> try and solve the infrastructure problem.
>>
>> Daniel
>>
>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
>> wrote:
>> > If people don't know git or svn, they are going to have to learn one or
>> the
>> > other if they want to work with open source projects. It might as well be
>> > git, since that's where things are going.
>> >
>> > 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>> >
>> >> Apache is currently doing a trial with git as the primary repo using the
>> >> CouchDB project.  Other projects may be able to volunteer to join the
>> >> trial, I'm not sure.
>> >>
>> >> see http://git-wip-us.apache.org/
>> >>
>> >> I suggest that if you are interested in this join the apache
>> >> infrastructure-dev list.
>> >>
>> >>
>> >>
>> >> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>> >>
>> >> >What's the work?
>> >> >
>> >> >Russell Jurney http://datasyndrome.com
>> >> >
>> >> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> wrote:
>> >> >
>> >> >> All that's left is for someone to volunteer to do the work.
>> >> >>
>> >> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
>> [EMAIL PROTECTED]>
>> >> >>wrote:
>> >> >>
>> >> >>> What do we have to do to be the first real project that uses git?
>> >> >>> Let's do that. Or, let's just sink svn to github.
>> >> >>>
>> >> >>> It will propel the project forward.
>> >> >>>
>> >> >>> Russell Jurney
>> >> >>> twitter.com/rjurney
>> >> >>> [EMAIL PROTECTED]
>> >> >>> datasyndrome.com
>> >> >>>
>> >> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
>> wrote:
>> >> >>>
>> >> >>>> I think this is the tweet (lacking the entire discussion tree that
>> we
>> >> >>>>had
>> >> >>>> re git) where I was pointing out that some incubator projects were
>> >> >>>>using
>> >> >>>> git.
>> >> >>>>
>> >> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
>> >> >>>>
>> >> >>>>
>> >> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>> >> >>>> <[EMAIL PROTECTED]>wrote:
>> >> >>>>
>> >> >>>>> I think this changed, and you are now allowed.  Looking for the
>> >> >>>>>tweets.
>> >> >>>>>
>> >> >>>>> Russell Jurney http://datasyndrome.com
>> >> >>>>>
>> >> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>> >> >>>>>wrote:
>> >> >>>>>
>> >> >>>>>> AFAIK Apache still does not support git as a primary repository.
>> >> >>>>>>You
>> >> >>>>> can use the git mirror, which Pig does.  If this has changed (or
>> >> >>>>>when it
>> >> >>>>> does), I'm +0 on changing, by which I mean I don't care which we
>> use.
>> >> >>>>>>
>> >> >>>>>> Alan.
>> >> >>>>>>
>> >> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>> >> >>>>>>
>> >> >>>>>>> Would anyone be opposed to doing this? I think you can apply to
>> do
>> >> >>>>>>>this
>> >> >>>>> via
>> >> >>>>>>> Apache, no? It would be nice to make git the first class
>> citizen of
>> >> >>>>>>> choice... forcing developers to use svn to work with pig is just
>> >> >>>>>>>another
>> >> >>>>>>> barrier, imho. I thought this had been bandied about on Twitter

Wait, this was discussed in that thread, and on twitter when I knocked
JIRA/svn.  We don't have to lose JIRA integration.  You can specify a url
to the git code in the tickets.  This is SO much better than uploading a
patch that it is a huge win, not a loss.

On Thu, Mar 22, 2012 at 2:18 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:

> There is downside for switching now:
> * Lose Jira integration
> * Lose review board integration
> * Lose code search integration
>
> It would be more beneficial if we get more Apache infrastructure
> support before we switch.
>
> On Thu, Mar 22, 2012 at 2:08 PM, Russell Jurney
> <[EMAIL PROTECTED]> wrote:
> > If there is already a trial going, the project would benefit from
> switching
> > to git, as we could then (I think?) accept pull requests on github.
>  Maybe
> > not, I'm not familiar with integrating multiple gits.  Barrier of entry
> for
> > contributing would then drop dramatically, making happy for all.
> >
> > On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> wrote:
> >
> >> This can be done in the future but I don't see there is an urgent need
> >> for that. I'd rather wait for Apache to standardize the process and we
> >> can easily follow and switch, rather than become the first several to
> >> try and solve the infrastructure problem.
> >>
> >> Daniel
> >>
> >> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> >> wrote:
> >> > If people don't know git or svn, they are going to have to learn one
> or
> >> the
> >> > other if they want to work with open source projects. It might as
> well be
> >> > git, since that's where things are going.
> >> >
> >> > 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >> >
> >> >> Apache is currently doing a trial with git as the primary repo using
> the
> >> >> CouchDB project.  Other projects may be able to volunteer to join the
> >> >> trial, I'm not sure.
> >> >>
> >> >> see http://git-wip-us.apache.org/
> >> >>
> >> >> I suggest that if you are interested in this join the apache
> >> >> infrastructure-dev list.
> >> >>
> >> >>
> >> >>
> >> >> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> wrote:
> >> >>
> >> >> >What's the work?
> >> >> >
> >> >> >Russell Jurney http://datasyndrome.com
> >> >> >
> >> >> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >> wrote:
> >> >> >
> >> >> >> All that's left is for someone to volunteer to do the work.
> >> >> >>
> >> >> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
> >> [EMAIL PROTECTED]>
> >> >> >>wrote:
> >> >> >>
> >> >> >>> What do we have to do to be the first real project that uses git?
> >> >> >>> Let's do that. Or, let's just sink svn to github.
> >> >> >>>
> >> >> >>> It will propel the project forward.
> >> >> >>>
> >> >> >>> Russell Jurney
> >> >> >>> twitter.com/rjurney
> >> >> >>> [EMAIL PROTECTED]
> >> >> >>> datasyndrome.com
> >> >> >>>
> >> >> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
> >> wrote:
> >> >> >>>
> >> >> >>>> I think this is the tweet (lacking the entire discussion tree
> that
> >> we
> >> >> >>>>had
> >> >> >>>> re git) where I was pointing out that some incubator projects
> were
> >> >> >>>>using
> >> >> >>>> git.
> >> >> >>>>
> >> >> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >> >> >>>> <[EMAIL PROTECTED]>wrote:
> >> >> >>>>
> >> >> >>>>> I think this changed, and you are now allowed.  Looking for the
> >> >> >>>>>tweets.
> >> >> >>>>>
> >> >> >>>>> Russell Jurney http://datasyndrome.com
> >> >> >>>>>
> >> >> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]
> >
> >> >> >>>>>wrote:
> >> >> >>>>>
> >> >> >>>>>> AFAIK Apache still does not support git as a primary
> repository.
> >> >> >>>>>>You
> >> >> >>>>> can use the git mirror, which Pig does.  If this has changed
> (or
> >> >> >>>>>when it
> >> >> >>>>> does), I'm +0 on changing, by which I mean I don't care which

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

There is a legal issue as well. Uploading a patch to JIRA requires the
user to grant apache license to use the code.  A pull request from github
does not.
This is all being hashed out elsewhere, none of us here are experts.
On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:

>If there is already a trial going, the project would benefit from
>switching
>to git, as we could then (I think?) accept pull requests on github.  Maybe
>not, I'm not familiar with integrating multiple gits.  Barrier of entry
>for
>contributing would then drop dramatically, making happy for all.
>
>On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:
>
>> This can be done in the future but I don't see there is an urgent need
>> for that. I'd rather wait for Apache to standardize the process and we
>> can easily follow and switch, rather than become the first several to
>> try and solve the infrastructure problem.
>>
>> Daniel
>>
>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
>> wrote:
>> > If people don't know git or svn, they are going to have to learn one
>>or
>> the
>> > other if they want to work with open source projects. It might as
>>well be
>> > git, since that's where things are going.
>> >
>> > 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>> >
>> >> Apache is currently doing a trial with git as the primary repo using
>>the
>> >> CouchDB project.  Other projects may be able to volunteer to join the
>> >> trial, I'm not sure.
>> >>
>> >> see http://git-wip-us.apache.org/
>> >>
>> >> I suggest that if you are interested in this join the apache
>> >> infrastructure-dev list.
>> >>
>> >>
>> >>
>> >> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>>wrote:
>> >>
>> >> >What's the work?
>> >> >
>> >> >Russell Jurney http://datasyndrome.com
>> >> >
>> >> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> wrote:
>> >> >
>> >> >> All that's left is for someone to volunteer to do the work.
>> >> >>
>> >> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
>> [EMAIL PROTECTED]>
>> >> >>wrote:
>> >> >>
>> >> >>> What do we have to do to be the first real project that uses git?
>> >> >>> Let's do that. Or, let's just sink svn to github.
>> >> >>>
>> >> >>> It will propel the project forward.
>> >> >>>
>> >> >>> Russell Jurney
>> >> >>> twitter.com/rjurney
>> >> >>> [EMAIL PROTECTED]
>> >> >>> datasyndrome.com
>> >> >>>
>> >> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
>> wrote:
>> >> >>>
>> >> >>>> I think this is the tweet (lacking the entire discussion tree
>>that
>> we
>> >> >>>>had
>> >> >>>> re git) where I was pointing out that some incubator projects
>>were
>> >> >>>>using
>> >> >>>> git.
>> >> >>>>
>> >> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
>> >> >>>>
>> >> >>>>
>> >> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>> >> >>>> <[EMAIL PROTECTED]>wrote:
>> >> >>>>
>> >> >>>>> I think this changed, and you are now allowed.  Looking for the
>> >> >>>>>tweets.
>> >> >>>>>
>> >> >>>>> Russell Jurney http://datasyndrome.com
>> >> >>>>>
>> >> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]>
>> >> >>>>>wrote:
>> >> >>>>>
>> >> >>>>>> AFAIK Apache still does not support git as a primary
>>repository.
>> >> >>>>>>You
>> >> >>>>> can use the git mirror, which Pig does.  If this has changed
>>(or
>> >> >>>>>when it
>> >> >>>>> does), I'm +0 on changing, by which I mean I don't care which
>>we
>> use.
>> >> >>>>>>
>> >> >>>>>> Alan.
>> >> >>>>>>
>> >> >>>>>> On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
>> >> >>>>>>
>> >> >>>>>>> Would anyone be opposed to doing this? I think you can apply
>>to
>> do
>> >> >>>>>>>this
>> >> >>>>> via
>> >> >>>>>>> Apache, no? It would be nice to make git the first class
>> citizen of
>> >> >>>>>>> choice... forcing developers to use svn to work with pig is
>>just
>> >> >>>>>>>another
>> >> >>>>>>> barrier, imho. I thought this had been bandied about on

That is fine.  Only committers can merge pull requests.  Not a problem.

I've never signed anything, and committers take my patches.  Works the same.

On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]>wrote:

>
> There is a legal issue as well. Uploading a patch to JIRA requires the
> user to grant apache license to use the code.  A pull request from github
> does not.
> This is all being hashed out elsewhere, none of us here are experts.
>
>
>
>
> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>
> >If there is already a trial going, the project would benefit from
> >switching
> >to git, as we could then (I think?) accept pull requests on github.  Maybe
> >not, I'm not familiar with integrating multiple gits.  Barrier of entry
> >for
> >contributing would then drop dramatically, making happy for all.
> >
> >On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> wrote:
> >
> >> This can be done in the future but I don't see there is an urgent need
> >> for that. I'd rather wait for Apache to standardize the process and we
> >> can easily follow and switch, rather than become the first several to
> >> try and solve the infrastructure problem.
> >>
> >> Daniel
> >>
> >> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> >> wrote:
> >> > If people don't know git or svn, they are going to have to learn one
> >>or
> >> the
> >> > other if they want to work with open source projects. It might as
> >>well be
> >> > git, since that's where things are going.
> >> >
> >> > 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >> >
> >> >> Apache is currently doing a trial with git as the primary repo using
> >>the
> >> >> CouchDB project.  Other projects may be able to volunteer to join the
> >> >> trial, I'm not sure.
> >> >>
> >> >> see http://git-wip-us.apache.org/
> >> >>
> >> >> I suggest that if you are interested in this join the apache
> >> >> infrastructure-dev list.
> >> >>
> >> >>
> >> >>
> >> >> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> >>wrote:
> >> >>
> >> >> >What's the work?
> >> >> >
> >> >> >Russell Jurney http://datasyndrome.com
> >> >> >
> >> >> >On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >> wrote:
> >> >> >
> >> >> >> All that's left is for someone to volunteer to do the work.
> >> >> >>
> >> >> >> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
> >> [EMAIL PROTECTED]>
> >> >> >>wrote:
> >> >> >>
> >> >> >>> What do we have to do to be the first real project that uses git?
> >> >> >>> Let's do that. Or, let's just sink svn to github.
> >> >> >>>
> >> >> >>> It will propel the project forward.
> >> >> >>>
> >> >> >>> Russell Jurney
> >> >> >>> twitter.com/rjurney
> >> >> >>> [EMAIL PROTECTED]
> >> >> >>> datasyndrome.com
> >> >> >>>
> >> >> >>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
> >> wrote:
> >> >> >>>
> >> >> >>>> I think this is the tweet (lacking the entire discussion tree
> >>that
> >> we
> >> >> >>>>had
> >> >> >>>> re git) where I was pointing out that some incubator projects
> >>were
> >> >> >>>>using
> >> >> >>>> git.
> >> >> >>>>
> >> >> >>>> https://twitter.com/#!/billgraham/status/174744199407738880
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
> >> >> >>>> <[EMAIL PROTECTED]>wrote:
> >> >> >>>>
> >> >> >>>>> I think this changed, and you are now allowed.  Looking for the
> >> >> >>>>>tweets.
> >> >> >>>>>
> >> >> >>>>> Russell Jurney http://datasyndrome.com
> >> >> >>>>>
> >> >> >>>>> On Mar 21, 2012, at 9:36 AM, Alan Gates <[EMAIL PROTECTED]
> >
> >> >> >>>>>wrote:
> >> >> >>>>>
> >> >> >>>>>> AFAIK Apache still does not support git as a primary
> >>repository.
> >> >> >>>>>>You
> >> >> >>>>> can use the git mirror, which Pig does.  If this has changed
> >>(or
> >> >> >>>>>when it
> >> >> >>>>> does), I'm +0 on changing, by which I mean I don't care which
> >>we
> >> use.
> >> >> >>>>>>
>

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

There is a check box you check when you upload a patch. If we committed without verifying you checked it, thats an unfortunate oversight.

No, you cant send a pull request via github to apache. That's a github (commercial entity) feature, not a git (open source vcs) feature.

Yes you can post a link on a Jira and ask people for review prior to submitting a formal patch.  No that's not review board or Jira integration.

On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]> wrote:

> That is fine.  Only committers can merge pull requests.  Not a problem.
>
> I've never signed anything, and committers take my patches.  Works the same.
>
> On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]>wrote:
>
>>
>> There is a legal issue as well. Uploading a patch to JIRA requires the
>> user to grant apache license to use the code.  A pull request from github
>> does not.
>> This is all being hashed out elsewhere, none of us here are experts.
>>
>>
>>
>>
>> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
>>
>>> If there is already a trial going, the project would benefit from
>>> switching
>>> to git, as we could then (I think?) accept pull requests on github.  Maybe
>>> not, I'm not familiar with integrating multiple gits.  Barrier of entry
>>> for
>>> contributing would then drop dramatically, making happy for all.
>>>
>>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
>> wrote:
>>>
>>>> This can be done in the future but I don't see there is an urgent need
>>>> for that. I'd rather wait for Apache to standardize the process and we
>>>> can easily follow and switch, rather than become the first several to
>>>> try and solve the infrastructure problem.
>>>>
>>>> Daniel
>>>>
>>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <[EMAIL PROTECTED]>
>>>> wrote:
>>>>> If people don't know git or svn, they are going to have to learn one
>>>> or
>>>> the
>>>>> other if they want to work with open source projects. It might as
>>>> well be
>>>>> git, since that's where things are going.
>>>>>
>>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>>>>>
>>>>>> Apache is currently doing a trial with git as the primary repo using
>>>> the
>>>>>> CouchDB project.  Other projects may be able to volunteer to join the
>>>>>> trial, I'm not sure.
>>>>>>
>>>>>> see http://git-wip-us.apache.org/
>>>>>>
>>>>>> I suggest that if you are interested in this join the apache
>>>>>> infrastructure-dev list.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>
>>>>>>> What's the work?
>>>>>>>
>>>>>>> Russell Jurney http://datasyndrome.com
>>>>>>>
>>>>>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>>
>>>>>>>> All that's left is for someone to volunteer to do the work.
>>>>>>>>
>>>>>>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
>>>> [EMAIL PROTECTED]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> What do we have to do to be the first real project that uses git?
>>>>>>>>> Let's do that. Or, let's just sink svn to github.
>>>>>>>>>
>>>>>>>>> It will propel the project forward.
>>>>>>>>>
>>>>>>>>> Russell Jurney
>>>>>>>>> twitter.com/rjurney
>>>>>>>>> [EMAIL PROTECTED]
>>>>>>>>> datasyndrome.com
>>>>>>>>>
>>>>>>>>> On Mar 21, 2012, at 9:04 PM, Bill Graham <[EMAIL PROTECTED]>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I think this is the tweet (lacking the entire discussion tree
>>>> that
>>>> we
>>>>>>>>>> had
>>>>>>>>>> re git) where I was pointing out that some incubator projects
>>>> were
>>>>>>>>>> using
>>>>>>>>>> git.
>>>>>>>>>>
>>>>>>>>>> https://twitter.com/#!/billgraham/status/174744199407738880
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
>>>>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>>>>
>>>>>>>>>>> I think this changed, and you are now allowed.  Looking for the
>>>>>>>>>>> tweets.
>>>>>>>>>>>
>>>>>>>>>>

My 2 cents, based on the S4 project experience so far (they have git) is +1
but later.

The process with git is still a bit fuzzy and not fully integrated and
standardized like the one with svn.
I personally use git for all my dev work with Pig, but then switch to svn
to generate the final patch. A bit cumbersome but not so bad.

Switching now will generate confusion and is not that urgent in my humble
opinion.

Cheers,
--
Gianmarco

On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> There is a check box you check when you upload a patch. If we committed
> without verifying you checked it, thats an unfortunate oversight.
>
> No, you cant send a pull request via github to apache. That's a github
> (commercial entity) feature, not a git (open source vcs) feature.
>
> Yes you can post a link on a Jira and ask people for review prior to
> submitting a formal patch.  No that's not review board or Jira integration.
>
>
>
> On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
> wrote:
>
> > That is fine.  Only committers can merge pull requests.  Not a problem.
> >
> > I've never signed anything, and committers take my patches.  Works the
> same.
> >
> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
> >wrote:
> >
> >>
> >> There is a legal issue as well. Uploading a patch to JIRA requires the
> >> user to grant apache license to use the code.  A pull request from
> github
> >> does not.
> >> This is all being hashed out elsewhere, none of us here are experts.
> >>
> >>
> >>
> >>
> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]> wrote:
> >>
> >>> If there is already a trial going, the project would benefit from
> >>> switching
> >>> to git, as we could then (I think?) accept pull requests on github.
>  Maybe
> >>> not, I'm not familiar with integrating multiple gits.  Barrier of entry
> >>> for
> >>> contributing would then drop dramatically, making happy for all.
> >>>
> >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> >> wrote:
> >>>
> >>>> This can be done in the future but I don't see there is an urgent need
> >>>> for that. I'd rather wait for Apache to standardize the process and we
> >>>> can easily follow and switch, rather than become the first several to
> >>>> try and solve the infrastructure problem.
> >>>>
> >>>> Daniel
> >>>>
> >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
> [EMAIL PROTECTED]>
> >>>> wrote:
> >>>>> If people don't know git or svn, they are going to have to learn one
> >>>> or
> >>>> the
> >>>>> other if they want to work with open source projects. It might as
> >>>> well be
> >>>>> git, since that's where things are going.
> >>>>>
> >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >>>>>
> >>>>>> Apache is currently doing a trial with git as the primary repo using
> >>>> the
> >>>>>> CouchDB project.  Other projects may be able to volunteer to join
> the
> >>>>>> trial, I'm not sure.
> >>>>>>
> >>>>>> see http://git-wip-us.apache.org/
> >>>>>>
> >>>>>> I suggest that if you are interested in this join the apache
> >>>>>> infrastructure-dev list.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> >>>> wrote:
> >>>>>>
> >>>>>>> What's the work?
> >>>>>>>
> >>>>>>> Russell Jurney http://datasyndrome.com
> >>>>>>>
> >>>>>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >>>> wrote:
> >>>>>>>
> >>>>>>>> All that's left is for someone to volunteer to do the work.
> >>>>>>>>
> >>>>>>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
> >>>> [EMAIL PROTECTED]>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> What do we have to do to be the first real project that uses git?
> >>>>>>>>> Let's do that. Or, let's just sink svn to github.
> >>>>>>>>>
> >>>>>>>>> It will propel the project forward.
> >>>>>>>>>
> >>>>>>>>> Russell Jurney
> >>>>>>>>> twitter.com/rjurney
> >>>>>>>>> [EMAIL PROTECTED]
> >>>>>>>>> datasyndrome.com

Gianmarco, can you elaborate a bit on the fuzziness?

On Tue, Mar 27, 2012 at 2:26 AM, Gianmarco De Francisci Morales <
[EMAIL PROTECTED]> wrote:

> My 2 cents, based on the S4 project experience so far (they have git) is +1
> but later.
>
> The process with git is still a bit fuzzy and not fully integrated and
> standardized like the one with svn.
> I personally use git for all my dev work with Pig, but then switch to svn
> to generate the final patch. A bit cumbersome but not so bad.
>
> Switching now will generate confusion and is not that urgent in my humble
> opinion.
>
> Cheers,
> --
> Gianmarco
>
>
>
> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
> > There is a check box you check when you upload a patch. If we committed
> > without verifying you checked it, thats an unfortunate oversight.
> >
> > No, you cant send a pull request via github to apache. That's a github
> > (commercial entity) feature, not a git (open source vcs) feature.
> >
> > Yes you can post a link on a Jira and ask people for review prior to
> > submitting a formal patch.  No that's not review board or Jira
> integration.
> >
> >
> >
> > On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
> > wrote:
> >
> > > That is fine.  Only committers can merge pull requests.  Not a problem.
> > >
> > > I've never signed anything, and committers take my patches.  Works the
> > same.
> > >
> > > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
> > >wrote:
> > >
> > >>
> > >> There is a legal issue as well. Uploading a patch to JIRA requires the
> > >> user to grant apache license to use the code.  A pull request from
> > github
> > >> does not.
> > >> This is all being hashed out elsewhere, none of us here are experts.
> > >>
> > >>
> > >>
> > >>
> > >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> wrote:
> > >>
> > >>> If there is already a trial going, the project would benefit from
> > >>> switching
> > >>> to git, as we could then (I think?) accept pull requests on github.
> >  Maybe
> > >>> not, I'm not familiar with integrating multiple gits.  Barrier of
> entry
> > >>> for
> > >>> contributing would then drop dramatically, making happy for all.
> > >>>
> > >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> > >> wrote:
> > >>>
> > >>>> This can be done in the future but I don't see there is an urgent
> need
> > >>>> for that. I'd rather wait for Apache to standardize the process and
> we
> > >>>> can easily follow and switch, rather than become the first several
> to
> > >>>> try and solve the infrastructure problem.
> > >>>>
> > >>>> Daniel
> > >>>>
> > >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
> > [EMAIL PROTECTED]>
> > >>>> wrote:
> > >>>>> If people don't know git or svn, they are going to have to learn
> one
> > >>>> or
> > >>>> the
> > >>>>> other if they want to work with open source projects. It might as
> > >>>> well be
> > >>>>> git, since that's where things are going.
> > >>>>>
> > >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> > >>>>>
> > >>>>>> Apache is currently doing a trial with git as the primary repo
> using
> > >>>> the
> > >>>>>> CouchDB project.  Other projects may be able to volunteer to join
> > the
> > >>>>>> trial, I'm not sure.
> > >>>>>>
> > >>>>>> see http://git-wip-us.apache.org/
> > >>>>>>
> > >>>>>> I suggest that if you are interested in this join the apache
> > >>>>>> infrastructure-dev list.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> > >>>> wrote:
> > >>>>>>
> > >>>>>>> What's the work?
> > >>>>>>>
> > >>>>>>> Russell Jurney http://datasyndrome.com
> > >>>>>>>
> > >>>>>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> > >>>> wrote:
> > >>>>>>>
> > >>>>>>>> All that's left is for someone to volunteer to do the work.
> > >>>>>>>>
> > >>>>>>>> On Mar 21, 2012, at 9:17 PM, Russell Jurney <
> > >>>> [EMAIL PROTECTED]>

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

The fact is that git does not impose a development model, so it requires a
bit more self discipline compared to svn.
For example, let's say you create one branch for every Jira.
And imagine you want to keep posting patches to Jira so that people can
download and apply them, or have an equivalent.
The patch in git would be the diff between the last commit before the merge
and the start of the branch.
But then you must be very careful with not cross merging among branches, no
cherry-picking, and be very careful with rebasing.
What do you do if your brach cannot merge and you need to rebase it?
What if other people had branched off your branch and you rebase it?

These are not issues that cannot be solved but it takes a bit of discipline
and thought on how to design and integrate the new development model.

Cheers,
--
Gianmarco

On Tue, Mar 27, 2012 at 11:36, Russell Jurney <[EMAIL PROTECTED]>wrote:

> Gianmarco, can you elaborate a bit on the fuzziness?
>
> On Tue, Mar 27, 2012 at 2:26 AM, Gianmarco De Francisci Morales <
> [EMAIL PROTECTED]> wrote:
>
> > My 2 cents, based on the S4 project experience so far (they have git) is
> +1
> > but later.
> >
> > The process with git is still a bit fuzzy and not fully integrated and
> > standardized like the one with svn.
> > I personally use git for all my dev work with Pig, but then switch to svn
> > to generate the final patch. A bit cumbersome but not so bad.
> >
> > Switching now will generate confusion and is not that urgent in my humble
> > opinion.
> >
> > Cheers,
> > --
> > Gianmarco
> >
> >
> >
> > On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> wrote:
> >
> > > There is a check box you check when you upload a patch. If we committed
> > > without verifying you checked it, thats an unfortunate oversight.
> > >
> > > No, you cant send a pull request via github to apache. That's a github
> > > (commercial entity) feature, not a git (open source vcs) feature.
> > >
> > > Yes you can post a link on a Jira and ask people for review prior to
> > > submitting a formal patch.  No that's not review board or Jira
> > integration.
> > >
> > >
> > >
> > > On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > That is fine.  Only committers can merge pull requests.  Not a
> problem.
> > > >
> > > > I've never signed anything, and committers take my patches.  Works
> the
> > > same.
> > > >
> > > > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <
> [EMAIL PROTECTED]
> > > >wrote:
> > > >
> > > >>
> > > >> There is a legal issue as well. Uploading a patch to JIRA requires
> the
> > > >> user to grant apache license to use the code.  A pull request from
> > > github
> > > >> does not.
> > > >> This is all being hashed out elsewhere, none of us here are experts.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> > wrote:
> > > >>
> > > >>> If there is already a trial going, the project would benefit from
> > > >>> switching
> > > >>> to git, as we could then (I think?) accept pull requests on github.
> > >  Maybe
> > > >>> not, I'm not familiar with integrating multiple gits.  Barrier of
> > entry
> > > >>> for
> > > >>> contributing would then drop dramatically, making happy for all.
> > > >>>
> > > >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]
> >
> > > >> wrote:
> > > >>>
> > > >>>> This can be done in the future but I don't see there is an urgent
> > need
> > > >>>> for that. I'd rather wait for Apache to standardize the process
> and
> > we
> > > >>>> can easily follow and switch, rather than become the first several
> > to
> > > >>>> try and solve the infrastructure problem.
> > > >>>>
> > > >>>> Daniel
> > > >>>>
> > > >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
> > > [EMAIL PROTECTED]>
> > > >>>> wrote:
> > > >>>>> If people don't know git or svn, they are going to have to learn
> > one
> > > >>>> or
> > > >>>> the

As much as I love git I also don't think now is the time to switch. We
currently have a solution that allows people to develop with svn or with
git, depending on their preferences. It's also possible to collaborate with
other developers on large patches using git and post links to diff's on
github.

The only pain point is that code submissions to JIRAs must be in patch form
(from svn or git), not links to diffs or pull requests. This pain does not
justify migrating from SVN to git imho. Not to mention that migrating
wouldn't fix this pain point.

Also there are still many developers out there who are more comfortable
using SVN. While I agree that git is the way if the future, we should be
hesitant of alienating an svn user who stumbles on a bug and wants to
submit a patch but doesn't know git.

I fail to see any real advantage to making git the primary repo at this
point.
On Tue, Mar 27, 2012 at 9:41 AM, Gianmarco De Francisci Morales <
[EMAIL PROTECTED]> wrote:

> The fact is that git does not impose a development model, so it requires a
> bit more self discipline compared to svn.
> For example, let's say you create one branch for every Jira.
> And imagine you want to keep posting patches to Jira so that people can
> download and apply them, or have an equivalent.
> The patch in git would be the diff between the last commit before the merge
> and the start of the branch.
> But then you must be very careful with not cross merging among branches, no
> cherry-picking, and be very careful with rebasing.
> What do you do if your brach cannot merge and you need to rebase it?
> What if other people had branched off your branch and you rebase it?
>
> These are not issues that cannot be solved but it takes a bit of discipline
> and thought on how to design and integrate the new development model.
>
> Cheers,
> --
> Gianmarco
>
>
>
> On Tue, Mar 27, 2012 at 11:36, Russell Jurney <[EMAIL PROTECTED]
> >wrote:
>
> > Gianmarco, can you elaborate a bit on the fuzziness?
> >
> > On Tue, Mar 27, 2012 at 2:26 AM, Gianmarco De Francisci Morales <
> > [EMAIL PROTECTED]> wrote:
> >
> > > My 2 cents, based on the S4 project experience so far (they have git)
> is
> > +1
> > > but later.
> > >
> > > The process with git is still a bit fuzzy and not fully integrated and
> > > standardized like the one with svn.
> > > I personally use git for all my dev work with Pig, but then switch to
> svn
> > > to generate the final patch. A bit cumbersome but not so bad.
> > >
> > > Switching now will generate confusion and is not that urgent in my
> humble
> > > opinion.
> > >
> > > Cheers,
> > > --
> > > Gianmarco
> > >
> > >
> > >
> > > On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > > There is a check box you check when you upload a patch. If we
> committed
> > > > without verifying you checked it, thats an unfortunate oversight.
> > > >
> > > > No, you cant send a pull request via github to apache. That's a
> github
> > > > (commercial entity) feature, not a git (open source vcs) feature.
> > > >
> > > > Yes you can post a link on a Jira and ask people for review prior to
> > > > submitting a formal patch.  No that's not review board or Jira
> > > integration.
> > > >
> > > >
> > > >
> > > > On Mar 22, 2012, at 5:59 PM, Russell Jurney <
> [EMAIL PROTECTED]>
> > > > wrote:
> > > >
> > > > > That is fine.  Only committers can merge pull requests.  Not a
> > problem.
> > > > >
> > > > > I've never signed anything, and committers take my patches.  Works
> > the
> > > > same.
> > > > >
> > > > > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <
> > [EMAIL PROTECTED]
> > > > >wrote:
> > > > >
> > > > >>
> > > > >> There is a legal issue as well. Uploading a patch to JIRA requires
> > the
> > > > >> user to grant apache license to use the code.  A pull request from
> > > > github
> > > > >> does not.
> > > > >> This is all being hashed out elsewhere, none of us here are
> experts.
> > > > >>
> > > > >>
> > >
*Note that I'm no longer using my Yahoo! email address. Please email me at
[EMAIL PROTECTED] going forward.*

On the Avro project, several folk generate a patch using git and upload
that to the JIRA, it patches fine using unix 'patch'.
Why do you need to switch to svn to generate the patch?

A committer needs to apply the patch to a location checked out with svn,
but that is trivial.

On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
wrote:

>My 2 cents, based on the S4 project experience so far (they have git) is
>+1
>but later.
>
>The process with git is still a bit fuzzy and not fully integrated and
>standardized like the one with svn.
>I personally use git for all my dev work with Pig, but then switch to svn
>to generate the final patch. A bit cumbersome but not so bad.
>
>Switching now will generate confusion and is not that urgent in my humble
>opinion.
>
>Cheers,
>--
>Gianmarco
>
>
>
>On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> There is a check box you check when you upload a patch. If we committed
>> without verifying you checked it, thats an unfortunate oversight.
>>
>> No, you cant send a pull request via github to apache. That's a github
>> (commercial entity) feature, not a git (open source vcs) feature.
>>
>> Yes you can post a link on a Jira and ask people for review prior to
>> submitting a formal patch.  No that's not review board or Jira
>>integration.
>>
>>
>>
>> On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
>> wrote:
>>
>> > That is fine.  Only committers can merge pull requests.  Not a
>>problem.
>> >
>> > I've never signed anything, and committers take my patches.  Works the
>> same.
>> >
>> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
>> >wrote:
>> >
>> >>
>> >> There is a legal issue as well. Uploading a patch to JIRA requires
>>the
>> >> user to grant apache license to use the code.  A pull request from
>> github
>> >> does not.
>> >> This is all being hashed out elsewhere, none of us here are experts.
>> >>
>> >>
>> >>
>> >>
>> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>>wrote:
>> >>
>> >>> If there is already a trial going, the project would benefit from
>> >>> switching
>> >>> to git, as we could then (I think?) accept pull requests on github.
>>  Maybe
>> >>> not, I'm not familiar with integrating multiple gits.  Barrier of
>>entry
>> >>> for
>> >>> contributing would then drop dramatically, making happy for all.
>> >>>
>> >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
>> >> wrote:
>> >>>
>> >>>> This can be done in the future but I don't see there is an urgent
>>need
>> >>>> for that. I'd rather wait for Apache to standardize the process
>>and we
>> >>>> can easily follow and switch, rather than become the first several
>>to
>> >>>> try and solve the infrastructure problem.
>> >>>>
>> >>>> Daniel
>> >>>>
>> >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
>> [EMAIL PROTECTED]>
>> >>>> wrote:
>> >>>>> If people don't know git or svn, they are going to have to learn
>>one
>> >>>> or
>> >>>> the
>> >>>>> other if they want to work with open source projects. It might as
>> >>>> well be
>> >>>>> git, since that's where things are going.
>> >>>>>
>> >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>> >>>>>
>> >>>>>> Apache is currently doing a trial with git as the primary repo
>>using
>> >>>> the
>> >>>>>> CouchDB project.  Other projects may be able to volunteer to join
>> the
>> >>>>>> trial, I'm not sure.
>> >>>>>>
>> >>>>>> see http://git-wip-us.apache.org/
>> >>>>>>
>> >>>>>> I suggest that if you are interested in this join the apache
>> >>>>>> infrastructure-dev list.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On 3/21/12 9:57 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>> >>>> wrote:
>> >>>>>>
>> >>>>>>> What's the work?
>> >>>>>>>
>> >>>>>>> Russell Jurney http://datasyndrome.com
>> >>>>>>>
>> >>>>>>> On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> >>>> wrote:
>> >>>>>>>
>> >>>>>>>> All that's left is for someone to volunteer to do the work.

Using text patches is the problem as I see it.  We should be using...
something else.  Doesn't git's functionality enable phasing out text
patches?

On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey <[EMAIL PROTECTED]>wrote:

> On the Avro project, several folk generate a patch using git and upload
> that to the JIRA, it patches fine using unix 'patch'.
> Why do you need to switch to svn to generate the patch?
>
> A committer needs to apply the patch to a location checked out with svn,
> but that is trivial.
>
> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
> wrote:
>
> >My 2 cents, based on the S4 project experience so far (they have git) is
> >+1
> >but later.
> >
> >The process with git is still a bit fuzzy and not fully integrated and
> >standardized like the one with svn.
> >I personally use git for all my dev work with Pig, but then switch to svn
> >to generate the final patch. A bit cumbersome but not so bad.
> >
> >Switching now will generate confusion and is not that urgent in my humble
> >opinion.
> >
> >Cheers,
> >--
> >Gianmarco
> >
> >
> >
> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >
> >> There is a check box you check when you upload a patch. If we committed
> >> without verifying you checked it, thats an unfortunate oversight.
> >>
> >> No, you cant send a pull request via github to apache. That's a github
> >> (commercial entity) feature, not a git (open source vcs) feature.
> >>
> >> Yes you can post a link on a Jira and ask people for review prior to
> >> submitting a formal patch.  No that's not review board or Jira
> >>integration.
> >>
> >>
> >>
> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
> >> wrote:
> >>
> >> > That is fine.  Only committers can merge pull requests.  Not a
> >>problem.
> >> >
> >> > I've never signed anything, and committers take my patches.  Works the
> >> same.
> >> >
> >> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
> >> >wrote:
> >> >
> >> >>
> >> >> There is a legal issue as well. Uploading a patch to JIRA requires
> >>the
> >> >> user to grant apache license to use the code.  A pull request from
> >> github
> >> >> does not.
> >> >> This is all being hashed out elsewhere, none of us here are experts.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> >>wrote:
> >> >>
> >> >>> If there is already a trial going, the project would benefit from
> >> >>> switching
> >> >>> to git, as we could then (I think?) accept pull requests on github.
> >>  Maybe
> >> >>> not, I'm not familiar with integrating multiple gits.  Barrier of
> >>entry
> >> >>> for
> >> >>> contributing would then drop dramatically, making happy for all.
> >> >>>
> >> >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> >> >> wrote:
> >> >>>
> >> >>>> This can be done in the future but I don't see there is an urgent
> >>need
> >> >>>> for that. I'd rather wait for Apache to standardize the process
> >>and we
> >> >>>> can easily follow and switch, rather than become the first several
> >>to
> >> >>>> try and solve the infrastructure problem.
> >> >>>>
> >> >>>> Daniel
> >> >>>>
> >> >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
> >> [EMAIL PROTECTED]>
> >> >>>> wrote:
> >> >>>>> If people don't know git or svn, they are going to have to learn
> >>one
> >> >>>> or
> >> >>>> the
> >> >>>>> other if they want to work with open source projects. It might as
> >> >>>> well be
> >> >>>>> git, since that's where things are going.
> >> >>>>>
> >> >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >> >>>>>
> >> >>>>>> Apache is currently doing a trial with git as the primary repo
> >>using
> >> >>>> the
> >> >>>>>> CouchDB project.  Other projects may be able to volunteer to join
> >> the
> >> >>>>>> trial, I'm not sure.
> >> >>>>>>
> >> >>>>>> see http://git-wip-us.apache.org/
> >> >>>>>>
> >> >>>>>> I suggest that if you are interested in this join the apache
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

Could you enumerate the problems you have with text patches?

I can think of 1, but would like to hear your list.

Dmitriy

On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
<[EMAIL PROTECTED]> wrote:
> Using text patches is the problem as I see it.  We should be using...
> something else.  Doesn't git's functionality enable phasing out text
> patches?
>
> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey <[EMAIL PROTECTED]>wrote:
>
>> On the Avro project, several folk generate a patch using git and upload
>> that to the JIRA, it patches fine using unix 'patch'.
>> Why do you need to switch to svn to generate the patch?
>>
>> A committer needs to apply the patch to a location checked out with svn,
>> but that is trivial.
>>
>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
>> wrote:
>>
>> >My 2 cents, based on the S4 project experience so far (they have git) is
>> >+1
>> >but later.
>> >
>> >The process with git is still a bit fuzzy and not fully integrated and
>> >standardized like the one with svn.
>> >I personally use git for all my dev work with Pig, but then switch to svn
>> >to generate the final patch. A bit cumbersome but not so bad.
>> >
>> >Switching now will generate confusion and is not that urgent in my humble
>> >opinion.
>> >
>> >Cheers,
>> >--
>> >Gianmarco
>> >
>> >
>> >
>> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>> >
>> >> There is a check box you check when you upload a patch. If we committed
>> >> without verifying you checked it, thats an unfortunate oversight.
>> >>
>> >> No, you cant send a pull request via github to apache. That's a github
>> >> (commercial entity) feature, not a git (open source vcs) feature.
>> >>
>> >> Yes you can post a link on a Jira and ask people for review prior to
>> >> submitting a formal patch.  No that's not review board or Jira
>> >>integration.
>> >>
>> >>
>> >>
>> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
>> >> wrote:
>> >>
>> >> > That is fine.  Only committers can merge pull requests.  Not a
>> >>problem.
>> >> >
>> >> > I've never signed anything, and committers take my patches.  Works the
>> >> same.
>> >> >
>> >> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
>> >> >wrote:
>> >> >
>> >> >>
>> >> >> There is a legal issue as well. Uploading a patch to JIRA requires
>> >>the
>> >> >> user to grant apache license to use the code.  A pull request from
>> >> github
>> >> >> does not.
>> >> >> This is all being hashed out elsewhere, none of us here are experts.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>> >>wrote:
>> >> >>
>> >> >>> If there is already a trial going, the project would benefit from
>> >> >>> switching
>> >> >>> to git, as we could then (I think?) accept pull requests on github.
>> >>  Maybe
>> >> >>> not, I'm not familiar with integrating multiple gits.  Barrier of
>> >>entry
>> >> >>> for
>> >> >>> contributing would then drop dramatically, making happy for all.
>> >> >>>
>> >> >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
>> >> >> wrote:
>> >> >>>
>> >> >>>> This can be done in the future but I don't see there is an urgent
>> >>need
>> >> >>>> for that. I'd rather wait for Apache to standardize the process
>> >>and we
>> >> >>>> can easily follow and switch, rather than become the first several
>> >>to
>> >> >>>> try and solve the infrastructure problem.
>> >> >>>>
>> >> >>>> Daniel
>> >> >>>>
>> >> >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
>> >> [EMAIL PROTECTED]>
>> >> >>>> wrote:
>> >> >>>>> If people don't know git or svn, they are going to have to learn
>> >>one
>> >> >>>> or
>> >> >>>> the
>> >> >>>>> other if they want to work with open source projects. It might as
>> >> >>>> well be
>> >> >>>>> git, since that's where things are going.
>> >> >>>>>
>> >> >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
>> >> >>>>>

I usually do that for two reasons.
One, I feel better when I test that the patch correctly applies to the svn
tree. What I usually do is to generate a diff from git and apply it with
patch on the svn tree.
Two, I need to use the svn tree to commit the patch anyway.

Cheers,

--
Gianmarco

On Tue, Mar 27, 2012 at 20:16, Scott Carey <[EMAIL PROTECTED]> wrote:

> On the Avro project, several folk generate a patch using git and upload
> that to the JIRA, it patches fine using unix 'patch'.
> Why do you need to switch to svn to generate the patch?
>
> A committer needs to apply the patch to a location checked out with svn,
> but that is trivial.
>
> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
> wrote:
>
> >My 2 cents, based on the S4 project experience so far (they have git) is
> >+1
> >but later.
> >
> >The process with git is still a bit fuzzy and not fully integrated and
> >standardized like the one with svn.
> >I personally use git for all my dev work with Pig, but then switch to svn
> >to generate the final patch. A bit cumbersome but not so bad.
> >
> >Switching now will generate confusion and is not that urgent in my humble
> >opinion.
> >
> >Cheers,
> >--
> >Gianmarco
> >
> >
> >
> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >
> >> There is a check box you check when you upload a patch. If we committed
> >> without verifying you checked it, thats an unfortunate oversight.
> >>
> >> No, you cant send a pull request via github to apache. That's a github
> >> (commercial entity) feature, not a git (open source vcs) feature.
> >>
> >> Yes you can post a link on a Jira and ask people for review prior to
> >> submitting a formal patch.  No that's not review board or Jira
> >>integration.
> >>
> >>
> >>
> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney <[EMAIL PROTECTED]>
> >> wrote:
> >>
> >> > That is fine.  Only committers can merge pull requests.  Not a
> >>problem.
> >> >
> >> > I've never signed anything, and committers take my patches.  Works the
> >> same.
> >> >
> >> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey <[EMAIL PROTECTED]
> >> >wrote:
> >> >
> >> >>
> >> >> There is a legal issue as well. Uploading a patch to JIRA requires
> >>the
> >> >> user to grant apache license to use the code.  A pull request from
> >> github
> >> >> does not.
> >> >> This is all being hashed out elsewhere, none of us here are experts.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
> >>wrote:
> >> >>
> >> >>> If there is already a trial going, the project would benefit from
> >> >>> switching
> >> >>> to git, as we could then (I think?) accept pull requests on github.
> >>  Maybe
> >> >>> not, I'm not familiar with integrating multiple gits.  Barrier of
> >>entry
> >> >>> for
> >> >>> contributing would then drop dramatically, making happy for all.
> >> >>>
> >> >>> On Thu, Mar 22, 2012 at 1:58 PM, Daniel Dai <[EMAIL PROTECTED]>
> >> >> wrote:
> >> >>>
> >> >>>> This can be done in the future but I don't see there is an urgent
> >>need
> >> >>>> for that. I'd rather wait for Apache to standardize the process
> >>and we
> >> >>>> can easily follow and switch, rather than become the first several
> >>to
> >> >>>> try and solve the infrastructure problem.
> >> >>>>
> >> >>>> Daniel
> >> >>>>
> >> >>>> On Thu, Mar 22, 2012 at 12:02 PM, Jonathan Coveney <
> >> [EMAIL PROTECTED]>
> >> >>>> wrote:
> >> >>>>> If people don't know git or svn, they are going to have to learn
> >>one
> >> >>>> or
> >> >>>> the
> >> >>>>> other if they want to work with open source projects. It might as
> >> >>>> well be
> >> >>>>> git, since that's where things are going.
> >> >>>>>
> >> >>>>> 2012/3/22 Scott Carey <[EMAIL PROTECTED]>
> >> >>>>>
> >> >>>>>> Apache is currently doing a trial with git as the primary repo
> >>using
> >> >>>> the
> >> >>>>>> CouchDB project.  Other projects may be able to volunteer to join
> >> the

Git was built with use case #1 being Linux developers exchanging patches
as text via e-mail.  I am not sure what binary patch support Linus plans
or what it would help other than being more compact.  One disadvantage is
that it is then hard to review simple changes by simply reading the patch
itself in a text editor.  I have +1'd many near-trivial changes after only
glancing at the text of the patch.
  
SVN is (slowly) catching up to have better patch features.  'svn patch' is
now in 1.7, 1.8 will enhance it, and eventually there is planned support
for git patch extensions. In the long run the differences between the
tools for day-to-day work will shrink from where it is now.  Subversion is
planning 'svn shelve' to make it more git-like when working locally, for
example.

On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:

>Could you enumerate the problems you have with text patches?
>
>I can think of 1, but would like to hear your list.
>
>Dmitriy
>
>On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
><[EMAIL PROTECTED]> wrote:
>> Using text patches is the problem as I see it.  We should be using...
>> something else.  Doesn't git's functionality enable phasing out text
>> patches?
>>
>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>><[EMAIL PROTECTED]>wrote:
>>
>>> On the Avro project, several folk generate a patch using git and upload
>>> that to the JIRA, it patches fine using unix 'patch'.
>>> Why do you need to switch to svn to generate the patch?
>>>
>>> A committer needs to apply the patch to a location checked out with
>>>svn,
>>> but that is trivial.
>>>
>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> >My 2 cents, based on the S4 project experience so far (they have git)
>>>is
>>> >+1
>>> >but later.
>>> >
>>> >The process with git is still a bit fuzzy and not fully integrated and
>>> >standardized like the one with svn.
>>> >I personally use git for all my dev work with Pig, but then switch to
>>>svn
>>> >to generate the final patch. A bit cumbersome but not so bad.
>>> >
>>> >Switching now will generate confusion and is not that urgent in my
>>>humble
>>> >opinion.
>>> >
>>> >Cheers,
>>> >--
>>> >Gianmarco
>>> >
>>> >
>>> >
>>> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>>>wrote:
>>> >
>>> >> There is a check box you check when you upload a patch. If we
>>>committed
>>> >> without verifying you checked it, thats an unfortunate oversight.
>>> >>
>>> >> No, you cant send a pull request via github to apache. That's a
>>>github
>>> >> (commercial entity) feature, not a git (open source vcs) feature.
>>> >>
>>> >> Yes you can post a link on a Jira and ask people for review prior to
>>> >> submitting a formal patch.  No that's not review board or Jira
>>> >>integration.
>>> >>
>>> >>
>>> >>
>>> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney
>>><[EMAIL PROTECTED]>
>>> >> wrote:
>>> >>
>>> >> > That is fine.  Only committers can merge pull requests.  Not a
>>> >>problem.
>>> >> >
>>> >> > I've never signed anything, and committers take my patches.
>>>Works the
>>> >> same.
>>> >> >
>>> >> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey
>>><[EMAIL PROTECTED]
>>> >> >wrote:
>>> >> >
>>> >> >>
>>> >> >> There is a legal issue as well. Uploading a patch to JIRA
>>>requires
>>> >>the
>>> >> >> user to grant apache license to use the code.  A pull request
>>>from
>>> >> github
>>> >> >> does not.
>>> >> >> This is all being hashed out elsewhere, none of us here are
>>>experts.
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On 3/22/12 2:08 PM, "Russell Jurney" <[EMAIL PROTECTED]>
>>> >>wrote:
>>> >> >>
>>> >> >>> If there is already a trial going, the project would benefit
>>>from
>>> >> >>> switching
>>> >> >>> to git, as we could then (I think?) accept pull requests on
>>>github.
>>> >>  Maybe
>>> >> >>> not, I'm not familiar with integrating multiple gits.  Barrier
>>>of
>>> >>entry
>>> >> >>> for
>>> >> >>> contributing would then drop dramatically, making happy for all.

Some more info is available here, for the Cassandra project:

https://issues.apache.org/jira/browse/INFRA-4254
https://github.com/apache/cassandra
http://wiki.apache.org/cassandra/HowToContribute

I have a proposal to make... since we're not yet up for this, but do agree
that it is the future: what if we move Piggybank to github?

We can do this at the hackathon we're having at Twitter - I forgot the date?

On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]>wrote:

> Git was built with use case #1 being Linux developers exchanging patches
> as text via e-mail.  I am not sure what binary patch support Linus plans
> or what it would help other than being more compact.  One disadvantage is
> that it is then hard to review simple changes by simply reading the patch
> itself in a text editor.  I have +1'd many near-trivial changes after only
> glancing at the text of the patch.
>
> SVN is (slowly) catching up to have better patch features.  'svn patch' is
> now in 1.7, 1.8 will enhance it, and eventually there is planned support
> for git patch extensions. In the long run the differences between the
> tools for day-to-day work will shrink from where it is now.  Subversion is
> planning 'svn shelve' to make it more git-like when working locally, for
> example.
>
> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>
> >Could you enumerate the problems you have with text patches?
> >
> >I can think of 1, but would like to hear your list.
> >
> >Dmitriy
> >
> >On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
> ><[EMAIL PROTECTED]> wrote:
> >> Using text patches is the problem as I see it.  We should be using...
> >> something else.  Doesn't git's functionality enable phasing out text
> >> patches?
> >>
> >> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
> >><[EMAIL PROTECTED]>wrote:
> >>
> >>> On the Avro project, several folk generate a patch using git and upload
> >>> that to the JIRA, it patches fine using unix 'patch'.
> >>> Why do you need to switch to svn to generate the patch?
> >>>
> >>> A committer needs to apply the patch to a location checked out with
> >>>svn,
> >>> but that is trivial.
> >>>
> >>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
> >>> wrote:
> >>>
> >>> >My 2 cents, based on the S4 project experience so far (they have git)
> >>>is
> >>> >+1
> >>> >but later.
> >>> >
> >>> >The process with git is still a bit fuzzy and not fully integrated and
> >>> >standardized like the one with svn.
> >>> >I personally use git for all my dev work with Pig, but then switch to
> >>>svn
> >>> >to generate the final patch. A bit cumbersome but not so bad.
> >>> >
> >>> >Switching now will generate confusion and is not that urgent in my
> >>>humble
> >>> >opinion.
> >>> >
> >>> >Cheers,
> >>> >--
> >>> >Gianmarco
> >>> >
> >>> >
> >>> >
> >>> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >>>wrote:
> >>> >
> >>> >> There is a check box you check when you upload a patch. If we
> >>>committed
> >>> >> without verifying you checked it, thats an unfortunate oversight.
> >>> >>
> >>> >> No, you cant send a pull request via github to apache. That's a
> >>>github
> >>> >> (commercial entity) feature, not a git (open source vcs) feature.
> >>> >>
> >>> >> Yes you can post a link on a Jira and ask people for review prior to
> >>> >> submitting a formal patch.  No that's not review board or Jira
> >>> >>integration.
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney
> >>><[EMAIL PROTECTED]>
> >>> >> wrote:
> >>> >>
> >>> >> > That is fine.  Only committers can merge pull requests.  Not a
> >>> >>problem.
> >>> >> >
> >>> >> > I've never signed anything, and committers take my patches.
> >>>Works the
> >>> >> same.
> >>> >> >
> >>> >> > On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey
> >>><[EMAIL PROTECTED]
> >>> >> >wrote:
> >>> >> >
> >>> >> >>
> >>> >> >> There is a legal issue as well. Uploading a patch to JIRA
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

Oh, and https://issues.apache.org/jira/browse/CASSANDRA-3676

On Tue, Apr 3, 2012 at 3:36 PM, Russell Jurney <[EMAIL PROTECTED]>wrote:

> Some more info is available here, for the Cassandra project:
>
> https://issues.apache.org/jira/browse/INFRA-4254
> https://github.com/apache/cassandra
> http://wiki.apache.org/cassandra/HowToContribute
>
> I have a proposal to make... since we're not yet up for this, but do agree
> that it is the future: what if we move Piggybank to github?
>
> We can do this at the hackathon we're having at Twitter - I forgot the
> date?
>
> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]>wrote:
>
>> Git was built with use case #1 being Linux developers exchanging patches
>> as text via e-mail.  I am not sure what binary patch support Linus plans
>> or what it would help other than being more compact.  One disadvantage is
>> that it is then hard to review simple changes by simply reading the patch
>> itself in a text editor.  I have +1'd many near-trivial changes after only
>> glancing at the text of the patch.
>>
>> SVN is (slowly) catching up to have better patch features.  'svn patch' is
>> now in 1.7, 1.8 will enhance it, and eventually there is planned support
>> for git patch extensions. In the long run the differences between the
>> tools for day-to-day work will shrink from where it is now.  Subversion is
>> planning 'svn shelve' to make it more git-like when working locally, for
>> example.
>>
>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>
>> >Could you enumerate the problems you have with text patches?
>> >
>> >I can think of 1, but would like to hear your list.
>> >
>> >Dmitriy
>> >
>> >On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>> ><[EMAIL PROTECTED]> wrote:
>> >> Using text patches is the problem as I see it.  We should be using...
>> >> something else.  Doesn't git's functionality enable phasing out text
>> >> patches?
>> >>
>> >> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>> >><[EMAIL PROTECTED]>wrote:
>> >>
>> >>> On the Avro project, several folk generate a patch using git and
>> upload
>> >>> that to the JIRA, it patches fine using unix 'patch'.
>> >>> Why do you need to switch to svn to generate the patch?
>> >>>
>> >>> A committer needs to apply the patch to a location checked out with
>> >>>svn,
>> >>> but that is trivial.
>> >>>
>> >>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]
>> >
>> >>> wrote:
>> >>>
>> >>> >My 2 cents, based on the S4 project experience so far (they have git)
>> >>>is
>> >>> >+1
>> >>> >but later.
>> >>> >
>> >>> >The process with git is still a bit fuzzy and not fully integrated
>> and
>> >>> >standardized like the one with svn.
>> >>> >I personally use git for all my dev work with Pig, but then switch to
>> >>>svn
>> >>> >to generate the final patch. A bit cumbersome but not so bad.
>> >>> >
>> >>> >Switching now will generate confusion and is not that urgent in my
>> >>>humble
>> >>> >opinion.
>> >>> >
>> >>> >Cheers,
>> >>> >--
>> >>> >Gianmarco
>> >>> >
>> >>> >
>> >>> >
>> >>> >On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> >>>wrote:
>> >>> >
>> >>> >> There is a check box you check when you upload a patch. If we
>> >>>committed
>> >>> >> without verifying you checked it, thats an unfortunate oversight.
>> >>> >>
>> >>> >> No, you cant send a pull request via github to apache. That's a
>> >>>github
>> >>> >> (commercial entity) feature, not a git (open source vcs) feature.
>> >>> >>
>> >>> >> Yes you can post a link on a Jira and ask people for review prior
>> to
>> >>> >> submitting a formal patch.  No that's not review board or Jira
>> >>> >>integration.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On Mar 22, 2012, at 5:59 PM, Russell Jurney
>> >>><[EMAIL PROTECTED]>
>> >>> >> wrote:
>> >>> >>
>> >>> >> > That is fine.  Only committers can merge pull requests.  Not a
>> >>> >>problem.
>> >>> >> >
>> >>> >> > I've never signed anything, and committers take my patches.

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

Major +1 for moving Piggybank to github.  

Alan.

On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:

> Some more info is available here, for the Cassandra project:
>
> https://issues.apache.org/jira/browse/INFRA-4254
> https://github.com/apache/cassandra
> http://wiki.apache.org/cassandra/HowToContribute
>
> I have a proposal to make... since we're not yet up for this, but do agree
> that it is the future: what if we move Piggybank to github?
>
> We can do this at the hackathon we're having at Twitter - I forgot the date?
>
> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]>wrote:
>
>> Git was built with use case #1 being Linux developers exchanging patches
>> as text via e-mail.  I am not sure what binary patch support Linus plans
>> or what it would help other than being more compact.  One disadvantage is
>> that it is then hard to review simple changes by simply reading the patch
>> itself in a text editor.  I have +1'd many near-trivial changes after only
>> glancing at the text of the patch.
>>
>> SVN is (slowly) catching up to have better patch features.  'svn patch' is
>> now in 1.7, 1.8 will enhance it, and eventually there is planned support
>> for git patch extensions. In the long run the differences between the
>> tools for day-to-day work will shrink from where it is now.  Subversion is
>> planning 'svn shelve' to make it more git-like when working locally, for
>> example.
>>
>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>
>>> Could you enumerate the problems you have with text patches?
>>>
>>> I can think of 1, but would like to hear your list.
>>>
>>> Dmitriy
>>>
>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>>> <[EMAIL PROTECTED]> wrote:
>>>> Using text patches is the problem as I see it.  We should be using...
>>>> something else.  Doesn't git's functionality enable phasing out text
>>>> patches?
>>>>
>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>>>> <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> On the Avro project, several folk generate a patch using git and upload
>>>>> that to the JIRA, it patches fine using unix 'patch'.
>>>>> Why do you need to switch to svn to generate the patch?
>>>>>
>>>>> A committer needs to apply the patch to a location checked out with
>>>>> svn,
>>>>> but that is trivial.
>>>>>
>>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>
>>>>>> My 2 cents, based on the S4 project experience so far (they have git)
>>>>> is
>>>>>> +1
>>>>>> but later.
>>>>>>
>>>>>> The process with git is still a bit fuzzy and not fully integrated and
>>>>>> standardized like the one with svn.
>>>>>> I personally use git for all my dev work with Pig, but then switch to
>>>>> svn
>>>>>> to generate the final patch. A bit cumbersome but not so bad.
>>>>>>
>>>>>> Switching now will generate confusion and is not that urgent in my
>>>>> humble
>>>>>> opinion.
>>>>>>
>>>>>> Cheers,
>>>>>> --
>>>>>> Gianmarco
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>>>
>>>>>>> There is a check box you check when you upload a patch. If we
>>>>> committed
>>>>>>> without verifying you checked it, thats an unfortunate oversight.
>>>>>>>
>>>>>>> No, you cant send a pull request via github to apache. That's a
>>>>> github
>>>>>>> (commercial entity) feature, not a git (open source vcs) feature.
>>>>>>>
>>>>>>> Yes you can post a link on a Jira and ask people for review prior to
>>>>>>> submitting a formal patch.  No that's not review board or Jira
>>>>>>> integration.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mar 22, 2012, at 5:59 PM, Russell Jurney
>>>>> <[EMAIL PROTECTED]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> That is fine.  Only committers can merge pull requests.  Not a
>>>>>>> problem.
>>>>>>>>
>>>>>>>> I've never signed anything, and committers take my patches.
>>>>> Works the
>>>>>>> same.
>>>>>>>>
>>>>>>>> On Thu, Mar 22, 2012 at 3

Ok, so we just need a date.  Twitter on April <blank> we will be moving
piggybank to github (and other awesome things).

On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:

> Major +1 for moving Piggybank to github.
>
> Alan.
>
> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
>
> > Some more info is available here, for the Cassandra project:
> >
> > https://issues.apache.org/jira/browse/INFRA-4254
> > https://github.com/apache/cassandra
> > http://wiki.apache.org/cassandra/HowToContribute
> >
> > I have a proposal to make... since we're not yet up for this, but do
> agree
> > that it is the future: what if we move Piggybank to github?
> >
> > We can do this at the hackathon we're having at Twitter - I forgot the
> date?
> >
> > On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
> >wrote:
> >
> >> Git was built with use case #1 being Linux developers exchanging patches
> >> as text via e-mail.  I am not sure what binary patch support Linus plans
> >> or what it would help other than being more compact.  One disadvantage
> is
> >> that it is then hard to review simple changes by simply reading the
> patch
> >> itself in a text editor.  I have +1'd many near-trivial changes after
> only
> >> glancing at the text of the patch.
> >>
> >> SVN is (slowly) catching up to have better patch features.  'svn patch'
> is
> >> now in 1.7, 1.8 will enhance it, and eventually there is planned support
> >> for git patch extensions. In the long run the differences between the
> >> tools for day-to-day work will shrink from where it is now.  Subversion
> is
> >> planning 'svn shelve' to make it more git-like when working locally, for
> >> example.
> >>
> >> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
> >>
> >>> Could you enumerate the problems you have with text patches?
> >>>
> >>> I can think of 1, but would like to hear your list.
> >>>
> >>> Dmitriy
> >>>
> >>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
> >>> <[EMAIL PROTECTED]> wrote:
> >>>> Using text patches is the problem as I see it.  We should be using...
> >>>> something else.  Doesn't git's functionality enable phasing out text
> >>>> patches?
> >>>>
> >>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
> >>>> <[EMAIL PROTECTED]>wrote:
> >>>>
> >>>>> On the Avro project, several folk generate a patch using git and
> upload
> >>>>> that to the JIRA, it patches fine using unix 'patch'.
> >>>>> Why do you need to switch to svn to generate the patch?
> >>>>>
> >>>>> A committer needs to apply the patch to a location checked out with
> >>>>> svn,
> >>>>> but that is trivial.
> >>>>>
> >>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
> [EMAIL PROTECTED]>
> >>>>> wrote:
> >>>>>
> >>>>>> My 2 cents, based on the S4 project experience so far (they have
> git)
> >>>>> is
> >>>>>> +1
> >>>>>> but later.
> >>>>>>
> >>>>>> The process with git is still a bit fuzzy and not fully integrated
> and
> >>>>>> standardized like the one with svn.
> >>>>>> I personally use git for all my dev work with Pig, but then switch
> to
> >>>>> svn
> >>>>>> to generate the final patch. A bit cumbersome but not so bad.
> >>>>>>
> >>>>>> Switching now will generate confusion and is not that urgent in my
> >>>>> humble
> >>>>>> opinion.
> >>>>>>
> >>>>>> Cheers,
> >>>>>> --
> >>>>>> Gianmarco
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >>>>> wrote:
> >>>>>>
> >>>>>>> There is a check box you check when you upload a patch. If we
> >>>>> committed
> >>>>>>> without verifying you checked it, thats an unfortunate oversight.
> >>>>>>>
> >>>>>>> No, you cant send a pull request via github to apache. That's a
> >>>>> github
> >>>>>>> (commercial entity) feature, not a git (open source vcs) feature.
> >>>>>>>
> >>>>>>> Yes you can post a link on a Jira and ask people for review prior
> to
> >>>>>>> submitting a formal patch.  No that's not review board or Jira
> >>>>>>> integration.
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

Do people prefer a workday or a weekend?

2012/4/3 Russell Jurney <[EMAIL PROTECTED]>

> Ok, so we just need a date.  Twitter on April <blank> we will be moving
> piggybank to github (and other awesome things).
>
> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
>
> > Major +1 for moving Piggybank to github.
> >
> > Alan.
> >
> > On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
> >
> > > Some more info is available here, for the Cassandra project:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-4254
> > > https://github.com/apache/cassandra
> > > http://wiki.apache.org/cassandra/HowToContribute
> > >
> > > I have a proposal to make... since we're not yet up for this, but do
> > agree
> > > that it is the future: what if we move Piggybank to github?
> > >
> > > We can do this at the hackathon we're having at Twitter - I forgot the
> > date?
> > >
> > > On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
> > >wrote:
> > >
> > >> Git was built with use case #1 being Linux developers exchanging
> patches
> > >> as text via e-mail.  I am not sure what binary patch support Linus
> plans
> > >> or what it would help other than being more compact.  One disadvantage
> > is
> > >> that it is then hard to review simple changes by simply reading the
> > patch
> > >> itself in a text editor.  I have +1'd many near-trivial changes after
> > only
> > >> glancing at the text of the patch.
> > >>
> > >> SVN is (slowly) catching up to have better patch features.  'svn
> patch'
> > is
> > >> now in 1.7, 1.8 will enhance it, and eventually there is planned
> support
> > >> for git patch extensions. In the long run the differences between the
> > >> tools for day-to-day work will shrink from where it is now.
>  Subversion
> > is
> > >> planning 'svn shelve' to make it more git-like when working locally,
> for
> > >> example.
> > >>
> > >> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
> > >>
> > >>> Could you enumerate the problems you have with text patches?
> > >>>
> > >>> I can think of 1, but would like to hear your list.
> > >>>
> > >>> Dmitriy
> > >>>
> > >>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
> > >>> <[EMAIL PROTECTED]> wrote:
> > >>>> Using text patches is the problem as I see it.  We should be
> using...
> > >>>> something else.  Doesn't git's functionality enable phasing out text
> > >>>> patches?
> > >>>>
> > >>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
> > >>>> <[EMAIL PROTECTED]>wrote:
> > >>>>
> > >>>>> On the Avro project, several folk generate a patch using git and
> > upload
> > >>>>> that to the JIRA, it patches fine using unix 'patch'.
> > >>>>> Why do you need to switch to svn to generate the patch?
> > >>>>>
> > >>>>> A committer needs to apply the patch to a location checked out with
> > >>>>> svn,
> > >>>>> but that is trivial.
> > >>>>>
> > >>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
> > [EMAIL PROTECTED]>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> My 2 cents, based on the S4 project experience so far (they have
> > git)
> > >>>>> is
> > >>>>>> +1
> > >>>>>> but later.
> > >>>>>>
> > >>>>>> The process with git is still a bit fuzzy and not fully integrated
> > and
> > >>>>>> standardized like the one with svn.
> > >>>>>> I personally use git for all my dev work with Pig, but then switch
> > to
> > >>>>> svn
> > >>>>>> to generate the final patch. A bit cumbersome but not so bad.
> > >>>>>>
> > >>>>>> Switching now will generate confusion and is not that urgent in my
> > >>>>> humble
> > >>>>>> opinion.
> > >>>>>>
> > >>>>>> Cheers,
> > >>>>>> --
> > >>>>>> Gianmarco
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]
> >
> > >>>>> wrote:
> > >>>>>>
> > >>>>>>> There is a check box you check when you upload a patch. If we
> > >>>>> committed
> > >>>>>>> without verifying you checked it, thats an unfortunate oversight.
> > >>>>>>>
> > >>>>>>> No, you cant send a pull request via github to apache. That's a

I prefer weekdays, but I'm flexible.

Russell Jurney http://datasyndrome.com

On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:

> Do people prefer a workday or a weekend?
>
> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
>
>> Ok, so we just need a date.  Twitter on April <blank> we will be moving
>> piggybank to github (and other awesome things).
>>
>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>
>>> Major +1 for moving Piggybank to github.
>>>
>>> Alan.
>>>
>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
>>>
>>>> Some more info is available here, for the Cassandra project:
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-4254
>>>> https://github.com/apache/cassandra
>>>> http://wiki.apache.org/cassandra/HowToContribute
>>>>
>>>> I have a proposal to make... since we're not yet up for this, but do
>>> agree
>>>> that it is the future: what if we move Piggybank to github?
>>>>
>>>> We can do this at the hackathon we're having at Twitter - I forgot the
>>> date?
>>>>
>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
>>>> wrote:
>>>>
>>>>> Git was built with use case #1 being Linux developers exchanging
>> patches
>>>>> as text via e-mail.  I am not sure what binary patch support Linus
>> plans
>>>>> or what it would help other than being more compact.  One disadvantage
>>> is
>>>>> that it is then hard to review simple changes by simply reading the
>>> patch
>>>>> itself in a text editor.  I have +1'd many near-trivial changes after
>>> only
>>>>> glancing at the text of the patch.
>>>>>
>>>>> SVN is (slowly) catching up to have better patch features.  'svn
>> patch'
>>> is
>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
>> support
>>>>> for git patch extensions. In the long run the differences between the
>>>>> tools for day-to-day work will shrink from where it is now.
>> Subversion
>>> is
>>>>> planning 'svn shelve' to make it more git-like when working locally,
>> for
>>>>> example.
>>>>>
>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> Could you enumerate the problems you have with text patches?
>>>>>>
>>>>>> I can think of 1, but would like to hear your list.
>>>>>>
>>>>>> Dmitriy
>>>>>>
>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>>>>>> <[EMAIL PROTECTED]> wrote:
>>>>>>> Using text patches is the problem as I see it.  We should be
>> using...
>>>>>>> something else.  Doesn't git's functionality enable phasing out text
>>>>>>> patches?
>>>>>>>
>>>>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>
>>>>>>>> On the Avro project, several folk generate a patch using git and
>>> upload
>>>>>>>> that to the JIRA, it patches fine using unix 'patch'.
>>>>>>>> Why do you need to switch to svn to generate the patch?
>>>>>>>>
>>>>>>>> A committer needs to apply the patch to a location checked out with
>>>>>>>> svn,
>>>>>>>> but that is trivial.
>>>>>>>>
>>>>>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
>>> [EMAIL PROTECTED]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> My 2 cents, based on the S4 project experience so far (they have
>>> git)
>>>>>>>> is
>>>>>>>>> +1
>>>>>>>>> but later.
>>>>>>>>>
>>>>>>>>> The process with git is still a bit fuzzy and not fully integrated
>>> and
>>>>>>>>> standardized like the one with svn.
>>>>>>>>> I personally use git for all my dev work with Pig, but then switch
>>> to
>>>>>>>> svn
>>>>>>>>> to generate the final patch. A bit cumbersome but not so bad.
>>>>>>>>>
>>>>>>>>> Switching now will generate confusion and is not that urgent in my
>>>>>>>> humble
>>>>>>>>> opinion.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> --
>>>>>>>>> Gianmarco
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]
>>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> There is a check box you check when you upload a patch. If we
>>>>>>>> committed

Russell, you saw that the Cassandra thing still requires people to
upload patches to JIRA?

D

On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <[EMAIL PROTECTED]> wrote:
> I prefer weekdays, but I'm flexible.
>
> Russell Jurney http://datasyndrome.com
>
> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:
>
>> Do people prefer a workday or a weekend?
>>
>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
>>
>>> Ok, so we just need a date.  Twitter on April <blank> we will be moving
>>> piggybank to github (and other awesome things).
>>>
>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>>
>>>> Major +1 for moving Piggybank to github.
>>>>
>>>> Alan.
>>>>
>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
>>>>
>>>>> Some more info is available here, for the Cassandra project:
>>>>>
>>>>> https://issues.apache.org/jira/browse/INFRA-4254
>>>>> https://github.com/apache/cassandra
>>>>> http://wiki.apache.org/cassandra/HowToContribute
>>>>>
>>>>> I have a proposal to make... since we're not yet up for this, but do
>>>> agree
>>>>> that it is the future: what if we move Piggybank to github?
>>>>>
>>>>> We can do this at the hackathon we're having at Twitter - I forgot the
>>>> date?
>>>>>
>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
>>>>> wrote:
>>>>>
>>>>>> Git was built with use case #1 being Linux developers exchanging
>>> patches
>>>>>> as text via e-mail.  I am not sure what binary patch support Linus
>>> plans
>>>>>> or what it would help other than being more compact.  One disadvantage
>>>> is
>>>>>> that it is then hard to review simple changes by simply reading the
>>>> patch
>>>>>> itself in a text editor.  I have +1'd many near-trivial changes after
>>>> only
>>>>>> glancing at the text of the patch.
>>>>>>
>>>>>> SVN is (slowly) catching up to have better patch features.  'svn
>>> patch'
>>>> is
>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
>>> support
>>>>>> for git patch extensions. In the long run the differences between the
>>>>>> tools for day-to-day work will shrink from where it is now.
>>> Subversion
>>>> is
>>>>>> planning 'svn shelve' to make it more git-like when working locally,
>>> for
>>>>>> example.
>>>>>>
>>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>> Could you enumerate the problems you have with text patches?
>>>>>>>
>>>>>>> I can think of 1, but would like to hear your list.
>>>>>>>
>>>>>>> Dmitriy
>>>>>>>
>>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>>>>>>> <[EMAIL PROTECTED]> wrote:
>>>>>>>> Using text patches is the problem as I see it.  We should be
>>> using...
>>>>>>>> something else.  Doesn't git's functionality enable phasing out text
>>>>>>>> patches?
>>>>>>>>
>>>>>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>>
>>>>>>>>> On the Avro project, several folk generate a patch using git and
>>>> upload
>>>>>>>>> that to the JIRA, it patches fine using unix 'patch'.
>>>>>>>>> Why do you need to switch to svn to generate the patch?
>>>>>>>>>
>>>>>>>>> A committer needs to apply the patch to a location checked out with
>>>>>>>>> svn,
>>>>>>>>> but that is trivial.
>>>>>>>>>
>>>>>>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
>>>> [EMAIL PROTECTED]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> My 2 cents, based on the S4 project experience so far (they have
>>>> git)
>>>>>>>>> is
>>>>>>>>>> +1
>>>>>>>>>> but later.
>>>>>>>>>>
>>>>>>>>>> The process with git is still a bit fuzzy and not fully integrated
>>>> and
>>>>>>>>>> standardized like the one with svn.
>>>>>>>>>> I personally use git for all my dev work with Pig, but then switch
>>>> to
>>>>>>>>> svn
>>>>>>>>>> to generate the final patch. A bit cumbersome but not so bad.
>>>>>>>>>>
>>>>>>>>>> Switching now will generate confusion and is not that urgent in my
>>>>>>>>> humble
>>>>>>>>>> opinion.
>>>>>>>>>>
>>>>>>>>>> Cheers,

+1 workday

Thanks,
Prashant

On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:

> Do people prefer a workday or a weekend?
>
> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
>
>> Ok, so we just need a date.  Twitter on April <blank> we will be moving
>> piggybank to github (and other awesome things).
>>
>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>
>>> Major +1 for moving Piggybank to github.
>>>
>>> Alan.
>>>
>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
>>>
>>>> Some more info is available here, for the Cassandra project:
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-4254
>>>> https://github.com/apache/cassandra
>>>> http://wiki.apache.org/cassandra/HowToContribute
>>>>
>>>> I have a proposal to make... since we're not yet up for this, but do
>>> agree
>>>> that it is the future: what if we move Piggybank to github?
>>>>
>>>> We can do this at the hackathon we're having at Twitter - I forgot the
>>> date?
>>>>
>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
>>>> wrote:
>>>>
>>>>> Git was built with use case #1 being Linux developers exchanging
>> patches
>>>>> as text via e-mail.  I am not sure what binary patch support Linus
>> plans
>>>>> or what it would help other than being more compact.  One disadvantage
>>> is
>>>>> that it is then hard to review simple changes by simply reading the
>>> patch
>>>>> itself in a text editor.  I have +1'd many near-trivial changes after
>>> only
>>>>> glancing at the text of the patch.
>>>>>
>>>>> SVN is (slowly) catching up to have better patch features.  'svn
>> patch'
>>> is
>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
>> support
>>>>> for git patch extensions. In the long run the differences between the
>>>>> tools for day-to-day work will shrink from where it is now.
>> Subversion
>>> is
>>>>> planning 'svn shelve' to make it more git-like when working locally,
>> for
>>>>> example.
>>>>>
>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> Could you enumerate the problems you have with text patches?
>>>>>>
>>>>>> I can think of 1, but would like to hear your list.
>>>>>>
>>>>>> Dmitriy
>>>>>>
>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>>>>>> <[EMAIL PROTECTED]> wrote:
>>>>>>> Using text patches is the problem as I see it.  We should be
>> using...
>>>>>>> something else.  Doesn't git's functionality enable phasing out text
>>>>>>> patches?
>>>>>>>
>>>>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>
>>>>>>>> On the Avro project, several folk generate a patch using git and
>>> upload
>>>>>>>> that to the JIRA, it patches fine using unix 'patch'.
>>>>>>>> Why do you need to switch to svn to generate the patch?
>>>>>>>>
>>>>>>>> A committer needs to apply the patch to a location checked out with
>>>>>>>> svn,
>>>>>>>> but that is trivial.
>>>>>>>>
>>>>>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
>>> [EMAIL PROTECTED]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> My 2 cents, based on the S4 project experience so far (they have
>>> git)
>>>>>>>> is
>>>>>>>>> +1
>>>>>>>>> but later.
>>>>>>>>>
>>>>>>>>> The process with git is still a bit fuzzy and not fully integrated
>>> and
>>>>>>>>> standardized like the one with svn.
>>>>>>>>> I personally use git for all my dev work with Pig, but then switch
>>> to
>>>>>>>> svn
>>>>>>>>> to generate the final patch. A bit cumbersome but not so bad.
>>>>>>>>>
>>>>>>>>> Switching now will generate confusion and is not that urgent in my
>>>>>>>> humble
>>>>>>>>> opinion.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> --
>>>>>>>>> Gianmarco
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Mar 24, 2012 at 01:27, Dmitriy Ryaboy <[EMAIL PROTECTED]
>>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> There is a check box you check when you upload a patch. If we
>>>>>>>> committed
>>>>>>>>>> without verifying you checked it, thats an unfortunate oversight.

No, that is not good :(

Weekday for the hackathon?

Russell Jurney http://datasyndrome.com

On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> Russell, you saw that the Cassandra thing still requires people to
> upload patches to JIRA?
>
> D
>
> On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <[EMAIL PROTECTED]> wrote:
>> I prefer weekdays, but I'm flexible.
>>
>> Russell Jurney http://datasyndrome.com
>>
>> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]> wrote:
>>
>>> Do people prefer a workday or a weekend?
>>>
>>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
>>>
>>>> Ok, so we just need a date.  Twitter on April <blank> we will be moving
>>>> piggybank to github (and other awesome things).
>>>>
>>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Major +1 for moving Piggybank to github.
>>>>>
>>>>> Alan.
>>>>>
>>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
>>>>>
>>>>>> Some more info is available here, for the Cassandra project:
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/INFRA-4254
>>>>>> https://github.com/apache/cassandra
>>>>>> http://wiki.apache.org/cassandra/HowToContribute
>>>>>>
>>>>>> I have a proposal to make... since we're not yet up for this, but do
>>>>> agree
>>>>>> that it is the future: what if we move Piggybank to github?
>>>>>>
>>>>>> We can do this at the hackathon we're having at Twitter - I forgot the
>>>>> date?
>>>>>>
>>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <[EMAIL PROTECTED]
>>>>>> wrote:
>>>>>>
>>>>>>> Git was built with use case #1 being Linux developers exchanging
>>>> patches
>>>>>>> as text via e-mail.  I am not sure what binary patch support Linus
>>>> plans
>>>>>>> or what it would help other than being more compact.  One disadvantage
>>>>> is
>>>>>>> that it is then hard to review simple changes by simply reading the
>>>>> patch
>>>>>>> itself in a text editor.  I have +1'd many near-trivial changes after
>>>>> only
>>>>>>> glancing at the text of the patch.
>>>>>>>
>>>>>>> SVN is (slowly) catching up to have better patch features.  'svn
>>>> patch'
>>>>> is
>>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
>>>> support
>>>>>>> for git patch extensions. In the long run the differences between the
>>>>>>> tools for day-to-day work will shrink from where it is now.
>>>> Subversion
>>>>> is
>>>>>>> planning 'svn shelve' to make it more git-like when working locally,
>>>> for
>>>>>>> example.
>>>>>>>
>>>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
>>>>>>>
>>>>>>>> Could you enumerate the problems you have with text patches?
>>>>>>>>
>>>>>>>> I can think of 1, but would like to hear your list.
>>>>>>>>
>>>>>>>> Dmitriy
>>>>>>>>
>>>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
>>>>>>>> <[EMAIL PROTECTED]> wrote:
>>>>>>>>> Using text patches is the problem as I see it.  We should be
>>>> using...
>>>>>>>>> something else.  Doesn't git's functionality enable phasing out text
>>>>>>>>> patches?
>>>>>>>>>
>>>>>>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
>>>>>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>>>>>
>>>>>>>>>> On the Avro project, several folk generate a patch using git and
>>>>> upload
>>>>>>>>>> that to the JIRA, it patches fine using unix 'patch'.
>>>>>>>>>> Why do you need to switch to svn to generate the patch?
>>>>>>>>>>
>>>>>>>>>> A committer needs to apply the patch to a location checked out with
>>>>>>>>>> svn,
>>>>>>>>>> but that is trivial.
>>>>>>>>>>
>>>>>>>>>> On 3/27/12 2:26 AM, "Gianmarco De Francisci Morales" <
>>>>> [EMAIL PROTECTED]>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> My 2 cents, based on the S4 project experience so far (they have
>>>>> git)
>>>>>>>>>> is
>>>>>>>>>>> +1
>>>>>>>>>>> but later.
>>>>>>>>>>>
>>>>>>>>>>> The process with git is still a bit fuzzy and not fully integrated
>>>>> and
>>>>>>>>>>> standardized like the one with svn.
>>>>>>>>>>> I personally use git for all my dev work with Pig, but then switch

As I said, the integration is still cumbersome.
There are legal issues with not uploading patches to Jira.

Anyway, +1 for moving Piggybank to git (github could be a good choice in
this case).

Cheers,
--
Gianmarco

On Wed, Apr 4, 2012 at 06:48, Russell Jurney <[EMAIL PROTECTED]>wrote:

> No, that is not good :(
>
> Weekday for the hackathon?
>
> Russell Jurney http://datasyndrome.com
>
> On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
> > Russell, you saw that the Cassandra thing still requires people to
> > upload patches to JIRA?
> >
> > D
> >
> > On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <[EMAIL PROTECTED]>
> wrote:
> >> I prefer weekdays, but I'm flexible.
> >>
> >> Russell Jurney http://datasyndrome.com
> >>
> >> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Do people prefer a workday or a weekend?
> >>>
> >>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
> >>>
> >>>> Ok, so we just need a date.  Twitter on April <blank> we will be
> moving
> >>>> piggybank to github (and other awesome things).
> >>>>
> >>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]>
> wrote:
> >>>>
> >>>>> Major +1 for moving Piggybank to github.
> >>>>>
> >>>>> Alan.
> >>>>>
> >>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
> >>>>>
> >>>>>> Some more info is available here, for the Cassandra project:
> >>>>>>
> >>>>>> https://issues.apache.org/jira/browse/INFRA-4254
> >>>>>> https://github.com/apache/cassandra
> >>>>>> http://wiki.apache.org/cassandra/HowToContribute
> >>>>>>
> >>>>>> I have a proposal to make... since we're not yet up for this, but do
> >>>>> agree
> >>>>>> that it is the future: what if we move Piggybank to github?
> >>>>>>
> >>>>>> We can do this at the hackathon we're having at Twitter - I forgot
> the
> >>>>> date?
> >>>>>>
> >>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <
> [EMAIL PROTECTED]
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Git was built with use case #1 being Linux developers exchanging
> >>>> patches
> >>>>>>> as text via e-mail.  I am not sure what binary patch support Linus
> >>>> plans
> >>>>>>> or what it would help other than being more compact.  One
> disadvantage
> >>>>> is
> >>>>>>> that it is then hard to review simple changes by simply reading the
> >>>>> patch
> >>>>>>> itself in a text editor.  I have +1'd many near-trivial changes
> after
> >>>>> only
> >>>>>>> glancing at the text of the patch.
> >>>>>>>
> >>>>>>> SVN is (slowly) catching up to have better patch features.  'svn
> >>>> patch'
> >>>>> is
> >>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
> >>>> support
> >>>>>>> for git patch extensions. In the long run the differences between
> the
> >>>>>>> tools for day-to-day work will shrink from where it is now.
> >>>> Subversion
> >>>>> is
> >>>>>>> planning 'svn shelve' to make it more git-like when working
> locally,
> >>>> for
> >>>>>>> example.
> >>>>>>>
> >>>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]> wrote:
> >>>>>>>
> >>>>>>>> Could you enumerate the problems you have with text patches?
> >>>>>>>>
> >>>>>>>> I can think of 1, but would like to hear your list.
> >>>>>>>>
> >>>>>>>> Dmitriy
> >>>>>>>>
> >>>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
> >>>>>>>> <[EMAIL PROTECTED]> wrote:
> >>>>>>>>> Using text patches is the problem as I see it.  We should be
> >>>> using...
> >>>>>>>>> something else.  Doesn't git's functionality enable phasing out
> text
> >>>>>>>>> patches?
> >>>>>>>>>
> >>>>>>>>> On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey
> >>>>>>>>> <[EMAIL PROTECTED]>wrote:
> >>>>>>>>>
> >>>>>>>>>> On the Avro project, several folk generate a patch using git and
> >>>>> upload
> >>>>>>>>>> that to the JIRA, it patches fine using unix 'patch'.
> >>>>>>>>>> Why do you need to switch to svn to generate the patch?
> >>>>>>>>>>
> >>>>>>>>>> A committer needs to apply the patch to a location checked out

I agree.  I think we'll see a massive uptick in contributors to Piggybank
if it is on github.  I think we can start getting companies like Twitter
and LinkedIn to think about contributing to Piggybank instead of rolling
their own github repos.

On Wed, Apr 4, 2012 at 7:49 AM, Gianmarco De Francisci Morales <
[EMAIL PROTECTED]> wrote:

> As I said, the integration is still cumbersome.
> There are legal issues with not uploading patches to Jira.
>
> Anyway, +1 for moving Piggybank to git (github could be a good choice in
> this case).
>
> Cheers,
> --
> Gianmarco
>
>
>
> On Wed, Apr 4, 2012 at 06:48, Russell Jurney <[EMAIL PROTECTED]
> >wrote:
>
> > No, that is not good :(
> >
> > Weekday for the hackathon?
> >
> > Russell Jurney http://datasyndrome.com
> >
> > On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> >
> > > Russell, you saw that the Cassandra thing still requires people to
> > > upload patches to JIRA?
> > >
> > > D
> > >
> > > On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <
> [EMAIL PROTECTED]>
> > wrote:
> > >> I prefer weekdays, but I'm flexible.
> > >>
> > >> Russell Jurney http://datasyndrome.com
> > >>
> > >> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> > wrote:
> > >>
> > >>> Do people prefer a workday or a weekend?
> > >>>
> > >>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
> > >>>
> > >>>> Ok, so we just need a date.  Twitter on April <blank> we will be
> > moving
> > >>>> piggybank to github (and other awesome things).
> > >>>>
> > >>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]>
> > wrote:
> > >>>>
> > >>>>> Major +1 for moving Piggybank to github.
> > >>>>>
> > >>>>> Alan.
> > >>>>>
> > >>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
> > >>>>>
> > >>>>>> Some more info is available here, for the Cassandra project:
> > >>>>>>
> > >>>>>> https://issues.apache.org/jira/browse/INFRA-4254
> > >>>>>> https://github.com/apache/cassandra
> > >>>>>> http://wiki.apache.org/cassandra/HowToContribute
> > >>>>>>
> > >>>>>> I have a proposal to make... since we're not yet up for this, but
> do
> > >>>>> agree
> > >>>>>> that it is the future: what if we move Piggybank to github?
> > >>>>>>
> > >>>>>> We can do this at the hackathon we're having at Twitter - I forgot
> > the
> > >>>>> date?
> > >>>>>>
> > >>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <
> > [EMAIL PROTECTED]
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Git was built with use case #1 being Linux developers exchanging
> > >>>> patches
> > >>>>>>> as text via e-mail.  I am not sure what binary patch support
> Linus
> > >>>> plans
> > >>>>>>> or what it would help other than being more compact.  One
> > disadvantage
> > >>>>> is
> > >>>>>>> that it is then hard to review simple changes by simply reading
> the
> > >>>>> patch
> > >>>>>>> itself in a text editor.  I have +1'd many near-trivial changes
> > after
> > >>>>> only
> > >>>>>>> glancing at the text of the patch.
> > >>>>>>>
> > >>>>>>> SVN is (slowly) catching up to have better patch features.  'svn
> > >>>> patch'
> > >>>>> is
> > >>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is planned
> > >>>> support
> > >>>>>>> for git patch extensions. In the long run the differences between
> > the
> > >>>>>>> tools for day-to-day work will shrink from where it is now.
> > >>>> Subversion
> > >>>>> is
> > >>>>>>> planning 'svn shelve' to make it more git-like when working
> > locally,
> > >>>> for
> > >>>>>>> example.
> > >>>>>>>
> > >>>>>>> On 3/27/12 10:43 PM, "Dmitriy Ryaboy" <[EMAIL PROTECTED]>
> wrote:
> > >>>>>>>
> > >>>>>>>> Could you enumerate the problems you have with text patches?
> > >>>>>>>>
> > >>>>>>>> I can think of 1, but would like to hear your list.
> > >>>>>>>>
> > >>>>>>>> Dmitriy
> > >>>>>>>>
> > >>>>>>>> On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
> > >>>>>>>> <[EMAIL PROTECTED]> wrote:
> > >>>>>>>>> Using text patches is the problem as I see it.  We should be

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

+1 to piggybank on github.

The one tricky part will be setting up the repos, build and artifact
publishing components in a way that handles dependency management of
version X of piggybank with version Y of Pig.
On Wed, Apr 4, 2012 at 11:35 AM, Russell Jurney <[EMAIL PROTECTED]>wrote:

> I agree.  I think we'll see a massive uptick in contributors to Piggybank
> if it is on github.  I think we can start getting companies like Twitter
> and LinkedIn to think about contributing to Piggybank instead of rolling
> their own github repos.
>
> On Wed, Apr 4, 2012 at 7:49 AM, Gianmarco De Francisci Morales <
> [EMAIL PROTECTED]> wrote:
>
> > As I said, the integration is still cumbersome.
> > There are legal issues with not uploading patches to Jira.
> >
> > Anyway, +1 for moving Piggybank to git (github could be a good choice in
> > this case).
> >
> > Cheers,
> > --
> > Gianmarco
> >
> >
> >
> > On Wed, Apr 4, 2012 at 06:48, Russell Jurney <[EMAIL PROTECTED]
> > >wrote:
> >
> > > No, that is not good :(
> > >
> > > Weekday for the hackathon?
> > >
> > > Russell Jurney http://datasyndrome.com
> > >
> > > On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> > >
> > > > Russell, you saw that the Cassandra thing still requires people to
> > > > upload patches to JIRA?
> > > >
> > > > D
> > > >
> > > > On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <
> > [EMAIL PROTECTED]>
> > > wrote:
> > > >> I prefer weekdays, but I'm flexible.
> > > >>
> > > >> Russell Jurney http://datasyndrome.com
> > > >>
> > > >> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> > > wrote:
> > > >>
> > > >>> Do people prefer a workday or a weekend?
> > > >>>
> > > >>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
> > > >>>
> > > >>>> Ok, so we just need a date.  Twitter on April <blank> we will be
> > > moving
> > > >>>> piggybank to github (and other awesome things).
> > > >>>>
> > > >>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <[EMAIL PROTECTED]
> >
> > > wrote:
> > > >>>>
> > > >>>>> Major +1 for moving Piggybank to github.
> > > >>>>>
> > > >>>>> Alan.
> > > >>>>>
> > > >>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
> > > >>>>>
> > > >>>>>> Some more info is available here, for the Cassandra project:
> > > >>>>>>
> > > >>>>>> https://issues.apache.org/jira/browse/INFRA-4254
> > > >>>>>> https://github.com/apache/cassandra
> > > >>>>>> http://wiki.apache.org/cassandra/HowToContribute
> > > >>>>>>
> > > >>>>>> I have a proposal to make... since we're not yet up for this,
> but
> > do
> > > >>>>> agree
> > > >>>>>> that it is the future: what if we move Piggybank to github?
> > > >>>>>>
> > > >>>>>> We can do this at the hackathon we're having at Twitter - I
> forgot
> > > the
> > > >>>>> date?
> > > >>>>>>
> > > >>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <
> > > [EMAIL PROTECTED]
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>>> Git was built with use case #1 being Linux developers
> exchanging
> > > >>>> patches
> > > >>>>>>> as text via e-mail.  I am not sure what binary patch support
> > Linus
> > > >>>> plans
> > > >>>>>>> or what it would help other than being more compact.  One
> > > disadvantage
> > > >>>>> is
> > > >>>>>>> that it is then hard to review simple changes by simply reading
> > the
> > > >>>>> patch
> > > >>>>>>> itself in a text editor.  I have +1'd many near-trivial changes
> > > after
> > > >>>>> only
> > > >>>>>>> glancing at the text of the patch.
> > > >>>>>>>
> > > >>>>>>> SVN is (slowly) catching up to have better patch features.
>  'svn
> > > >>>> patch'
> > > >>>>> is
> > > >>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is
> planned
> > > >>>> support
> > > >>>>>>> for git patch extensions. In the long run the differences
> between
> > > the
> > > >>>>>>> tools for day-to-day work will shrink from where it is now.
> > > >>>> Subversion
> > > >>>>> is
> > > >>>>>>> planning 'svn shelve' to make it more git-like when working
> > > locally,

*Note that I'm no longer using my Yahoo! email address. Please email me at
[EMAIL PROTECTED] going forward.*

I figure we can tackle that on hackday.

On Wed, Apr 4, 2012 at 1:30 PM, Bill Graham <[EMAIL PROTECTED]> wrote:

> +1 to piggybank on github.
>
> The one tricky part will be setting up the repos, build and artifact
> publishing components in a way that handles dependency management of
> version X of piggybank with version Y of Pig.
>
>
> On Wed, Apr 4, 2012 at 11:35 AM, Russell Jurney <[EMAIL PROTECTED]
> >wrote:
>
> > I agree.  I think we'll see a massive uptick in contributors to Piggybank
> > if it is on github.  I think we can start getting companies like Twitter
> > and LinkedIn to think about contributing to Piggybank instead of rolling
> > their own github repos.
> >
> > On Wed, Apr 4, 2012 at 7:49 AM, Gianmarco De Francisci Morales <
> > [EMAIL PROTECTED]> wrote:
> >
> > > As I said, the integration is still cumbersome.
> > > There are legal issues with not uploading patches to Jira.
> > >
> > > Anyway, +1 for moving Piggybank to git (github could be a good choice
> in
> > > this case).
> > >
> > > Cheers,
> > > --
> > > Gianmarco
> > >
> > >
> > >
> > > On Wed, Apr 4, 2012 at 06:48, Russell Jurney <[EMAIL PROTECTED]
> > > >wrote:
> > >
> > > > No, that is not good :(
> > > >
> > > > Weekday for the hackathon?
> > > >
> > > > Russell Jurney http://datasyndrome.com
> > > >
> > > > On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > > > Russell, you saw that the Cassandra thing still requires people to
> > > > > upload patches to JIRA?
> > > > >
> > > > > D
> > > > >
> > > > > On Tue, Apr 3, 2012 at 5:16 PM, Russell Jurney <
> > > [EMAIL PROTECTED]>
> > > > wrote:
> > > > >> I prefer weekdays, but I'm flexible.
> > > > >>
> > > > >> Russell Jurney http://datasyndrome.com
> > > > >>
> > > > >> On Apr 3, 2012, at 5:11 PM, Jonathan Coveney <[EMAIL PROTECTED]>
> > > > wrote:
> > > > >>
> > > > >>> Do people prefer a workday or a weekend?
> > > > >>>
> > > > >>> 2012/4/3 Russell Jurney <[EMAIL PROTECTED]>
> > > > >>>
> > > > >>>> Ok, so we just need a date.  Twitter on April <blank> we will be
> > > > moving
> > > > >>>> piggybank to github (and other awesome things).
> > > > >>>>
> > > > >>>> On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates <
> [EMAIL PROTECTED]
> > >
> > > > wrote:
> > > > >>>>
> > > > >>>>> Major +1 for moving Piggybank to github.
> > > > >>>>>
> > > > >>>>> Alan.
> > > > >>>>>
> > > > >>>>> On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
> > > > >>>>>
> > > > >>>>>> Some more info is available here, for the Cassandra project:
> > > > >>>>>>
> > > > >>>>>> https://issues.apache.org/jira/browse/INFRA-4254
> > > > >>>>>> https://github.com/apache/cassandra
> > > > >>>>>> http://wiki.apache.org/cassandra/HowToContribute
> > > > >>>>>>
> > > > >>>>>> I have a proposal to make... since we're not yet up for this,
> > but
> > > do
> > > > >>>>> agree
> > > > >>>>>> that it is the future: what if we move Piggybank to github?
> > > > >>>>>>
> > > > >>>>>> We can do this at the hackathon we're having at Twitter - I
> > forgot
> > > > the
> > > > >>>>> date?
> > > > >>>>>>
> > > > >>>>>> On Wed, Mar 28, 2012 at 6:16 PM, Scott Carey <
> > > > [EMAIL PROTECTED]
> > > > >>>>>> wrote:
> > > > >>>>>>
> > > > >>>>>>> Git was built with use case #1 being Linux developers
> > exchanging
> > > > >>>> patches
> > > > >>>>>>> as text via e-mail.  I am not sure what binary patch support
> > > Linus
> > > > >>>> plans
> > > > >>>>>>> or what it would help other than being more compact.  One
> > > > disadvantage
> > > > >>>>> is
> > > > >>>>>>> that it is then hard to review simple changes by simply
> reading
> > > the
> > > > >>>>> patch
> > > > >>>>>>> itself in a text editor.  I have +1'd many near-trivial
> changes
> > > > after
> > > > >>>>> only
> > > > >>>>>>> glancing at the text of the patch.
> > > > >>>>>>>
> > > > >>>>>>> SVN is (slowly) catching up to have better patch features.
> >  'svn
> > > > >>>> patch'
> > > > >>>>> is
> > > > >>>>>>> now in 1.7, 1.8 will enhance it, and eventually there is

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com