20140113

Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2014-01-13 16:31:30
Size: 1846
Editor: jdstrand
Comment:
Revision 3 as of 2014-01-13 17:24:01
Size: 3337
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Meeting (DRAFT) == == Meeting ==
Line 31: Line 31:
   * pending updates
Line 33: Line 34:
    * userspace dfa discussion with jjohansen
    * prep for upstream meeting
    * testing work and patch review
Line 34: Line 38:
   * !AppArmor
    * trusty upload with dbus eavesdropping policy support and parser improvements
    * kdbus
    * ecryptfs triage
Line 36: Line 44:
    * dfa test coordination
    * prep for upstream meeting
    * ipc and stacking
Line 37: Line 48:
   * happy place
   * leftover community from last week
   * MIR audits
   * apparmor patch review
Line 38: Line 53:
   * oxide
    * fix 2 (known) runtime errors. One should be fixed, other is being worked on. Hopefully, with these should have working armhf builds
    * bug:1267893 (Oxide - Shutdown crash due to possible mesa race at startup)
Line 44: Line 62:
    * ipc and stacking
     * design iteration and some implementation to be done
     * bugs in current implementation causing OOPSes. Once fixed, should have packages in the ppa
Line 45: Line 66:
    * pending apparmor upload is all that is needed (and removing apparmor=0 to the command line)
   * yama
    * work is done. testing is not. need to run autopilot tests with yama enabled. Advised to talk to xnox, sergiusens and/or qa team
Line 46: Line 70:
   * kdbus investigations     * functional armhf builds this week
    * uploads to ubuntu - i'm waiting on qt5.2 landing for that
    * CI - i need to respond to an email from CI team
    * [ACTION] chrisccoulson to benchmark oxide and qtwebkit once armhf builds work
    * [ACTION] chrisccoulson to send results of benchmarks to list
   * kdbus investigations - will pick up again this week after feedback from last week

Meeting

Attendance

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

Not present

  • None

Agenda

  • Announcements
  • Actions
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • weekly role: triage
      • pending updates: openstack and openjdk-7
      • sponsor tyhicks apparmor upload
      • work items as time allows
    • mdeslaur
      • weekly role: community
      • pending updates
    • sbeattie
      • AppArmor

        • userspace dfa discussion with jjohansen
        • prep for upstream meeting
        • testing work and patch review
    • tyhicks
      • AppArmor

        • trusty upload with dbus eavesdropping policy support and parser improvements
        • kdbus
        • ecryptfs triage
    • jjohansen
      • AppArmor

        • dfa test coordination
        • prep for upstream meeting
        • ipc and stacking
    • sarnold
      • happy place
      • leftover community from last week
      • MIR audits
      • apparmor patch review
    • chrisccoulson
      • oxide
        • fix 2 (known) runtime errors. One should be fixed, other is being worked on. Hopefully, with these should have working armhf builds
        • bug:1267893 (Oxide - Shutdown crash due to possible mesa race at startup)
  • 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
    • status updates:
      • AppArmor work items

        • ipc and stacking
          • design iteration and some implementation to be done
          • bugs in current implementation causing OOPSes. Once fixed, should have packages in the ppa
      • apparmor for emulator
        • pending apparmor upload is all that is needed (and removing apparmor=0 to the command line)
      • yama
        • work is done. testing is not. need to run autopilot tests with yama enabled. Advised to talk to xnox, sergiusens and/or qa team
      • oxide
        • functional armhf builds this week
        • uploads to ubuntu - i'm waiting on qt5.2 landing for that
        • CI - i need to respond to an email from CI team
        • [ACTION] chrisccoulson to benchmark oxide and qtwebkit once armhf builds work
        • [ACTION] chrisccoulson to send results of benchmarks to list
      • kdbus investigations - will pick up again this week after feedback from last week

Log

Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-01-13-16.32.html

MeetingLogs/Security/20140113 (last edited 2014-01-13 17:24:01 by jdstrand)