Re: Mailinglists, was: Re: Bugtracker Status

[Koen Kooi <k.kooi@student.utwente.nl>]

On 05-02-09 15:06, Koen Kooi wrote:
> On 23-01-09 12:06, Koen Kooi wrote:
>> On 23-01-09 11:30, Valentin Longchamp wrote:
>>> Otavio Salvador wrote:
>>>> I propose to change the workflow a bit (and reuse few points you've
>>>> proposed):
>>>>
>>>> 1. stop using bugtracker to handle patches
>>>> 2. use mailing list to handle patches (comments bellow)
>>>> 3. drop autobuilder bug reporting (comments bellow)
>>>>
>>>> Besides, I have no objection about your points 2.2 and 2.3 but I'm too
>>>> new in the OE environment to comment about them so let me comment
>>>> about my points:
>>>>
>>>> 1 and 2:
>>>>
>>>> We're trying to get more people to review the changes to be done in
>>>> OE dev tree and bugzilla UI is horrible and difficult to use (at
>>>> least for me). Most people ends up redoing someone else patch since
>>>> we don't watch carefully the bugtrack.
>>>>
>>>> I propose we move to mailing list reviewing process mostly like Linux
>>>> kernel does. We can use PatchWork
>>>> (http://ozlabs.org/~jk/projects/patchwork/)
>>>> tool to make our life easier. I see some pros for that:
>>>>
>>>> . people will get more review into the patches
>>>> . people will be aware of ongoing work and what is being prepared to
>>>> be merged
>>>> . less forgotten patches
>>>> . less duplicated work
>>>>
>>>> I also see a single con for that:
>>>>
>>>> . more mailing list traffic
>>>>
>>>
>>> Even if I am not very much involved in the OE development, I completely
>>> agree with Otavio. The few patches that I have proposed are often stuck
>>> on the bugzilla. Maybe it would be better with a mailing-list.
>>>
>>> Furthermore, now that we use git, we have plenty of tools to send
>>> patches to a mailing-list (format-patch, send-email and am).
>>>
>>> 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.
>
> 15:01 < _boto> i have posted into issue ml
> 15:02 < _boto> i wondered that the rest of mails were created by bugzilla
>
> No objections, only support for my proposal, so can this get implemented
> now?

Still no objections and still no action. Can I shut down the unneeded 
lists myself now?

regards,

Koen