On 18 June 2012 17:57, Roger Teague <[email protected]> wrote: > Probably a bit off topic but one of the benefits I am seeing from connect is > helping to keep ARM development teams in-step with Linaro WGs and also it's a > good platform for ARM to share our latest thinking and where we are going > with topics such as V8a and big.LITTLE. However Connect morphs I'm keen to > have a route where I can keep this contact growing. I also think it's a > unique place where we can demonstrate to members how Linaro is ideally > positioned to exploit the unique interaction with ARM SW eng' and Linaro. > E.g., join Linaro and you get to participate in key meetings with BOTH Linaro > and ARM experts available and it's a perfect way to bootstrap your dev. > Projects. Happy to keep these closed to members only of $$$ to attend. ???
I agree with Roger. For instance, the Android team was able to have high bandwidth discussions and create and plan 3 cards as well as kick off the work of those cards at Connect: http://cards.linaro.org/browse/CARD-137 - Integrate ARMs browser benchmarks into LAVA http://cards.linaro.org/browse/CARD-136 - Integrate ARM's system benchmarks into LAVA http://cards.linaro.org/browse/CARD-136 - Linaro Android as a Benchmarking Platform > > -----Original Message----- > From: Jesse Barker [mailto:[email protected]] > Sent: 18 June 2012 22:53 > To: Joey STANFORD > Cc: Deepak Saxena; Christian Robottom Reis; Paul Larson; Ricardo Salveti; > Loïc Minier; Mounir Bsaibes; Ilias Biris; TSC Operational Subcommittee; > Linaro Tech Leads; Proj Mgmt Mailing List > Subject: Re: 2012q3 Linaro Connect (was: Re: What 2012Q3 means, was Re: > Explicit resourcing for cards, was Re: Proposal to improve the roadmap > process - PLANNED state) > > On Thu, Jun 14, 2012 at 12:27 PM, Joey STANFORD <[email protected]> wrote: >> Hi, >> >> >>> I'd like to expand on this and bring up that I think Connect needs to move >>> away from planning based on individual teams to cross-organizational >>> tracks. I think this will alleviate of the scheduling pressure we had this >>> time >>> and create a more cohesive experience for everyone involved. So instead >>> of having a bunch of random sessions in one day, we could have 3 tracks per >>> day (ex: Android Upstreaming, Neon Optimizations, KVM) and we can have >>> sessions from any groups that are relevant to that topic. This would mean >>> that on certain days some groups may not have a session scheduled but >>> I think that's OK. >> >> Interesting idea. >> >> Doing this has some advantages: >> >> * You don't need summit's "maximize attendee session time" algorithm >> and could get by fine without it. >> >> * Topic based tracks pulls the entire organization together to work >> on epic projects, which I suspect is the way we want to move to. It >> points us towards organization goals vs individual and team goals. >> >> * Since you're working on topics, the ability to callout what those >> sessions are should become much easier and can be done much earlier. >> This would also eliminate the need for the Sunday night "let's huddle >> and fix the schedule" activity. Even if we kept it, I suspect it would >> go dramatically quicker. >> >> * We'd see a reduction in meeting rooms but an increase in >> fishbowl/circular ballroom size rooms. Hangouts would be easier since >> there would be less machines to care for each hour but we would have >> need for additional microphones. >> >> >> There is one big challenge I can see... >> >> * Big rooms, lots of people, lots of interruptions. 50 minutes might >> not be enough so perhaps we'd need to double the session time. This >> would mean two large sessions per track per day (since we only do this >> in the morning) for a total of 6 big sessions a day. I often have >> felt that a 50 minute session time is too short for productive work >> anyway. Basically we could run each session like a 2 hour >> mini-summit. Each session would likely need to have several topics >> but that's par for course a lot of the time now. >> >> >> I can accommodate networking, scheduler, and AV for this without a >> problem. It /might/ be difficult finding a place with larger style >> rooms though. It's challenging to reconfigure the plenary style room >> to something that work for this format. > > Isn't this basically how Linux Plumbers is run (with half-day > microconferences), and don't we have some experts from the LPC > planning committee available to us to find out how they do it > (assuming this is actually what we want to do)? > > cheers, > Jesse > >> >> Joey > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
