[Ironpython-users] Codeplex -> GitHub Issue Migration (Was: Differences with pyc-compiled assemblies?)

[Slide]

On Sun, Nov 25, 2012 at 1:20 AM, Jeff Hardy <jdhardy at gmail.com> wrote:

> Good work! For the most part, I like it. There are a couple of minor
> improvements I'd like to see:
>
> * can you parse the XML-formatted issues (e.g.
> http://ironpython.codeplex.com/workitem/23970) and get the interesting
> information (reporter, date, affected version) out of that?
>

Yeah, this shouldn't be too hard. I'm going to delete the test repo I
created and create a new one to test the import again. Another thing I am
running into is the rate limiting on GitHub, I need to optimize a few
requests to reduce the number and get around the rate limiting.


> * can you move all of the old metadata to the bottom of the issue,
> under "Original Codeplex Issue"?
>

I'm assuming you mean the "Item Details" stuff from the issues on CodePlex?


> * the attachment links aren't being rendered properly. Probably just a
> slight issue with the Markdown you're using.
>

I'll take a look at this as well, I think I reversed the [] and () in the
markdown.


>
> For the attachments, the only other reasonable thing I can think of is
> to put them in S3. I don't really see any issue with just linking to
> the attachments on Codeplex, though, since I doubt they'll go away any
> time soon. I'm sure it would be possible if non-trivial to move them
> all later anyway.
>
>
I can take a look at S3, it looks like they have a free tier of 5GB of
storage which should be more than plenty. Once I'm to a point where it
looks like how you want, is there a login account I should use to import
into GitHub so that the issues don't look like they are from me, or does
anyone care about that part?

slide


>
> On Sat, Nov 24, 2012 at 7:41 PM, Slide <slide.o.mix at gmail.com> wrote:
> > Take a look at https://github.com/slide/test/issues?state=open and let
> me
> > know what you think. I know I need to reverse the order of the comments
> > once imported to GitHub, so don't look at that, but tell me what you
> think
> > about the data I am importing and the format as well. Attachments are
> kind
> > of tricky, I am currently just putting a link back to the original
> > attachment on CodePlex, but there is probably a better way to do that.
> >
> > slide
> >
> >
> > On Sat, Nov 24, 2012 at 8:15 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
> >>
> >> The completist in me would like to see everything moved, but I would
> >> be quite happy with just the open issues. I'm OK with losing who it's
> >> assign to and what the target release is, but I would hate to lose
> >> comments or attached files. If possible I'd like to keep the user who
> >> created/commented, but that might not be possible with the different
> >> sets of users.
> >>
> >> - Jeff
> >>
> >> On Sat, Nov 24, 2012 at 4:04 PM, Slide <slide.o.mix at gmail.com> wrote:
> >> > Are we wanting to migrate all closed issues as well, or just the ones
> >> > that
> >> > are open? I tried using that script I found and it wasn't very
> robust. I
> >> > have written something that pulls out quite a bit of information from
> >> > the
> >> > CodePlex issues site into a sqlite database and then I can import into
> >> > GitHub issues. I just need to know what information we want to
> transfer
> >> > and
> >> > keep.
> >> >
> >> >
> >> > On Tue, Nov 13, 2012 at 10:31 AM, Jeff Hardy <jdhardy at gmail.com>
> wrote:
> >> >>
> >> >> On Mon, Nov 12, 2012 at 10:39 AM, Slide <slide.o.mix at gmail.com>
> wrote:
> >> >> > Yes, codeplex has issues with pasting code, horrible horrible
> issues.
> >> >>
> >> >> If anyone knows of a Codeplex -> GitHub issue migration script, I'd
> be
> >> >> happy to hear about it.
> >> >>
> >> >> - Jeff
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Website: http://earl-of-code.com
> >
> >
> >
> >
> > --
> > Website: http://earl-of-code.com
>



-- 
Website: http://earl-of-code.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20121125/c1c55bbc/attachment.html>