Difference between revisions of "Android mainlining interest group meeting 2012"

From eLinux.org
Jump to: navigation, search
(Agenda)
(Agenda)
Line 43: Line 43:
 
** Other goals (maybe desire to ease Linaro integration?)
 
** Other goals (maybe desire to ease Linaro integration?)
 
* Review of 3.3 staging area: drivers/staging/android
 
* Review of 3.3 staging area: drivers/staging/android
* Review of specific patches
+
* Review of specific patches/features
 
** Tim Bird - status of logger
 
** Tim Bird - status of logger
 
** Hiroshi Doyu - status of Ion
 
** Hiroshi Doyu - status of Ion
Line 56: Line 56:
 
** wiki page, mailing list, blueprint, what else?
 
** wiki page, mailing list, blueprint, what else?
 
** how can volunteers get involved?
 
** how can volunteers get involved?
** framework/guidelines for involving (or not involving) Google
+
** framework/guidelines for involving (and not involving) Google
*** avoiding regressions for staging code
+
*** avoiding regressions for staging code (minimizing churn for working code)
 
* Plans going forward
 
* Plans going forward
 
** Collab summit logger meeting?
 
** Collab summit logger meeting?
 
** Other upcoming events (ELC, ELC Europe, future Connect events)
 
** Other upcoming events (ELC, ELC Europe, future Connect events)

Revision as of 18:52, 7 February 2012

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)
  • Colin Cross (probably)
  • maybe some other Google developers (depending on topics discussed, according to Brian Swetland)
  • 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...
  • 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)