[oe] Mailinglists, was: Re: Bugtracker Status

[Chris Larson]

On Fri, Jan 23, 2009 at 5:00 AM, Petr Stetiar <ynezz at true.cz> wrote:
> Koen Kooi <k.kooi at student.utwente.nl> [2009-01-23 12:06:54]:
>
>> On 23-01-09 11:30, Valentin Longchamp wrote:
>> >I would definitely support a patch review style like on the linux kernel
>> >mailing-lists even if this implies a high-traffic list (with simple
>> >filter rules in your mail client, it's easy to handle). However, I don't
>> >think it would be a good idea to have two lists.
>>
>> I'd go even further by saying we should reorganize the mailinglists into
>> this:
>>
>> * oe mailinglist for humans
>> * combined commit + autobuild log list for non-humans
>>
>> That should reduce confusion which list to use (oe-user, oe-devel, etc)
>> for sending mails and more people get to see patches flying by. Even if
>> you don't review them having more code snippets on the list is usefull
>> for newcomers.
>
> That would be awesome.

I don't know if you guys are aware, but the pybugz project has a
commandline tool that interfaces with bugzilla.  It actually works
really well from the little time I've spent with it so far.  It'd be
much, much nicer than the web interface for people's workflows, and
then we wouldn't lose the advantages of a bts.

See http://www.liquidx.net/pybugz/ - the example workflow section, specifically.
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.