Migrate to Github

Originally reported by: Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco)

---

In order to be more visible and friendly to more contributors, CherryPy should consider moving to Github.

Github is the canonical and preferred hosting for most open source projects.

I'm willing to help with the process, but I first want to get the nod from @cyraxjoe and @Lawouach. Also, we'll need to create a CherryPy org (if there's not a better one to host it).

I propose migrating the existing issues to Github using https://github.com/jeffwidman/bitbucket-issue-migration or one of its many forks. I'm happy to test and execute that.

---

• Bitbucket: https://bitbucket.org/cherrypy/cherrypy/issue/1410

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

Hey Jason,

I'm all for it! I think there had been other people stating they were for it too.

As long as we manage to keep our history and we don't kill the bitbucket repo (keep it as a read-only to github for a long while so people can still refer to it).

Thanks for the proposal and offering to undertake the task.

Original comment by Joel Rivera (Bitbucket: cyraxjoe, GitHub: cyraxjoe):

---

Hi Jason,

I totally support this initiative and I'm willing to help on any task related to get it done 😃

Thanks!

Original comment by Joel Rivera (Bitbucket: cyraxjoe, GitHub: cyraxjoe):

---

@bhch we currently maintain a github mirror: https://github.com/cherrypy/cherrypy

Would you mind on expressing the reason behind preferring Mercurial over Git for a project that you don't actively contribute to? Just curios, do you maintain some sort of fork?

Personally I like Mercurial. But pragmatically GitHub is where the conversation is happening most of the time and if the move increase the engagement into the project (which I believe it will) then the change is justified.

Also, we don't really benefit for any peculiarity from mercurial. So the preferences is mostly a matter of personal taste or philosophy but from the perspective of the project I would always prefer the alternative that add less friction for contribution. Lot of people already knows git and it has become the defacto for main stream open source.

Original comment by Konstantin Molchanov (Bitbucket: moigagoo, GitHub: moigagoo):

---

Just a sidenote: after moving to GitHub, you could add a Gitter chat to the repo that would replace IRC. Gitter provides a convenient way to engage in a discussion with the developers and community members. It offers markdown, history, and email notifications, which really makes IRC pale in comparison.

Although I like hg more, I totally support the move to GitHub. I agree with Joel—personal tastes should not affect project-wide decisions.

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

I think @nicklasb is interested too.

Original comment by Nicklas Börjesson (Bitbucket: nicklasb, GitHub: nicklasb):

---

Yeah, this sounds great!

I agree on basically everything said here:
+1 moving to github. For example I just had to rewrite this response because the page refreshed or something.

+1 WRT mercurial, an open source project should aim to lower the bar for participation, and it is not like GIT is evil, closed source and proprietary

+1 using gitter, it is really usable. Actually very usable.

+1 keeping the bitbucket repo read-only.

+1 Creating an organization at github. However, isn't /cherrypy already an organisation?

WRT to moving issues, yeah if that works, great. It would be good if the issues on bitbucket could get a not that they have been moved at the end.

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

I'm all for it too.

My only concern about gitter is that it requires a github account, not everyone may want that. Are there bots that could bridge to IRC?

Original comment by Nicklas Börjesson (Bitbucket: nicklasb, GitHub: nicklasb):

---

Well, it is sort of that we now instead expect people to have google, IRC and bitbucket accounts instead.
I would think that it is quite uncommon to not have github accounts among open source developers.

I'd rather not involve IRC in any way, seems like that would just complicate stuff. Gitter is very de facto on github. And rightfully so IMO.

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

We can certainly give gitter a spin anyway :D

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

@Lawouach or @cyraxjoe, do you know who administers the Github CherryPy org? I'm not a yet a member. Could you add me as an admin so I might create test repos and test migrating the issues?

Also, there's a problem with the existing mirror - it already has pull requests against it, and since Github uses the same number sequence for pull requests and issues, it won't be possible to migrate the existing set of issues from bitbucket to the existing Github mirror and retain numbering (which is highly useful). I recommend wiping (or renaming/archiving) the existing Github repo and creating a new one, resetting the issues for a clean migration.

Who is it that maintains the current Github mirror? How is that accomplished (with hg-git perhaps)? I'd like to see if I can make a clone that links to both Git and Mercurial repos as well.

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

Hey Jason, what's your nickname on github?

Original comment by Nicklas Börjesson (Bitbucket: nicklasb, GitHub: nicklasb):

---

I would agree on a clean sheet on the github repo. Renaming the current into cherrypy_obsolete or something would keep the issues for later migration if needed(which doesn't seem likely).

Original comment by Sylvain Hellegouarch (Bitbucket: Lawouach, GitHub: Lawouach):

---

Okay found it.

You're admin on it now.

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

Issue migration is blocked due to issue 42 in the issue migration script.

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

Working around issue 42, I now am blocked by issue 65:

Imported Issue: https://api.github.com/repos/jaraco/cherrypy-mig-test-6/issues/558
Completed 558 of 1411 issues
Traceback (most recent call last):
  File "migrate.py", line 542, in <module>
    sys.exit(main(options))
  File "migrate.py", line 194, in main
    status_url, options.gh_auth, headers).json()['issue_url']
  File "migrate.py", line 518, in verify_github_issue_import_finished
    .format(status_url, respo.status_code)
RuntimeError: Failed to check GitHub issue import status url: https://api.github.com/repos/jaraco/cherrypy-mig-test-6/import/issues/558353 due to unexpected HTTP status code: 404