On Tue, Sep 17, 2013 at 8:29 PM, Aaron Meurer <[email protected]> wrote: > The Google Code tracker should be preferred, for now. > > I had opened the GitHub issue tracker as an experiment, to see if it > attracted more issue reports. I had been debating whether to move our > issues to the GitHub tracker. Unfortunately, I haven't had the time to > play around with the migration tools I found, so it stalled. > > There are advantages to each tracker. I suppose since the cat is out > of the bag so to speak, it would be nice to get some community input > on this. I can enumerate what I think are the advantages/disadvantages > of each if you would like. > > Also, if anyone wants to play with a migration script, just create an > empty repo on GitHub and try migrating the issues to there. I can > point out the scripts that I found so far if anyone wants to give it a > go. It's honestly not much more than you would find from the first few > pages of a Google search, though.
I would move to github --- if nothing, unlike Google they provide a nice API, so that we can download them and move them to some other service. Ondrej -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
