[Kolab-devel] Kolab issue tracker situation

[Jeroen van Meeuwen (Kolab Systems)]

On 2011-11-09 12:43, Thomas Koch wrote:
> Hi,
>
> I've started to learn kolab this week for my bachelor thesis work 
> about
> calendaring standards vs. REST. I found a couple of minor issues here 
> and
> there and wanted to fill issues in the issue tracker (and also help 
> out
> fixing).
>
> Now the issue tracker itself seems to be a major issue. Many more 
> then 1000
> unresolved issues means that the issue tracker isn't used as it 
> should or
> isn't usable. And a project without an issue tracker is a nightmare.
>
> What do you think about the situation? What's the status? Can I help
> out? I've administrator experience with Mantis and Flyspray so far 
> and evaluated a few
> other systems. I know there's no such thing (yet) as a great free 
> issue
> tracker.
>
> Others that might be worth a lock, all of them distributed 
> commandline tools:
> http://search.cpan.org/dist/App-SD/
> https://github.com/andychilton/cil
> http://bugseverywhere.org
> or Debian's bug tracking software debbugs
>

We have https://bugzilla.kolabsys.com in use today, closing down 
Roundup at issues.kolab.org is pending the definitive list of things to 
do and a timeline to go along with it.

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08