Re: [Python-markdown-discuss] Re-organization of tracker.

[Herbert P. <her...@gm...>]

i've moved away from sourceforge a long time ago (for bug tracking)
because it was (and obviously is) extremely slow.. first i've used my
own implementation of a bug tracker.. but since i actually wanted to
track bugs, and not fix the bugtracker.. i eventually moved to google
code hosting .. the issue tracker is very minimalistic but still
powerful enough - http://code.google.com/p/sct-project/issues/list
(the only thing which is annoying to me is that users who are not part
of the project can't add 'Labels' and since everything is done by
labels (including the categories feature request, bug report, etc.) i
basically have to edit all incoming bug reports to add the correct
labels.. but it is very fast and all labels can be customized by the
project admin ..)

On 10/30/07, Waylan Limberg <wa...@gm...> wrote:
> On 10/30/07, Yuri Takhteyev <yu...@cs...> wrote:
> > > The limitations of this site are rather annoying. It doesn't help that
> > > it's painfully slow.
> >
> > Should we move?
>
> That would be fine by me.
>
> > I am not exactly a big fan of sourceforge myself and
> > would have moved earlier, if I had the opportunity to research the
> > alternatives.
>
> If I have some time, I'll do some research myself. If anyone else out
> there has some input, please do speak up.
>
>
>
> --
> ----
> Waylan Limberg
> wa...@gm...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>