Hello,
An update for this task. I will run script 6th April to add
references for github issues on google code. See this:
https://github.com/sympy/sympy/issues/7235#issuecomment-38809765
and discussion below.
Unfortunately, a lot of email notifications will appear (for issue owner or
for
On Thu, Apr 3, 2014 at 5:07 AM, Sergey Kirpichev skirpic...@gmail.com wrote:
Hello,
An update for this task. I will run script 6th April to add
references for github issues on google code. See this:
https://github.com/sympy/sympy/issues/7235#issuecomment-38809765
and discussion below.
You can go to https://code.google.com/hosting/settings and disable emails
to yourself during this period (under the Issue Tracker section). If you
have starred a lot of issues or are CCd on a lot of issues I recommend
doing this.
Aaron Meurer
On Thu, Apr 3, 2014 at 6:07 AM, Sergey Kirpichev
On Thu, Apr 3, 2014 at 9:00 AM, Aaron Meurer asmeu...@gmail.com wrote:
You can go to https://code.google.com/hosting/settings and disable emails to
yourself during this period (under the Issue Tracker section). If you have
starred a lot of issues or are CCd on a lot of issues I recommend doing
Yes, applause! Thanks for doing this.
Jason
moorepants.info
+01 530-601-9791
On Thu, Mar 20, 2014 at 6:23 PM, Ondřej Čertík ondrej.cer...@gmail.comwrote:
I totally missed this, this is absolutely fantastic! Thanks a lot
Sergey and Aaron for all the work. That helps a lot.
Ondrej
On Fri,
On Fri, Mar 28, 2014 at 11:02:53AM -0400, Jason Moore wrote:
Yes, applause! Thanks for doing this.
Jason
This is not done yet. See this:
https://github.com/sympy/sympy/issues/7235
--
You received this message because you are subscribed to the Google Groups
sympy group.
To unsubscribe
I totally missed this, this is absolutely fantastic! Thanks a lot
Sergey and Aaron for all the work. That helps a lot.
Ondrej
On Fri, Mar 7, 2014 at 8:30 PM, Matthew Rocklin mrock...@gmail.com wrote:
This is fantastic.
On Fri, Mar 7, 2014 at 3:14 AM, Sergey Kirpichev skirpic...@gmail.com
Everything is on the github.
https://github.com/sympy/sympy/issues/7235
On Thursday, March 6, 2014 12:32:21 AM UTC+4, Aaron Meurer wrote:
This is done. It took some time because I was only able to update 200
issues at a time. I accidentally sent out an email on one of them, so
sorry about
Thanks a ton for doing all the work for this. This will be a huge boost to
the community.
Aaron Meurer
On Mar 7, 2014, at 5:14 AM, Sergey Kirpichev skirpic...@gmail.com wrote:
Everything is on the github.
https://github.com/sympy/sympy/issues/7235
On Thursday, March 6, 2014 12:32:21 AM UTC+4,
This is fantastic.
On Fri, Mar 7, 2014 at 3:14 AM, Sergey Kirpichev skirpic...@gmail.comwrote:
Everything is on the github.
https://github.com/sympy/sympy/issues/7235
On Thursday, March 6, 2014 12:32:21 AM UTC+4, Aaron Meurer wrote:
This is done. It took some time because I was only
On Tue, Mar 04, 2014 at 04:12:41PM -0500, Jason Moore wrote:
As far as I know it is [1]moorepa...@gmail.com on both accounts. I'm not
sure why mine is messed up.
For example on google code:
On Tue, Mar 04, 2014 at 02:20:32PM -0600, Aaron Meurer wrote:
My understanding was that it could be fixed after import if the user
adds that email to their account.
No. That's why there a fallback user.
But let's just canonicalize those
four users on their know GitHub emails.
Done for
Hi Sergey,
On Wed, Mar 5, 2014 at 2:54 AM, Sergey B Kirpichev skirpic...@gmail.com wrote:
On Tue, Mar 04, 2014 at 02:20:32PM -0600, Aaron Meurer wrote:
My understanding was that it could be fixed after import if the user
adds that email to their account.
No. That's why there a fallback
On Wed, Mar 05, 2014 at 09:20:52AM -0700, Ondřej Čertík wrote:
What remains to be done before we can do the migration?
Decide if we want to do import Live-labeled issues
to the sympylive repo.
If not, we can start import right now. Script
On Wed, Mar 5, 2014 at 10:02 AM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Wed, Mar 05, 2014 at 09:20:52AM -0700, Ondřej Čertík wrote:
What remains to be done before we can do the migration?
Decide if we want to do import Live-labeled issues
to the sympylive repo.
Either is fine with
Yes, let's get it done. Should I freeze the google code issues?
Aaron Meurer
Sent from my iPhone.
On Mar 5, 2014, at 11:11 AM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Wed, Mar 5, 2014 at 10:02 AM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Wed, Mar 05, 2014 at 09:20:52AM
On Wed, Mar 05, 2014 at 12:43:17PM -0600, Aaron S. Meurer wrote:
Yes, let's get it done. Should I freeze the google code issues?
Yes. Then I'll run export script and then
1) upload zip file with exported data and provide the link for you
2) ask support to import it to the test repo
This is done. It took some time because I was only able to update 200
issues at a time. I accidentally sent out an email on one of them, so
sorry about that.
Now only the owners of the Google Code repo can edit issues, which is
just me and Ondrej. If you want to take a shot at forward links on
Any feedback?
I don't have a good idea what to do next. Every mentioned
problem in the test repo was solved one way or another (see
labels Migration-Bugs and Migration-Bugs-Done).
We can do a new test (final?) import as before, in one repo,
or we can also split issues, labeled Live (~80) to a
When I looked at this I was generally impressed by it. I'm sure that we'll
run into lots of issues *after* we make the transition. Until then it
looks great!
On Tue, Mar 4, 2014 at 3:14 AM, Sergey Kirpichev skirpic...@gmail.comwrote:
Any feedback?
I don't have a good idea what to do next.
I agree. Unless there are known major issues, we should do the final
import. Let me know when you want me to freeze the Google Code issues.
Aaron Meurer
On Tue, Mar 4, 2014 at 9:37 AM, Matthew Rocklin mrock...@gmail.com wrote:
When I looked at this I was generally impressed by it. I'm sure
On Tue, Mar 04, 2014 at 10:59:40AM -0600, Aaron Meurer wrote:
I agree. Unless there are known major issues, we should do the final
import. Let me know when you want me to freeze the Google Code issues.
I think, it's important to fix contacts first. Wery unlikely
if we can do this after import.
My understanding was that it could be fixed after import if the user
adds that email to their account. But let's just canonicalize those
four users on their know GitHub emails.
Raoul, David, Jason, Sachin, can you tell us which emails you have on
your GitHub account and which one(s) you have on
As far as I know it is moorepa...@gmail.com on both accounts. I'm not sure
why mine is messed up.
For example on google code:
https://code.google.com/p/sympy/issues/detail?id=2781q=mechanicscolspec=ID%20Type%20Status%20Priority%20Milestone%20Reporter%20Summary%20Stars
Jason
moorepants.info
I just double-checked and I have a comment on issue 1867, but no issues
reported (or assigned).
https://code.google.com/p/sympy/issues/detail?id=1867
My e-mail address is the same on both Google Code and on GitHub
(tim.la...@gmail.com).
Cheers,
Tim.
On 2014-03-04, at 4:12 PM, Jason Moore
My email address is the same on Google Code and
Github: li.david...@gmail.com
David
On Tuesday, March 4, 2014 1:20:32 PM UTC-7, Aaron Meurer wrote:
My understanding was that it could be fixed after import if the user
adds that email to their account. But let's just canonicalize those
four
On Wed, Feb 19, 2014 at 06:14:10PM -0600, Aaron Meurer wrote:
Are they OK with creating a dummy user for this?
Yes, probably we can create a separate user for this.
It can be specified, as I think to any sympy's developer. Quote support:
---8---
By default, the fallback user will be the
On Tue, Feb 18, 2014 at 05:15:49PM -0600, Aaron Meurer wrote:
Who will be the default user for the sympy import?
It can be specified, as I think to any sympy's developer. Quote support:
---8---
By default, the fallback user will be the user on who's behalf we are
doing the import. However, we
Are they OK with creating a dummy user for this?
Aaron Meurer
On Wed, Feb 19, 2014 at 3:04 AM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Tue, Feb 18, 2014 at 05:15:49PM -0600, Aaron Meurer wrote:
Who will be the default user for the sympy import?
It can be specified, as I think to
On Tue, Feb 18, 2014 at 1:42 AM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Mon, Feb 17, 2014 at 06:40:22PM -0600, Aaron Meurer wrote:
Also a wrong username
That's expected. Everything that doesn't map to existing
GitHub's accounts - going to be created by default user
(the owner of
Hello,
On Sun, Feb 16, 2014 at 1:05 PM, Sergey Kirpichev skirpic...@gmail.comwrote:
[...]
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:
On Mon, Feb 17, 2014 at 12:32 PM, Sergey Kirpichev skirpic...@gmail.com wrote:
Hello,
On Sun, Feb 16, 2014 at 1:05 PM, Sergey Kirpichev skirpic...@gmail.comwrote:
[...]
Other tasks for volunteers (in random order):
1) Find problems in the test import (to be in:
On Mon, Feb 17, 2014 at 06:40:22PM -0600, Aaron Meurer wrote:
Also a wrong username
That's expected. Everything that doesn't map to existing
GitHub's accounts - going to be created by default user
(the owner of this repo in this import).
We should fix authors.json first, at least for the core
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
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
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
On Sun, Feb 16, 2014 at 11:17:18AM -0600, Aaron Meurer wrote:
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.
Yes, they
On Sun, Feb 16, 2014 at 11:48 AM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Sun, Feb 16, 2014 at 11:17:18AM -0600, Aaron Meurer wrote:
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
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.
Aaron Meurer
On Mon, Jan 13, 2014 at 3:34 PM, Alberto Donizetti
alb.donize...@gmail.com wrote:
Hi,
I just wanted to point out that the contributing section of
Hi,
I just wanted to point out that the contributing section of the User's
Guide doesn't say
anything about the issues tracking migration to *github*, so there are few
links, here:
http://docs.sympy.org/latest/guide.html#contributing
in the improving the code subsection, that point to the old
On Tue, Dec 17, 2013 at 12:27:49AM -0700, Aaron Meurer wrote:
I went ahead and did it in case it helps:
https://sourceforge.net/p/sympy-gcode-import/tickets/.
I've sent you some suggestions from the GitHub's support stuff. That may
be a better variant (we can preserve timestamps, users and so
This is awesome. To clarify, GitHub is offering to do a non-API
import, which means that it will happen instantly, and won't produce
notifications to everyone.
There are still some things we should try to get working (the first
two are not a huge priority if it doesn't because we can edit issues
On Tue, Dec 17, 2013 at 11:29 PM, Aaron Meurer asmeu...@gmail.com wrote:
This is awesome. To clarify, GitHub is offering to do a non-API
import, which means that it will happen instantly, and won't produce
notifications to everyone.
That's very nice of them.
There are still some things we
SourceForge just announced Google Code import, so if there are any
good SourceForge to GitHub issue migrators, it might make a good
intermediary.
http://sourceforge.net/p/forge/documentation/Google%20Code%20Importer/#issuestickets
Aaron Meurer
On Sun, Dec 15, 2013 at 5:56 AM, Sergey Kirpichev
I went ahead and did it in case it helps:
https://sourceforge.net/p/sympy-gcode-import/tickets/.
Aaron Meurer
On Mon, Dec 16, 2013 at 8:52 PM, Aaron Meurer asmeu...@gmail.com wrote:
SourceForge just announced Google Code import, so if there are any
good SourceForge to GitHub issue migrators,
FYI
For now, only 1921 issues are imported. I hit Github API rate-limit cutoff
5 times.
Some benchmarks:
1-433
real59m58.321s
user0m50.891s
sys0m3.572s
443-835 # first limit rate hit
real79m14.635s
user0m49.791s
sys0m3.776s
835-1214
real59m52.420s
user0m51.331s
On Fri, Dec 13, 2013 at 11:03:50AM -0700, Aaron Meurer wrote:
I think the issue was that it didn't support GitHub 2-factor
authentication.
I don't think that's an issue - we can use a special
GH account to do this job.
btw, now test import goes to
I already noticed some issues with various underscores and * and ** in
plain text being converted to markdown rendering. Can we maybe use
some tool to automatically escape these special characters. See for
instance https://github.com/asmeurer/GitHub-Issues-Test/issues/16.
On Sat, Dec 14, 2013 at
On Thu, Dec 12, 2013 at 3:27 PM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
On Thu, Dec 12, 2013 at 02:31:57PM -0700, Aaron Meurer wrote:
That was one that I tried that didn't work out of the box.
Why?
I think the issue was that it didn't support GitHub 2-factor
authentication. I didn't
On Thursday, December 12, 2013 7:57:02 AM UTC+4, Aaron Meurer wrote:
Does anyone know of any good tools to do this?
https://github.com/arthur-debert/google-code-issues-migrator
looks as the best.
Does anyone know of other projects that have done this that I
can get into contact with?
On Thu, Dec 12, 2013 at 5:01 AM, Sergey Kirpichev skirpic...@gmail.com wrote:
On Thursday, December 12, 2013 7:57:02 AM UTC+4, Aaron Meurer wrote:
Does anyone know of any good tools to do this?
https://github.com/arthur-debert/google-code-issues-migrator
looks as the best.
That was one
On Thu, Dec 12, 2013 at 02:31:57PM -0700, Aaron Meurer wrote:
That was one that I tried that didn't work out of the box.
Why?
How is it going? Do you hit the GitHub rate limit?
No.
What about the Google Code one?
As well. No.
Let me know how long it takes total.
But please take into
52 matches
Mail list logo
