Re: Google Code repository

[Andrew Plotkin]

Ori wrote:

> OK, turns out I need some permissions to convert the issues.
> Google's script needs a JSON dump file of all issues, and that's only
> available to owners:

Who are the owners? Ben Cressey and Chris Armstrong, I see. Are they still
reading this?

Also, should I file new bugs on Google Code or Github? (Found an exciting
new crash calling glk_image_draw_scaled...)

--Z

--
"And Aholibamah bare Jeush, and Jaalam, and Korah: these were the borogoves..."
*

[Christopher Armstrong]

>
> On Mar 17, 2015, at 11:26 PM, Andrew Plotkin <zgo...@eblong.com> wrote:
>
> Ori wrote:
>
>> OK, turns out I need some permissions to convert the issues.
>> Google's script needs a JSON dump file of all issues, and that's only available to owners:
>
> Who are the owners? Ben Cressey and Chris Armstrong, I see. Are they still reading this?
>

I am. I can add more administrators — I just need a Google Account email address.

I saw the email from google groups and hoped Ben would take care of it, of course ;-)

-radix

[Andrew Plotkin]

If you could add Ori Avtalion as an administrator, that would be helpful. Not sure whether that's his gmail address or avtalion.name address?

Then he can export the issues from the Google account and import them into Github.

[Ori Avtalion]

My gmail acct is saltyhorse@...

[Ori Avtalion]

I'm trying a different approach that doesn't require permissions:
Using Google Code's export process to copy the issues to a personal Github repo, then using a different script to copy the issues between the Github repositories.

[Ori Avtalion]

The issues have been copied to my personal repository:
https://github.com/salty-horse/garglk/issues/

If I wish to copy issues from there to garglk/garglk, I'll have to either:
1) manually edit one of the existing issue-copying scripts - because they all add metadata that shows which Github project the issues were copied from - ugly, since the issues already have "copied-from-google-code" metadata.

2) Delete garglk/garglk, and use Github's "transfer project", which will copy everything, and then I'll force-push my clean github project, and re-do the wiki pages - This seems the cleanest approach, which I could have done initially :(

3) Wait for the json dump of the issues by an admin of the Google Code project.

If people don't mind (2) requiring people to "re-watch" the repository after I delete it, I don't see a huge problem with it.

[Christopher Armstrong]

Okie doke, I’ve added you.

On Mar 22, 2015, at 12:40 AM, Ori Avtalion <o...@avtalion.name> wrote:

My gmail acct is saltyhorse@...

--
You received this message because you are subscribed to the Google Groups "garglk-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to garglk-dev+...@googlegroups.com.
To post to this group, send email to gargl...@googlegroups.com.
Visit this group at http://groups.google.com/group/garglk-dev.
For more options, visit https://groups.google.com/d/optout.

[Ori Avtalion]

Thanks, Christopher!

OK, I did some tests. Google's script seems to produce issues of worse quality than their automated export tool:

Script: https://github.com/salty-horse/garglk_test/issues/18

Tool: https://github.com/salty-horse/garglk/issues/18

Does anyone object to me deleting garglk/garglk, then transferring salty-horse/garglk to it (just for the issues), then force-pushing the repository?

[Andrew Plotkin]

On Sun, 22 Mar 2015, Ori Avtalion wrote:

> Does anyone object to me deleting garglk/garglk, then transferring
> salty-horse/garglk to it (just for the issues), then force-pushing the
> repository?

Go for it.

[Ori Avtalion]

OK! I deleted the repository and in its place is a brand new one, which is exactly the same as before, except it has the imported issues.

https://github.com/garglk/garglk

Would have been slightly simpler if I originally used Google's Export button.

Here's a checklist of what I copied over, in case I missed anything:

1) Same git repository as before. (No changes, but there may be some ssh errors if you try to fetch the same URL as before)

2) Same wiki repository as before (a few pages that I converted from Google Code using their wiki->markdown tool). Documentation-wise, it needs updating of svn->git links in the Developers guide, and perhaps create a nice download page with the latest release binaries)

3) Issues imported from Google Code using their closed-source service.

4) Files uploaded to https://github.com/garglk/garglk/releases/tag/stable-2011.1

5) Invited Ben to the garglk org again.

[Andrew Plotkin]

On Sunday, March 22, 2015 at 4:46:16 PM UTC-4, Ori Avtalion wrote:

OK! I deleted the repository and in its place is a brand new one, which is exactly the same as before, except it has the imported issues.

https://github.com/garglk/garglk

Would have been slightly simpler if I originally used Google's Export button.

In the imported issues, attachments still point at the Google Code server.

 

[Zarf]

On Sun, 22 Mar 2015, Andrew Plotkin wrote:

> In the imported issues, attachments still point at the Google Code server.

Grr. Google screwing up quoting. That was what I meant to report.

[Ori Avtalion]

On Sun, 22 Mar 2015, Andrew Plotkin wrote:

In the imported issues, attachments still point at the Google Code server.

Github's issue system doesn't allow attaching files, which may explain this missing feature.

Looking at the JSON output from Google Code [1], the project has 80 attachments.

I can start by downloading them for backup, and we can decide what to do with them later...?

[1] https://www.dropbox.com/s/zzyjxnnafvym3rb/garglk_google_code.json.gz?dl=0