Registered by Jorge Castro

Orlando, Fl, USA

09:00 EDT on Monday, 2010-10-25
17:00 EDT on Friday, 2010-10-29

Meeting drivers

Each meeting has a person, or team, responsible for deciding which items are accepted for the agenda. This team is called the "meeting driver" and for UDS N they are:

You should contact the meeting driver if you have any additional questions about the structure or agenda of the meeting.


Latest 5 additions to the meeting agenda

Continued outreach to interested developers.
Revisit this discussion for Natty, is the desired implementation for Natty? _____ We've split this into 2 blueprints. 1. Implementation planning (this blueprint) 2. Process and Policy - now here: ______________...
Discussion around the requirements of an Android build system, and where there is possible overlap with our existing systems.
Discussion of LTTng reveals that on ARM, LTTng and perf make conflicting use of the cycle counter, each trying to work around hardware bugs. How do we fix this? Are there any other points where coordination/consolidation is needed?
Some testsuites use the network, big files, and other resources, which might not be available on a buildd. Specify a way how a buildd announces available test resouces, so that as many tests as possible can be run, depending on the resources available in the build environment.

There are a total of 359 specifications on the meeting agenda. There are 8 specifications proposed which the organisers will review. You can view the full current agenda here.