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 -- View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4840780.html Sent from the Moose mailing list archive at Nabble.com.

Awesome :)

Thanks! Doru

On Mon, Aug 3, 2015 at 5:58 PM, Sean P. DeNigris sean@clipperadams.com 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

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 -- View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4840821.html Sent from the Moose mailing list archive at Nabble.com.

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.

Doru, it would be great to have this url somewhere on the moose website. Can you it please? This is important :-)

Alexandre

Yes!

Alexandre

Doru, is this okay to do such a transfer?

Alexandre

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 -- View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4841370.html Sent from the Moose mailing list archive at Nabble.com.

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 sean@clipperadams.com 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Tue, Aug 11, 2015 at 10:54 PM, Alexandre Bergel alexandre.bergel@me.com wrote:

The truth is that we have not used this repo for a while. Nowadays, all the tools produced by ObjectProfile are within the scope of Moose. So it makes sense to stick to the Moose issue tracker.

It might be worth advising that on that repo home & wiki pages. Otherwise people randomly searching for "ObjectProfile" may get a wrong impression of abandonment from last activity date on the tracker. cheers -ben

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

On Aug 11, 2015, at 10:54 AM, Ben Coman btc@openInWorld.com wrote:

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 sean@clipperadams.com 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

Hi Sean,

Thanks for your fine work. I just notice that if you load the previos main page at [1] you get a github message saying that the repository is empty. Maybe some people can have old bookmarks to the root web adreess and this could be misleading. Just wondering if this is the expected or there is something else to be done.

[1] https://code.google.com/p/moose-technology/

Cheers,

Offray

On 11/08/15 08:03, Sean P. DeNigris 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 Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Sean P. DeNigris wrote

I'd like to also copy the wiki pages before re-enabling

I don't know which wiki pages are still relevant, so I created an issue with a link to the files (https://github.com/moosetechnology/Moose/issues/1129). Since the GitHub repo now has a readme and license, I've re-enabled the redirect. HTH.

----- Cheers, Sean -- View this message in context: http://forum.world.st/Moving-Issues-to-GitHub-tp4840767p4842124.html Sent from the Moose mailing list archive at Nabble.com.