TechnicalBoardAgenda

Differences between revisions 648 and 649
Revision 648 as of 2018-05-22 19:09:18
Size: 2568
Editor: vorlon
Comment:
Revision 649 as of 2018-05-22 19:12:06
Size: 2617
Editor: adconrad
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
  * ''ACTION:'' infinity to call for confirmation of LTS status from all flavours.
  * ''ACTION:'' infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates
  * ''ACTION:'' infinity to call for confirmation of LTS status from all flavours. (done)
  * ''ACTION:'' infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates (see https://wiki.ubuntu.com/MAASUpdates)

This page records the Agenda for the next meeting of the Ubuntu Technical Board. Please see the Ubuntu Governance page for details on participation.

If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing technical-board@lists.ubuntu.com. They may decide that your issue should be discussed at the next meeting, in which case they will add it to this page.

The meeting schedule is available on the fridge calendar. We meet in channel #ubuntu-meeting-2 on chat.freenode.net.

The next meeting is set for 2018-05-22, 20:00 London time. chair: slangasek, backup: stgraber The agenda will include the following:

  • Apologies:
  • Action review:
    • ACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.

    • ACTION: infinity to call for confirmation of LTS status from all flavours. (done)

    • ACTION: infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates (see https://wiki.ubuntu.com/MAASUpdates)

    • ACTION: slangasek and mdeslaur to more clearly define third party seeded snap security policy

    • ACTION: tsimonq2 to email proposed policy for flavor-notification of daemons being added to all flavors (e.g. snapd into desktop-common)

  • [slangasek] - Review of the seeded snaps policy

  • [doko] LP: #1770748: Dropping patches added for main inclusion and delegation of maintainership
    • Asking the TB, when it's correct dropping patches formally added for main inclusion.
    • Asking the TB, if such a change is appropriate doing by a community member.
    • Asking the TB, if donating the ownership for maintenance for a package is an appropriate move (although I'm unsure if the TB is the correct addressee).
  • [Add new agenda items above this line - include your name]
  • Scan the mailing list archive for anything we missed (standing item)

  • Check up on community bugs (standing item)

  • Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)

Logs from previous meetings may be found at http://irclogs.ubuntu.com/ or http://ubottu.com/meetingology/logs/ubuntu-meeting-2/. Logs from older meetings are available via MootBot.


CategoryUbuntuTeams

TechnicalBoardAgenda (last edited 2024-03-26 20:13:08 by racb)