Google Code is shutting down

[GoogleCodeExporter]

As you may be aware, Google Coe will be shutting down in January 2016 
http://google-opensource.blogspot.fr/2015/03/farewell-to-google-code.html

I was wondering if there's a plan in place to move the project to another code 
hosting service?

Moving to Github would be easy thanks to the "Export to Github" button provided 
in the toolbar. You may want to join forces with semi-active forks on Github. 
For example https://github.com/chazmcgarvey/tint2 has some commits that aren't 
in this repo yet.

Original issue reported on code.google.com by nodiscc on 13 Mar 2015 at 8:50

[GoogleCodeExporter]

Indeed. We have to decide before August when the repo becomes read only.

I am curious to see what vim and python decide when the flame wars settle:

https://groups.google.com/forum/#!msg/vim_dev/ehzfCDccmek/PU1sTZNdsTUJ)
http://thread.gmane.org/gmane.comp.python.devel/150459/focus=150484
https://www.python.org/dev/peps/pep-0481/

Personally I have a bad opinion about GitHub for various technical and 
non-technical reasons, so the chances of me opening an account there are very 
low.

Original comment by mrovi9...@gmail.com on 13 Mar 2015 at 11:14

• Changed state: Accepted
• Added labels: Priority-High, Type-Task
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I'd be fine with any hosting provider, as long as nothing is lost (code, doc, 
issues), it doesn't inject crapware in downloads (sourceforge), and the move is 
properly advertised some time before shutdown (think about distro package 
maintainers).

Github has the advantage of a larger userbase, so more drive-by contributions, 
and the usability/fetaures are ok; however I agree there may be technical and 
ethical issues with it (closed source, "everything on github" monoculture, 
etc.). A free software solution would be preferable IMHO. Gitlab for example, 
if you're willing to self-host one. There are also public Gitlab instances 
(https://about.gitlab.com/gitlab-com/, https://git.framasoft.org/ ...). 

Thanks for your reply and the interesting links

Original comment by nodiscc on 14 Mar 2015 at 11:15

[GoogleCodeExporter]

I have to talk to the other devs and we will make a decision in time.

The code will be easy to move no matter what hosting we switch to.

The wiki will require a bit of work, but it's only a dozen of pages or so, so 
it can be done easily by hand. We could probably convert it into markdown or 
even html and add it to the repo.

Regarding the issue tracker, I downloaded a dump to see if it works. It looks 
complete. It's only 3MB of mostly text data so we could probably even add it to 
the repository before we move, just to make sure nothing is lost. However it 
may need some pre-processing to remove emails and other private info that may 
be there.

Speaking in general, if I understand correctly, all the code from Google Code 
will continue to be served statically from googlesource.com even after Google 
Code shuts down. This is so that inactive projects do not disappear forever. So 
it might be a good idea to merge the docs and the issues into the repo just to 
make sure nothing will be lost under any circumstances.

Original comment by mrovi9...@gmail.com on 14 Mar 2015 at 4:39

[GoogleCodeExporter]

Posting this to keep track of the work. Feel free to offer opinions/suggestions.

I attempted to mirror tint2 on GitLab and BitBucket. Here are the results:

https://gitlab.com/o9000/tint2
https://bitbucket.org/o9000/tint2

Main differences:

* Issue tracker : GitLab is better
  * Labels: GitLab supports multiple labels, BitBucket supports only one label: Component. But we could probably add labels like "(openbox)" at the end of the issue title as a poor man's workaround.
  * Search: GitLab issue search returns less results than BitBucket's (which seems to return identical results as Google Code). But it's a bug and will probably be fixed.
  * UI: BitBucket looks clean, GitLab looks "cool" but a bit messy.
  * Workflow: BitBucket has predefined non-customizable status values, which lack for instance NeedInfo and Wishlist. On GitLab we can use labels for this.

* Downloads : BitBucket is slightly better
  * BitBucket supports arbitrary downloads, GitLab supports only downloading a specific commit.

* Wiki: BitBucket is slightly better
  * BitBucket can be configured to open directly the wiki homepage (similar to Google Code), while GitLab always opens the commit log (and they said this will not change).

In the end GitLab looks better, but I have not made my mind yet.

Original comment by mrovi9...@gmail.com on 22 Mar 2015 at 11:37

[GoogleCodeExporter]

Project moved to GitLab.

You can find this issue at: https://gitlab.com/o9000/tint2/issues/475

Original comment by mrovi9...@gmail.com on 25 Apr 2015 at 11:13

• Added labels: GitLab