Re: [matplotlib-devel] git migration this weekend

[Eric F. <ef...@ha...>]

On 02/26/2011 01:44 PM, Fernando Perez wrote:
> On Sat, Feb 26, 2011 at 3:24 PM, Darren Dale<dsd...@gm...>  wrote:
>>
>> I agree that the github interface is not great. The github devs seem
>> to know that everybody complains about it.
>
> Yup.  I hold on to the hope that, because it's so egregiously,
> painfully broken and braindead and it stands out so badly in
> comparison to the rest of github (which is brilliant), that it won't
> be too long before this improves. Granted, we can't know what's on
> their internal todo list, but those guys are obviously good and listen
> to feedback (from what I've seen elsewhere on the site), and their bug
> tracker has become something of a laughing stock, so I can only
> imagine that they're actually working on it.
>
> In the meantime, Min recently pointed out this interesting alternative:
>
> http://githubissues.heroku.com/#darrendale/mpl-issues

It is impressive, and improves some aspects, but I don't see that it 
makes the github tracker usable for new tickets.  I don't see any 
facility for attaching a file--is this correct?  We really want users 
with problems and suggestions to attach minimal example files, patches, 
whatever--as downloadable files, not pasted into the comment box.

My inclination would be to keep using the SF tracker exclusively until 
the github tracker improves substantially, and then switch.

Eric

>
> You can point it to any repository you want, and it makes interacting
> with the issue list far, far saner than via github itself.
>
> We're using now that interface ourselves for IPython:
>
> http://githubissues.heroku.com/#ipython/ipython
>
> and I have to say that I like it quite a bit.  For those on OSX, this
> can even be installed to run locally, with the feel of a native app
> (it's still a webkit app, but it launches like a local app).
>
> Something to keep in mind as you make the decision...
>
> In the end, in IPython we decided to move to github in order to
> benefit from the close integration between pull requests, bugs and
> commits.  Pull requests automatically create an issue, one can close
> bugs automatically from the commit message, etc.  I figured these
> things would be nice to have for an everyday workflow, and that
> eventually github itself would improve its native bug system.
>
> Cheers,
>
> f
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search&  Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel