Basically the key things that came out of the language summit are two
things. One is that to move over cpython will require matching what we have
now, so when a commit lands on the repo that bugs.python.org gets a message
and a way to associate an issue with a PR (probably something like
detecting "Issue #" in the title of the PR and then making the association
on bugs.python.org). Otherwise dealing w/ sys._mercurial/sys._git and
updating the devguide are the only requirements.
Two, in order to shutdown Rietveld we will need to back up the database of
code reviews and dump the review information in some readable format (maybe
something as simple as running wget over Rietveld).
I just read a very interesting article about a new forge, Pagure:
"Pagure and Fedora"
Pagure looks like a clone of GitHub implemented in Python (!) (Python
2 only yet, oooooh, but a Python 3 port is ongoing) and storing all
data in Git! Excellent. Data: code, documentation, tickets, pull
requests, etc. Just everything.
The main difference with GitHub is that you can more easily extract
data to move to a new forge later. I also understand that it's free to
host your own server, since Pagure is a libre (free) software (GitHub
requires a license, no?).
As written in the article, the GitHub still has a major advantage: its
"network" (its community).
I also shared the article because I read another very interesting
article about Gerrit. Mike Bayer writes that Gerrit reviews are as
much importants as changes themself. IMHO he's right, the information
of reviews are very important and we should take to keep... especially
if tomorrow we move to another forge ;-)
It looks like we are going to loose all Rietveld reviews when moving
to GitHub. What if we move to Pagure tomorrow? :-p
The CPython move to GitHub seems to have started. It looks like Pagure
is still young, and GitHub has many advantages, but well, I wanted to
share this project with you ;-)
Note: GitHub was down a few minutes this morning ;-)
My name is Anish Shah and I will be working on GitHub integration under
GSoC 2016. This mail is briefing you all about the progress till now.
 A new "GitHub PR URL" field on issue page - A developer can submit a
link to GH pull request that he made.
 Link PR in comments - currently, issue number and PEP gets link
automatically in comments. Same way, "PR 123", "pull request 123" or
"pullrequest 123" will get linked automatically.
 Link GitHub PR automatically to b.p.o issues. - On GitHub, if there's a
string like "fixes #123" in PR comments/title/body, then it gets linked to
issue 123 automatically. Using GitHub webhooks, we can link PR to b.p.o
issues if there's a string like "fixes bpo123".
 Show PR status (open/closed/merged) on b.p.o issues page.
Some things that I will be working over the next few weeks are :-
- Posting some of the PR review comments on b.p.o.
- Auto-conversion of patches to PR
Hey there fellow core-workflowers; I've been following the GitHub transition
for a while now, and have some questions (which may have been answered
already, I apologize in advance if so!).
So, I read the PEP again to see if it was answered, seems it wasn't clear
(or I'm visually impaired, you get to choose). I understand that there's
already a semi-official mirror of the cpython repo on GitHub, and I've been
wondering why it isn't enough for our needs. Sure, a bunch of stuff needs to
be done (like the CLA bot and the PR <-> issue linking), but surely they
could be done on the current mirror. My workflow uses the GitHub mirror, and
my patches are compatible with b.p.o and Rietveld. Is there something I'm
missing as to why we can't re-use this one?
Then, as someone who's been using git and GitHub for almost everything
code-related and never touched Mercurial, is there something I can do to
help with the transition? I would really love a more accessible workflow for
both core developers and external contributors as soon as possible (don't we
all?), so if I can help I'd love to; I do realize I'm a bit late to the
Keep up the good work!
Now that I'm comfortable declaring the code for the CLA bot finished (
https://github.com/python/the-knights-who-say-ni), the next step is to
finalize the command(s) we are going to use to convert hg repositories to
git for migration to GitHub. Senthil, are you ready to make a final
Once I have the conversion command(s) documented in PEP 512 and I have
created the "Python core" team on GitHub for all of the current Python core
developers, I will migrate https://hg.python.org/devinabox to make sure
that everything works. After that has been verified as working I will then
look at migrating https://hg.python.org/devguide/ and
https://hg.python.org/peps/ (will take a little bit more effort for both to
get the web builds updated, and peps requires getting the PEP editors
on-board). The benchmarks repo might actually not get migrated as there is
talk of starting that repo from scratch.
It's looking like we will stay on track to get at least one repository
migrated by PyCon US!
https://github.com/python/devinabox now exists! A huge thank you to
everyone who has helped out so far in making this transition reach this
point, especially Maciej and Ezio for the b.p.o stuff and Senthil for
leading the git migration work.
Next up is the peps and devguide repos. For peps I need to:
1. See if the unofficial mirror is actually good enough to use
2. Find out where the command is being run to checkout and build the
peps from hg so it can use git instead
3. Figure out how to turn off the mirroring
4. If the unofficial mirror isn't good enough, then migrate the repo
The devguide is similar but w/o the worry of checking for any mirror.
The benchmarks migration is on hold until a decision is made over on the
speed@ mailing list as to whether that repo will be started from scratch.
The cpython repo can't be migrated until I get the Python core team to tell
me exactly what functionality must exist before a migration can occur. That
will be discussed at the language summit at PyCon US this year, so I should
have a better idea of what takes priority after having that discussion.
Hi The Knights Who Say "Ni",
Brett Cannon has invited you to join the Python organization on GitHub. Head over to https://github.com/python to check out Python's profile.
To join Python, follow this link:
Some helpful tips:
- If you get a 404 page, make sure you’re signed in as the-knights-who-say-ni.
- You can also accept the invitation by visiting the organization page directly at https://github.com/python
If you were not expecting this invitation, you can ignore this email.
The GitHub Team