New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Google Code to GitHub #29

Closed
Grundlefleck opened this Issue Dec 5, 2012 · 12 comments

Comments

Projects
None yet
2 participants
@Grundlefleck
Contributor

Grundlefleck commented Dec 5, 2012

Original author: Grundlefleck@gmail.com (July 19, 2012 20:43:27)

It has been suggested that I move the project from googlecode to GitHub to improve the likelihood of collaboration.

I'm open to the idea, but a bit wary of the problems it may cause:

  • transferring wiki/issues etc
  • confusion for users having two sites (or the problem of closing the google code version altogether and having old links not work)
  • safely migrating version control history

Intended benefits are:

  • increased collaboration, GitHub provides a much easier way of suggesting improvements by way of pull requests
  • would be easier to stop using a nested scm structure (googlecode project holds 3 projects in one)

I'm inclined to be a bit lazy about this, and maybe see if there is more desire for collaborating.

Original issue: http://code.google.com/p/mutability-detector/issues/detail?id=28

@ghost ghost assigned Grundlefleck Dec 5, 2012

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 5, 2012

How far are with this with issues? Nearly done - I think we can soon close it!

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 5, 2012

The issue importing is now complete, thanks to https://github.com/arthur-debert/google-code-issues-migrator

There's still some things to be done that I can think of:

  • host html version of Javadoc, like [0]. This could be part of the new GitHub Pages that the project has[1]
  • clean up the wiki/GitHub pages to be more friendly. Maybe this could just be transferring the contents of the main wiki page to the README.md
  • change google code project to show in an obvious way that GitHub is the active host
  • add jar downloads to GitHub (or should I just link to Maven central for downloads and forget hosting separate files on GitHub?)

There's also a couple of things I think I'll just do when I get to them, just including them here to remind myself:

  • update scm links in Cloudbees Jenkins job
  • update scm links in various pom.xmls
  • change http://mutabilitydetector.org to redirect to new GitHub Pages

You've done an excellent job on this @neomatrix369 :)

[0] https://mutability-detector.googlecode.com/svn/trunk/MutabilityDetector/trunk/javadoc/latest/org/mutabilitydetector/unittesting/MutabilityAssert.html
[1] http://mutabilitydetector.github.com/MutabilityDetector/

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 5, 2012

Cool thanks, it was a pleasure, still a bit blue that "python script" (google-code-issues-migrator) didn't work for me fully. Nevermind!

Is there anything from this list you want me to do? Just let me know and I'll sort them out this week.

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 5, 2012

Btw did you check if any of the projects compile, I was working on it last night and then gave up as it got too late! But I will attempt to do it during the weekend.

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 5, 2012

If you could have a go at hosting the javadoc in the GitHub pages site, that'd be cool.

The Pages live in a branch[0], and it looks like it would be straight forward to:

  • run 'mvn javadoc:javadoc' in MutabilityDetector
  • take the resultant javadocs dir (target/site/apidocs) and commit that to the gh-pages branch somewhere
  • link to the MutabilityAssert[1] class from the main page

I think it's fine just to have Javadocs for trunk/HEAD/whatever git calls it, no need to tag versions of the javadoc.

Sound like something you would like to do?

I have so far checked that MutabilityDetector compiles, didn't check the other projects. That would be a good excuse to go fix the Jenkins set up to find out :)

[0] https://github.com/MutabilityDetector/MutabilityDetector/tree/gh-pages
[1] like this: https://mutability-detector.googlecode.com/svn/trunk/MutabilityDetector/trunk/javadoc/latest/org/mutabilitydetector/unittesting/MutabilityAssert.html

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 5, 2012

Okay sounds like a plan, i'll go through the list and start fixing the elementary ones first before picking the next level tasks. I;ll keep you posted!

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 9, 2012

All existing issues on google code have been marked as duplicates with a link to GitHub issues.

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 9, 2012

Downloads ported over. All downloads at google code now deprecated. Wiki pages and the main page ported over as well.

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 9, 2012

@neomatrix369 I think I've completed all this, as well as rebuilding the JavaDocs. Could you take a look at the old page on google code and make sure that it would be obvious to anyone coming along that the project has been migrated?

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 9, 2012

Okay will do, sorry I didn;t get a chance to look at it, I got tied up with
other things.

Looks good but the font size could be up-ed to make it more obvious the
moment to step into the page.

Also would it make sense to link up the wiki from the google code page to
the wiki on the github page?

Cheers,
Mani

On Sun, Dec 9, 2012 at 9:10 PM, Graham Allan notifications@github.comwrote:

@neomatrix369 https://github.com/neomatrix369 I think I've completed
all this, as well as rebuilding the JavaDocs. Could you take a look at the
old page on google code and make sure that it would be obvious to anyone
coming along that the project has been migrated?


Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-11176032.

Twitter: @theNeomatrix369
Blog: http://neomatrix369.wordpress.com http://neomatrxi369.wordpress.com

Don't chase success, rather aim for "Excellence", and success will come
chasing after you!

@neomatrix369

This comment has been minimized.

Member

neomatrix369 commented Dec 9, 2012

Since this one is now completed, do you have another issue among the list
of them that you see fit to assign to me?

Cheers,
Mani

On Sun, Dec 9, 2012 at 9:48 PM, Mani Sarkar sadhak001@gmail.com wrote:

Okay will do, sorry I didn;t get a chance to look at it, I got tied up
with other things.

Looks good but the font size could be up-ed to make it more obvious the
moment to step into the page.

Also would it make sense to link up the wiki from the google code page to
the wiki on the github page?

Cheers,
Mani

On Sun, Dec 9, 2012 at 9:10 PM, Graham Allan notifications@github.comwrote:

@neomatrix369 https://github.com/neomatrix369 I think I've completed
all this, as well as rebuilding the JavaDocs. Could you take a look at the
old page on google code and make sure that it would be obvious to anyone
coming along that the project has been migrated?


Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-11176032.

Twitter: @theNeomatrix369
Blog: http://neomatrix369.wordpress.comhttp://neomatrxi369.wordpress.com

Don't chase success, rather aim for "Excellence", and success will come
chasing after you!

Twitter: @theNeomatrix369
Blog: http://neomatrix369.wordpress.com http://neomatrxi369.wordpress.com

Don't chase success, rather aim for "Excellence", and success will come
chasing after you!

@Grundlefleck

This comment has been minimized.

Contributor

Grundlefleck commented Dec 9, 2012

Can't up the font size any more unfortunately. I've changed the single wiki entry to contain a link to GitHub wiki. Think this issue is closeable.

I'll take a look at other issues and see if there's anything suitable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment