[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Thoughts from a former KDE, currently Mozilla developer
From:       Gary Greene <greeneg () tolharadys ! net>
Date:       2010-12-09 3:27:48
Message-ID: 07F782FA-8D42-4761-BAAF-F1299A15F232 () tolharadys ! net
[Download RAW message or body]


On 8 Dec 2010, at 8:55 AM, Thiago Macieira wrote:

> Em Terça-feira, 7 de Dezembro de 2010, às 11:22:47, Benoit Jacob escreveu:
> > *****
> > 1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
> > 
> > KDE uses a Mailing list for most its development discussion, and only
> > uses trackers (bugzilla, reviewboard) for specific tasks (user bug
> > reports, patch review).
> > 
> > Mozilla uses a (modern, well-configured) bugzilla for almost
> > everything including 90% of development discussion.
> > 
> > My point here is not to advertise bugzilla specifically (though I love
> > it), but issue trackers in general.
> > 
> > An issue tracker, contrary to a mailing list, allows to efficiently
> > keep track of what TODO items remain to be done, how they must be
> > prioritized, etc. It also is much more convenient for core
> > contributors because it allows them to handle issues later, so they
> > can reclaim control of how they spend their time, instead of having to
> > constantly handle the flow of emails.
> 
> Hi Benoît
> 
> Thanks for your suggestions. A couple of comments from me:
> 
> The issue tracker and the mailing lists are not mutually exclusive things. The 
> issue tracker is a very good tool for, well, tracking issues -- bug reports, 
> suggestions, even feature planning, requirements, unrelated tasks, etc. In 
> some projects, it's also used for controlling the integration system (like 
> WebKit). This I support and I think KDE should use more often.
> 
> One feature missing in Bugzilla is proper rich formatting, like a wiki.
> 
> The mailing list is where discussions happen and decisions are made.
> 
> Code reviews currently happen on mailing lists and that's how I prefer it. 
> Some projects, apparently like Mozilla, do it all on the issue tracker. WebKit 
> does it.
> 
> For Qt, what I'm trying to find is a system that integrates the review system 
> to the mailing list. Something like we have for kde-bugs-dist: two-way, with 
> enough information so people can filter incoming emails.
> 
> If I can't find such a system, I'll settle for a system with easy command-line 
> access and mailing list logging (one-way only).
> 

You might want to look at http://code.google.com/appengine/articles/rietveld.html as \
it does a fairly good job, and has a decent command line tool.

--

 
> > Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]