> Thanks a ton for doing this Sergey. +1
On Sun, Feb 16, 2014 at 9:17 AM, Aaron Meurer <asmeu...@gmail.com> wrote: > Thanks a ton for doing this Sergey. > > I should add that you're going to help review issue quality, don't > need to care about about closed issues. Closed issue discussions are > not used very often, and we do plan to keep the google code site > around as read only. > > Aaron Meurer > > > On Feb 16, 2014, at 3:05 AM, Sergey Kirpichev <skirpic...@gmail.com> > wrote: > > > > Hello, > > > > here is an update for our issues migration task... > > > > 1) A tool (works with pyquery-1.2.4, everything else - from the Debian > > Wheezy) > > > https://github.com/skirpichev/google-code-issues-migrator/blob/my2/exportissues.py > > to do export in the suggested format. > > 2) authors.json - database to workaround for > > email resolving (probably, we should keep this private) > > > > I will ask the GitHub support to do first test import. But > > it would be nice if we solve some problems with authors.json first: > > 1) We should check this file (It's mostly the product of manual > > conversion, probably there are typos/errors). > > 2) Some people from the core team (as well as others) use multiple > > emails and/or different gc-accounts. I think, we want to be sure > > they all map to one gh account. An example: > > "https://code.google.com/u/104039945248245758823/": > ondrej.c...@gmail.com > > "https://code.google.com/u/110772626676693391932/": > ondrej.c...@gmail.com > > > > Either we should map these emails to one canonical email in > > authors.json, or these people must be sure to add multiple emails > > to their github account. > > > > Other tasks for volunteers (in random order): > > 1) Find problems in the test import (to be in: > > https://github.com/skirpichev-test/issues-test2 > > Please report issues in the same repo and add label: > > Migration-Bugs. > > 2) Figure out how to add comment for each Google Code > > issue after migration, pointing to the new issue on GitHub. > > 3) Change SymPy's (and, maybe other projects as well) sources > > to use GitHub's issue numbers, not Google Code ones. > > Some patterns: > > @deprecated(..., issue=123, ...) > > def test_issue_123(): > > see issue #123 > > and so on... > > > > We should be very careful here, as there is a lot > > of GitHub's issues already. > > > >> On Fri, Jan 17, 2014 at 5:09 AM, Aaron Meurer <asmeu...@gmail.com> > wrote: > >> Well, we haven't actually done the migration yet, but when we do, > >> we'll weed out all instances of "code.google.com" from the codebase. > > > > -- > > You received this message because you are subscribed to the Google > Groups "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sympy+unsubscr...@googlegroups.com. > > To post to this group, send email to sympy@googlegroups.com. > > Visit this group at http://groups.google.com/group/sympy. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
