[SciPy-Dev] Trac performance?

Denis Laxalde denis.laxalde@mcgill...
Mon Feb 6 08:20:32 CST 2012


Ralf Gommers wrote:
> > I think moving stuff out from the Trac could be useful in any case,
> > as its account management is not so transparent. As for the
> > developer wiki info --- how about turning on wikis on Github and
> > using them? Does someone have experience on how usable they
> > actually are? 
> 
> Haven't got experience, but see that they were just revamped two
> weeks ago: https://github.com/blog/774-git-powered-wikis-improved.
> They still look quite simplistic, but we don't need much.

I also think a github wiki is sufficient. It's quite easy to work with
and the fact that the content is stored in git is definitely a plus IMO.
Otherwise, there is also the current scipy.org wiki (MoinMoin) but I
guess there's a good reason for not using it?

> > As for dropping Trac completely -- last time around, I think the
> > Github issues system lacked features. I think they've added some
> > stuff since then, though.
> >  
> 
> If the database locked errors can be solved, I think Trac is still
> better than Github.

And you probably also keep a higher control on data since github issues
are not stored in git but in a database (though there's an API to access
it).

-- 
Denis


More information about the SciPy-Dev mailing list