[Numpy-discussion] Migrating issues to GitHub
Thu Feb 16 12:25:36 CST 2012
On Wed, Feb 15, 2012 at 12:11 PM, Thouis (Ray) Jones <email@example.com>wrote:
> On Sat, Feb 11, 2012 at 21:54, Fernando Perez <firstname.lastname@example.org>
> > On Sat, Feb 11, 2012 at 12:36 PM, Pauli Virtanen <email@example.com> wrote:
> >> The lack of attachments is the main problem with this transition. It's
> >> not so seldom that numerical input data or scripts demonstrating an
> >> issue come useful. This is probably less of an issue for Numpy than for
> >> Scipy, though.
> > We've taken to using gist for scripts/data and free image hosting
> > sites for screenshots, using
> > <img src="http://.... /img>
> CellProfiler recently transitioned to Github issues from an internal
> Jira server.
In another thread Jira was proposed as an alternative to Trac. Can you
point out some of its strengths and weaknesses, and tell us why you decided
to move away from it?
> Since most of our bug reports require some sort of
> attachment to be useful, we put up a page at cellprofiler.org/issues
> that uses Github's authentication API to file bugs with attachments.
> The bug report itself gets added to the github issues, the attachment
> gets stored on our server, and links to the latter appear in the
> bug page: http://cellprofiler.org/issues/
> example issue: https://github.com/CellProfiler/CellProfiler/issues/260
> It was pretty simple to put together (a few hours by one developer).
> The need for a github account keeps it from being spammed. If that's
> too much of a bar, I expect it could have a branch-cut in behavior:
> witha github account, the report goes straight into the Github
> issues, otherwise, it gets queued for review and mail sent to some
> (hopefully low-traffic) list.
> Ray Jones
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion