[OH-Dev] Issue Management Migration to GitHub Issues

[Asheesh Laroia]

Well, everyone, I have mass-imported our issues.

Huge thanks to Louis who put together the code that made this possible. I
made some minor tweaks to the code, and you can find it (and my frantic
commit log messages) here: https://github.com/paulproteus/oh-issuemover .
Louis, you're welcome to merge any of my changes, if you want them!

Here are some things I have done:

* Imported all the bugs into GitHub issues (which may have caused about *30,000
emails to be sent*, received by about 25 people, sorry about that).

* Added redirects so http://openhatch.org/bugs/issue1000 redirects to
https://github.com/openhatch/oh-mainline/issues/1315

* Archived the old Roundup data at e.g.
roundup-archive.openhatch.org/bugs/issue1000

* Switched off Roundup, on linode.openhatch.org.

* Published the archived data at
https://github.com/openhatch/oh-roundup-archive/

The archived data is the result of me using "wget" a bunch to download
"issue" data (rather than storing the original database), plus copying all
the "files" directly from the Roundup instance.

The original Roundup database is not deleted. It will hang around in MySQL
for a while, I guess.

I think that's all I can think to say. Welcome to this crazy new world.


On Thu, Aug 7, 2014 at 8:26 AM, Asheesh Laroia <asheesh at asheesh.org> wrote:

> On Thu, Aug 7, 2014 at 12:17 AM, Dirk Bächle <tshortik at gmx.de> wrote:
>
>>  Hi Asheesh,
>>
>>
>> On 07.08.2014 08:30, Asheesh Laroia wrote:
>>
>>  Huge props for Louis for doing all the research on this over PyCon. I
>> found the scripts he was using, and made and tested them out, and made a
>> few changes, and here is my latest test import:
>>
>>  https://github.com/imported-from-roundup/test/issues
>>
>> One known issue: I link to a domain I haven't set up yet,
>> http://roundup-archive.openhatch.org/ , which is where I'll keep the
>> files and /bugs/ URLs after I take a snapshot of them (and then I'll turn
>> off Roundup!).
>>
>>
>>  One other thing I plan to do is to redirect requests to
>> openhatch.org/bugs/issueXYZ to github.com/openhatch/oh-mainline/issuesXYZ
>> .
>>
>>  Any feedback on this format, before I do the real import to
>> oh-mainline's issue tracker? If there are no blockers, I'm tempted to do
>> that tomorrow, and then it'll be all done.
>>
>> I don't know if this is a show-stopper for the migration, but I just
>> looked through the imported bugs at GitHub and see that all their "latest
>> modification time" is squashed to the runtime of the conversion scripts.
>> This is probably expected, but maybe there is a way to tweak the "add
>> time", such that you don't lose part of your (time) history.
>> I sometimes find it useful to be able to see "Oh, that's a bug from long
>> ago with no recent action. I'll have a look at it."
>>
>
> Hi Dirk! Thanks for the response! It's always great to know someone else
> is interested.
>
> From what I can tell, the Github Issues API doesn't let us specify a last
> modified timestamp:
> https://developer.github.com/v3/issues/#create-an-issue
>
> But we do have some text on the bug that indicates last modified date. See
> https://github.com/imported-from-roundup/test/issues/991 and
> https://github.com/imported-from-roundup/test/issues/1026 to see that.
>
> If you have an idea for how to better-display that "Last modified" date
> imported from Roundup, I'd love to hear.
>
> Either way, thank you again for the response!
>
> -- Asheesh.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/devel/attachments/20140807/98f19a33/attachment.html>