From brett at python.org  Fri Feb  5 20:57:15 2016
From: brett at python.org (Brett Cannon)
Date: Sat, 06 Feb 2016 01:57:15 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to git?
Message-ID: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>

https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git

There appear to be multiple ways to convert hg repos to git, but no clear
winner. It would be great if some one/people took on the task of evaluating
the tools available out there by converting the cpython repo and seeing
which one has the best results.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160206/f7f39aef/attachment.html>

From brett at python.org  Fri Feb  5 21:01:57 2016
From: brett at python.org (Brett Cannon)
Date: Sat, 06 Feb 2016 02:01:57 +0000
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
Message-ID: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>

https://www.python.org/dev/peps/pep-0512/#adding-github-username-support-to-bugs-python-org

In order for the CLA bot to work, I need people to be able to add their
GitHub usernames to their bugs.python.org profile. I also need some API(s)
that I can hit from the bot that lets me pass in a GitHub username -- or
names, since there can be more than one, but I'm also fine making multiple
individual requests instead of multiple names in a single request -- and
get back some kind of signed/not signed/no GitHub username response (can
even be GitHub username -> b.p.o username in one call and then b.p.o CLA
status as another if that's easier).

I'm not sure if Ezio was planning to own this or not, so I'm asking if
anyone wants to take this on or help Ezio with the work if he does want to
lead it (or R. David if he wants to lead it).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160206/759b0334/attachment.html>

From nicolas.alvarez at gmail.com  Fri Feb  5 21:39:11 2016
From: nicolas.alvarez at gmail.com (=?UTF-8?Q?Nicol=C3=A1s_Alvarez?=)
Date: Fri, 5 Feb 2016 23:39:11 -0300
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
Message-ID: <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>

2016-02-05 22:57 GMT-03:00 Brett Cannon <brett at python.org>:
> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>
> There appear to be multiple ways to convert hg repos to git, but no clear
> winner. It would be great if some one/people took on the task of evaluating
> the tools available out there by converting the cpython repo and seeing
> which one has the best results.

I said I'd look into this. I didn't. Shame on me.

Trying fast-export now :)

-- 
Nicol?s

From nicolas.alvarez at gmail.com  Sat Feb  6 01:03:59 2016
From: nicolas.alvarez at gmail.com (=?UTF-8?Q?Nicol=C3=A1s_Alvarez?=)
Date: Sat, 6 Feb 2016 03:03:59 -0300
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
Message-ID: <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>

2016-02-05 23:39 GMT-03:00 Nicol?s Alvarez <nicolas.alvarez at gmail.com>:
> 2016-02-05 22:57 GMT-03:00 Brett Cannon <brett at python.org>:
>> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>>
>> There appear to be multiple ways to convert hg repos to git, but no clear
>> winner. It would be great if some one/people took on the task of evaluating
>> the tools available out there by converting the cpython repo and seeing
>> which one has the best results.
>
> I said I'd look into this. I didn't. Shame on me.
>
> Trying fast-export now :)

Update: The fast-export tool started at about 500 revs/sec but
progressively slowed down. Now it's 90% done after churning for two
hours, and each merge commit (of which there are many!) takes an
entire second by itself. I don't feel like staying awake to see it
finish.

-- 
Nicol?s

From phd at phdru.name  Sat Feb  6 10:50:51 2016
From: phd at phdru.name (Oleg Broytman)
Date: Sat, 6 Feb 2016 16:50:51 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
Message-ID: <20160206155051.GA27318@phdru.name>

Hello!

On Sat, Feb 06, 2016 at 01:57:15AM +0000, Brett Cannon <brett at python.org> wrote:
> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
> 
> There appear to be multiple ways to convert hg repos to git, but no clear
> winner. It would be great if some one/people took on the task of evaluating
> the tools available out there by converting the cpython repo and seeing
> which one has the best results.

   Let's me try git-remote-hg transport.

$ hg clone https://hg.python.org/cpython/ cpython-hg

$ time git clone hg::cpython-hg cpython-git
real  39m44.600s
user  45m54.192s
sys   1m4.184s

$ cd cpython-git/
* master                          6bd585f merge from 3.5
  remotes/origin/HEAD             -> origin/master
  remotes/origin/branches/2.7     9842886 Fix userinfo example presented in urllib2 howto.
  remotes/origin/branches/3.2     51e4a9f Issue #25940: On Windows, connecting to port 444 returns ETIMEDOUT
  remotes/origin/branches/3.3     a017765 Issue #25940: Merge ETIMEDOUT fix from 3.2 into 3.3
  remotes/origin/branches/3.4     1b9c53a reject negative data_size
  remotes/origin/branches/3.5     411a8a5 Fix userinfo example presented in urllib2 howto.
  remotes/origin/branches/default 6bd585f merge from 3.5
  remotes/origin/master           6bd585f merge from 3.5

$ git log --decorate --graph -5
*   commit 6bd585f (HEAD, origin/master, origin/branches/default, origin/HEAD, refs/hg/origin/branches/default, refs/hg/origin/bookmarks/master, master)
|\  Merge: 10cbbbf 411a8a5
| | Author: Senthil Kumaran <senthil at uthcode.com>
| | Date:   Fri Feb 5 19:37:47 2016 -0800
| | 
| |     merge from 3.5
| |   
| * commit 411a8a5 (origin/branches/3.5, refs/hg/origin/branches/3.5)
| | Author: Senthil Kumaran <senthil at uthcode.com>
| | Date:   Fri Feb 5 19:37:23 2016 -0800
| | 
| |     Fix userinfo example presented in urllib2 howto.
| |   
* | commit 10cbbbf
| | Author: Yury Selivanov <yselivanov at sprymix.com>
| | Date:   Fri Feb 5 19:40:01 2016 -0500
| | 
| |     Issue #26288: Optimize PyLong_AsDouble.
| |   
* | commit e5185e7
| | Author: Eric V. Smith <eric at trueblade.com>
| | Date:   Fri Feb 5 18:26:20 2016 -0500
| | 
| |     Switch to more idiomatic C code.
| |   
* | commit b59cb8f
| | Author: Eric V. Smith <eric at trueblade.com>
| | Date:   Fri Feb 5 18:23:08 2016 -0500

PS. git-remote-hg provides bidirectional transport. You can continue
pulling from Mercurial repository(ies) and you can commit and push back
to Mercurial repository(ies).

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From rymg19 at gmail.com  Sat Feb  6 11:37:44 2016
From: rymg19 at gmail.com (Ryan Gonzalez)
Date: Sat, 06 Feb 2016 10:37:44 -0600
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
Message-ID: <A14427B8-1D05-42CA-A903-2EDCAEBE9949@gmail.com>

I'll try hg-git!

On February 5, 2016 7:57:15 PM CST, Brett Cannon <brett at python.org> wrote:
>https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>
>There appear to be multiple ways to convert hg repos to git, but no
>clear
>winner. It would be great if some one/people took on the task of
>evaluating
>the tools available out there by converting the cpython repo and seeing
>which one has the best results.
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>core-workflow mailing list
>core-workflow at python.org
>https://mail.python.org/mailman/listinfo/core-workflow
>This list is governed by the PSF Code of Conduct:
>https://www.python.org/psf/codeofconduct

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160206/c7cde836/attachment-0001.html>

From phd at phdru.name  Sat Feb  6 11:48:16 2016
From: phd at phdru.name (Oleg Broytman)
Date: Sat, 6 Feb 2016 17:48:16 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <20160206155051.GA27318@phdru.name>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
Message-ID: <20160206164816.GA29207@phdru.name>

On Sat, Feb 06, 2016 at 04:50:51PM +0100, Oleg Broytman <phd at phdru.name> wrote:
> Hello!
> 
> On Sat, Feb 06, 2016 at 01:57:15AM +0000, Brett Cannon <brett at python.org> wrote:
> > https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
> > 
> > There appear to be multiple ways to convert hg repos to git, but no clear
> > winner. It would be great if some one/people took on the task of evaluating
> > the tools available out there by converting the cpython repo and seeing
> > which one has the best results.
> 
>    Let's me try git-remote-hg transport.
> 
> $ hg clone https://hg.python.org/cpython/ cpython-hg
> 
> $ time git clone hg::cpython-hg cpython-git
> real  39m44.600s
> user  45m54.192s
> sys   1m4.184s
> 
> $ cd cpython-git/

$ git remote add gh git at github.com:phdru/cpython.git

$ git push --all gh

   See the result at https://github.com/phdru/cpython

PS. I am `phdru' at Github.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From encukou at gmail.com  Sat Feb  6 11:57:47 2016
From: encukou at gmail.com (Petr Viktorin)
Date: Sat, 6 Feb 2016 17:57:47 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <20160206164816.GA29207@phdru.name>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
Message-ID: <56B6260B.4050105@gmail.com>

On 02/06/2016 05:48 PM, Oleg Broytman wrote:
> On Sat, Feb 06, 2016 at 04:50:51PM +0100, Oleg Broytman <phd at phdru.name> wrote:
>> Hello!
>>
>> On Sat, Feb 06, 2016 at 01:57:15AM +0000, Brett Cannon <brett at python.org> wrote:
>>> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>>>
>>> There appear to be multiple ways to convert hg repos to git, but no clear
>>> winner. It would be great if some one/people took on the task of evaluating
>>> the tools available out there by converting the cpython repo and seeing
>>> which one has the best results.
>>
>>    Let's me try git-remote-hg transport.
>>
>> $ hg clone https://hg.python.org/cpython/ cpython-hg
>>
>> $ time git clone hg::cpython-hg cpython-git
>> real  39m44.600s
>> user  45m54.192s
>> sys   1m4.184s
>>
>> $ cd cpython-git/
> 
> $ git remote add gh git at github.com:phdru/cpython.git
> 
> $ git push --all gh
> 
>    See the result at https://github.com/phdru/cpython

You might also want to try something like

   $ git repack -a -d -f --depth=250 --window=250

after importing to decrease the size of the repository for everyone
pulling from you.

(Reference: https://gcc.gnu.org/ml/gcc/2007-12/msg00165.html)


From phd at phdru.name  Sat Feb  6 12:16:28 2016
From: phd at phdru.name (Oleg Broytman)
Date: Sat, 6 Feb 2016 18:16:28 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56B6260B.4050105@gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
Message-ID: <20160206171628.GA30545@phdru.name>

On Sat, Feb 06, 2016 at 05:57:47PM +0100, Petr Viktorin <encukou at gmail.com> wrote:
> On 02/06/2016 05:48 PM, Oleg Broytman wrote:
> > $ git remote add gh git at github.com:phdru/cpython.git
> > 
> > $ git push --all gh
> > 
> >    See the result at https://github.com/phdru/cpython
> 
> You might also want to try something like
> 
>    $ git repack -a -d -f --depth=250 --window=250
> 
> after importing to decrease the size of the repository for everyone
> pulling from you.
> 
> (Reference: https://gcc.gnu.org/ml/gcc/2007-12/msg00165.html)

   See the discussion of this old and outdated message at PEP 103:
https://www.python.org/dev/peps/pep-0103/#database-maintenance

   The recommended parameters for git repack are --depth=20 --window=250
See http://vcscompare.blogspot.ru/2008/06/git-repack-parameters.html

   But yes, you're right, git gc/repack is very much recommended.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From ezio.melotti at gmail.com  Sat Feb  6 13:25:51 2016
From: ezio.melotti at gmail.com (Ezio Melotti)
Date: Sat, 6 Feb 2016 20:25:51 +0200
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
In-Reply-To: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
References: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
Message-ID: <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>

On Sat, Feb 6, 2016 at 4:01 AM, Brett Cannon <brett at python.org> wrote:
> https://www.python.org/dev/peps/pep-0512/#adding-github-username-support-to-bugs-python-org
>
> In order for the CLA bot to work, I need people to be able to add their
> GitHub usernames to their bugs.python.org profile. I also need some API(s)
> that I can hit from the bot that lets me pass in a GitHub username -- or
> names, since there can be more than one, but I'm also fine making multiple
> individual requests instead of multiple names in a single request -- and get
> back some kind of signed/not signed/no GitHub username response (can even be
> GitHub username -> b.p.o username in one call and then b.p.o CLA status as
> another if that's easier).
>
> I'm not sure if Ezio was planning to own this or not, so I'm asking if
> anyone wants to take this on or help Ezio with the work if he does want to
> lead it (or R. David if he wants to lead it).

Adding this should be relatively easy -- the new field must be added
to the schema and a few extra lines in the templates should be added
as well to allow users to add/edit/see it.  Testing it is a bit more
difficult though.
For the API, we can add a temporary page to retrieve the git user name
as json or wait until I finish reviewing and merging the REST API
patch (any help on this is more than welcome).
I'm trying to set up a docker container with a test instance of the
tracker and create a few test issues/users, so that I can test things
more conveniently.  It might also be useful to make a psf account on
dockerhub (or somewhere else) where to keep this and possibly other
containers.

Best Regards,
Ezio Melotti

From brett at python.org  Sat Feb  6 14:22:08 2016
From: brett at python.org (Brett Cannon)
Date: Sat, 06 Feb 2016 19:22:08 +0000
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
In-Reply-To: <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>
References: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
 <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>
Message-ID: <CAP1=2W5XshWAbff4znaVLzQKODtcfoS9TbhZ_ac6u8F8FtYhpQ@mail.gmail.com>

On Sat, 6 Feb 2016 at 10:25 Ezio Melotti <ezio.melotti at gmail.com> wrote:

> On Sat, Feb 6, 2016 at 4:01 AM, Brett Cannon <brett at python.org> wrote:
> >
> https://www.python.org/dev/peps/pep-0512/#adding-github-username-support-to-bugs-python-org
> >
> > In order for the CLA bot to work, I need people to be able to add their
> > GitHub usernames to their bugs.python.org profile. I also need some
> API(s)
> > that I can hit from the bot that lets me pass in a GitHub username -- or
> > names, since there can be more than one, but I'm also fine making
> multiple
> > individual requests instead of multiple names in a single request -- and
> get
> > back some kind of signed/not signed/no GitHub username response (can
> even be
> > GitHub username -> b.p.o username in one call and then b.p.o CLA status
> as
> > another if that's easier).
> >
> > I'm not sure if Ezio was planning to own this or not, so I'm asking if
> > anyone wants to take this on or help Ezio with the work if he does want
> to
> > lead it (or R. David if he wants to lead it).
>
> Adding this should be relatively easy -- the new field must be added
> to the schema and a few extra lines in the templates should be added
> as well to allow users to add/edit/see it.  Testing it is a bit more
> difficult though.
> For the API, we can add a temporary page to retrieve the git user name
> as json or wait until I finish reviewing and merging the REST API
> patch (any help on this is more than welcome).
> I'm trying to set up a docker container with a test instance of the
> tracker and create a few test issues/users, so that I can test things
> more conveniently.  It might also be useful to make a psf account on
> dockerhub (or somewhere else) where to keep this and possibly other
> containers.
>

IOW if people want to help in a way that involves coding, then please help
Ezio with b.p.o stuff. This is also beneficial long-term for maintaining
the issue tracker and changes that will be needed in the future for getting
cpython moved over.

As for a PSF account on dockerhub, I would ask the PSF infra team what they
think and have them administer it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160206/38c38a74/attachment.html>

From brett at python.org  Sat Feb  6 14:42:47 2016
From: brett at python.org (Brett Cannon)
Date: Sat, 06 Feb 2016 19:42:47 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <20160206171628.GA30545@phdru.name>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
Message-ID: <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>

FIrst off, thanks to everyone who has stepped out and started running
various approaches to test them out! Any and all help is appreciated since
there are a lot of parts to this transition and I definitely don't want to
do it on my own (especially since Python 2.7 would have its last release by
the time I would finish with all the work).

Second, does anyone -- or group of people -- want to own this and figure
out what to try out, keep track of what has been tried, come up with some
way to evaluate the results (both for accuracy in the conversion but also
if there is some way to say one is better than another), and come back to
the list with a solution? All I ask is you try to do it in the open
(whether it's by a Google Doc that's open to the public for comment or a
GitHub repo, I don't care) so people who want to help can? It seems there
are people definitely willing to try out the tools and report back, but I'm
looking for someone/people to organize the effort and come back to me with
a thought-out solution so I don't have to. :)


On Sat, 6 Feb 2016 at 09:16 Oleg Broytman <phd at phdru.name> wrote:

> On Sat, Feb 06, 2016 at 05:57:47PM +0100, Petr Viktorin <encukou at gmail.com>
> wrote:
> > On 02/06/2016 05:48 PM, Oleg Broytman wrote:
> > > $ git remote add gh git at github.com:phdru/cpython.git
> > >
> > > $ git push --all gh
> > >
> > >    See the result at https://github.com/phdru/cpython
> >
> > You might also want to try something like
> >
> >    $ git repack -a -d -f --depth=250 --window=250
> >
> > after importing to decrease the size of the repository for everyone
> > pulling from you.
> >
> > (Reference: https://gcc.gnu.org/ml/gcc/2007-12/msg00165.html)
>
>    See the discussion of this old and outdated message at PEP 103:
> https://www.python.org/dev/peps/pep-0103/#database-maintenance
>
>    The recommended parameters for git repack are --depth=20 --window=250
> See http://vcscompare.blogspot.ru/2008/06/git-repack-parameters.html
>
>    But yes, you're right, git gc/repack is very much recommended.
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            phd at phdru.name
>            Programmers don't die, they just GOSUB without RETURN.
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160206/a0ead9d8/attachment-0001.html>

From ncoghlan at gmail.com  Sun Feb  7 02:21:28 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Sun, 7 Feb 2016 17:21:28 +1000
Subject: [core-workflow] Presentation on Rust's GitHub based automation tools
Message-ID: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>

I was at linux.conf.au 2016 last week, and one of the presentations
was from Mozilla's Emily Dunham on some of the infrastructure
automation they use with Rust and other GitHub based projects:
https://www.youtube.com/watch?v=dIageYT0Vgg

In addition to their merge bot project homu (which we've talked about
previously), they also have:

highfive (a greeter bot): https://github.com/nrc/highfive
starters (an issue curator): https://starters.servo.org/

The first project looks for folks submitting their first PR or issue,
and responds with some standard info to save humans from having to do
it later (like pointers to the Code of Conduct and the Contributor
Licensing Agreement, as well as explanations of how the contribution
process works)

The second one is designed to provide a better answer to the "How do I
get started?" question by making it easy for developers to tag simpler
issues. This could presumably also be used to provide separate views
based on what folks want to work on (e.g. documentation, Python code,
C code)

While these wouldn't necessarily be something we wanted to set up
immediately, it likely makes a lot of sense to try to share the tool
maintenance load with Mozilla rather than going for a completely
custom setup.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From ncoghlan at gmail.com  Sun Feb  7 02:29:34 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Sun, 7 Feb 2016 17:29:34 +1000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
 <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
Message-ID: <CADiSq7fyOvKVmGHRVT5CVZkygn7DHHGJpzyM5GYvKHzbBt6zfw@mail.gmail.com>

On 7 February 2016 at 05:42, Brett Cannon <brett at python.org> wrote:
> FIrst off, thanks to everyone who has stepped out and started running
> various approaches to test them out! Any and all help is appreciated since
> there are a lot of parts to this transition and I definitely don't want to
> do it on my own (especially since Python 2.7 would have its last release by
> the time I would finish with all the work).
>
> Second, does anyone -- or group of people -- want to own this and figure out
> what to try out, keep track of what has been tried, come up with some way to
> evaluate the results (both for accuracy in the conversion but also if there
> is some way to say one is better than another), and come back to the list
> with a solution? All I ask is you try to do it in the open (whether it's by
> a Google Doc that's open to the public for comment or a GitHub repo, I don't
> care) so people who want to help can? It seems there are people definitely
> willing to try out the tools and report back, but I'm looking for
> someone/people to organize the effort and come back to me with a thought-out
> solution so I don't have to. :)

For beaker-project.org, I found it really useful to have an
"administrivia" repo in our Gerrit instance for all the random scripts
that didn't have a proper home, but we also didn't want the sole copy
living on someone's hard drive.

Creating a similar repo (e.g. "core-workflow") under
https://github.com/python would likely be useful here, since it would
not only give people a place to collaborate on utility scripts, but
also an ad hoc issue tracker for tasks that don't have a more
appropriate home.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From ncoghlan at gmail.com  Sun Feb  7 02:24:00 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Sun, 7 Feb 2016 17:24:00 +1000
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
In-Reply-To: <CAP1=2W5XshWAbff4znaVLzQKODtcfoS9TbhZ_ac6u8F8FtYhpQ@mail.gmail.com>
References: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
 <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>
 <CAP1=2W5XshWAbff4znaVLzQKODtcfoS9TbhZ_ac6u8F8FtYhpQ@mail.gmail.com>
Message-ID: <CADiSq7dufL+Yk_dLKk4rbLU5TXNyV3G3-zQQcow0kPEqNjiTcA@mail.gmail.com>

On 7 February 2016 at 05:22, Brett Cannon <brett at python.org> wrote:
> IOW if people want to help in a way that involves coding, then please help
> Ezio with b.p.o stuff. This is also beneficial long-term for maintaining the
> issue tracker and changes that will be needed in the future for getting
> cpython moved over.
>
> As for a PSF account on dockerhub, I would ask the PSF infra team what they
> think and have them administer it.

A PSF account on DockerHub sounds like a good idea to me - that would
likely also be useful for hosting the reference image for the
manylinux1 build environment.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From berker.peksag at gmail.com  Sun Feb  7 04:14:43 2016
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Sun, 7 Feb 2016 11:14:43 +0200
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
Message-ID: <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>

On Sun, Feb 7, 2016 at 9:21 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> I was at linux.conf.au 2016 last week, and one of the presentations
> was from Mozilla's Emily Dunham on some of the infrastructure
> automation they use with Rust and other GitHub based projects:
> https://www.youtube.com/watch?v=dIageYT0Vgg

I just watched it, great talk. Thanks for sharing!

> In addition to their merge bot project homu (which we've talked about
> previously), they also have:
>
> highfive (a greeter bot): https://github.com/nrc/highfive

This is a good idea.

> starters (an issue curator): https://starters.servo.org/
>
> While these wouldn't necessarily be something we wanted to set up
> immediately, it likely makes a lot of sense to try to share the tool
> maintenance load with Mozilla rather than going for a completely
> custom setup.

The biggest problem of these tools is that they don't provide an API
or a framework to use as a base. They have a lot of project specific
code and they don't work on Python 3. So you'll need to write your own
code anyway. We are going to write a lot of bots in the next months so
I think we will eventually create some sort of framework to share some
code.

Coordinating with Mozilla (or any other organization) requires a big
amount of time, and I simply don't have enough time and motivation
right now. However, I'm planning to send an email to the
django-developers list [1] when I finish to document my bot. I have a
test organization at https://github.com/fayton. See also
https://github.com/fayton/cpython/pull/1 for an example pull request
(the name of the bot is just a placeholder, Brett will give it a name
:))

--Berker

[1] They might be interested since we (will) have almost identical
workflow with them (they also have multiple maintenance branches for
example)

From soltysh at gmail.com  Sun Feb  7 05:23:10 2016
From: soltysh at gmail.com (Maciej Szulik)
Date: Sun, 7 Feb 2016 11:23:10 +0100
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
Message-ID: <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>

On Sun, Feb 7, 2016 at 10:14 AM, Berker Peksa? <berker.peksag at gmail.com> wrote:
> On Sun, Feb 7, 2016 at 9:21 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> I was at linux.conf.au 2016 last week, and one of the presentations
>> was from Mozilla's Emily Dunham on some of the infrastructure
>> automation they use with Rust and other GitHub based projects:
>> https://www.youtube.com/watch?v=dIageYT0Vgg
>
> I just watched it, great talk. Thanks for sharing!
>
>> In addition to their merge bot project homu (which we've talked about
>> previously), they also have:
>>
>> highfive (a greeter bot): https://github.com/nrc/highfive
>
> This is a good idea.
>
>> starters (an issue curator): https://starters.servo.org/
>>
>> While these wouldn't necessarily be something we wanted to set up
>> immediately, it likely makes a lot of sense to try to share the tool
>> maintenance load with Mozilla rather than going for a completely
>> custom setup.
>
> The biggest problem of these tools is that they don't provide an API
> or a framework to use as a base. They have a lot of project specific
> code and they don't work on Python 3. So you'll need to write your own
> code anyway. We are going to write a lot of bots in the next months so
> I think we will eventually create some sort of framework to share some
> code.

Talking from the position of owning a similar bot in OpenShift, I quite
certain that it's really hard to have common base. Since these bots
address specific project and there are not two exactly the same projects
with  exactly the same workflow. I think what Nick meant to show is,
what we should target, more or less at least.


> Coordinating with Mozilla (or any other organization) requires a big
> amount of time, and I simply don't have enough time and motivation
> right now. However, I'm planning to send an email to the
> django-developers list [1] when I finish to document my bot. I have a
> test organization at https://github.com/fayton. See also
> https://github.com/fayton/cpython/pull/1 for an example pull request
> (the name of the bot is just a placeholder, Brett will give it a name
> :))
>
> --Berker
>
> [1] They might be interested since we (will) have almost identical
> workflow with them (they also have multiple maintenance branches for
> example)
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct

Maciej

From brett at python.org  Sun Feb  7 14:27:23 2016
From: brett at python.org (Brett Cannon)
Date: Sun, 07 Feb 2016 19:27:23 +0000
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
Message-ID: <CAP1=2W6ANRXbzsjO=Qsdj2SbbVrVFCjVf=cOh_CLsZ8zwRSqKw@mail.gmail.com>

On Sun, 7 Feb 2016 at 02:23 Maciej Szulik <soltysh at gmail.com> wrote:

> On Sun, Feb 7, 2016 at 10:14 AM, Berker Peksa? <berker.peksag at gmail.com>
> wrote:
> > On Sun, Feb 7, 2016 at 9:21 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> >> I was at linux.conf.au 2016 last week, and one of the presentations
> >> was from Mozilla's Emily Dunham on some of the infrastructure
> >> automation they use with Rust and other GitHub based projects:
> >> https://www.youtube.com/watch?v=dIageYT0Vgg
> >
> > I just watched it, great talk. Thanks for sharing!
> >
> >> In addition to their merge bot project homu (which we've talked about
> >> previously), they also have:
> >>
> >> highfive (a greeter bot): https://github.com/nrc/highfive



The greeter bit could be rolled into
https://github.com/brettcannon/knights-who-say-ni since it has to watch for
newly opened pull requests for the CLA check anyway.



>
> >
> > This is a good idea.
> >
> >> starters (an issue curator): https://starters.servo.org/
> >>
> >> While these wouldn't necessarily be something we wanted to set up
> >> immediately, it likely makes a lot of sense to try to share the tool
> >> maintenance load with Mozilla rather than going for a completely
> >> custom setup.
> >
> > The biggest problem of these tools is that they don't provide an API
> > or a framework to use as a base. They have a lot of project specific
> > code and they don't work on Python 3. So you'll need to write your own
> > code anyway. We are going to write a lot of bots in the next months so
> > I think we will eventually create some sort of framework to share some
> > code.
>
> Talking from the position of owning a similar bot in OpenShift, I quite
> certain that it's really hard to have common base. Since these bots
> address specific project and there are not two exactly the same projects
> with  exactly the same workflow. I think what Nick meant to show is,
> what we should target, more or less at least.
>

Having started writing the CLA bot, I can attest that it's tough to
abstract it all in a way that's easy to swap out the parts. I am trying to
do my best, though, so that when it comes to swap out either the server
host, contribution host, or CLA records host it won't be a complete rewrite.

-Brett


>
>
> > Coordinating with Mozilla (or any other organization) requires a big
> > amount of time, and I simply don't have enough time and motivation
> > right now. However, I'm planning to send an email to the
> > django-developers list [1] when I finish to document my bot. I have a
> > test organization at https://github.com/fayton. See also
> > https://github.com/fayton/cpython/pull/1 for an example pull request
> > (the name of the bot is just a placeholder, Brett will give it a name
> > :))
> >
> > --Berker
> >
> > [1] They might be interested since we (will) have almost identical
> > workflow with them (they also have multiple maintenance branches for
> > example)
> > _______________________________________________
> > core-workflow mailing list
> > core-workflow at python.org
> > https://mail.python.org/mailman/listinfo/core-workflow
> > This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
> Maciej
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160207/fdc316f0/attachment.html>

From rymg19 at gmail.com  Sun Feb  7 17:50:29 2016
From: rymg19 at gmail.com (Ryan Gonzalez)
Date: Sun, 7 Feb 2016 16:50:29 -0600
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <A14427B8-1D05-42CA-A903-2EDCAEBE9949@gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <A14427B8-1D05-42CA-A903-2EDCAEBE9949@gmail.com>
Message-ID: <CAO41-mMWa=oP8Fkpbp5B00EiKktp7XRY4GaV-2FZJrLy2TKvLw@mail.gmail.com>

Well, hg-git might not work...

I cloned the CPython repo. I then ran `hg gexport`, which converts the
repository to Git. Took three hours, but it worked!

However, actually attempted to push the result to a Git repo failed
miserably. After five hours, Mercurial ran out of memory in the "adding
objects" stage. And I have 6 GB of RAM!

Right now, I'm trying to see if I can work around it. This may not work
out, though.

On Sat, Feb 6, 2016 at 10:37 AM, Ryan Gonzalez <rymg19 at gmail.com> wrote:

> I'll try hg-git!
>
> On February 5, 2016 7:57:15 PM CST, Brett Cannon <brett at python.org> wrote:
>>
>>
>> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>>
>> There appear to be multiple ways to convert hg repos to git, but no clear
>> winner. It would be great if some one/people took on the task of evaluating
>> the tools available out there by converting the cpython repo and seeing
>> which one has the best results.
>>
>> ------------------------------
>>
>> core-workflow mailing list
>> core-workflow at python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
>>
>>
> --
> Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
>



-- 
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something?s wrong.
http://kirbyfan64.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160207/b190b7a8/attachment.html>

From ncoghlan at gmail.com  Sun Feb  7 23:07:17 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Mon, 8 Feb 2016 14:07:17 +1000
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
Message-ID: <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>

On 7 February 2016 at 20:23, Maciej Szulik <soltysh at gmail.com> wrote:
> Talking from the position of owning a similar bot in OpenShift, I quite
> certain that it's really hard to have common base. Since these bots
> address specific project and there are not two exactly the same projects
> with  exactly the same workflow. I think what Nick meant to show is,
> what we should target, more or less at least.

It was a combination of a suggestion and a question. The suggestion
was "Rust's automation UX seems nice, I think it would be desirable to
target similar capabilities for CPython", the question was "Would it
be feasible to collaborate on actual automation development?".

It sounds like the pragmatic answer to the latter is "No, the
additional coordination overhead isn't worth the potential pay-off",
and I think that's fine - our respective communities can still learn
from each other when it comes to our definitions of "What does 'good'
look like?" in workflow design.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From motoom at xs4all.nl  Mon Feb  8 04:18:35 2016
From: motoom at xs4all.nl (Michiel Overtoom)
Date: Mon, 8 Feb 2016 10:18:35 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAO41-mMWa=oP8Fkpbp5B00EiKktp7XRY4GaV-2FZJrLy2TKvLw@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <A14427B8-1D05-42CA-A903-2EDCAEBE9949@gmail.com>
 <CAO41-mMWa=oP8Fkpbp5B00EiKktp7XRY4GaV-2FZJrLy2TKvLw@mail.gmail.com>
Message-ID: <8F1B5D38-6402-47A4-9DE0-484583BC91A8@xs4all.nl>


Hi,

ESR wrote a repository migration tool which probably could be used for this, Reposurgeon:

  http://www.catb.org/esr/reposurgeon/

He used it (among other things) to migrate the huge emacs repository to git: http://esr.ibiblio.org/?p=5634

PS. Reposurgon is written in Python ;-)

Greetings,


From brett at python.org  Mon Feb  8 12:14:46 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 08 Feb 2016 17:14:46 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <8F1B5D38-6402-47A4-9DE0-484583BC91A8@xs4all.nl>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <A14427B8-1D05-42CA-A903-2EDCAEBE9949@gmail.com>
 <CAO41-mMWa=oP8Fkpbp5B00EiKktp7XRY4GaV-2FZJrLy2TKvLw@mail.gmail.com>
 <8F1B5D38-6402-47A4-9DE0-484583BC91A8@xs4all.nl>
Message-ID: <CAP1=2W5PvcUh2v+3uXBpRkc0FUwNkAs_fUK-8GPC6OSX_u-6PA@mail.gmail.com>

On Mon, 8 Feb 2016 at 01:19 Michiel Overtoom <motoom at xs4all.nl> wrote:

>
> Hi,
>
> ESR wrote a repository migration tool which probably could be used for
> this, Reposurgeon:
>
>   http://www.catb.org/esr/reposurgeon/
>
> He used it (among other things) to migrate the huge emacs repository to
> git: http://esr.ibiblio.org/?p=5634
>
> PS. Reposurgon is written in Python ;-)
>

If you (or anyone else) wants to try converting the cpython repo using the
tool that would be appreciated!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160208/08e43fd9/attachment.html>

From francismb at email.de  Mon Feb  8 12:34:12 2016
From: francismb at email.de (francismb)
Date: Mon, 8 Feb 2016 18:34:12 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CADiSq7fyOvKVmGHRVT5CVZkygn7DHHGJpzyM5GYvKHzbBt6zfw@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CADiSq7fyOvKVmGHRVT5CVZkygn7DHHGJpzyM5GYvKHzbBt6zfw@mail.gmail.com>
Message-ID: <56B8D194.4040800@email.de>

Hi,

On 02/07/2016 08:29 AM, Nick Coghlan wrote:

> 
> Creating a similar repo (e.g. "core-workflow") under
> https://github.com/python would likely be useful here, since it would
> not only give people a place to collaborate on utility scripts, but
> also an ad hoc issue tracker for tasks that don't have a more
> appropriate home.
> 
+1, plus IMHO it would help to document the workflow.

Regards,
francis

From senthil at uthcode.com  Mon Feb  8 12:47:25 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Mon, 8 Feb 2016 09:47:25 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
 <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
Message-ID: <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>

Hi Brett,

On Sat, Feb 6, 2016 at 11:42 AM, Brett Cannon <brett at python.org> wrote:

> It seems there are people definitely willing to try out the tools and
> report back, but I'm looking for someone/people to organize the effort and
> come back to me with a thought-out solution so I don't have to. :)
>

I wanted to get involved with this process. I am ready to help you here.

https://github.com/orsenthil/cpython-hg-to-git

Here I started documenting our discussion so far. I will continue to
evaluate the tools (with other developers this list) and we'll try to come
up with a conclusive suggestion for our migration.

Thank you,
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160208/669bdb05/attachment.html>

From brett at python.org  Mon Feb  8 13:17:09 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 08 Feb 2016 18:17:09 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56B8D194.4040800@email.de>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CADiSq7fyOvKVmGHRVT5CVZkygn7DHHGJpzyM5GYvKHzbBt6zfw@mail.gmail.com>
 <56B8D194.4040800@email.de>
Message-ID: <CAP1=2W6Zrjn+dQT1ShS6wnPpb9-H9Akub6hw-JJ5EbERsaiFAw@mail.gmail.com>

On Mon, 8 Feb 2016 at 09:34 francismb <francismb at email.de> wrote:

> Hi,
>
> On 02/07/2016 08:29 AM, Nick Coghlan wrote:
>
> >
> > Creating a similar repo (e.g. "core-workflow") under
> > https://github.com/python would likely be useful here, since it would
> > not only give people a place to collaborate on utility scripts, but
> > also an ad hoc issue tracker for tasks that don't have a more
> > appropriate home.
> >
> +1, plus IMHO it would help to document the workflow.
>

The workflow will be documented in the devguide, so that's not a worry. As
for collecting things in a repo like that, it's a possibility, but it does
require me managing it since I will have to manually add people to have
commit access as we don't even have the core devs on GitHub yet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160208/5f8b9dce/attachment.html>

From brett at python.org  Mon Feb  8 13:23:03 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 08 Feb 2016 18:23:03 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
Message-ID: <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>

On Mon, 8 Feb 2016 at 09:54 Senthil Kumaran <senthil at uthcode.com> wrote:

> Hi Brett,
>
> On Sat, Feb 6, 2016 at 11:42 AM, Brett Cannon <brett at python.org> wrote:
>
>> It seems there are people definitely willing to try out the tools and
>> report back, but I'm looking for someone/people to organize the effort and
>> come back to me with a thought-out solution so I don't have to. :)
>>
>
> I wanted to get involved with this process. I am ready to help you here.
>
> https://github.com/orsenthil/cpython-hg-to-git
>
> Here I started documenting our discussion so far. I will continue to
> evaluate the tools (with other developers this list) and we'll try to come
> up with a conclusive suggestion for our migration.
>
>
Thanks to much, Senthil! When I get a chance I will update the PEP to say
this step of the migration is in process and you as in charge of it.

-Brett

P.S.: For this whole migration I'm going to try and delegate where
appropriate, so this won't be the last time I reach out for help. I
anticipate helping with bugs.python.org is going to be the biggest
stumbling block/need. And for those that wanted GitLab over GitHub, a vast
majority of this migration is Git host-agnostic, and so this is necessary
for after we leave GitHub (either because we're unhappy with GitHub or
because it's simply time to move; nothing is forever).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160208/dc8a2296/attachment-0001.html>

From soltysh at gmail.com  Mon Feb  8 16:11:22 2016
From: soltysh at gmail.com (Maciej Szulik)
Date: Mon, 8 Feb 2016 22:11:22 +0100
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
 <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>
Message-ID: <CALC2N4Z3NSetnwzDgJQapb5chtDDp+YYeFaSUr4CkOJwnw0qJg@mail.gmail.com>

On Mon, Feb 8, 2016 at 5:07 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 7 February 2016 at 20:23, Maciej Szulik <soltysh at gmail.com> wrote:
>> Talking from the position of owning a similar bot in OpenShift, I quite
>> certain that it's really hard to have common base. Since these bots
>> address specific project and there are not two exactly the same projects
>> with  exactly the same workflow. I think what Nick meant to show is,
>> what we should target, more or less at least.
>
> It was a combination of a suggestion and a question. The suggestion
> was "Rust's automation UX seems nice, I think it would be desirable to
> target similar capabilities for CPython", the question was "Would it
> be feasible to collaborate on actual automation development?".
>
> It sounds like the pragmatic answer to the latter is "No, the
> additional coordination overhead isn't worth the potential pay-off",
> and I think that's fine - our respective communities can still learn
> from each other when it comes to our definitions of "What does 'good'
> look like?" in workflow design.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

I've also reminded one really handy solution described in the presentation,
which is auto-assigning PR to the owner of certain area. With the list we keep
here: https://docs.python.org/devguide/experts.html we could pretty easily
do such mechanism. This will be handy for the devs because assigning
a specific issue will trigger an email notification of such, which in turn is
similar to our noisy in bug tracker. Otherwise the PRs might end up hanging
there until somebody will do that manually.

Having said that Brett if you need help with it - I'm here to help you.

Cheers,
Maciej

From brett at python.org  Tue Feb  9 13:54:32 2016
From: brett at python.org (Brett Cannon)
Date: Tue, 09 Feb 2016 18:54:32 +0000
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CALC2N4Z3NSetnwzDgJQapb5chtDDp+YYeFaSUr4CkOJwnw0qJg@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
 <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>
 <CALC2N4Z3NSetnwzDgJQapb5chtDDp+YYeFaSUr4CkOJwnw0qJg@mail.gmail.com>
Message-ID: <CAP1=2W6OonAerbV0MoU7YRp04swk37PFLOa3BDUvP-Ec1B1b2A@mail.gmail.com>

On Mon, 8 Feb 2016 at 13:11 Maciej Szulik <soltysh at gmail.com> wrote:

> On Mon, Feb 8, 2016 at 5:07 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> > On 7 February 2016 at 20:23, Maciej Szulik <soltysh at gmail.com> wrote:
> >> Talking from the position of owning a similar bot in OpenShift, I quite
> >> certain that it's really hard to have common base. Since these bots
> >> address specific project and there are not two exactly the same projects
> >> with  exactly the same workflow. I think what Nick meant to show is,
> >> what we should target, more or less at least.
> >
> > It was a combination of a suggestion and a question. The suggestion
> > was "Rust's automation UX seems nice, I think it would be desirable to
> > target similar capabilities for CPython", the question was "Would it
> > be feasible to collaborate on actual automation development?".
> >
> > It sounds like the pragmatic answer to the latter is "No, the
> > additional coordination overhead isn't worth the potential pay-off",
> > and I think that's fine - our respective communities can still learn
> > from each other when it comes to our definitions of "What does 'good'
> > look like?" in workflow design.
> >
> > Cheers,
> > Nick.
> >
> > --
> > Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>
> I've also reminded one really handy solution described in the presentation,
> which is auto-assigning PR to the owner of certain area. With the list we
> keep
> here: https://docs.python.org/devguide/experts.html we could pretty easily
> do such mechanism. This will be handy for the devs because assigning
> a specific issue will trigger an email notification of such, which in turn
> is
> similar to our noisy in bug tracker. Otherwise the PRs might end up hanging
> there until somebody will do that manually.
>
> Having said that Brett if you need help with it - I'm here to help you.
>

:) Thanks. Once we have migrated the repositories over we can start
discussing enhancements to the workflow like automatic reviewer assignment
(and I personally have some ideas about PR assignment as well for when
there isn't an expert).

But I don't want to get too distracted by this bonus work when we haven't
even started most of the work required to simply match our current
workflow. It's great that people are excited about making things better and
I don't want to squash people's energy to help, but I also don't want to
get too distracted by enhancements when we haven't even started a bunch of
the minimum work to even move to GitHub, let alone take advantage of what
bonus features it will bring to the table.

My current worry is that we are going to get blocked on Roundup work
because right now only Ezio and R. David know how that stuff works. Once
the CLA bot is finished I'm going to shift to helping with that, but it
will obviously go faster if others can also help with bugs.python.org work
because we can't switch over until we have a minimum workflow that matches
our current one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160209/09e511a0/attachment.html>

From soltysh at gmail.com  Wed Feb 10 07:29:12 2016
From: soltysh at gmail.com (Maciej Szulik)
Date: Wed, 10 Feb 2016 13:29:12 +0100
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CAP1=2W6OonAerbV0MoU7YRp04swk37PFLOa3BDUvP-Ec1B1b2A@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
 <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>
 <CALC2N4Z3NSetnwzDgJQapb5chtDDp+YYeFaSUr4CkOJwnw0qJg@mail.gmail.com>
 <CAP1=2W6OonAerbV0MoU7YRp04swk37PFLOa3BDUvP-Ec1B1b2A@mail.gmail.com>
Message-ID: <CALC2N4Z+ShfVVQ8csNYsJrDb-Ve=ZHVLkvng0LhK3QOJxRDpYw@mail.gmail.com>

On Tue, Feb 9, 2016 at 7:54 PM, Brett Cannon <brett at python.org> wrote:
>
>
> On Mon, 8 Feb 2016 at 13:11 Maciej Szulik <soltysh at gmail.com> wrote:
>>
>> On Mon, Feb 8, 2016 at 5:07 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> > On 7 February 2016 at 20:23, Maciej Szulik <soltysh at gmail.com> wrote:
>> >> Talking from the position of owning a similar bot in OpenShift, I quite
>> >> certain that it's really hard to have common base. Since these bots
>> >> address specific project and there are not two exactly the same
>> >> projects
>> >> with  exactly the same workflow. I think what Nick meant to show is,
>> >> what we should target, more or less at least.
>> >
>> > It was a combination of a suggestion and a question. The suggestion
>> > was "Rust's automation UX seems nice, I think it would be desirable to
>> > target similar capabilities for CPython", the question was "Would it
>> > be feasible to collaborate on actual automation development?".
>> >
>> > It sounds like the pragmatic answer to the latter is "No, the
>> > additional coordination overhead isn't worth the potential pay-off",
>> > and I think that's fine - our respective communities can still learn
>> > from each other when it comes to our definitions of "What does 'good'
>> > look like?" in workflow design.
>> >
>> > Cheers,
>> > Nick.
>> >
>> > --
>> > Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>>
>> I've also reminded one really handy solution described in the
>> presentation,
>> which is auto-assigning PR to the owner of certain area. With the list we
>> keep
>> here: https://docs.python.org/devguide/experts.html we could pretty easily
>> do such mechanism. This will be handy for the devs because assigning
>> a specific issue will trigger an email notification of such, which in turn
>> is
>> similar to our noisy in bug tracker. Otherwise the PRs might end up
>> hanging
>> there until somebody will do that manually.
>>
>> Having said that Brett if you need help with it - I'm here to help you.
>
>
> :) Thanks. Once we have migrated the repositories over we can start
> discussing enhancements to the workflow like automatic reviewer assignment
> (and I personally have some ideas about PR assignment as well for when there
> isn't an expert).
>
> But I don't want to get too distracted by this bonus work when we haven't
> even started most of the work required to simply match our current workflow.
> It's great that people are excited about making things better and I don't
> want to squash people's energy to help, but I also don't want to get too
> distracted by enhancements when we haven't even started a bunch of the
> minimum work to even move to GitHub, let alone take advantage of what bonus
> features it will bring to the table.
>
> My current worry is that we are going to get blocked on Roundup work because
> right now only Ezio and R. David know how that stuff works. Once the CLA bot
> is finished I'm going to shift to helping with that, but it will obviously
> go faster if others can also help with bugs.python.org work because we can't
> switch over until we have a minimum workflow that matches our current one.

What's there to be done and how can I help with that, in that case?

Maciej

From brett at python.org  Wed Feb 10 15:30:43 2016
From: brett at python.org (Brett Cannon)
Date: Wed, 10 Feb 2016 20:30:43 +0000
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CALC2N4Z+ShfVVQ8csNYsJrDb-Ve=ZHVLkvng0LhK3QOJxRDpYw@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
 <CAF4280JKfkApfvAt_S9088q=JqWJjNs5VDBU7bo3Ma9s4zFugA@mail.gmail.com>
 <CALC2N4Ygm2B35ipTJRrgXMq49CwXDyXY+ad3m1D91yQKUKeZfQ@mail.gmail.com>
 <CADiSq7e7-+2A7ffVVhnMBzuWpY2EUP5G7D3FV+SWeDYx0p+65w@mail.gmail.com>
 <CALC2N4Z3NSetnwzDgJQapb5chtDDp+YYeFaSUr4CkOJwnw0qJg@mail.gmail.com>
 <CAP1=2W6OonAerbV0MoU7YRp04swk37PFLOa3BDUvP-Ec1B1b2A@mail.gmail.com>
 <CALC2N4Z+ShfVVQ8csNYsJrDb-Ve=ZHVLkvng0LhK3QOJxRDpYw@mail.gmail.com>
Message-ID: <CAP1=2W4ryjjO4=44pG2SdMdYGCPKXffzUtDCJFPjh-zB459TFA@mail.gmail.com>

See
https://mail.python.org/pipermail/core-workflow/2016-February/000469.html and
Ezio's follow-up (and yes, you can help :) .

On Wed, 10 Feb 2016 at 04:29 Maciej Szulik <soltysh at gmail.com> wrote:

> On Tue, Feb 9, 2016 at 7:54 PM, Brett Cannon <brett at python.org> wrote:
> >
> >
> > On Mon, 8 Feb 2016 at 13:11 Maciej Szulik <soltysh at gmail.com> wrote:
> >>
> >> On Mon, Feb 8, 2016 at 5:07 AM, Nick Coghlan <ncoghlan at gmail.com>
> wrote:
> >> > On 7 February 2016 at 20:23, Maciej Szulik <soltysh at gmail.com> wrote:
> >> >> Talking from the position of owning a similar bot in OpenShift, I
> quite
> >> >> certain that it's really hard to have common base. Since these bots
> >> >> address specific project and there are not two exactly the same
> >> >> projects
> >> >> with  exactly the same workflow. I think what Nick meant to show is,
> >> >> what we should target, more or less at least.
> >> >
> >> > It was a combination of a suggestion and a question. The suggestion
> >> > was "Rust's automation UX seems nice, I think it would be desirable to
> >> > target similar capabilities for CPython", the question was "Would it
> >> > be feasible to collaborate on actual automation development?".
> >> >
> >> > It sounds like the pragmatic answer to the latter is "No, the
> >> > additional coordination overhead isn't worth the potential pay-off",
> >> > and I think that's fine - our respective communities can still learn
> >> > from each other when it comes to our definitions of "What does 'good'
> >> > look like?" in workflow design.
> >> >
> >> > Cheers,
> >> > Nick.
> >> >
> >> > --
> >> > Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> >>
> >> I've also reminded one really handy solution described in the
> >> presentation,
> >> which is auto-assigning PR to the owner of certain area. With the list
> we
> >> keep
> >> here: https://docs.python.org/devguide/experts.html we could pretty
> easily
> >> do such mechanism. This will be handy for the devs because assigning
> >> a specific issue will trigger an email notification of such, which in
> turn
> >> is
> >> similar to our noisy in bug tracker. Otherwise the PRs might end up
> >> hanging
> >> there until somebody will do that manually.
> >>
> >> Having said that Brett if you need help with it - I'm here to help you.
> >
> >
> > :) Thanks. Once we have migrated the repositories over we can start
> > discussing enhancements to the workflow like automatic reviewer
> assignment
> > (and I personally have some ideas about PR assignment as well for when
> there
> > isn't an expert).
> >
> > But I don't want to get too distracted by this bonus work when we haven't
> > even started most of the work required to simply match our current
> workflow.
> > It's great that people are excited about making things better and I don't
> > want to squash people's energy to help, but I also don't want to get too
> > distracted by enhancements when we haven't even started a bunch of the
> > minimum work to even move to GitHub, let alone take advantage of what
> bonus
> > features it will bring to the table.
> >
> > My current worry is that we are going to get blocked on Roundup work
> because
> > right now only Ezio and R. David know how that stuff works. Once the CLA
> bot
> > is finished I'm going to shift to helping with that, but it will
> obviously
> > go faster if others can also help with bugs.python.org work because we
> can't
> > switch over until we have a minimum workflow that matches our current
> one.
>
> What's there to be done and how can I help with that, in that case?
>
> Maciej
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160210/2fddc143/attachment.html>

From brett at python.org  Wed Feb 10 17:16:23 2016
From: brett at python.org (Brett Cannon)
Date: Wed, 10 Feb 2016 22:16:23 +0000
Subject: [core-workflow] Presentation on Rust's GitHub based automation
 tools
In-Reply-To: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
References: <CADiSq7cH-N66hDicbWV4bU4r4xhA2FBGd4AAf2RT4Gq1n3R77g@mail.gmail.com>
Message-ID: <CAP1=2W4id=ffv4ojkqFhMB1kU3pt2yvBMEAnar6jLC7Dznxb9w@mail.gmail.com>

On Sat, 6 Feb 2016 at 23:21 Nick Coghlan <ncoghlan at gmail.com> wrote:

> I was at linux.conf.au 2016 last week, and one of the presentations
> was from Mozilla's Emily Dunham on some of the infrastructure
> automation they use with Rust and other GitHub based projects:
> https://www.youtube.com/watch?v=dIageYT0Vgg


I finally had the time to watch the video. It's very interesting and
basically mirrors what I'm hoping is going to be possible for us once we
migrate to GitHub (i.e., automate as much as we can). While it doesn't
change any of the plans for reaching parity support to the hg workflow, it
is something to revisit when it comes time to look at adding new features
to our workflow (and maybe even share the bots if it happens to make sense).

-Brett


>
>
> In addition to their merge bot project homu (which we've talked about
> previously), they also have:
>
> highfive (a greeter bot): https://github.com/nrc/highfive
> starters (an issue curator): https://starters.servo.org/
>
> The first project looks for folks submitting their first PR or issue,
> and responds with some standard info to save humans from having to do
> it later (like pointers to the Code of Conduct and the Contributor
> Licensing Agreement, as well as explanations of how the contribution
> process works)
>
> The second one is designed to provide a better answer to the "How do I
> get started?" question by making it easy for developers to tag simpler
> issues. This could presumably also be used to provide separate views
> based on what folks want to work on (e.g. documentation, Python code,
> C code)
>
> While these wouldn't necessarily be something we wanted to set up
> immediately, it likely makes a lot of sense to try to share the tool
> maintenance load with Mozilla rather than going for a completely
> custom setup.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160210/04937a5a/attachment.html>

From bussonniermatthias at gmail.com  Thu Feb 11 19:04:13 2016
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Thu, 11 Feb 2016 16:04:13 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
 <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
 <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
Message-ID: <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>

Hey,

I just saw the GitHub released a tool to import Mercurial repo:

https://github.com/blog/2110-migrate-your-code-with-the-github-importer

Thought it might be usefull for this thread.

I'm currently trying to import to see how it looks, have been stuck at
0% for a few minutes now.

-- 
M

Will be at there if import succeed.
https://github.com/Carreau/cpython-test



On Mon, Feb 8, 2016 at 10:23 AM, Brett Cannon <brett at python.org> wrote:
>
>
> On Mon, 8 Feb 2016 at 09:54 Senthil Kumaran <senthil at uthcode.com> wrote:
>>
>> Hi Brett,
>>
>> On Sat, Feb 6, 2016 at 11:42 AM, Brett Cannon <brett at python.org> wrote:
>>>
>>> It seems there are people definitely willing to try out the tools and
>>> report back, but I'm looking for someone/people to organize the effort and
>>> come back to me with a thought-out solution so I don't have to. :)
>>
>>
>> I wanted to get involved with this process. I am ready to help you here.
>>
>> https://github.com/orsenthil/cpython-hg-to-git
>>
>> Here I started documenting our discussion so far. I will continue to
>> evaluate the tools (with other developers this list) and we'll try to come
>> up with a conclusive suggestion for our migration.
>>
>
> Thanks to much, Senthil! When I get a chance I will update the PEP to say
> this step of the migration is in process and you as in charge of it.
>
> -Brett
>
> P.S.: For this whole migration I'm going to try and delegate where
> appropriate, so this won't be the last time I reach out for help. I
> anticipate helping with bugs.python.org is going to be the biggest stumbling
> block/need. And for those that wanted GitLab over GitHub, a vast majority of
> this migration is Git host-agnostic, and so this is necessary for after we
> leave GitHub (either because we're unhappy with GitHub or because it's
> simply time to move; nothing is forever).
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct

From nicholas.chammas at gmail.com  Thu Feb 11 19:25:44 2016
From: nicholas.chammas at gmail.com (Nicholas Chammas)
Date: Fri, 12 Feb 2016 00:25:44 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
 <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
 <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
Message-ID: <CAOhmDzfjELWT4Vm-5UbysiwO+D9n6oP+uekt8U6-HzUc_ZCAuw@mail.gmail.com>

> I'm currently trying to import to see how it looks, have been stuck at
0% for a few minutes now.

Doing the same myself. Got to 73% and it restarted. Am back at 73% now.

Already reached out to GitHub to make them aware of the issue.

Will report here when/if I have results.

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/ac1be0ba/attachment.html>

From nicolas.alvarez at gmail.com  Thu Feb 11 19:43:29 2016
From: nicolas.alvarez at gmail.com (=?UTF-8?Q?Nicol=C3=A1s_Alvarez?=)
Date: Thu, 11 Feb 2016 21:43:29 -0300
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
Message-ID: <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>

2016-02-06 3:03 GMT-03:00 Nicol?s Alvarez <nicolas.alvarez at gmail.com>:
> 2016-02-05 23:39 GMT-03:00 Nicol?s Alvarez <nicolas.alvarez at gmail.com>:
>> 2016-02-05 22:57 GMT-03:00 Brett Cannon <brett at python.org>:
>>> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>>>
>>> There appear to be multiple ways to convert hg repos to git, but no clear
>>> winner. It would be great if some one/people took on the task of evaluating
>>> the tools available out there by converting the cpython repo and seeing
>>> which one has the best results.
>>
>> I said I'd look into this. I didn't. Shame on me.
>>
>> Trying fast-export now :)
>
> Update: The fast-export tool started at about 500 revs/sec but
> progressively slowed down. Now it's 90% done after churning for two
> hours, and each merge commit (of which there are many!) takes an
> entire second by itself. I don't feel like staying awake to see it
> finish.

I tried fast-export, and I don't really see anything wrong with the
repository. The size is 221MB.

It depends on how crazy you want to go. For example, SVN-era merges
don't appear as merges, but looks like some SVN-era branches don't
exist in Hg to begin with (Would I need to get cpython-fullhistory?
Cloning it gives me a 400 Bad Request). Do we care about that?

Or, changes that come from non-committers could have their Author
field modified, maybe based on the ACKS file modification. It's
feasible but will take time and manual work. Do we care about that?

-- 
Nicol?s

From senthil at uthcode.com  Thu Feb 11 20:07:41 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Thu, 11 Feb 2016 17:07:41 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
 <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
 <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
 <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
Message-ID: <CAPOVWOQy_hpMJFe48dui5c+VEg-MxvVMpa7Vv-e0Hjzcyrx_gA@mail.gmail.com>

On Thu, Feb 11, 2016 at 4:04 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> I just saw the GitHub released a tool to import Mercurial repo:
>
> https://github.com/blog/2110-migrate-your-code-with-the-github-importer
>
> Thought it might be usefull for this thread.
>
> I'm currently trying to import to see how it looks, have been stuck at
> 0% for a few minutes now.
>

Yeah, I noticed it too and I has said that it will send an email once the
import it done.
Let's see if this feature provides all the things are looking for.

This is interesting one for our needs.

Thanks,
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160211/32ea217c/attachment.html>

From brett at python.org  Thu Feb 11 22:07:37 2016
From: brett at python.org (Brett Cannon)
Date: Fri, 12 Feb 2016 03:07:37 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
Message-ID: <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>

On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez <nicolas.alvarez at gmail.com>
wrote:

> 2016-02-06 3:03 GMT-03:00 Nicol?s Alvarez <nicolas.alvarez at gmail.com>:
> > 2016-02-05 23:39 GMT-03:00 Nicol?s Alvarez <nicolas.alvarez at gmail.com>:
> >> 2016-02-05 22:57 GMT-03:00 Brett Cannon <brett at python.org>:
> >>>
> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
> >>>
> >>> There appear to be multiple ways to convert hg repos to git, but no
> clear
> >>> winner. It would be great if some one/people took on the task of
> evaluating
> >>> the tools available out there by converting the cpython repo and seeing
> >>> which one has the best results.
> >>
> >> I said I'd look into this. I didn't. Shame on me.
> >>
> >> Trying fast-export now :)
> >
> > Update: The fast-export tool started at about 500 revs/sec but
> > progressively slowed down. Now it's 90% done after churning for two
> > hours, and each merge commit (of which there are many!) takes an
> > entire second by itself. I don't feel like staying awake to see it
> > finish.
>
> I tried fast-export, and I don't really see anything wrong with the
> repository. The size is 221MB.
>
> It depends on how crazy you want to go. For example, SVN-era merges
> don't appear as merges, but looks like some SVN-era branches don't
> exist in Hg to begin with (Would I need to get cpython-fullhistory?
> Cloning it gives me a 400 Bad Request). Do we care about that?
>

Good question. If you are not an even clone it then that shows how much
people who are. Honestly I wouldn't worry since we have the history in the
hg repo (converting from svn was necessary to have it available without the
server).


> Or, changes that come from non-committers could have their Author
> field modified, maybe based on the ACKS file modification. It's
> feasible but will take time and manual work. Do we care about that?
>

That would be great but too much effort.

Brett


> --
> Nicol?s
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/1afc9963/attachment-0001.html>

From brett at python.org  Thu Feb 11 22:14:25 2016
From: brett at python.org (Brett Cannon)
Date: Fri, 12 Feb 2016 03:14:25 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAPOVWOQy_hpMJFe48dui5c+VEg-MxvVMpa7Vv-e0Hjzcyrx_gA@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name> <20160206164816.GA29207@phdru.name>
 <56B6260B.4050105@gmail.com> <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
 <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
 <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
 <CAPOVWOQy_hpMJFe48dui5c+VEg-MxvVMpa7Vv-e0Hjzcyrx_gA@mail.gmail.com>
Message-ID: <CAP1=2W4ptgnz9a27WH+Wv8dw-XbipoE2smqLE2V1C_NnQk8_Dw@mail.gmail.com>

On Thu, 11 Feb 2016 at 17:07 Senthil Kumaran <senthil at uthcode.com> wrote:

>
> On Thu, Feb 11, 2016 at 4:04 PM, Matthias Bussonnier <
> bussonniermatthias at gmail.com> wrote:
>
>> I just saw the GitHub released a tool to import Mercurial repo:
>>
>> https://github.com/blog/2110-migrate-your-code-with-the-github-importer
>>
>> Thought it might be usefull for this thread.
>>
>> I'm currently trying to import to see how it looks, have been stuck at
>> 0% for a few minutes now.
>>
>
> Yeah, I noticed it too and I has said that it will send an email once the
> import it done.
> Let's see if this feature provides all the things are looking for.
>
> This is interesting one for our needs.
>

Two things. One, I just updated listing Senthil as in charge of evaluating
the tools. Should go live in an hour or so (aside: I'm going to delete my
GitHub repo for the PEP so I don't have to keep track of two copies; can't
wait until we get this done enough to move the peps repo over).

Two, thanks for everyone who jumped on the GitHub blog post and posting
here! I noticed myself and was coming to comment when I noticed Matthias,
Nick, Nicol?s, and Senthil had beaten me to it. :) As Senthil said, it's
very interesting to see this option open up to us and will need to see how
they do. Hopefully it will work out (or at least we can help GitHub fix
their tooling if they can't handle the cpython repo's deep history).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/71948c33/attachment.html>

From ethan at stoneleaf.us  Thu Feb 11 22:27:54 2016
From: ethan at stoneleaf.us (Ethan Furman)
Date: Thu, 11 Feb 2016 19:27:54 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
Message-ID: <56BD513A.8020508@stoneleaf.us>

On 02/11/2016 07:07 PM, Brett Cannon wrote:
 > On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez wrote:

 >> It depends on how crazy you want to go. For example, SVN-era merges
 >> don't appear as merges, but looks like some SVN-era branches don't
 >> exist in Hg to begin with (Would I need to get cpython-fullhistory?
 >> Cloning it gives me a 400 Bad Request). Do we care about that?

 > If you are not an even clone it then that shows how much
 > people who are.

Um, could you repeat that?  In English?  :)

--
~Ethan~

From brett at python.org  Thu Feb 11 23:19:30 2016
From: brett at python.org (Brett Cannon)
Date: Fri, 12 Feb 2016 04:19:30 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56BD513A.8020508@stoneleaf.us>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <56BD513A.8020508@stoneleaf.us>
Message-ID: <CAP1=2W5K_y0yL=j84ES5uc5e9FzD_q3tdNOcXKNjtMFQ8BxXvg@mail.gmail.com>

On Thu, Feb 11, 2016, 19:27 Ethan Furman <ethan at stoneleaf.us> wrote:

> On 02/11/2016 07:07 PM, Brett Cannon wrote:
>  > On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez wrote:
>
>  >> It depends on how crazy you want to go. For example, SVN-era merges
>  >> don't appear as merges, but looks like some SVN-era branches don't
>  >> exist in Hg to begin with (Would I need to get cpython-fullhistory?
>  >> Cloning it gives me a 400 Bad Request). Do we care about that?
>
>  > If you are not an even clone it then that shows how much
>  > people who are.
>
> Um, could you repeat that?  In English?  :)
>

If you aren't able to even clone it then that shows how much people care.

Brett


> --
> ~Ethan~
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/b35e064e/attachment.html>

From vadmium+py at gmail.com  Fri Feb 12 01:04:19 2016
From: vadmium+py at gmail.com (Martin Panter)
Date: Fri, 12 Feb 2016 06:04:19 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
Message-ID: <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>

On 12 February 2016 at 03:07, Brett Cannon <brett at python.org> wrote:
> On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez <nicolas.alvarez at gmail.com>
> wrote:
>> I tried fast-export, and I don't really see anything wrong with the
>> repository. The size is 221MB.

One thing I?m slightly curious about is how much the result differs
from <https://github.com/python/cpython> or other results, and if so,
what the differences are. The differences could be serious (mangled
history), or they could be trivial things like stripping trailing
newlines from commit messages, or skipping commits that don?t change
any files.

>> It depends on how crazy you want to go. For example, SVN-era merges
>> don't appear as merges, but looks like some SVN-era branches don't
>> exist in Hg to begin with (Would I need to get cpython-fullhistory?
>> Cloning it gives me a 400 Bad Request). Do we care about that?
>
> Good question. If you are not an even clone it then that shows how much
> people who are. Honestly I wouldn't worry since we have the history in the
> hg repo (converting from svn was necessary to have it available without the
> server).

I care a bit. If I get the time, I would like to figure out a robust
way to convert the Subversion history to Git so that the svnmerge
information is included as proper merges.

Another concern for me is that some of the useful history is not even
in Mercurial. For example <https://hg.python.org/lookup/r70152> is an
svnmerge from ^/python/branches/io-c into ^/python/branches/py3k, but
the Mercurial repository doesn?t have the branch history, so all the
merged-in Subversion revisions such as r68683 are missing.

Some other highlights on my quest to investigate the holy Subversion
respository (I can post my full notes somewhere if ppl are
interested):

* It is nice to have a local mirror of the Subversion repository so
that experimenting with different options and programs isn?t horribly
slow. But I don?t want to mirror everything or overload the server
because there are other projects stored in the repository that seem to
take up a lot of space (and download time).

* What is the story with the cpython-fullhistory Mercurial repository?
On the surface it almost looks like an out-of-date copy of the main
repository, but I notice some subtle differences, e.g. revision ids
for early tags are different, v1.0.0 tag is added.

* Some Subversion revisions actually merge stuff from outside the
Python tree (e.g. <https://hg.python.org/lookup/r88662> from
^/sandbox/trunk/2to3/lib2to3 into
^/branches/release27-maint/Lib/lib2to3. Not sure if it is worth trying
to salvage these merges; I never noticed them when working on Python.

>> Or, changes that come from non-committers could have their Author
>> field modified, maybe based on the ACKS file modification. It's
>> feasible but will take time and manual work. Do we care about that?
>
> That would be great but too much effort.

I think it would not be worth it, and could even be detrimenal. You
would be trying to guess based on incomplete and unreliable
information. Maybe one person wrote a test, another wrote the
implementation, and a third wrote the documentation, but it was all
committed at once. Maybe the author was already in ACKS and the
committer did not mention who the author was in the message. I think
it is safer to not pretend the author field is alway accurate.

From nicolas.alvarez at gmail.com  Fri Feb 12 01:27:37 2016
From: nicolas.alvarez at gmail.com (=?UTF-8?Q?Nicol=C3=A1s_Alvarez?=)
Date: Fri, 12 Feb 2016 03:27:37 -0300
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
Message-ID: <CANPC-ttQ0-UEzvW34kp5r5iOaJeACodHYca1AsORS=Q8jW-OCA@mail.gmail.com>

2016-02-12 3:04 GMT-03:00 Martin Panter <vadmium+py at gmail.com>:
> On 12 February 2016 at 03:07, Brett Cannon <brett at python.org> wrote:
>> On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez <nicolas.alvarez at gmail.com>
>> wrote:
>>> It depends on how crazy you want to go. For example, SVN-era merges
>>> don't appear as merges, but looks like some SVN-era branches don't
>>> exist in Hg to begin with (Would I need to get cpython-fullhistory?
>>> Cloning it gives me a 400 Bad Request). Do we care about that?
>>
>> Good question. If you are not an even clone it then that shows how much
>> people who are. Honestly I wouldn't worry since we have the history in the
>> hg repo (converting from svn was necessary to have it available without the
>> server).
>
> I care a bit. If I get the time, I would like to figure out a robust
> way to convert the Subversion history to Git so that the svnmerge
> information is included as proper merges.

I migrated most of KDE from SVN to Git, progressively converting a
single million-revision repository into hundreds of per-app Git
repositories.

Is it still possible to access the SVN repository? :)

> Some other highlights on my quest to investigate the holy Subversion
> respository (I can post my full notes somewhere if ppl are
> interested):
>
> * It is nice to have a local mirror of the Subversion repository so
> that experimenting with different options and programs isn?t horribly
> slow. But I don?t want to mirror everything or overload the server
> because there are other projects stored in the repository that seem to
> take up a lot of space (and download time).

The svn2git tool we used in KDE *requires* the repository to be local,
because the libsvn API it uses works with repositories, not server
URLs.

-- 
Nicol?s

From vadmium+py at gmail.com  Fri Feb 12 01:32:33 2016
From: vadmium+py at gmail.com (Martin Panter)
Date: Fri, 12 Feb 2016 06:32:33 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANPC-ttQ0-UEzvW34kp5r5iOaJeACodHYca1AsORS=Q8jW-OCA@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CANPC-ttQ0-UEzvW34kp5r5iOaJeACodHYca1AsORS=Q8jW-OCA@mail.gmail.com>
Message-ID: <CA+eR4cG4bvFDLDghwVj+ffP3OZO_y3EjeqMBFZSL41WHJNCF7A@mail.gmail.com>

On 12 February 2016 at 06:27, Nicol?s Alvarez <nicolas.alvarez at gmail.com> wrote:
> 2016-02-12 3:04 GMT-03:00 Martin Panter <vadmium+py at gmail.com>:
>> On 12 February 2016 at 03:07, Brett Cannon <brett at python.org> wrote:
>>> On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez <nicolas.alvarez at gmail.com>
>>> wrote:
>>>> It depends on how crazy you want to go. For example, SVN-era merges
>>>> don't appear as merges, but looks like some SVN-era branches don't
>>>> exist in Hg to begin with (Would I need to get cpython-fullhistory?
>>>> Cloning it gives me a 400 Bad Request). Do we care about that?
>>>
>>> Good question. If you are not an even clone it then that shows how much
>>> people who are. Honestly I wouldn't worry since we have the history in the
>>> hg repo (converting from svn was necessary to have it available without the
>>> server).
>>
>> I care a bit. If I get the time, I would like to figure out a robust
>> way to convert the Subversion history to Git so that the svnmerge
>> information is included as proper merges.
>
> I migrated most of KDE from SVN to Git, progressively converting a
> single million-revision repository into hundreds of per-app Git
> repositories.
>
> Is it still possible to access the SVN repository? :)

svn info https://svn.python.org/projects/python

>> Some other highlights on my quest to investigate the holy Subversion
>> respository (I can post my full notes somewhere if ppl are
>> interested):
>>
>> * It is nice to have a local mirror of the Subversion repository so
>> that experimenting with different options and programs isn?t horribly
>> slow. But I don?t want to mirror everything or overload the server
>> because there are other projects stored in the repository that seem to
>> take up a lot of space (and download time).
>
> The svn2git tool we used in KDE *requires* the repository to be local,
> because the libsvn API it uses works with repositories, not server
> URLs.

From phd at phdru.name  Fri Feb 12 03:33:53 2016
From: phd at phdru.name (Oleg Broytman)
Date: Fri, 12 Feb 2016 09:33:53 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
Message-ID: <20160212083353.GA10246@phdru.name>

Hi!

On Fri, Feb 12, 2016 at 06:04:19AM +0000, Martin Panter <vadmium+py at gmail.com> wrote:
> One thing I???m slightly curious about is how much the result differs
> from <https://github.com/python/cpython> or other results, and if so,
> what the differences are. The differences could be serious (mangled
> history), or they could be trivial things like stripping trailing
> newlines from commit messages, or skipping commits that don???t change
> any files.

   git-remote-hg that I have been using can be configured to produce
commits compatible with hg-git. If the repo above was created with
hg-git I can rerun my conversion with hg-git compatibility turned on.
Then it may be compared with the mentioned repository.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From soltysh at gmail.com  Fri Feb 12 04:10:28 2016
From: soltysh at gmail.com (Maciej Szulik)
Date: Fri, 12 Feb 2016 10:10:28 +0100
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
In-Reply-To: <CADiSq7dufL+Yk_dLKk4rbLU5TXNyV3G3-zQQcow0kPEqNjiTcA@mail.gmail.com>
References: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
 <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>
 <CAP1=2W5XshWAbff4znaVLzQKODtcfoS9TbhZ_ac6u8F8FtYhpQ@mail.gmail.com>
 <CADiSq7dufL+Yk_dLKk4rbLU5TXNyV3G3-zQQcow0kPEqNjiTcA@mail.gmail.com>
Message-ID: <CALC2N4ZXqqKmP5AN0E1NDUBm14Br2xy6mS2KcQKXW5ZBwPf7Fw@mail.gmail.com>

On Sun, Feb 7, 2016 at 8:24 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 7 February 2016 at 05:22, Brett Cannon <brett at python.org> wrote:
>> IOW if people want to help in a way that involves coding, then please help
>> Ezio with b.p.o stuff. This is also beneficial long-term for maintaining the
>> issue tracker and changes that will be needed in the future for getting
>> cpython moved over.
>>
>> As for a PSF account on dockerhub, I would ask the PSF infra team what they
>> think and have them administer it.
>
> A PSF account on DockerHub sounds like a good idea to me - that would
> likely also be useful for hosting the reference image for the
> manylinux1 build environment.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct

Ezio I followed the steps you've sent me yesterday, and I was able to cleanly
setup my roundup instance. I've made slight changes, cleaned up the
structure and added
readme and makefile. My fork is under (branch dev):
https://github.com/soltysh/docker-b.p.o/tree/dev
I should start working on adding the new field later today. Will keep
you informed about the progress.

Maciej

From senthil at uthcode.com  Fri Feb 12 09:00:20 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Fri, 12 Feb 2016 06:00:20 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <20160206155051.GA27318@phdru.name>
 <20160206164816.GA29207@phdru.name> <56B6260B.4050105@gmail.com>
 <20160206171628.GA30545@phdru.name>
 <CAP1=2W43F45ajgW48b6ikF4-xDkaQLjakPYs4uaYzA9Ne=y4+g@mail.gmail.com>
 <CAPOVWOQZxdzos5ov9+FhHGHksRJpQsVHmvdwNpLKwJrqds19yQ@mail.gmail.com>
 <CAP1=2W7dzc5b-nFccmzL5KWYVPjnMpkz8Bv09vMdt2EfP51RqQ@mail.gmail.com>
 <CANJQusURCPrwYHb1B6D6zXx+QnXWesZu4hcFj92ywSusgdJ1JQ@mail.gmail.com>
Message-ID: <CAPOVWOQHUJxSz223cPQt4S49Py4s0yfEO0j-HOVk10JqXFPTbg@mail.gmail.com>

On Thu, Feb 11, 2016 at 4:04 PM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> I just saw the GitHub released a tool to import Mercurial repo:
>
> https://github.com/blog/2110-migrate-your-code-with-the-github-importer
>


Turns out that our CPython repository size is too big for this importer
tool to handle.
It fails for me consistently at 78% and I tried more than 10 times to push
the limit to 78%.

As Brett mentioned, I will report this to github.com team and let's
continue our evaluation of other tools
which can successfully complete the hg-> git translation of the repo.

-- 
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/650dcd4f/attachment-0001.html>

From pierre-yves.david at ens-lyon.org  Fri Feb 12 09:20:49 2016
From: pierre-yves.david at ens-lyon.org (Pierre-Yves David)
Date: Fri, 12 Feb 2016 14:20:49 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
Message-ID: <56BDEA41.8010206@ens-lyon.org>



On 02/06/2016 01:57 AM, Brett Cannon wrote:
> https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercurial-repository-to-git
>
> There appear to be multiple ways to convert hg repos to git, but no
> clear winner. It would be great if some one/people took on the task of
> evaluating the tools available out there by converting the cpython repo
> and seeing which one has the best results.

We, at Facebook, have been happily using hg-git in production for 
bidirectional conversion of repositories of insane sizes.

I would look in that direction for your conversion.

-- 
Pierre-Yves David

From senthil at uthcode.com  Fri Feb 12 09:37:05 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Fri, 12 Feb 2016 06:37:05 -0800 (PST)
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56BDEA41.8010206@ens-lyon.org>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
Message-ID: <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>

Hi Pierre,

  

Do you have external documents that you could point us to so that it help us
with the research?

Thanks for sharing this detail on hg&lt;-&gt;git already working for a huge
repo.

  

\--  
Senthil

  

> On Feb 12 2016, at 6:28 am, Pierre-Yves David &lt;pierre-yves.david at ens-
lyon.org&gt; wrote:  

>

> On 02/06/2016 01:57 AM, Brett Cannon wrote:  
&gt; https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a
-mercurial-repository-to-git  
&gt;  
&gt; There appear to be multiple ways to convert hg repos to git, but no  
&gt; clear winner. It would be great if some one/people took on the task of  
&gt; evaluating the tools available out there by converting the cpython repo  
&gt; and seeing which one has the best results.

>

> We, at Facebook, have been happily using hg-git in production for  
bidirectional conversion of repositories of insane sizes.

>

> I would look in that direction for your conversion.

>

> \--  
Pierre-Yves David  
_______________________________________________  
core-workflow mailing list  
core-workflow at python.org  
https://mail.python.org/mailman/listinfo/core-workflow  
This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/365a5919/attachment.html>

From pierre-yves.david at ens-lyon.org  Fri Feb 12 09:41:08 2016
From: pierre-yves.david at ens-lyon.org (Pierre-Yves David)
Date: Fri, 12 Feb 2016 14:41:08 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
 <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>
Message-ID: <56BDEF04.5000808@ens-lyon.org>



On 02/12/2016 02:37 PM, Senthil Kumaran wrote:
> Hi Pierre,
>
> Do you have external documents that you could point us to so that it
> help us with the research?
> Thanks for sharing this detail on hg<->git already working for a huge repo.

I would expect the hg-git documentation to be the place to start.

-- 
Pierre-Yves David

From rymg19 at gmail.com  Fri Feb 12 11:02:11 2016
From: rymg19 at gmail.com (Ryan Gonzalez)
Date: Fri, 12 Feb 2016 10:02:11 -0600
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56BDEF04.5000808@ens-lyon.org>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
 <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>
 <56BDEF04.5000808@ens-lyon.org>
Message-ID: <794886B0-FFDE-4285-ADEE-A25D372405CB@gmail.com>

How did you manage to push the repo somewhere? hg-git successfully exported all the changesets for me, but I couldn't push to a directory, and my computer ran out of memory twice during the adding objects stage when trying to push to GitHub.

On February 12, 2016 8:41:08 AM CST, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>
>
>On 02/12/2016 02:37 PM, Senthil Kumaran wrote:
>> Hi Pierre,
>>
>> Do you have external documents that you could point us to so that it
>> help us with the research?
>> Thanks for sharing this detail on hg<->git already working for a huge
>repo.
>
>I would expect the hg-git documentation to be the place to start.
>
>-- 
>Pierre-Yves David
>_______________________________________________
>core-workflow mailing list
>core-workflow at python.org
>https://mail.python.org/mailman/listinfo/core-workflow
>This list is governed by the PSF Code of Conduct:
>https://www.python.org/psf/codeofconduct

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160212/8964ba5d/attachment.html>

From phd at phdru.name  Fri Feb 12 12:13:01 2016
From: phd at phdru.name (Oleg Broytman)
Date: Fri, 12 Feb 2016 18:13:01 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <794886B0-FFDE-4285-ADEE-A25D372405CB@gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
 <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>
 <56BDEF04.5000808@ens-lyon.org>
 <794886B0-FFDE-4285-ADEE-A25D372405CB@gmail.com>
Message-ID: <20160212171301.GA5298@phdru.name>

On Fri, Feb 12, 2016 at 10:02:11AM -0600, Ryan Gonzalez <rymg19 at gmail.com> wrote:
> How did you manage to push the repo somewhere? hg-git successfully exported all the changesets for me, but I couldn't push to a directory, and my computer ran out of memory twice during the adding objects stage when trying to push to GitHub.

   As for Github, push in smaller batches, something like

$ git log --oneline | wc -l
92979

$ git push github master~45000:refs/heads/master

$ git push github master:master

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From phd at phdru.name  Fri Feb 12 12:25:38 2016
From: phd at phdru.name (Oleg Broytman)
Date: Fri, 12 Feb 2016 18:25:38 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <20160212171301.GA5298@phdru.name>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
 <9r2yz9z2iv9pxcg88dvxmzmov-0@mailer.nylas.com>
 <56BDEF04.5000808@ens-lyon.org>
 <794886B0-FFDE-4285-ADEE-A25D372405CB@gmail.com>
 <20160212171301.GA5298@phdru.name>
Message-ID: <20160212172538.GA5788@phdru.name>

On Fri, Feb 12, 2016 at 06:13:01PM +0100, Oleg Broytman <phd at phdru.name> wrote:
> On Fri, Feb 12, 2016 at 10:02:11AM -0600, Ryan Gonzalez <rymg19 at gmail.com> wrote:
> > How did you manage to push the repo somewhere? hg-git successfully exported all the changesets for me, but I couldn't push to a directory, and my computer ran out of memory twice during the adding objects stage when trying to push to GitHub.
> 
>    As for Github, push in smaller batches, something like
> 
> $ git log --oneline | wc -l
> 92979
> 
> $ git push github master~45000:refs/heads/master
> 
> $ git push github master:master

   And after that

$ git push --all github

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            phd at phdru.name
           Programmers don't die, they just GOSUB without RETURN.

From soltysh at gmail.com  Fri Feb 12 17:08:07 2016
From: soltysh at gmail.com (Maciej Szulik)
Date: Fri, 12 Feb 2016 23:08:07 +0100
Subject: [core-workflow] Help needed: adding GitHub usernames to
 bugs.python.org
In-Reply-To: <CALC2N4ZXqqKmP5AN0E1NDUBm14Br2xy6mS2KcQKXW5ZBwPf7Fw@mail.gmail.com>
References: <CAP1=2W4AtaHCYuMaj3r+EyA2EUzoMeYJVH_SYmooX1=5s0ZuCw@mail.gmail.com>
 <CACBhJdG9-yhz=wih4bcaNraOc8C=P-2W9BAOM=2SLrJZ43UhRg@mail.gmail.com>
 <CAP1=2W5XshWAbff4znaVLzQKODtcfoS9TbhZ_ac6u8F8FtYhpQ@mail.gmail.com>
 <CADiSq7dufL+Yk_dLKk4rbLU5TXNyV3G3-zQQcow0kPEqNjiTcA@mail.gmail.com>
 <CALC2N4ZXqqKmP5AN0E1NDUBm14Br2xy6mS2KcQKXW5ZBwPf7Fw@mail.gmail.com>
Message-ID: <CALC2N4beH+DwszcdOEDnM7hUDsCXpYxMf7TYDse+TLk+2zFzuA@mail.gmail.com>

Ezio the patch was sent here:
http://psf.upfronthosting.co.za/roundup/meta/issue579
Lemme know if this is what you want?

Maciej

On Fri, Feb 12, 2016 at 10:10 AM, Maciej Szulik <soltysh at gmail.com> wrote:
> On Sun, Feb 7, 2016 at 8:24 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> On 7 February 2016 at 05:22, Brett Cannon <brett at python.org> wrote:
>>> IOW if people want to help in a way that involves coding, then please help
>>> Ezio with b.p.o stuff. This is also beneficial long-term for maintaining the
>>> issue tracker and changes that will be needed in the future for getting
>>> cpython moved over.
>>>
>>> As for a PSF account on dockerhub, I would ask the PSF infra team what they
>>> think and have them administer it.
>>
>> A PSF account on DockerHub sounds like a good idea to me - that would
>> likely also be useful for hosting the reference image for the
>> manylinux1 build environment.
>>
>> Cheers,
>> Nick.
>>
>> --
>> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>> _______________________________________________
>> core-workflow mailing list
>> core-workflow at python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
>
> Ezio I followed the steps you've sent me yesterday, and I was able to cleanly
> setup my roundup instance. I've made slight changes, cleaned up the
> structure and added
> readme and makefile. My fork is under (branch dev):
> https://github.com/soltysh/docker-b.p.o/tree/dev
> I should start working on adding the new field later today. Will keep
> you informed about the progress.
>
> Maciej

From brett at python.org  Fri Feb 12 20:15:55 2016
From: brett at python.org (Brett Cannon)
Date: Sat, 13 Feb 2016 01:15:55 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
Message-ID: <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>

I don't remember the story behind cpython-fullhistory, but it's obviously
incomplete since just stopped post conversion. You will need to find
someone who knows (I'd ask on python-dev).

Also realize that this will be  our fourth VCS (cvs, svn, hg, now git).
This is not going to be a perfect history of the semantic actions of
commits from the beginning of time just due to the fact that these VCS
tools all use different concepts.

On Thu, Feb 11, 2016, 22:04 Martin Panter <vadmium+py at gmail.com> wrote:

> On 12 February 2016 at 03:07, Brett Cannon <brett at python.org> wrote:
> > On Thu, Feb 11, 2016, 16:43 Nicol?s Alvarez <nicolas.alvarez at gmail.com>
> > wrote:
> >> I tried fast-export, and I don't really see anything wrong with the
> >> repository. The size is 221MB.
>
> One thing I?m slightly curious about is how much the result differs
> from <https://github.com/python/cpython> or other results, and if so,
> what the differences are. The differences could be serious (mangled
> history), or they could be trivial things like stripping trailing
> newlines from commit messages, or skipping commits that don?t change
> any files.
>
> >> It depends on how crazy you want to go. For example, SVN-era merges
> >> don't appear as merges, but looks like some SVN-era branches don't
> >> exist in Hg to begin with (Would I need to get cpython-fullhistory?
> >> Cloning it gives me a 400 Bad Request). Do we care about that?
> >
> > Good question. If you are not an even clone it then that shows how much
> > people who are. Honestly I wouldn't worry since we have the history in
> the
> > hg repo (converting from svn was necessary to have it available without
> the
> > server).
>
> I care a bit. If I get the time, I would like to figure out a robust
> way to convert the Subversion history to Git so that the svnmerge
> information is included as proper merges.
>
> Another concern for me is that some of the useful history is not even
> in Mercurial. For example <https://hg.python.org/lookup/r70152> is an
> svnmerge from ^/python/branches/io-c into ^/python/branches/py3k, but
> the Mercurial repository doesn?t have the branch history, so all the
> merged-in Subversion revisions such as r68683 are missing.
>
> Some other highlights on my quest to investigate the holy Subversion
> respository (I can post my full notes somewhere if ppl are
> interested):
>
> * It is nice to have a local mirror of the Subversion repository so
> that experimenting with different options and programs isn?t horribly
> slow. But I don?t want to mirror everything or overload the server
> because there are other projects stored in the repository that seem to
> take up a lot of space (and download time).
>
> * What is the story with the cpython-fullhistory Mercurial repository?
> On the surface it almost looks like an out-of-date copy of the main
> repository, but I notice some subtle differences, e.g. revision ids
> for early tags are different, v1.0.0 tag is added.
>
> * Some Subversion revisions actually merge stuff from outside the
> Python tree (e.g. <https://hg.python.org/lookup/r88662> from
> ^/sandbox/trunk/2to3/lib2to3 into
> ^/branches/release27-maint/Lib/lib2to3. Not sure if it is worth trying
> to salvage these merges; I never noticed them when working on Python.
>
> >> Or, changes that come from non-committers could have their Author
> >> field modified, maybe based on the ACKS file modification. It's
> >> feasible but will take time and manual work. Do we care about that?
> >
> > That would be great but too much effort.
>
> I think it would not be worth it, and could even be detrimenal. You
> would be trying to guess based on incomplete and unreliable
> information. Maybe one person wrote a test, another wrote the
> implementation, and a third wrote the documentation, but it was all
> committed at once. Maybe the author was already in ACKS and the
> committer did not mention who the author was in the message. I think
> it is safer to not pretend the author field is alway accurate.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160213/fc5c9fad/attachment-0001.html>

From ncoghlan at gmail.com  Fri Feb 12 21:56:21 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Sat, 13 Feb 2016 12:56:21 +1000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
Message-ID: <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>

On 13 February 2016 at 11:15, Brett Cannon <brett at python.org> wrote:
> I don't remember the story behind cpython-fullhistory, but it's obviously
> incomplete since just stopped post conversion. You will need to find someone
> who knows (I'd ask on python-dev).
>
> Also realize that this will be  our fourth VCS (cvs, svn, hg, now git). This
> is not going to be a perfect history of the semantic actions of commits from
> the beginning of time just due to the fact that these VCS tools all use
> different concepts.

There's also the fact that prior to the move to SourceForge in 2000,
all changes had to be funneled through the half dozen or so people
with write access to the CVS tree:
https://docs.python.org/3/whatsnew/2.0.html#new-development-process

I think it's definitely OK if future code archaeologists need to dig
into the SVN repository to get a more complete view of CPython's
history.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From senthil at uthcode.com  Sat Feb 13 23:27:30 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Sat, 13 Feb 2016 20:27:30 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56BDEA41.8010206@ens-lyon.org>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
Message-ID: <CAPOVWOSx-q6L9U1Enh7Q61Cf3zK1H8QwHreqPexYvAL90JPjUA@mail.gmail.com>

On Fri, Feb 12, 2016 at 6:20 AM, Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:

> We, at Facebook, have been happily using hg-git in production for
> bidirectional conversion of repositories of insane sizes.


I played with hg-git tool and was able to migrate the hg cpython default
branch to git successfully. I have documented the steps here:
https://github.com/orsenthil/cpython-hg-to-git/blob/master/README.md

import.github.com is unable to handle the size of our repo. I have reported
this to github.com and let's see if we get any support from them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160213/797a919b/attachment.html>

From nicolas.alvarez at gmail.com  Sat Feb 13 23:32:54 2016
From: nicolas.alvarez at gmail.com (=?UTF-8?Q?Nicol=C3=A1s_Alvarez?=)
Date: Sun, 14 Feb 2016 01:32:54 -0300
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAPOVWOSx-q6L9U1Enh7Q61Cf3zK1H8QwHreqPexYvAL90JPjUA@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <56BDEA41.8010206@ens-lyon.org>
 <CAPOVWOSx-q6L9U1Enh7Q61Cf3zK1H8QwHreqPexYvAL90JPjUA@mail.gmail.com>
Message-ID: <CANPC-tv3WYWAPoC_fr9iyHPyQmAoW8HyimuaVkiTn5fd8bqHBQ@mail.gmail.com>

2016-02-14 1:27 GMT-03:00 Senthil Kumaran <senthil at uthcode.com>:
> On Fri, Feb 12, 2016 at 6:20 AM, Pierre-Yves David
> <pierre-yves.david at ens-lyon.org> wrote:
>>
>> We, at Facebook, have been happily using hg-git in production for
>> bidirectional conversion of repositories of insane sizes.
>
>
> I played with hg-git tool and was able to migrate the hg cpython default
> branch to git successfully. I have documented the steps here:
> https://github.com/orsenthil/cpython-hg-to-git/blob/master/README.md

Did you repack the git repository after importing with hg-git and
before pushing it? Every repository import tool I know of produces
extremely suboptimal pack files. fast-export initially gave me a 3GB
monstrosity before I ran "git gc --aggressive".

-- 
Nicol?s

From pierre-yves.david at ens-lyon.org  Sun Feb 14 12:24:05 2016
From: pierre-yves.david at ens-lyon.org (Pierre-Yves David)
Date: Sun, 14 Feb 2016 17:24:05 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
 <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
Message-ID: <56C0B835.9050806@ens-lyon.org>

On 02/13/2016 02:56 AM, Nick Coghlan wrote:
> On 13 February 2016 at 11:15, Brett Cannon <brett at python.org> wrote:
>> I don't remember the story behind cpython-fullhistory, but it's obviously
>> incomplete since just stopped post conversion. You will need to find someone
>> who knows (I'd ask on python-dev).
>>
>> Also realize that this will be  our fourth VCS (cvs, svn, hg, now git). This
>> is not going to be a perfect history of the semantic actions of commits from
>> the beginning of time just due to the fact that these VCS tools all use
>> different concepts.
>
> There's also the fact that prior to the move to SourceForge in 2000,
> all changes had to be funneled through the half dozen or so people
> with write access to the CVS tree:
> https://docs.python.org/3/whatsnew/2.0.html#new-development-process
>
> I think it's definitely OK if future code archaeologists need to dig
> into the SVN repository to get a more complete view of CPython's
> history.

I've never met a project who did not regret such decision at some point. 
Keeping older history is usually valuable. Mercurial have powerful 
enough tool to let you get all the history back together, I assume git 
probably have that power too.

This is your call, but I strongly recommend taking advantage of this 
migration to put everything back together.

-- 
Pierre-Yves David

From encukou at gmail.com  Mon Feb 15 05:12:00 2016
From: encukou at gmail.com (Petr Viktorin)
Date: Mon, 15 Feb 2016 11:12:00 +0100
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56C0B835.9050806@ens-lyon.org>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
 <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
 <56C0B835.9050806@ens-lyon.org>
Message-ID: <56C1A470.9010302@gmail.com>

On 02/14/2016 06:24 PM, Pierre-Yves David wrote:
> On 02/13/2016 02:56 AM, Nick Coghlan wrote:
>> On 13 February 2016 at 11:15, Brett Cannon <brett at python.org> wrote:
>>> I don't remember the story behind cpython-fullhistory, but it's
>>> obviously
>>> incomplete since just stopped post conversion. You will need to find
>>> someone
>>> who knows (I'd ask on python-dev).
>>>
>>> Also realize that this will be  our fourth VCS (cvs, svn, hg, now
>>> git). This
>>> is not going to be a perfect history of the semantic actions of
>>> commits from
>>> the beginning of time just due to the fact that these VCS tools all use
>>> different concepts.
>>
>> There's also the fact that prior to the move to SourceForge in 2000,
>> all changes had to be funneled through the half dozen or so people
>> with write access to the CVS tree:
>> https://docs.python.org/3/whatsnew/2.0.html#new-development-process
>>
>> I think it's definitely OK if future code archaeologists need to dig
>> into the SVN repository to get a more complete view of CPython's
>> history.
> 
> I've never met a project who did not regret such decision at some point.
> Keeping older history is usually valuable. Mercurial have powerful
> enough tool to let you get all the history back together, I assume git
> probably have that power too.
> 
> This is your call, but I strongly recommend taking advantage of this
> migration to put everything back together.
> 

While "putting everything back together" would be great, it doesn't
*have* to block the migration. Git has a command called "git replace"
that lets you do this later.

The Linux kernel (which switched to Git before Git migration tools
existed) has a separate "early history" repo that you can "prepend" to
the main one. Then, in your local copy, it looks like one unbroken
history. Since Git commits are snapshots and not deltas, this works
amazingly well -- it's just telling Git's object retrieval routine to
retrieve <object X> instead of <object Y>. The disadvantage is that it
has to be done in each clone individually -- no one can rewrite history
for others.

Two commands every future historian would have to do:
    git fetch <url_for_old_history>
    git replace --graft <first_commit_of_new_history>
<last_commit_of_old_history>



From nicholas.chammas at gmail.com  Mon Feb 15 16:39:01 2016
From: nicholas.chammas at gmail.com (Nicholas Chammas)
Date: Mon, 15 Feb 2016 21:39:01 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56C1A470.9010302@gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
 <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
 <56C0B835.9050806@ens-lyon.org> <56C1A470.9010302@gmail.com>
Message-ID: <CAOhmDzco65L5S-dLgKNew-Wtqum6ooZC2BCe+2TLHWOxL7wjWA@mail.gmail.com>

Response from GitHub staff regarding using their Importer
<https://import.github.com/> to import CPython:

Unfortunately, the repository is too large to migrate using the importer.
I?d recommend converting it to git locally using something like
hg-fast-export. Due to its size, you?ll need to push the local repo to
GitHub in chunks.

So it seems like Importer is a no-go.

Nick
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160215/8afa6b2b/attachment.html>

From senthil at uthcode.com  Mon Feb 15 16:44:19 2016
From: senthil at uthcode.com (Senthil Kumaran)
Date: Mon, 15 Feb 2016 13:44:19 -0800
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <CAOhmDzco65L5S-dLgKNew-Wtqum6ooZC2BCe+2TLHWOxL7wjWA@mail.gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
 <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
 <56C0B835.9050806@ens-lyon.org> <56C1A470.9010302@gmail.com>
 <CAOhmDzco65L5S-dLgKNew-Wtqum6ooZC2BCe+2TLHWOxL7wjWA@mail.gmail.com>
Message-ID: <CAPOVWOSjac6T-St_e3W=cmpH_YesN_9sZCz_VShmjqj0wBzxxA@mail.gmail.com>

On Mon, Feb 15, 2016 at 1:39 PM, Nicholas Chammas <
nicholas.chammas at gmail.com> wrote:

> So it seems like Importer is a no-go.


Yes, I got the same response from github.

However, the tools like hg-git are able to accomplish the task and we will
be able to carry forward with those.

-- 
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160215/fdb313c5/attachment.html>

From pierre-yves.david at ens-lyon.org  Mon Feb 15 16:55:01 2016
From: pierre-yves.david at ens-lyon.org (Pierre-Yves David)
Date: Mon, 15 Feb 2016 21:55:01 +0000
Subject: [core-workflow] Help needed: best way to convert hg repos to
 git?
In-Reply-To: <56C1A470.9010302@gmail.com>
References: <CAP1=2W54cDPJiQscP+X_dh1F1JhiDdfCUK=07PRtZT0c=RGK1Q@mail.gmail.com>
 <CANPC-tt3sbK5PbU4vaO8zaL53vC5wDWne5i3iRTZPXXS3cp_Vg@mail.gmail.com>
 <CANPC-tvwh=iQ7kFboFkJbD1aOnLB0vqSi=LOtSHkiyh=k54pCA@mail.gmail.com>
 <CANPC-tv5cVKp3OJCQXA06-FWiSQt9SLR8wznwyotBk4tFZEnrw@mail.gmail.com>
 <CAP1=2W453TT5MaHCy77XauV6N5SJxkRQ1j8ZZ32o1-HdZ-Ehew@mail.gmail.com>
 <CA+eR4cEjqoL5NWke_H8w8OCHLp-g63tQwEH0upt86au=7MT98A@mail.gmail.com>
 <CAP1=2W5i5+4vTFLzvq8Z2qriUKO0_VozUGQBG=c8pntUgWLM2w@mail.gmail.com>
 <CADiSq7dT+EHi-fithBau8bPbgbxiZDzf3yhdn+FS1Rxed_bs2Q@mail.gmail.com>
 <56C0B835.9050806@ens-lyon.org> <56C1A470.9010302@gmail.com>
Message-ID: <56C24935.7050604@ens-lyon.org>



On 02/15/2016 10:12 AM, Petr Viktorin wrote:
> On 02/14/2016 06:24 PM, Pierre-Yves David wrote:
>> On 02/13/2016 02:56 AM, Nick Coghlan wrote:
>>> On 13 February 2016 at 11:15, Brett Cannon <brett at python.org> wrote:
>>>> I don't remember the story behind cpython-fullhistory, but it's
>>>> obviously
>>>> incomplete since just stopped post conversion. You will need to find
>>>> someone
>>>> who knows (I'd ask on python-dev).
>>>>
>>>> Also realize that this will be  our fourth VCS (cvs, svn, hg, now
>>>> git). This
>>>> is not going to be a perfect history of the semantic actions of
>>>> commits from
>>>> the beginning of time just due to the fact that these VCS tools all use
>>>> different concepts.
>>>
>>> There's also the fact that prior to the move to SourceForge in 2000,
>>> all changes had to be funneled through the half dozen or so people
>>> with write access to the CVS tree:
>>> https://docs.python.org/3/whatsnew/2.0.html#new-development-process
>>>
>>> I think it's definitely OK if future code archaeologists need to dig
>>> into the SVN repository to get a more complete view of CPython's
>>> history.
>>
>> I've never met a project who did not regret such decision at some point.
>> Keeping older history is usually valuable. Mercurial have powerful
>> enough tool to let you get all the history back together, I assume git
>> probably have that power too.
>>
>> This is your call, but I strongly recommend taking advantage of this
>> migration to put everything back together.
>>
>
> While "putting everything back together" would be great, it doesn't
> *have* to block the migration. Git has a command called "git replace"
> that lets you do this later.
>
> The Linux kernel (which switched to Git before Git migration tools
> existed) has a separate "early history" repo that you can "prepend" to
> the main one. Then, in your local copy, it looks like one unbroken
> history. Since Git commits are snapshots and not deltas, this works
> amazingly well -- it's just telling Git's object retrieval routine to
> retrieve <object X> instead of <object Y>. The disadvantage is that it
> has to be done in each clone individually -- no one can rewrite history
> for others.
>
> Two commands every future historian would have to do:
>      git fetch <url_for_old_history>
>      git replace --graft <first_commit_of_new_history>
> <last_commit_of_old_history>

While this exists, I believe this would be much more convenient to have 
the history right in the first place.

But that's not my call.

-- 
Pierre-Yves David

From donald at stufft.io  Mon Feb 22 06:00:41 2016
From: donald at stufft.io (Donald Stufft)
Date: Mon, 22 Feb 2016 06:00:41 -0500
Subject: [core-workflow] Octohook (for Python Github Bots)
Message-ID: <96444799-8E7E-416A-B600-5E0B13C37298@stufft.io>

I just saw this https://github.com/pyupio/octohook and thought it might be useful for CPython?s Github hooks.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160222/14a8534d/attachment.sig>

From brett at python.org  Mon Feb 22 12:47:35 2016
From: brett at python.org (Brett Cannon)
Date: Mon, 22 Feb 2016 17:47:35 +0000
Subject: [core-workflow] Octohook (for Python Github Bots)
In-Reply-To: <96444799-8E7E-416A-B600-5E0B13C37298@stufft.io>
References: <96444799-8E7E-416A-B600-5E0B13C37298@stufft.io>
Message-ID: <CAP1=2W5JmMBAKLBPE2_Nxpbu0RSTxJPv8VO_x7jRjePeGty4rg@mail.gmail.com>

On Mon, 22 Feb 2016 at 03:00 Donald Stufft <donald at stufft.io> wrote:

> I just saw this https://github.com/pyupio/octohook and thought it might
> be useful for CPython?s Github hooks.
>

Thanks for the link! At least for the CLA bot I've already taken care of a
good chunk of that functionality:
https://github.com/brettcannon/knights-who-say-ni . Plus I also prefer to
use async/await on a PaaS platform than have to rely on gunicorn on docker
to hit our potential perf needs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160222/b32418eb/attachment.html>