Shall we move issues to a new issue tracker (github / youtrack)

[GoogleCodeExporter]

After moving to github, it might prove interesting to move other stuff there, 
especially issues.

It seems some people have scripts for that :
http://trentm.com/2012/03/google-code-to-github.html

Questions are :
 - what about people that follow issues ?
 - shall we remove the issues here ? or just close them, and adding a link to the new issue tracker ?
 - what about search engine indexing ?
 - ... ?

Original issue reported on code.google.com by brice.du...@gmail.com on 26 Jul 2012 at 9:26

[GoogleCodeExporter]

We should not maintain 2 issue trackers for sure. One of them needs to go ;)

I'm ok with giving the github a try wrt issue tracking.

I don't think it's high priority to migrate the issues. However, if you're keen 
on it we can have it early :)

I'm not worried too much about users that follow issues / search engine. It's 
good that you've pointed that out, though. 

Original comment by szcze...@gmail.com on 12 Oct 2012 at 4:42

[GoogleCodeExporter]

Hi,
I'm currently taking a look at this issue with Brice at Paris Hackergarten.

We found this Python script that does the migration: 
https://github.com/tfmorris/google-code-issues-migrator

I've cloned the Mockito Github project and am currently testing the script by 
migrating the issues to my clone: https://github.com/olim7t/mockito/issues

Here at the steps I followed:

Enable issues on target repository (from admin tab).

Install scripts:

     git clone https://github.com/tfmorris/google-code-issues-migrator
     git clone https://github.com/tfmorris/PyGithub

Setup Python env (I had 2.6.1 installed by default on my machine):

     cd google-code-issues-migrator
     easy_install pip
     pip install gdata
     export PYTHONPATH=../PyGithub

Run the script (last 2 params are target Github user and project name):

     ./migrateissues.py mockito olim7t mockito

It will ask for your Github password at the beginning. I've taken a look at the 
sources and it doesn't seem to do anything funky with it.

Original comment by omichal...@xebia.fr on 18 Oct 2012 at 6:25

[GoogleCodeExporter]

There's a small problem with the batch: when an issue contains the string 
'@xxx', Github interprets it as a user handle and notifies the user that 
they've been mentioned. This happens for Java annotations and when google code 
users replied to each other using @. Email addresses are interpreted correctly.

When this matches an actual Github user, they get notified about an issue they 
have nothing to do with. See an example here: 
https://github.com/olim7t/mockito/issues/204#issuecomment-9576708

Out of courtesy, we should filter the @ character. The script already does that 
for #, so it shouldn't be too hard too had. I'll try to look into it this 
week-end.

Original comment by omichal...@xebia.fr on 18 Oct 2012 at 9:59

[GoogleCodeExporter]

"Email addresses are interpreted correctly" - this means that the submitters / 
commenters of the issues in google code will be correctly migrated over?

I don't find it easy enough working with google code. Change to github might 
solve some pains (and introduce others :). Few other problems with 
googlecode->github migration for issues:
 - github tracker is that one cannot search for tickets 'submitted by me'. I'm not sure how big this problem is (Peter from spock team says it's a blocker as many of his users exactly this way search for issues).
 - is it possible to turn off issues at google code? It is possible to do that in github (admin page).

We should migrate issues after: 
 - the source migration is done (e.g. google code site is updated, old source removed)
 - we have a plan to migrate other content: wiki, downloads, etc.

Original comment by szcze...@gmail.com on 19 Oct 2012 at 7:30

[GoogleCodeExporter]

> "Email addresses are interpreted correctly" - this means that the submitters 
/ commenters of the issues in google code will be correctly migrated over?

Nope this is related the @something github user notification, though users.

> github tracker is that one cannot search for tickets 'submitted by me'.
This is now possible (look for the 'Created by you' filter).
Although on the matter of migration, users that created issues on google code 
won't be creators of the transferred issues. This is a limitation regarding 
issue migration ; you need a Github account to create an issue (like any other 
open source repo), but users of google code might not have one on Github, hence 
the script uses the repo owner as the creator and add the email of the creator 
in the content of the issue comment. 

> is it possible to turn off issues at google code?
I don't think this is doable atm, maybe you can update the issue template to 
tell the users to report on github instead.

> we have a plan to migrate other content: wiki, downloads, etc.
I don't agree, issues might be more relevant before moving these.

Original comment by brice.du...@gmail.com on 19 Oct 2012 at 11:09

[GoogleCodeExporter]

 > we have a plan to migrate other content: wiki, downloads, etc.

I meant that I would like to have a plan - we can execute it later. It does not 
make sense to me to have issues and code on github but downloads and wiki on 
googlecode. I'd rather avoid migrating the issues and then start looking into 
migrating wiki, and discover that it's not doable or something :)

Also, I think we should avoid adding any overhead. E.g. migration of the issues 
should help us in something, not incur more churn. I guess it's obvious ;)

Original comment by szcze...@gmail.com on 19 Oct 2012 at 11:25