Fate vs Bugzilla for feature tracking

Ralf Habacker ralf.habacker at freenet.de
Wed Jan 21 22:28:06 GMT 2009


Allen Winter schrieb:
> On Wednesday 21 January 2009 4:37:35 pm Ingo Klöcker wrote:
>   
>> On Wednesday 21 January 2009, Aaron J. Seigo wrote:
>>     
>>> hello =)
>>>
>>> after a few weeks of (patient :) consultation with the Suse team
>>> working on Fate, i just blogged about the possibility of using Fate
>>> for feature tracking in KDE. you can read about it here:
>>>
>>>       
>
>
>   
>> Another alternative would be using Fate as tool for developers only, 
>> i.e. only developers would be able to create feature requests on Fate. 
>> If a developer wants to discuss (and eventually implement) a feature 
>> posted on Bugzilla he could create a new entry on Fate and link it to 
>> the corresponding Bugzilla entry. This way the developers could take 
>> advantage of Fate without confusing the users by having two different 
>> spots for reporting bugs resp. for submitting feature requests.
>>
>>     
> I like the idea of a developer tool, separate from bko.
>
> A place were patches and code-snippets and ideas and brainstorming can be co-located.
> This would not be a place for users to wander in.
>
> Sorta like how we separate TechBase from UserBase.
>
> So many patches and ideas get lost -- developers come and go -- and we lose
> good info a lot of the time.  Or we discuss the same stuff over and over again.
>
>
>   
May be something like gforge - a free sourceforge clone - could help in 
this area - http://gforge.org/projects/gforge/
It contains a bug/feature/patch tracker 
http://gforge.org/tracker/?group_id=152. Tracker items could be switch 
from one type into another and could be connect to tasks.  Also a plugin 
system is available. A vmware based installation for a quick inspection 
of how it works could be found at 
http://www.spisser.it-a.googlepages.com/gforge.htm

Regards
 Ralf






Regards

Ralf






More information about the kde-core-devel mailing list