Hi Mounir,
Looking at the TRs...
K2.1-K2.4: Yes, should combine sessions. One session for K2.1, K2.3 & K2.4 (linaro-kernel-o-devicetree). A second session for K2.2 (linaro-kernel-o-devicetree-howto)
K3.2, K3.5, K3.6: discuss in linaro-kernel-o-bootarchitecture session K3.1: (as already indicated) linaro-kernel-o-uefi session K3.3: Not planning to schedule a session; this is a low priority. But if someone else wants to take it on then I support it K3.4: No session planned, the scope of this task is known and it will probably show up as a task in a blueprint for 11.11
K5.3: Should be discussed as part of linaro-kernel-o-uefi session?
g.
On Mon, Apr 25, 2011 at 2:24 PM, Mounir Bsaibes mounir.bsaibes@linaro.org wrote:
I have created the UDS-session blueprints (blueprints to schedule the UDS sessions) as discussed in the meeting this morning. Take a look at the sessions specially the ownership and make sure you agree, you will have to run the session at UDS if you are the assignee (owner).
As it turned out, each major Technical Requirement will have one session, with the exception of k1 where k1.1 (fix arm/linus interface) will have 5 daily sessions. So, most of the sessions cover multiple topics, you may need have to co-ordinate with others to run your session.
https://wiki.linaro.org/WorkingGroups/Kernel/Cycle11.11SessionsSetup
Paul, you need to approve all these blueprints in order to start scheduling them.
Grant, You have registered sessions for boot architecture and DT, please send me the blueprints links so I can add them to this table.
Regards, Mounir
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel