Re: [Scons-dev] Trial SCons migration to git on github

[Russel Winder]

On Sat, 2016-01-09 at 14:09 +0100, Dirk Bächle wrote:
> 
[…]
> I would also like to make us a clear statement first, about what we
> want to change/migrate and why we want to do it. I'm currently 
> trying to find examples of large open-source projects (not some small
> repos, maintained by a single person) that have moved from 
> Mercurial to git. Can anyone give pointers?
> My goal here is to analyze the log/commit history in order to find
> out whether the migration actually did have a measurable effect 
> on things like "frequency of commits per month", "LOC touched per
> month", "new committers per month" and so on.

Probably the most high profile Mercurial → Git switch has been the Go
project.

The core of their rationale was workflow for pull request review and
acceptance. I suspect also that Google is trying to switch all their
work to Git.

Go switched from a Google hosted Mercurial repository with Rietveld as
the review system, to a Google hosted Git repository mirrored on GitHub
with Gerrit as the review system.
 
-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder



signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[William Blevins]

On Sun, Jan 10, 2016 at 1:41 PM, Russel Winder  wrote:

> On Sat, 2016-01-09 at 14:09 +0100, Dirk Bächle wrote:
> >
> […]
> > I would also like to make us a clear statement first, about what we
> > want to change/migrate and why we want to do it. I'm currently
> > trying to find examples of large open-source projects (not some small
> > repos, maintained by a single person) that have moved from
> > Mercurial to git. Can anyone give pointers?
> > My goal here is to analyze the log/commit history in order to find
> > out whether the migration actually did have a measurable effect
> > on things like "frequency of commits per month", "LOC touched per
> > month", "new committers per month" and so on.
>
> Probably the most high profile Mercurial → Git switch has been the Go
> project.
>
> The core of their rationale was workflow for pull request review and
> acceptance. I suspect also that Google is trying to switch all their
> work to Git.
>

Google policy is use Git Client with Perforce backend on all closed source
artifacts, so I'm not surprised they are trying to keep their other project
workflows similar...



>
> Go switched from a Google hosted Mercurial repository with Rietveld as
> the review system, to a Google hosted Git repository mirrored on GitHub
> with Gerrit as the review system.
>
> --
> Russel.
>
> =
> Dr Russel Winder  t: +44 20 7585 2200   voip:
> sip:russel.win...@ekiga.net
> 41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Gary Oberbrunner]

On Sun, Jan 10, 2016 at 4:26 AM, Dirk Bächle  wrote:

> On 09.01.2016 20:47, Bill Deegan wrote:
>
>> Dirk,
>>
>> For me, its "pain in having to remember how to do things in mercurial
>> which I only use for scons" each time I go to work on it I
>> have to refresh my mental cache.
>> Which I'm pretty sure wouldn't be measurable by such statistics. But (at
>> least for me) would increase the amount of fun it is to
>> work on the project.
>>
>>
> and this (I'm referring to the "increased fun" here) wouldn't result in
> "more commits" and "more bugfixes"? Jonathon Reinhart stated this point in
> his mail explicitly: more git -> more commits.


This is my situation as well -- SCons is the only project I contribute to
that still uses hg, and since I use git everywhere else I've become pretty
expert at it. It's in my fingers and I don't even think about it anymore. I
also have dozens of git aliases and config tweaks so I go pretty fast with
it. There is of course also the better data model, but of course that's
arguable so I'm only mentioning my personal situation -- but I suspect I'm
not unique. So would switching lead to more commits and bugfixes? I can't
say for sure but from what I've seen in hiring developers, almost everyone
knows git and puts it on their resume, and I only rarely see hg experience.
So it _might_ make it easier for other contributors.

As for using a git-hg bridge, that would help local usage for us git users,
but it doesn't change the underlying branching model. If it's decided not
to switch, I might consider trying that.

-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Dirk Bächle]

Hi Gary,

On 10.01.2016 16:05, Gary Oberbrunner wrote:


On Sun, Jan 10, 2016 at 4:26 AM, Dirk Bächle > wrote:

On 09.01.2016 20:47, Bill Deegan wrote:

Dirk,

For me, its "pain in having to remember how to do things in mercurial which 
I only use for scons" each time I go to work on it I
have to refresh my mental cache.
Which I'm pretty sure wouldn't be measurable by such statistics. But 
(at least for me) would increase the amount of fun it is to
work on the project.


and this (I'm referring to the "increased fun" here) wouldn't result in "more 
commits" and "more bugfixes"? Jonathon Reinhart
stated this point in his mail explicitly: more git -> more commits.


This is my situation as well -- SCons is the only project I contribute to that 
still uses hg, and since I use git everywhere else
I've become pretty expert at it. It's in my fingers and I don't even think 
about it anymore. I also have dozens of git aliases and
config tweaks so I go pretty fast with it. There is of course also the better 
data model, but of course that's arguable so I'm only
mentioning my personal situation -- but I suspect I'm not unique. So would 
switching lead to more commits and bugfixes? I can't say
for sure but from what I've seen in hiring developers, almost everyone knows 
git and puts it on their resume, and I only rarely see
hg experience. So it _might_ make it easier for other contributors.



if all you other core devs feel this way, then I'm not opposed to the idea. Feel free to switch to "git" anytime, and I will adapt 
to it. My goal with asking for reference projects was to be able to point to a benefit for the whole project...and not only for 
single contributors. But there really seems to be enough momentum behind this decision to just go with the "gut feelings" of you 
all...so be it then.


Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Saša Janiška]

On Ned, 2016-01-10 at 10:05 -0500, Gary Oberbrunner wrote:

> So would switching lead to more commits and bugfixes? I can't say for
> sure but from what I've seen in hiring developers, almost everyone
> knows git and puts it on their resume, and I only rarely see hg
> experience. So it _might_ make it easier for other contributors.

For the number of devs, size of the project as well as the number of
branches used in SCons you could use Fossil (with your own tracker.)
sincem, according to my observation SCons is not known by following the
herd. ;)


Sincerely,
Gour

-- 
One who restrains his senses, keeping them under full control, 
and fixes his consciousness upon Me, is known as a man of 
steady intelligence.




___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Jason Kenny]

If this is about using git. I see two options with the least amount of work.

1) User uses a git-hg plug-in to checkout with git.
or
2) Move the code in SCons to git in bitbucket. I don’t think we have a reason 
to do a major move to another site, when the current one works great with git 
as well.

Jason



From: Russel Winder
Sent: Sunday, January 10, 2016 7:49 AM
To: dl9...@darc.de; SCons developer list
Subject: Re: [Scons-dev] Trial SCons migration to git on github

On Sat, 2016-01-09 at 14:09 +0100, Dirk Bächle wrote:
> 
[…]
> I would also like to make us a clear statement first, about what we
> want to change/migrate and why we want to do it. I'm currently 
> trying to find examples of large open-source projects (not some small
> repos, maintained by a single person) that have moved from 
> Mercurial to git. Can anyone give pointers?
> My goal here is to analyze the log/commit history in order to find
> out whether the migration actually did have a measurable effect 
> on things like "frequency of commits per month", "LOC touched per
> month", "new committers per month" and so on.

Probably the most high profile Mercurial → Git switch has been the Go
project.

The core of their rationale was workflow for pull request review and
acceptance. I suspect also that Google is trying to switch all their
work to Git.

Go switched from a Google hosted Mercurial repository with Rietveld as
the review system, to a Google hosted Git repository mirrored on GitHub
with Gerrit as the review system.
 
-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Russel Winder]

On Sun, 2016-01-10 at 17:54 +0100, Saša Janiška wrote:
> 
[…]
> Correct - nothing close to BB/GH, only http://chiselapp.com/.
> 

The big up-side of Fossil is that the wiki and issue tracker are part
of the repository. The downside is lack of traction in the "market".

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder



signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Dirk Bächle]

Hi,

On 06.01.2016 22:16, Jason Kenny wrote:

I have done the opposite myself ( moved code from guthub to bitbucket) it is 
very easy either direction.

However I have to ask. Is this about moving to Git from HG or to Github?
I think these are two different questions.



