Welcome to the "Ubuntu-kernel-sru" mailing list

[Tim Gardner]

On 03/03/2011 08:39 AM, Brad Figg wrote:
> On 03/03/2011 07:28 AM, Tim Gardner wrote:
>> On 03/02/2011 09:49 AM, ubuntu-kernel-sru-request at lists.ubuntu.com wrote:
>>> Adding you to the kernel SRU mailing list.
>>>
>>> Welcome to the Ubuntu-kernel-sru at lists.ubuntu.com mailing list!
>>>
>>
>> Somehow this doesn't feel like the right thing to do. Why aren't we
>> using LP and subscribing teams to a public SRU project? If the purpose
>> of this list is for intra-team communication, then LP seems like a more
>> general and scalable solution. Furthermore, state transitions of the
>> tracking bugs attached to this project would automatically get forwarded
>> onto the project mailing list, informing all who are team members of the
>> next step in the process.
>>
>> We encourage our OEM and vendor brethren to use this model. Why aren't
>> we eating our own dogfood?
>>
>> rtg
>
> I guess I don't understand what your usage model for LP is. We have a
> release tracking bug for every release. That tracking bug is used by
> various parties to indicate the progress of the release.
>
> As you are aware we are looking at other ways to use LP and the tracking
> bugs to facilitate better transitioning and tracking of workflow.
>
> However, there may be other issues / discussions that pop up and are
> mostly relevant to just a select group of folks. Yes we could certainly
> use one of the existing mailing lists for that. We felt that we would
> disappear into the noise and it wouldn't be an effective means of
> communicating. And our goal here is better communication. We certainly
> are not trying to hide what we are doing.
>
> Am I missing your point?
>
> Brad

There are a number of advantages to using projects, the use of which 
does not preclude also having a mailing list associated with the project.

For example, the minutiae emails that Steve has been composing by hand 
announcing state changes of the various tracking bugs would be generated 
automatically whenever a comment is added to the bug or the status is 
updated. These emails have the further advantage  of having the URL to 
the bug report embedded in the email.

A project can be searched in order to list all of the bugs related to 
the project, making it much easier to find tracking bugs.

Membership of the teams is self managed as opposed to you and Steve 
having to manage subscriptions and moderate the list.

I'm sure there are some other good reasons. We can pursue this in person 
next week at Millbank.

rtg
-- 
Tim Gardner tim.gardner at canonical.com