Transition from svn to git

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Transition from svn to git

Ilan Schnell
Hello,

Anthony and I are planning to move ETS from svn to git
immediately after the 3.6.0 release next week, i.e. Friday,
January 28, next week.

We propose the following transition steps:
1.) make svn repository read-only
2.) move each svn project directory to a git repository on
    github (https://github.com/enthought), using svn2git
3.) updating the helper tool ets.py to use git
4.) allow developers to obtain push privileges

Make sure that any outstanding changes that you are
planning to submit, are either checked in (svn) by the
time of the release, or that you have saved diffs, so that
they can be pushed to github later.

Please let us know if you have any questions or concerns.

Thanks   Anthony and Ilan
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

bryce hendrix-2
How is ets.py to work on Windows? I really don't want cygwin as a requirement...

On Wed, Jan 19, 2011 at 11:13 AM, Ilan Schnell <[hidden email]> wrote:
Hello,

Anthony and I are planning to move ETS from svn to git
immediately after the 3.6.0 release next week, i.e. Friday,
January 28, next week.

We propose the following transition steps:
1.) make svn repository read-only
2.) move each svn project directory to a git repository on
   github (https://github.com/enthought), using svn2git
3.) updating the helper tool ets.py to use git
4.) allow developers to obtain push privileges

Make sure that any outstanding changes that you are
planning to submit, are either checked in (svn) by the
time of the release, or that you have saved diffs, so that
they can be pushed to github later.

Please let us know if you have any questions or concerns.

Thanks   Anthony and Ilan
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

sergey miryanov
In reply to this post by Ilan Schnell
It is a cool decision!

On Wed, Jan 19, 2011 at 10:13 PM, Ilan Schnell <[hidden email]> wrote:

> Hello,
>
> Anthony and I are planning to move ETS from svn to git
> immediately after the 3.6.0 release next week, i.e. Friday,
> January 28, next week.
>
> We propose the following transition steps:
> 1.) make svn repository read-only
> 2.) move each svn project directory to a git repository on
>    github (https://github.com/enthought), using svn2git
> 3.) updating the helper tool ets.py to use git
> 4.) allow developers to obtain push privileges
>
> Make sure that any outstanding changes that you are
> planning to submit, are either checked in (svn) by the
> time of the release, or that you have saved diffs, so that
> they can be pushed to github later.
>
> Please let us know if you have any questions or concerns.
>
> Thanks   Anthony and Ilan
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Gael Varoquaux
In reply to this post by Ilan Schnell
On Wed, Jan 19, 2011 at 11:13:20AM -0600, Ilan Schnell wrote:
> Anthony and I are planning to move ETS from svn to git
> immediately after the 3.6.0 release next week, i.e. Friday,
> January 28, next week.

> We propose the following transition steps:
> 1.) make svn repository read-only
> 2.) move each svn project directory to a git repository on
>     github (https://github.com/enthought), using svn2git

Awesome!

> Make sure that any outstanding changes that you are
> planning to submit, are either checked in (svn) by the
> time of the release, or that you have saved diffs, so that
> they can be pushed to github later.

Thanks for the warning.

G
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Anthony Scopatz
In reply to this post by bryce hendrix-2
msysgit (http://code.google.com/p/msysgit/)  is a one-stop installer for git on windows (that happens to use msys under the covers).    There is also TortoiseGit (http://code.google.com/p/tortoisegit/).

ets.py will simply call git, much like it does on other platforms.  

Be Well
Anthony

On Wed, Jan 19, 2011 at 11:15 AM, bryce hendrix <[hidden email]> wrote:
How is ets.py to work on Windows? I really don't want cygwin as a requirement...


On Wed, Jan 19, 2011 at 11:13 AM, Ilan Schnell <[hidden email]> wrote:
Hello,

Anthony and I are planning to move ETS from svn to git
immediately after the 3.6.0 release next week, i.e. Friday,
January 28, next week.

We propose the following transition steps:
1.) make svn repository read-only
2.) move each svn project directory to a git repository on
   github (https://github.com/enthought), using svn2git
3.) updating the helper tool ets.py to use git
4.) allow developers to obtain push privileges

Make sure that any outstanding changes that you are
planning to submit, are either checked in (svn) by the
time of the release, or that you have saved diffs, so that
they can be pushed to github later.

Please let us know if you have any questions or concerns.

Thanks   Anthony and Ilan
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Ilan Schnell
And there is also cygwin git, so people have plenty
of choices on Windows.

- Ilan

On Wed, Jan 19, 2011 at 11:23 AM, Anthony Scopatz
<[hidden email]> wrote:

> msysgit (http://code.google.com/p/msysgit/)  is a one-stop installer for git
> on windows (that happens to use msys under the covers).    There is also
> TortoiseGit (http://code.google.com/p/tortoisegit/).
> ets.py will simply call git, much like it does on other platforms.
> Be Well
> Anthony
>
> On Wed, Jan 19, 2011 at 11:15 AM, bryce hendrix <[hidden email]>
> wrote:
>>
>> How is ets.py to work on Windows? I really don't want cygwin as a
>> requirement...
>>
>> On Wed, Jan 19, 2011 at 11:13 AM, Ilan Schnell <[hidden email]>
>> wrote:
>>>
>>> Hello,
>>>
>>> Anthony and I are planning to move ETS from svn to git
>>> immediately after the 3.6.0 release next week, i.e. Friday,
>>> January 28, next week.
>>>
>>> We propose the following transition steps:
>>> 1.) make svn repository read-only
>>> 2.) move each svn project directory to a git repository on
>>>    github (https://github.com/enthought), using svn2git
>>> 3.) updating the helper tool ets.py to use git
>>> 4.) allow developers to obtain push privileges
>>>
>>> Make sure that any outstanding changes that you are
>>> planning to submit, are either checked in (svn) by the
>>> time of the release, or that you have saved diffs, so that
>>> they can be pushed to github later.
>>>
>>> Please let us know if you have any questions or concerns.
>>>
>>> Thanks   Anthony and Ilan
>>> _______________________________________________
>>> Enthought-Dev mailing list
>>> [hidden email]
>>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>>
>>
>> _______________________________________________
>> Enthought-Dev mailing list
>> [hidden email]
>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>>
>
>
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

bryce hendrix-2
In reply to this post by Anthony Scopatz
Does TortoiseGit install a git.exe on the path? The msysgit install does not update the PATH by default. Just things to consider when updating ets.py

<troll>
The more I use git on Windows, the less I like it. I know we've made up our minds, but the user experience for non-technical users is something we need to understand.
</troll>

Bryce

On Wed, Jan 19, 2011 at 11:23 AM, Anthony Scopatz <[hidden email]> wrote:
msysgit (http://code.google.com/p/msysgit/)  is a one-stop installer for git on windows (that happens to use msys under the covers).    There is also TortoiseGit (http://code.google.com/p/tortoisegit/).

ets.py will simply call git, much like it does on other platforms.  

Be Well
Anthony

On Wed, Jan 19, 2011 at 11:15 AM, bryce hendrix <[hidden email]> wrote:
How is ets.py to work on Windows? I really don't want cygwin as a requirement...


On Wed, Jan 19, 2011 at 11:13 AM, Ilan Schnell <[hidden email]> wrote:
Hello,

Anthony and I are planning to move ETS from svn to git
immediately after the 3.6.0 release next week, i.e. Friday,
January 28, next week.

We propose the following transition steps:
1.) make svn repository read-only
2.) move each svn project directory to a git repository on
   github (https://github.com/enthought), using svn2git
3.) updating the helper tool ets.py to use git
4.) allow developers to obtain push privileges

Make sure that any outstanding changes that you are
planning to submit, are either checked in (svn) by the
time of the release, or that you have saved diffs, so that
they can be pushed to github later.

Please let us know if you have any questions or concerns.

Thanks   Anthony and Ilan
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Gael Varoquaux
On Wed, Jan 19, 2011 at 11:46:09AM -0600, bryce hendrix wrote:
>    Does TortoiseGit install a git.exe on the path? The msysgit install does
>    not update the PATH by default. Just things to consider when updating
>    ets.py
>    <troll>
>    The more I use git on Windows, the less I like it. I know we've made up
>    our minds, but the user experience for non-technical users is something we
>    need to understand.
>    </troll>

Yeah, the user experience of git is pretty bad. I like git because of
github. Now github serves on svn too:

https://github.com/blog/626-announcing-svn-support

So if you feel that the user experience of git is really too bad, it
might be worth adding a switch to ets.py to use the svn support of github
:).

Another hint to improve a bit usability of git: under linux, use gitg
rather than gitk as your GUI.

Gael
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Anthony Scopatz
In reply to this post by bryce hendrix-2

On Wed, Jan 19, 2011 at 11:46 AM, bryce hendrix <[hidden email]> wrote:
Does TortoiseGit install a git.exe on the path? The msysgit install does not update the PATH by default. Just things to consider when updating ets.py

