[SciPy-Dev] Status of Migrating Issues to Github?

Skipper Seabold jsseabold@gmail....
Mon Feb 18 14:49:17 CST 2013

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/scipy-dev/attachments/20130218/8760ed15/attachment.html 

More information about the SciPy-Dev mailing list