search

wangyu190810 / cefpython

Automatically exported from code.google.com/p/cefpython
0 stars 0 forks source link

Migrate project to GitHub or Bitbucket #117

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Is there an easy way to migrate content from google code to github? The main 
concern is migrating content from the issue tracker and wiki pages.

Original issue reported on code.google.com by czarek.t...@gmail.com on 12 Mar 2014 at 6:25

GoogleCodeExporter commented 9 years ago 
There is a blog post on this topic here:
http://beets.radbox.org/blog/github-issues.html

The issues migration script is available here:
https://github.com/arthur-debert/google-code-issues-migrator

Original comment by allestue...@gmail.com on 4 Aug 2014 at 11:30

GoogleCodeExporter commented 9 years ago 
I tried the script. It had issues with text encoding, However, I managed 
(script attached) to migrate all the issues to a dummy project:
https://github.com/rtsh/test1/issues

Migrating the wiki has some linking problems:
https://github.com/rtsh/test1/wiki

Original comment by allestue...@gmail.com on 4 Aug 2014 at 1:19

Attachments:

GoogleCodeExporter commented 9 years ago 
@allestuetsmerweh Thanks for taking the time. On the wiki pages there are also 
broken headers, code blocks and indentation. In issues there are problems with 
formatting and posts containing html tags.

Original comment by czarek.t...@gmail.com on 4 Aug 2014 at 7:11

GoogleCodeExporter commented 9 years ago 
i spent some time fixing most errors of the wiki. it looks much better now.
Where exactly are there problems with formatting in issues?

Original comment by allestue...@gmail.com on 5 Aug 2014 at 12:19

GoogleCodeExporter commented 9 years ago 
I still see some problems on the wiki pages, eg. AudioVideo, Browser. In Issue 
112 comment #2 the html tags are cut. Also issues numbers do not match (Issue 
112 == Issue 109 on github).

Original comment by czarek.t...@gmail.com on 5 Aug 2014 at 3:04

GoogleCodeExporter commented 9 years ago 
We will also need a script for code.google, to add comments in issues informing 
about migration, with corresponding links to github. Whether to change issue 
title ("[migrated to github] ...") is for discussion.

Similar links will be needed on wiki pages, but this could be done manually or 
via git.

Original comment by czarek.t...@gmail.com on 5 Aug 2014 at 3:20

GoogleCodeExporter commented 9 years ago 
Here's what other maintainers did to inform users about the migration: 
(http://trentm.com/2012/03/google-code-to-github.html)

Summary: append (**MOVED TO GITHUB**)
Description: prepend = Note: This project has been moved to 
[https://github.com/... GitHub]. =
Wiki pages: prepend = Note: This project has been moved to 
[https://github.com/... GitHub]. =

Do you think it is necessary to comment on every issue with a link to the new 
issue? I mean you can search for issues on github...

Original comment by allestue...@gmail.com on 5 Aug 2014 at 9:01

GoogleCodeExporter commented 9 years ago 
As issues cannot be deleted on github, I had to move the issues test to a new 
repository:
https://github.com/rtsh/test2/issues
But now, the Issue-IDs match! (set option -s of the script)
As for the stripped HTML tags: they are migrated, but - as it is not formatted 
as a code block - aren't displayed, but interpreted as HTML. I edited that 
issue manually now.

Original comment by allestue...@gmail.com on 6 Aug 2014 at 11:06

GoogleCodeExporter commented 9 years ago 
The Browser wiki page looks very nice now with the indents. What method was 
used to migrate wiki pages and make the changes? I only see script for 
migrating issues. Also did you make any modifications to that script attached 
earlier?

Original comment by czarek.t...@gmail.com on 7 Aug 2014 at 9:06

GoogleCodeExporter commented 9 years ago 
The wiki can be cloned from gc and uploaded to github.
I did the conversion from gcwiki to markdown using some regex.
Unfortunately, i didn't log every regex I executed, but you can clone my wiki 
from github with all the changes.
Note that I was not yet able to review the whole wiki for broken links, etc.

As for the issues: No, I used exactly that script, but with the -s option.
I could also rename & transfer my repo to you on github. As you like.

Original comment by allestue...@gmail.com on 7 Aug 2014 at 10:50

GoogleCodeExporter commented 9 years ago 
For importing issues/comments, I think I will use a special account named "CEF 
Bot" to avoid confusion.

Original comment by czarek.t...@gmail.com on 8 Aug 2014 at 9:37

GoogleCodeExporter commented 9 years ago 
During the 31.0 release there have been multiple changes to wiki pages, so it 
will need to be migrated from scratch. Regexes that you've run would be useful.

Original comment by czarek.t...@gmail.com on 10 Aug 2014 at 6:26

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Ok, I tried to re-construct the regexes.
The attached script does this job pretty well.
However, there are still mistakes (e.g. list numbering in BuildOnWindows) that 
have to be corrected manually.

Original comment by allestue...@gmail.com on 10 Aug 2014 at 1:25

Attachments:

GoogleCodeExporter commented 9 years ago 
Is it possible to have labels on github wiki pages? I've just discoverd such 
feature on google-code and it's nice to have, see:
https://code.google.com/p/cefpython/w/list?q=label:ClientHandler
https://code.google.com/p/cefpython/w/list?q=label:Example

Original comment by czarek.t...@gmail.com on 11 Aug 2014 at 10:13

GoogleCodeExporter commented 9 years ago 
I don't think there is such a feature, but you surely can make a Wiki Page 
"ClientHandler" that contains Links to the different Wiki Pages on that topic.

Original comment by allestue...@gmail.com on 11 Aug 2014 at 11:16

GoogleCodeExporter commented 9 years ago 
It would be a good idea to remove big binary files from git history (Issue 103) 
during migration to Github. Currently repo is 400 MB because of these files.

Original comment by czarek.t...@gmail.com on 11 Jan 2015 at 7:35

GoogleCodeExporter commented 9 years ago 
Looks like migration to Github is inevitable. Google Code is closing in August, 
see http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html 
. A new button "Export to Github" appeared that should make things a lot easier.

Original comment by czarek.t...@gmail.com on 13 Mar 2015 at 9:47

GoogleCodeExporter commented 9 years ago 
Upstream CEF has migrated to bitbucket. Reasons for choosing bitbucket over 
github can be read here: 
http://www.magpcss.org/ceforum/viewtopic.php?p=24951#p24951

Original comment by czarek.t...@gmail.com on 16 Mar 2015 at 10:10

GoogleCodeExporter commented 9 years ago 
Another advantage of bitbucket over github is that you can have Table of 
Contents on wiki pages by inserting the [TOC] tag.

Original comment by czarek.t...@gmail.com on 16 Mar 2015 at 7:36