20140728

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2014-07-28 16:25:34 →
Size: 2028
Editor: jdstrand
Comment:
← Revision 2 as of 2014-07-28 16:57:25 → ⇥
Size: 2266
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
   * patch piloting
Line 36: Line 37:
    * once abstract socket patches are ready, integrate into Ubuntu     * incorporate abstract socket patches into Ubuntu
Line 39: Line 40:
    * abstract sockets
  * sarnold		     * abstract sockets: userspace and kernel
  * sarnold (gave update outside of meeting)
Line 44: Line 45:
    * webrtc-audio-processing MIR; if there's any spare     * webrtc-audio-processing MIR
Line 47: Line 48:
   * Triage/fix Bug:1348333 (Firefox 32 fails to build on 14.04 x86)
   * Fix Bug:1347924 (deadlock in oxide 1.1 after invoking some (unrelated) c++/qt functions)
   * chromium-browser sponsoring

Meeting (DRAFT)

Attendance

  • jdstrand
  • mdeslaur
  • sbeattie
  • tyhicks
  • jjohansen
  • chrisccoulson

Not present

  • sarnold

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • weekly role: happy place

      • AppArmor testing

      • performance reviews
      • pending updates
    • mdeslaur
      • weekly role: triage
      • pending updates
      • patch piloting
    • sbeattie

      • AppArmor

        • testing and anything else in support of abstract socket landing
    • tyhicks

      • AppArmor

        • incorporate abstract socket patches into Ubuntu
    • jjohansen

      • AppArmor

        • abstract sockets: userspace and kernel
    • sarnold (gave update outside of meeting)
      • weekly role: community
      • MIRs
        • trust-store
        • webrtc-audio-processing MIR

      • AppArmor patch reviews

    • chrisccoulson

      • Triage/fix 1348333 (Firefox 32 fails to build on 14.04 x86)

      • Fix 1347924 (deadlock in oxide 1.1 after invoking some (unrelated) c++/qt functions)

      • chromium-browser sponsoring
  • Highlighted packages

    The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. The highlighted packages for this week are:

    The Ubuntu Security team suggests that contributors look into merging Debian security updates in community-supported packages. If you would like to help Ubuntu but are not sure where to start, this is a great way to do so. See the available merges and SecurityTeam/UpdateProcedures for details on preparing Ubuntu security updates. If you have any questions, feel free to ask in #ubuntu-hardened. To find out other ways of helping out, please see SecurityTeam/GettingInvolved.

  • Miscellaneous and Questions

Log

Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-07-28-16.30.html

MeetingLogs/Security/20140728 (last edited 2014-07-28 16:58:57 by jdstrand)