<troll>
The more I use git on Windows, the less I like it. I know we've made up our minds, but the user experience for non-technical users is something we need to understand.
</troll>

These are valid points.  

<counter-troll>
ets.py is supposed to be a lightweight developer tool (i.e. non-technical users shouldn't be using it.  This is why we have EPD, PyPi, etc.)
</counter-troll> 

Be Well
Anthony
 
Bryce

On Wed, Jan 19, 2011 at 11:23 AM, Anthony Scopatz <[hidden email]> wrote:
msysgit (http://code.google.com/p/msysgit/)  is a one-stop installer for git on windows (that happens to use msys under the covers).    There is also TortoiseGit (http://code.google.com/p/tortoisegit/).

ets.py will simply call git, much like it does on other platforms.  

Be Well
Anthony

On Wed, Jan 19, 2011 at 11:15 AM, bryce hendrix <[hidden email]> wrote:
How is ets.py to work on Windows? I really don't want cygwin as a requirement...


On Wed, Jan 19, 2011 at 11:13 AM, Ilan Schnell <[hidden email]> wrote:
Hello,

Anthony and I are planning to move ETS from svn to git
immediately after the 3.6.0 release next week, i.e. Friday,
January 28, next week.

We propose the following transition steps:
1.) make svn repository read-only
2.) move each svn project directory to a git repository on
   github (https://github.com/enthought), using svn2git
3.) updating the helper tool ets.py to use git
4.) allow developers to obtain push privileges

Make sure that any outstanding changes that you are
planning to submit, are either checked in (svn) by the
time of the release, or that you have saved diffs, so that
they can be pushed to github later.

Please let us know if you have any questions or concerns.

Thanks   Anthony and Ilan
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Gael Varoquaux
On Wed, Jan 19, 2011 at 11:55:07AM -0600, Anthony Scopatz wrote:
>    These are valid points. �
>    <counter-troll>
>    ets.py is�supposed�to be a lightweight developer tool (i.e. non-technical
>    users shouldn't be using it. �This is why we have EPD, PyPi, etc.)
>    </counter-troll>�

I strongly disagree: the higher is the barrier to contribution for a
project, the less external contributors it will get.

Now, in the case of git, this is balanced by the fact that git and github
are hugely popular amongst geeks.

However, I have been able to witness the effects of the above statement
many times, and it applies to VCS, but also to difficulty of
build/install as difficulty of coding in the project.

Of course, you have to balance a legitimate desire for technical skills
(proper coding design, algorithmic knowledge, knowledge libraries or
low-level programming) with the desire to make things simpler to get more
coder. I have been leaning on the side of simplicity lately, as I find
that it also makes my own life easier.

That said, I am really happy to we are switching to git. I just
acknowledge its large flaws, and I wish that the git community would
acknowledge them more.

My 2 cents,

Gael

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Aris Koutsiamanis
Hi,
while I am not a contributor to the code, I was wondering why you did not go with Mercurial.
I quite sure you have already debated on the relative merits of both and that you have decided already.
However, there is one main advantage of using Mercurial: 
- it needs Python, and if someone is using ETS s/he will already have installed it => no other requirements (e.g. cygwin).

Just my 2 cents..
Cheers

On Wed, Jan 19, 2011 at 8:03 PM, Gael Varoquaux <[hidden email]> wrote:
On Wed, Jan 19, 2011 at 11:55:07AM -0600, Anthony Scopatz wrote:
>    These are valid points.  
>    <counter-troll>
>    ets.py is supposed to be a lightweight developer tool (i.e. non-technical
>    users shouldn't be using it.  This is why we have EPD, PyPi, etc.)
>    </counter-troll> 

I strongly disagree: the higher is the barrier to contribution for a
project, the less external contributors it will get.

Now, in the case of git, this is balanced by the fact that git and github
are hugely popular amongst geeks.

However, I have been able to witness the effects of the above statement
many times, and it applies to VCS, but also to difficulty of
build/install as difficulty of coding in the project.

Of course, you have to balance a legitimate desire for technical skills
(proper coding design, algorithmic knowledge, knowledge libraries or
low-level programming) with the desire to make things simpler to get more
coder. I have been leaning on the side of simplicity lately, as I find
that it also makes my own life easier.

That said, I am really happy to we are switching to git. I just
acknowledge its large flaws, and I wish that the git community would
acknowledge them more.

My 2 cents,

Gael

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Chris Colbert
Two of the big contributing factors: 1) speed 2) github

