On 19 April 2012 10:53, Christian Robottom Reis kiko@linaro.org wrote:
On Wed, Apr 18, 2012 at 10:43:56AM -0500, Zach Pfeffer wrote:
While we're planning for connect, I'd like to suggest that we do away with team tracks all together and just have topic tracks. This would align with our topic based approach to things now, and would be a way to breakdown our silo's. The topic track would be lead by a topic champion. What do people think?
I ask myself whether in practice it makes a difference. In practice, at Connect, you want somebody to own a certain set of sessions. Splitting this by team or by topic seems to have equal drawbacks on either side.
However, now that I look at this list I wonder why you didn't suggest additional topics for the listing for the Connect website in the thread I started -- I see at least a few which might have been appropriate:
Infrastructure Monitoring Continuous Integration Making Debug Easier Power Measurement A Unified Android/Ubuntu Distribution Community Engagement
Putting it into a separate document is scattering, not gathering ;-)
I just like working from a Google doc instead of email so I plugged everything in their. Figured others could just use it as a scratch pad. Is there another location that gives a complete list of all the topics from all the leads? Anyway, my experience with big.LITTLE showed me how awesome it is to have a great topic that each team sends engineers to and is lead by someone who may not be a tech lead at all, but is the domain expert. I figured if we had all the topics in a global view we could see what potential tiger teams could form and prioritize before we got to Hong Kong.
-- Christian Robottom Reis, Engineering VP Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 Linaro.org: Open Source Software for ARM SoCs