I would also like to make us a clear statement first, about what we want to change/migrate and why we want to do it. I'm currently 
trying to find examples of large open-source projects (not some small repos, maintained by a single person) that have moved from 
Mercurial to git. Can anyone give pointers?
My goal here is to analyze the log/commit history in order to find out whether the migration actually did have a measurable effect 
on things like "frequency of commits per month", "LOC touched per month", "new committers per month" and so on.


Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Bill Deegan]

Dirk,

For me, its "pain in having to remember how to do things in mercurial which
I only use for scons" each time I go to work on it I have to refresh my
mental cache.
Which I'm pretty sure wouldn't be measurable by such statistics. But (at
least for me) would increase the amount of fun it is to work on the project.

-Bill

On Sat, Jan 9, 2016 at 5:09 AM, Dirk Bächle  wrote:

> Hi,
>
> On 06.01.2016 22:16, Jason Kenny wrote:
>
>> I have done the opposite myself ( moved code from guthub to bitbucket) it
>> is very easy either direction.
>>
>> However I have to ask. Is this about moving to Git from HG or to Github?
>> I think these are two different questions.
>>
>>
> I would also like to make us a clear statement first, about what we want
> to change/migrate and why we want to do it. I'm currently trying to find
> examples of large open-source projects (not some small repos, maintained by
> a single person) that have moved from Mercurial to git. Can anyone give
> pointers?
> My goal here is to analyze the log/commit history in order to find out
> whether the migration actually did have a measurable effect on things like
> "frequency of commits per month", "LOC touched per month", "new committers
> per month" and so on.
>
> Best regards,
>
> Dirk
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[William Blevins]

It looks right at a glance.

On Wed, Jan 6, 2016 at 7:03 PM, Bill Deegan 
wrote:

> All,
>
> I wanted to see how hard this would be.
> Pretty simple. Github has a migrator which did all the work.
> If anyone wants to take a look and see if they find any issues with the
> migration take a look here
> https://github.com/bdbaddog/scons-gh-migrate
> -Bill
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Alexandre Feblot]

If I look at the branch pchdll in which 2 commits were done, githib doesn't 
show anything before those commits. This seems wrong.
https://bitbucket.org/scons/scons/commits/branch/pchdll 

https://github.com/bdbaddog/scons-gh-migrate/commits/pchdll 


Focusing on the first commit (VC11 needs PCH objects added to the link line.):
https://bitbucket.org/scons/scons/commits/552d60649cdbfc46979a493fb0d8a8618c892f79?at=pchdll
 

https://github.com/bdbaddog/scons-gh-migrate/commit/4de52be091f23e3b8c8e0027bd1d27b6bec92ef9
 


Bitbucket properly shows the single change in src/engine/SCons/Tool/mslink.py, 
whereas github seems to think that all files are just added to an empty project 
(making it impossible to see the actual change).

Conclusion: It looks like there is an issue with where branches are created 
from.

--
Alexandre Feblot

> Le 6 janv. 2016 à 20:28, William Blevins  a écrit :
> 
> It looks right at a glance.
> 
> On Wed, Jan 6, 2016 at 7:03 PM, Bill Deegan  > wrote:
> All,
> 
> I wanted to see how hard this would be.
> Pretty simple. Github has a migrator which did all the work.
> If anyone wants to take a look and see if they find any issues with the 
> migration take a look here
> https://github.com/bdbaddog/scons-gh-migrate 
> 
> -Bill
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org 
> https://pairlist2.pair.net/mailman/listinfo/scons-dev 
> 
> 
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Trial SCons migration to git on github

[Jason Kenny]

I have done the opposite myself ( moved code from guthub to bitbucket) it is 
very easy either direction.
However I have to ask. Is this about moving to Git from HG or to Github?I think 
these are two different questions.
Personally I see why some would want to move to git. However i don't see why 
one would want to move github as well.

Jason
Date: Wed, 6 Jan 2016 11:03:05 -0800
From: b...@baddogconsulting.com
To: scons-dev@scons.org
Subject: [Scons-dev] Trial SCons migration to git on github

All,

I wanted to see how hard this would be.
Pretty simple. Github has a migrator which did all the work.
If anyone wants to take a look and see if they find any issues with the 
migration take a look here
https://github.com/bdbaddog/scons-gh-migrate
-Bill


___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev   
  ___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev