linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00481
Re: Discussion of WI/BP process and kernel development @ LC'Q4
On Tue, 20 Sep 2011 19:29:23 -0700, Deepak Saxena <dsaxena@xxxxxxxxxx> wrote:
> too many cooks....
>
> I think it is important to have an open discussion with as many engineers
> across different WGs present, but I think there needs to be a smaller
> group of people driving the decisions on how we move forward.
Just to note that as a principle I think we should default to working in
an open and transparent manner, both for code, and for discussions like
this. I also think that the goals you give here are compatible with
having an open session for those that wish to come and give their input.
> From
> what I can tell, we have two problems we're trying to solve when
> it comes to tracking work:
Yes, I agree that this is an important distinction.
> 1. Managing the work we are doing, planning, understanding team load, etc
>
> 2. Providing a marketing tool to show value to our members.
>
> I think (1) is a conversation of interest to engineers and I think BPs/WIs
> are a good tool if used gently.
>
> I think engineers really don't care about (2) as they just want to do
> interesting work and I think connecting the BPs/WIs to status.linaro.org,
> which is in my opinion primarily a marketing tool, is not something
> that works. We need to find a different way to track progress in
> a way that is presentable to the TSC and I don't know that we
> need everyone's involvement in that conversation.
Have you looked at the discussions around the proposed changes to
status.linaro.org for the roadmap work? As I understand it one of the
main goals of the roadmap is to aid us in this communication, and the
changes that are proposed are in line with that, showing the state of
linaro in terms of which roadmap cards are planned, which are in
progress, and which are complete.
There will be some form of that mockup implemented and public prior to
Connect, and so attempting to limit the discussion would seem to be
counter-productive.
Those discussions have just taken place on techleads@ so far, but I now
realise that was likely an oversight on my part, and I see no problem
with further discussion around that happening at an open session at
Connect.
Just avoid putting an interesting title on the session and you won't be
overrun by engineers :-)
Thanks,
James
References