Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Android mainlining interest group meeting 2012

From eLinux.org
Revision as of 17:08, 9 February 2012 by Jstultz (Talk | contribs)

Jump to: navigation, search

This page has information about the Android mainlining interest group meeting, planned for early 2012.

Details

The meeting will be held:

  • during Linaro Connect
  • Time: 9:30 am to 12:00 pm
  • Date: February 10, 2012
  • Location: Bordeuax 3 room at the Sofitel, Hotel
  • City: Redwood Shores, California

See http://summit.linaro.org/lcq1-12/2012-02-10/ (I think you might need a Launchpad account to see this schedule)

RSVP

This meeting requires an invitation to attend, for logistical reasons. If you are interested and enthusiastic, unless we are overbooked it is likely you will get an invitation.

If you are interested in attending, please e-mail Tim Bird at: < tim (dot) bird (at) am.sony.com > and let him know.

Expected Attendees

  • Tim Bird
  • Horishi Doyu
  • Deepak Saxena
  • Dima Zavin (probably)
  • John Stultz
  • Paul McKenney (until 11:00)
  • Hisao Munakata
  • Magnus Damm - call-in (from Japan) to report on PM issues
  • Bjorn Andersson
  • Shuah Khan
  • Zach Pfeffer
  • Jason Parker

Agenda

  • Project goals
    • Ability to run AOSP on vanilla mainline kernel (not necessarily optimized)
      • Reality check - is this a valid or useful goal?
    • Other goals (maybe desire to ease Linaro integration?)
  • Review of 3.3 staging area: drivers/staging/android
  • Review of specific patches/features
    • Tim Bird - status of logger
    • Hiroshi Doyu - status of Ion
    • Magnus Damm - status of runtime PM (/wakelocks?)
    • John Stultz - ashmem & alarm-timers
    • Anton Vorontsov (Presented by JohnS): Low-memory-killer / memory notifications
  • What should NOT be upstream?
    • Board support
    • patches that have no hope
    • things the community would mangle...
  • Any expected future divergences?
  • Project management
    • wiki page, mailing list, blueprint, what else?
    • how can volunteers get involved?
    • framework/guidelines for involving (and not involving) Google
      • avoiding regressions for staging code (minimizing churn for working code)
  • Plans going forward
    • Collab summit logger meeting?
    • Other upcoming events (ELC, ELC Europe, future Connect events)