We'll migrate from bitbucket to github, see also GitHubvsBitBucket.

Plan

• create moinmoin github organisation: https://github.com/moinwiki/

• invite developers

• convert hg -> git repos

  • moin-1.3 repo with early versions (only releases) up to 1.3.5

  • moin-1.9 repo with 1.5 to 1.9.x (github importer ran against bitbucket repo)

  • moin repo with 2.0+ development (github importer ran against bitbucket repo)

  • moin/extensions -> "moin-legacy-ext"

  • xstatic* stuff

  • EmeraldTree

Repo Migration

github's own importer

• seems to work okish.
• strange branches - closed hg branches show up again (check: just delete them?)

This is what I used in the end.

fast-export

• seems to work ok
• needs a mapping file for authors (one time chance to clean up there)

Issues/Tickets Migration

jeffwidman's

https://github.com/jeffwidman/bitbucket-issue-migration

result: https://github.com/moinwiki/moin-2.0-issues-test1/issues

• good:
  • maintained
  • labels
• bad:
  • codebase: single file script, argparse, no setup.py, ...
  • username mapping only via commandline option

This is what I used in the end (with a small mod to create less boilerplate in the converted tickets).

ronny's

https://github.com/RonnyPfannschmidt-Attic/bitbucket_issue_migration

result: https://github.com/moinwiki/moin-2.0-issues-test2/issues

• good:
  • nice codebase (tests, click, modular, ...)
  • multi-step (fetch to local json, convert locally, upload json to github)
  • username mapping via json file
• bad:
  • unmaintained(?)
  • migration incomplete, github responded with 404 after 217 tickets
  • no labels
  • gh issue does not have correct timestamp metadata, original ts just in body