Migrate to GitHub/BitBucket

[GoogleCodeExporter]

As you probably know, google code is closing[1]. On August the repos will 
become read-only. So morelinq should probably move to github. 

Github will also make contributions more likely as people are already there.


[1] http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

Original issue reported on code.google.com by fsate...@gmail.com on 30 Apr 2015 at 1:18

[GoogleCodeExporter]

The export seems to work reasonably well[1], and it even exports issues.

Please migrate soonish.

(And also lets release 2.0! ;)

[1] https://github.com/fsateler/morelinq

Original comment by fsate...@gmail.com on 30 Apr 2015 at 1:24

[GoogleCodeExporter]

The current plan is to go with BitBucket as the repo is based on Hg and GitHub 
forces the uses of Git.

> Github will also make contributions more likely as people are already there

Those who wanted to contribute have done so without GitHub.

Original comment by azizatif on 30 Apr 2015 at 8:38

• Changed title: Migrate to GitHub/BitBucket
• Changed state: Accepted
• Added labels: Priority-Critical, Type-Task
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

Cool. Looking forward to it.

Original comment by fsate...@gmail.com on 30 Apr 2015 at 9:00

[GoogleCodeExporter]

the link for the export in case others are interested: 
http://code.google.com/export-to-github/

Also, in case it's of any future value, those who prefer Mercurial can still 
use it when interacting with git repos (whether or github or not) via 
http://hg-git.github.io/ although that may not be useful depending on which 
Mercurial client(s)/plugin(s) you're using.

Of course, if the repo stays in Mercurial, those who prefer git can use git-hg 
instead as well http://offbytwo.github.io/git-hg/

Original comment by james.ma...@gmail.com on 1 May 2015 at 2:25

[GoogleCodeExporter]

New home is at: https://bitbucket.org/morelinq/morelinq

The Hg source repository is mirrored.

Migration of wikis, links and issues is pending.

Original comment by azizatif on 19 May 2015 at 1:49

• Changed state: Started

[GoogleCodeExporter]

@azizatif \o/

Original comment by fsate...@gmail.com on 20 May 2015 at 3:08

[GoogleCodeExporter]

Wikis have been migrated:
https://bitbucket.org/morelinq/morelinq/wiki/browse/

Original comment by azizatif on 20 May 2015 at 4:38

[GoogleCodeExporter]

Documentation also migrated online:
http://morelinq.bitbucket.org/docs/api/

Original comment by azizatif on 20 May 2015 at 4:39

[GoogleCodeExporter]

I do not know if you knew this, but there is also automation to migrate issues:

https://code.google.com/p/support-tools/wiki/IssueExporterTool

Original comment by fsate...@gmail.com on 16 Jun 2015 at 8:14

[GoogleCodeExporter]

@fsateler Yes I do and I have been using it to exports wikis and issues mostly.

Original comment by azizatif on 16 Jun 2015 at 8:46

[GoogleCodeExporter]

@fsateler …the BitBucket adapter needs some work, like issue #100[1] that I 
just reported today.

[1] https://code.google.com/p/support-tools/issues/detail?id=100

Original comment by azizatif on 16 Jun 2015 at 8:49

[GoogleCodeExporter]

Hi Aziz!

For issue #100 for morelinq, should I file it somewhere else instead 
(BitBucket?) or will it get exported/copied over as part of the existing effort?

Thanks!

Original comment by james.ma...@gmail.com on 16 Jun 2015 at 8:58

[GoogleCodeExporter]

@james.manning Hadn't realize we're reaching 100 on MoreLINQ too! :) You can 
file it here on Google Code and it will be exported in due time. Once the 
migration is complete, this issue tracker will be disabled although I'm not 
sure if Google Code offers that option.

The only problem with migration is that user associations are lost. If you are 
manningj[1] on BitBucket then I can keep your association but otherwise 
impractical to ping everyone else.

I shouldn't be long with migration now. I'm hoping to have it addressed it by 
the end of this week but that's just how all best laid plans go. :)

[1] https://bitbucket.org/manningj

Original comment by azizatif on 16 Jun 2015 at 9:23

[GoogleCodeExporter]

For pure archival and historical interest (and, yes, because it can be done), 
the Subversion repo is now mirrored and available over at:
https://www.assembla.com/code/morelinq/subversion/nodes

Original comment by azizatif on 16 Jun 2015 at 9:33

[GoogleCodeExporter]

This issue has been migrated to:
https://github.com/MoreLINQ/morelinq/issues/99
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 21 Aug 2015 at 6:56