Moving Issues to GitHub

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Moving Issues to GitHub

Sean P. DeNigris
Administrator
In progress:
x. Export Google Issues to JSON since we have too many to use the Export button
x. Create GH access token for Python import script
x. Request GH raise our API rate limit so that script doesn't fall over so frequently
4. Re-run script to import remaining (almost all) issues
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

abergel
Excellent!

Thanks Sean!!

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 3, 2015, at 10:21 AM, Sean P. DeNigris <[hidden email]> wrote:

In progress:
x. Export Google Issues to JSON since we have too many to use the Export
button
x. Create GH access token for Python import script
x. Request GH raise our API rate limit so that script doesn't fall over so
frequently
4. Re-run script to import remaining (almost all) issues



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
abergel wrote
Thanks Sean!!
NP :)

In progress:
x. Export Google Issues to JSON since we have too many to use the Export button
x. Create GH access token for Python import script
x. Request GH raise our API rate limit so that script doesn't fall over so frequently
x. Rate limit removed
-. (17% done) Re-run script to import remaining (almost all) issues
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Tudor Girba-2
In reply to this post by abergel
Indeed. Thanks, Sean!

Doru

On Mon, Aug 3, 2015 at 3:45 PM, Alexandre Bergel <[hidden email]> wrote:
Excellent!

Thanks Sean!!

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 3, 2015, at 10:21 AM, Sean P. DeNigris <[hidden email]> wrote:

In progress:
x. Export Google Issues to JSON since we have too many to use the Export
button
x. Create GH access token for Python import script
x. Request GH raise our API rate limit so that script doesn't fall over so
frequently
4. Re-run script to import remaining (almost all) issues



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
In reply to this post by Sean P. DeNigris
Sean P. DeNigris wrote
In progress:
Export complete. Check out the result and see if it will work for us...
https://github.com/moosetechnology/Moose/issues

Labels and attachments (there was only one) seem to be intact
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Tudor Girba-2
Awesome :)

Thanks!
Doru

On Mon, Aug 3, 2015 at 5:58 PM, Sean P. DeNigris <[hidden email]> wrote:
Sean P. DeNigris wrote
> In progress:

Export complete. Check out the result and see if it will work for us...
https://github.com/moosetechnology/Moose/issues

Labels and attachments (there was only one) seem to be intact



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4840808.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
Tudor Girba-2 wrote
Thanks!
Sure... Although, spot checking further, I see that most issues are off by 1 ID, so I want to try it again...
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
Sean P. DeNigris wrote
I see that most issues are off by 1 ID, so I want to try it again...
Another try: (17% done) Re-run script with dummy issue #34 to import issues preserving IDs
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
Sean P. DeNigris wrote
Re-run script with dummy issue #34 to import issues preserving IDs
82% done. Seems like everything is going better this time. All issue IDs are the same as Google code so far. Just hit the rate limit... will try the rest in a bit...
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
Sean P. DeNigris wrote
Re-run script with dummy issue #34 to import issues preserving IDs
Export complete (round 2). Everything looks good. Issue comments, IDs, attachments, and labels intact. Check out the result and see if it will work for us...
https://github.com/moosetechnology/Moose/issues
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

abergel
This is truly excellent!

It all looks good by me.

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 4, 2015, at 7:16 AM, Sean P. DeNigris <[hidden email]> wrote:

Sean P. DeNigris wrote
Re-run script with dummy issue #34 to import issues preserving IDs

Export complete (round 2). Everything looks good. Issue comments, IDs,
attachments, and labels intact. Check out the result and see if it will work
for us...
https://github.com/moosetechnology/Moose/issues



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4840906.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

abergel
In reply to this post by Sean P. DeNigris
Doru, it would be great to have this url somewhere on the moose website.
Can you it please? This is important :-)

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 4, 2015, at 7:16 AM, Sean P. DeNigris <[hidden email]> wrote:

Sean P. DeNigris wrote
Re-run script with dummy issue #34 to import issues preserving IDs

Export complete (round 2). Everything looks good. Issue comments, IDs,
attachments, and labels intact. Check out the result and see if it will work
for us...
https://github.com/moosetechnology/Moose/issues



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4840906.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
abergel wrote
it would be great to have this url somewhere on the moose website
https://github.com/girba/moosetechnology.org/pull/1

BTW we should probably transfer this repo under the moosetechnology organization, no?
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

abergel
Yes!

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 5, 2015, at 11:48 AM, Sean P. DeNigris <[hidden email]> wrote:

abergel wrote
it would be great to have this url somewhere on the moose website

https://github.com/girba/moosetechnology.org/pull/1

BTW we should probably transfer this repo under the moosetechnology
organization, no?



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4841098.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
abergel wrote
Yes!
Pretty straightforward. It's available right in the repo setting. It even updates forks to point to the new repo (see https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization)
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

abergel
Doru, is this okay to do such a transfer?

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 5, 2015, at 12:03 PM, Sean P. DeNigris <[hidden email]> wrote:

abergel wrote
Yes!

Pretty straightforward. It's available right in the repo setting. It even
updates forks to point to the new repo (see
https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization)



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4841104.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Tudor Girba-2
sure. I put it in my repo because we did not have a team at that time

Doru

On Wed, Aug 5, 2015 at 5:34 PM, Alexandre Bergel <[hidden email]> wrote:
Doru, is this okay to do such a transfer?

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Aug 5, 2015, at 12:03 PM, Sean P. DeNigris <[hidden email]> wrote:

abergel wrote
Yes!

Pretty straightforward. It's available right in the repo setting. It even
updates forks to point to the new repo (see
https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization)



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4841104.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
Tudor Girba-2 wrote
sure
Cool. You just have to go to https://github.com/girba/moosetechnology.org/settings and on the bottom in the "Danger Zone" click "Transfer" and specify our new organization in the form.
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Sean P. DeNigris
Administrator
In reply to this post by Sean P. DeNigris
Sean P. DeNigris wrote
Export complete
As a final step, I marked the Google Code project as moved, which now redirects all links to GitHub. This is pretty cool! For example, https://code.google.com/p/moose-technology/issues/detail?id=1124 brings you to GitHub Issue 1124 :) If
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Moving Issues to GitHub

Ben Coman
What is the plan for...
https://code.google.com/p/objectprofile/

?
cheers -ben

On Tue, Aug 11, 2015 at 9:03 PM, Sean P. DeNigris <[hidden email]> wrote:

> Sean P. DeNigris wrote
>> Export complete
>
> As a final step, I marked the Google Code project as moved, which now
> redirects all links to GitHub. This is pretty cool! For example,
> https://code.google.com/p/moose-technology/issues/detail?id=1124 brings you
> to GitHub Issue 1124 :) If
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4842097.html
> Sent from the Moose mailing list archive at Nabble.com.
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12