not necessarily in that order.

On Wed, Jan 19, 2011 at 2:19 PM, Aris Koutsiamanis <[hidden email]> wrote:
Hi,
while I am not a contributor to the code, I was wondering why you did not go with Mercurial.
I quite sure you have already debated on the relative merits of both and that you have decided already.
However, there is one main advantage of using Mercurial: 
- it needs Python, and if someone is using ETS s/he will already have installed it => no other requirements (e.g. cygwin).

Just my 2 cents..
Cheers

On Wed, Jan 19, 2011 at 8:03 PM, Gael Varoquaux <[hidden email]> wrote:
On Wed, Jan 19, 2011 at 11:55:07AM -0600, Anthony Scopatz wrote:
>    These are valid points.  
>    <counter-troll>
>    ets.py is supposed to be a lightweight developer tool (i.e. non-technical
>    users shouldn't be using it.  This is why we have EPD, PyPi, etc.)
>    </counter-troll> 

I strongly disagree: the higher is the barrier to contribution for a
project, the less external contributors it will get.

Now, in the case of git, this is balanced by the fact that git and github
are hugely popular amongst geeks.

However, I have been able to witness the effects of the above statement
many times, and it applies to VCS, but also to difficulty of
build/install as difficulty of coding in the project.

Of course, you have to balance a legitimate desire for technical skills
(proper coding design, algorithmic knowledge, knowledge libraries or
low-level programming) with the desire to make things simpler to get more
coder. I have been leaning on the side of simplicity lately, as I find
that it also makes my own life easier.

That said, I am really happy to we are switching to git. I just
acknowledge its large flaws, and I wish that the git community would
acknowledge them more.

My 2 cents,

Gael

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Ilan Schnell
And also the fact that numpy is already on github.

- Ilan

On Wed, Jan 19, 2011 at 1:25 PM, Chris Colbert <[hidden email]> wrote:

> Two of the big contributing factors: 1) speed 2) github
> not necessarily in that order.
>
> On Wed, Jan 19, 2011 at 2:19 PM, Aris Koutsiamanis <[hidden email]>
> wrote:
>>
>> Hi,
>> while I am not a contributor to the code, I was wondering why you did not
>> go with Mercurial.
>> I quite sure you have already debated on the relative merits of both and
>> that you have decided already.
>> However, there is one main advantage of using Mercurial:
>> - it needs Python, and if someone is using ETS s/he will already have
>> installed it => no other requirements (e.g. cygwin).
>> Just my 2 cents..
>> Cheers
>> On Wed, Jan 19, 2011 at 8:03 PM, Gael Varoquaux
>> <[hidden email]> wrote:
>>>
>>> On Wed, Jan 19, 2011 at 11:55:07AM -0600, Anthony Scopatz wrote:
>>> >    These are valid points.
>>> >    <counter-troll>
>>> >    ets.py is supposed to be a lightweight developer tool (i.e.
>>> > non-technical
>>> >    users shouldn't be using it.  This is why we have EPD, PyPi, etc.)
>>> >    </counter-troll>
>>>
>>> I strongly disagree: the higher is the barrier to contribution for a
>>> project, the less external contributors it will get.
>>>
>>> Now, in the case of git, this is balanced by the fact that git and github
>>> are hugely popular amongst geeks.
>>>
>>> However, I have been able to witness the effects of the above statement
>>> many times, and it applies to VCS, but also to difficulty of
>>> build/install as difficulty of coding in the project.
>>>
>>> Of course, you have to balance a legitimate desire for technical skills
>>> (proper coding design, algorithmic knowledge, knowledge libraries or
>>> low-level programming) with the desire to make things simpler to get more
>>> coder. I have been leaning on the side of simplicity lately, as I find
>>> that it also makes my own life easier.
>>>
>>> That said, I am really happy to we are switching to git. I just
>>> acknowledge its large flaws, and I wish that the git community would
>>> acknowledge them more.
>>>
>>> My 2 cents,
>>>
>>> Gael
>>>
>>> _______________________________________________
>>> Enthought-Dev mailing list
>>> [hidden email]
>>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>>>
>>
>>
>> _______________________________________________
>> Enthought-Dev mailing list
>> [hidden email]
>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>>
>
>
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

bryce hendrix-2
In reply to this post by Chris Colbert
Chris,

We had a lengthy discussion (again) during lunch. I was asking why github is better than bitbucket. I came across this article from someone on the github team:


The arguments why github are as follows:
 1. bitbucket copied their website feature for feature.
 2. to fork on bitbucket you need to fill out a form
 3. github offers additional Post Services on jabber and IRC
 4. github has more users

I was expecting to see some technical advantage, but I'm not seeing it. Is there something I am missing?

On Wed, Jan 19, 2011 at 1:25 PM, Chris Colbert <[hidden email]> wrote:
Two of the big contributing factors: 1) speed 2) github

