Status of Migrating Issues to Github?
Hi, Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right? Thanks, Skipper
Hi, 18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it. Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840 The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long... -- Pauli Virtanen
On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it.
Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840
The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long...
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this. Trac Attachment (2/06/13): [Test data file]( http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_ha... ) Just a thought. Skipper
On Mon, Feb 18, 2013 at 1:28 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it.
Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840
The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long...
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Trac Attachment (2/06/13): [Test data file](http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_ha...)
That's what we did for the numpy trac->github migration. All the attachments from Trac still live there. An example: https://github.com/numpy/numpy/issues/2490 Ray
On Mon, Feb 18, 2013 at 1:53 PM, Thouis (Ray) Jones <thouis@gmail.com>wrote:
On Mon, Feb 18, 2013 at 1:28 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for
scipy
is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it.
Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840
The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long...
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Trac Attachment (2/06/13): [Test data file]( http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_ha... )
That's what we did for the numpy trac->github migration. All the attachments from Trac still live there.
An example: https://github.com/numpy/numpy/issues/2490
Hi Ray, This looks nice. Do the scripts for this migration live somewhere? Could you give an estimate (developer time-wise) how much work it was? Skipper
On Tue, Feb 19, 2013 at 7:01 AM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:53 PM, Thouis (Ray) Jones <thouis@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:28 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it.
Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840
The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long...
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Trac Attachment (2/06/13): [Test data file](http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_ha...)
That's what we did for the numpy trac->github migration. All the attachments from Trac still live there.
An example: https://github.com/numpy/numpy/issues/2490
Hi Ray,
This looks nice. Do the scripts for this migration live somewhere? Could you give an estimate (developer time-wise) how much work it was?
Parking this link here. https://github.com/roskakori/tratihubis Skipper
https://github.com/thouis/numpy-trac-migration Testing was key. I used my own repo for that, and did maybe 20 test imports before the real one (and still made a few mistakes). Tratihubis looks more polished. Ray On Tue, Feb 19, 2013 at 7:01 AM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:53 PM, Thouis (Ray) Jones <thouis@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:28 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
18.02.2013 20:02, Skipper Seabold kirjoitti:
Just curious what the status of migrating the issues to github for scipy is? I think this was on the table right?
It's on the table, but AFAIK nobody is actively working on it.
Though, I'm still kind of wondering a bit how I'd do bugreports such as this: http://projects.scipy.org/scipy/ticket/1840
The data file is an integral part of the report, and cannot easily be factored out. If I put it in Dropbox or some random place like that, it won't stay there necessarily for long...
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Trac Attachment (2/06/13): [Test data file](http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_ha...)
That's what we did for the numpy trac->github migration. All the attachments from Trac still live there.
An example: https://github.com/numpy/numpy/issues/2490
Hi Ray,
This looks nice. Do the scripts for this migration live somewhere? Could you give an estimate (developer time-wise) how much work it was?
Skipper
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
Hi, Frustrated with Trac again. Would like to do something about it. Is there anyway for me to download the trac database without access to the server that hosts it? If not, could I get (read-only) access or help to get this sorted by some other means? Thanks, Skipper
On Wed, Apr 17, 2013 at 1:15 AM, Skipper Seabold <jsseabold@gmail.com> wrote:
Hi,
Frustrated with Trac again. Would like to do something about it. Is there anyway for me to download the trac database without access to the server that hosts it? If not, could I get (read-only) access or help to get this sorted by some other means?
We can get you whatever you need. I'll contact you off-list. -- Robert Kern
18.02.2013 20:28, Skipper Seabold kirjoitti: [clip]
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Yes, we can deal with it in migration, but the point is that that won't work for new bug reports... -- Pauli Virtanen
On Mon, Feb 18, 2013 at 3:25 PM, Pauli Virtanen <pav@iki.fi> wrote:
18.02.2013 20:28, Skipper Seabold kirjoitti: [clip]
It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
Yes, we can deal with it in migration, but the point is that that won't work for new bug reports...
Ah. "do" meant report not fix. Well, the short answer I guess is that you can't. You could, however, always attach files to the mailing list, or you can just copy-paste that code into the actual issue, which is a bit easier on github IMO. It changes the reporting workflow a bit, but I don't think it's a deal breaker. I think the positives outweigh the negatives here. The reason I bring this up is that I find Trac to be a disincentive to report things, file enhancement issues, etc. now that almost all projects I work with regularly are on github. I doubt I'm the only one, but maybe I am. Skipper
participants (6)
-
Fernando Perez -
Matthew Brett -
Pauli Virtanen -
Robert Kern -
Skipper Seabold -
Thouis (Ray) Jones