not necessarily in that order.


On Wed, Jan 19, 2011 at 2:19 PM, Aris Koutsiamanis <[hidden email]> wrote:
Hi,
while I am not a contributor to the code, I was wondering why you did not go with Mercurial.
I quite sure you have already debated on the relative merits of both and that you have decided already.
However, there is one main advantage of using Mercurial: 
- it needs Python, and if someone is using ETS s/he will already have installed it => no other requirements (e.g. cygwin).

Just my 2 cents..
Cheers

On Wed, Jan 19, 2011 at 8:03 PM, Gael Varoquaux <[hidden email]> wrote:
On Wed, Jan 19, 2011 at 11:55:07AM -0600, Anthony Scopatz wrote:
>    These are valid points.  
>    <counter-troll>
>    ets.py is supposed to be a lightweight developer tool (i.e. non-technical
>    users shouldn't be using it.  This is why we have EPD, PyPi, etc.)
>    </counter-troll> 

I strongly disagree: the higher is the barrier to contribution for a
project, the less external contributors it will get.

Now, in the case of git, this is balanced by the fact that git and github
are hugely popular amongst geeks.

However, I have been able to witness the effects of the above statement
many times, and it applies to VCS, but also to difficulty of
build/install as difficulty of coding in the project.

Of course, you have to balance a legitimate desire for technical skills
(proper coding design, algorithmic knowledge, knowledge libraries or
low-level programming) with the desire to make things simpler to get more
coder. I have been leaning on the side of simplicity lately, as I find
that it also makes my own life easier.

That said, I am really happy to we are switching to git. I just
acknowledge its large flaws, and I wish that the git community would
acknowledge them more.

My 2 cents,

Gael

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Peter Wang
On Wed, Jan 19, 2011 at 1:35 PM, bryce hendrix <[hidden email]> wrote:

> Chris,
> We had a lengthy discussion (again) during lunch. I was asking why github is
> better than bitbucket. I came across this article from someone on the github
> team:
> http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html
> The arguments why github are as follows:
>  1. bitbucket copied their website feature for feature.
>  2. to fork on bitbucket you need to fill out a form
>  3. github offers additional Post Services on jabber and IRC
>  4. github has more users

Also 5. everyone talks about how great github is, but I don't see
equal numbers of people raving about bitbucket.  Or is this too meta?

But on a more serious note, I have also noted my reservations about
the user experience of git on Windows.  Ilan has commented that it
works fine under cygwin and there is also msysgit, but I still stand
by my objection that a windows tool requiring msys is like a Mac app
that uses X11: they both evoke a bit of distrust of further impedance
mismatch with the host OS.  I have no such reservations about
Mercurial, having used it on all three platforms for a while.

But I'm also with Robert in that I am a bit tired of this discussion,
and I'd rather us go with something and then maybe switch a little bit
later (if e.g. we find many Windows users and clients complaining
about having to use git).

-Peter
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Chris Colbert


On Wed, Jan 19, 2011 at 2:51 PM, Peter Wang <[hidden email]> wrote:
On Wed, Jan 19, 2011 at 1:35 PM, bryce hendrix <[hidden email]> wrote:
> Chris,
> We had a lengthy discussion (again) during lunch. I was asking why github is
> better than bitbucket. I came across this article from someone on the github
> team:
> http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html
> The arguments why github are as follows:
>  1. bitbucket copied their website feature for feature.
>  2. to fork on bitbucket you need to fill out a form
>  3. github offers additional Post Services on jabber and IRC
>  4. github has more users

Also 5. everyone talks about how great github is, but I don't see
equal numbers of people raving about bitbucket.  Or is this too meta?

But on a more serious note, I have also noted my reservations about
the user experience of git on Windows.  Ilan has commented that it
works fine under cygwin and there is also msysgit, but I still stand
by my objection that a windows tool requiring msys is like a Mac app
that uses X11: they both evoke a bit of distrust of further impedance
mismatch with the host OS.  I have no such reservations about
Mercurial, having used it on all three platforms for a while.

But I'm also with Robert in that I am a bit tired of this discussion,
and I'd rather us go with something and then maybe switch a little bit
later (if e.g. we find many Windows users and clients complaining
about having to use git).

I'm in this camp as well. I really don't care if we go with git or hg. However, I now have a bad taste in my mouth for bitbucket after seeing their blatant plagiarism of github. That's just not cool.
 

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Peter Wang
On Wed, Jan 19, 2011 at 1:58 PM, Chris Colbert <[hidden email]> wrote:
> However, I now have a bad taste in my mouth for bitbucket after seeing their
> blatant plagiarism of github. That's just not cool.

Well, github does ask everyone to fork them....

<ducks>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Gael Varoquaux
In reply to this post by bryce hendrix-2
On Wed, Jan 19, 2011 at 01:35:50PM -0600, bryce hendrix wrote:

>    We had a lengthy discussion (again) during lunch. I was asking why github
>    is better than bitbucket. I came across this article from someone on the
>    github team:
>    [1]http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html
>    The arguments why github are as follows:
>    �1. bitbucket copied their website feature for feature.
>    �2. to fork on bitbucket you need to fill out a form
>    �3. github offers additional Post Services on jabber and IRC
>    �4. github has more users
>    I was expecting to see some technical advantage, but I'm not seeing it. Is
>    there something I am missing?
The two aspects in favor of github are:

    1. Popularity: having a project on github gives it visibility to a
       bunch of coders. These are the people we want to interest. On top
       of that, in the scipy micro-community, people use github a lot,
       so it will be easier to draw from that lot.

    2. Usability:  Details like the forkqueue where you can integrate
       patches with one click, displaying the readme (formated if it's
       rest), serving svn, and (the killer feature, IMHO) commenting
       directly on commit.

1 is more important than 2, but in my experience 2 is nice.

It's funny, a year ago I was arguing against a switch to git+github on
the nipy and related projects. Looking back I can say that I strongly
dislike git, but the gains that come from github beat the pain from git.

My 2 cents,

Ga�l

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

Robert Kern
In reply to this post by Chris Colbert
On Wed, Jan 19, 2011 at 1:58 PM, Chris Colbert <[hidden email]> wrote:

>
> On Wed, Jan 19, 2011 at 2:51 PM, Peter Wang <[hidden email]> wrote:
>>
>> On Wed, Jan 19, 2011 at 1:35 PM, bryce hendrix <[hidden email]>
>> wrote:
>> > Chris,
>> > We had a lengthy discussion (again) during lunch. I was asking why
>> > github is
>> > better than bitbucket. I came across this article from someone on the
>> > github
>> > team:
>> > http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html

> I'm in this camp as well. I really don't care if we go with git or hg.
> However, I now have a bad taste in my mouth for bitbucket after seeing their
> blatant plagiarism of github. That's just not cool.

It is perhaps worth noting that that URL is literally, patently, and
unambiguously plagiarized from the original author, who now has this
up at its original location:

  http://schacon.github.com/bitbucket.html

--
Robert Kern
Enthought
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: Transition from svn to git

william ratcliff
In reply to this post by Gael Varoquaux
I actually like tortoisegit on windows.  On MacOs, I tend to just use the command line.  Is there a GUI that is actually good? 

William

On Wed, Jan 19, 2011 at 3:21 PM, Gael Varoquaux <[hidden email]> wrote:
On Wed, Jan 19, 2011 at 01:35:50PM -0600, bryce hendrix wrote:
>    We had a lengthy discussion (again) during lunch. I was asking why github
>    is better than bitbucket. I came across this article from someone on the
>    github team:
>    [1]http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html
>    The arguments why github are as follows:
>     1. bitbucket copied their website feature for feature.
>     2. to fork on bitbucket you need to fill out a form
>     3. github offers additional Post Services on jabber and IRC
>     4. github has more users
>    I was expecting to see some technical advantage, but I'm not seeing it. Is
>    there something I am missing?

The two aspects in favor of github are:

   1. Popularity: having a project on github gives it visibility to a
      bunch of coders. These are the people we want to interest. On top
      of that, in the scipy micro-community, people use github a lot,
      so it will be easier to draw from that lot.

   2. Usability:  Details like the forkqueue where you can integrate
      patches with one click, displaying the readme (formated if it's
      rest), serving svn, and (the killer feature, IMHO) commenting
      directly on commit.

1 is more important than 2, but in my experience 2 is nice.

It's funny, a year ago I was arguing against a switch to git+github on
the nipy and related projects. Looking back I can say that I strongly
dislike git, but the gains that come from github beat the pain from git.

My 2 cents,

Gaël

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
12