TechnicalBoardAgenda

Differences between revisions 619 and 674 (spanning 55 versions)
Revision 619 as of 2017-12-05 20:51:26
Size: 1948
Editor: stgraber
Comment:
Revision 674 as of 2020-06-01 21:49:12
Size: 3137
Editor: ddstreet
Comment: add section, and items, for requests from DMB
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The meeting schedule is available on the [[http://fridge.ubuntu.com/calendar|fridge calendar]]. We meet in channel '''#ubuntu-meeting-2''' on chat.freenode.net. The meeting schedule is available on the [[https://wiki.ubuntu.com/Fridge/Calendar|fridge calendar]]. We meet in channel '''#ubuntu-meeting-2''' on chat.freenode.net.
Line 7: Line 7:
The next meeting is set for 2017-12-19, 20:00 London time. chair: infinity, backup: kees The next meeting is set for 2019-10-22, 20:00 London time. chair: kees, backup: mdeslaur
Line 12: Line 12:
  * ''ACTION:'' infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates
  * ''ACTION:'' infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing (ETA: 16.04.3 release)
  * ''ACTION:'' slangasek to investigate getting tagged ubuntu-community bugs automatically forwarded to technical-board, and if not feasible, fall back to DMB sending signed emails to list for ACL requests
  * ''ACTION:'' vorlon to follow up w/ DMB on request to require 6-month expiry policy for flavor developer teams
  * ''ACTION:'' Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
  * ''ACTION:'' infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates (see https://wiki.ubuntu.com/MAASUpdates) (awaiting response from rbasak)
  * ''ACTION:'' formal ratification of third party seeded snap security policy, depends on:
  * ''ACTION:'' vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.
  * ''ACTION:'' vorlon to reply to seeded snap upload permissions question on list
  * ''ACTION:'' vorlon to chase up what's needed for a new TB election to happen
  * ''ACTION:'' xnox to start a draft summarizing the OEM archive portion of the meeting which vorlon, infinity, and mdeslaur will review, edit, and ratify before we move on to figuring out the next step ([2/3 subquorum required if one of us slacks, to avoid holding up the process])
## * [tsimonq2] Propose a shortening of support length from nine months for non-LTS releases.
## * tsimonq2 will send an email to the TB mailing list before the meeting with evidence and justification.
 * DMB requests
  * [[https://bugs.launchpad.net/ubuntu-community/+bug/1881666|Packageset modification for ~ubuntu-mate-uploaders]]
  * [[https://bugs.launchpad.net/ubuntu-community/+bug/1881653|PPU addition for ~alkisg]]
  * [[https://bugs.launchpad.net/ubuntu-community/+bug/1866679|PPU addition for ~rcj]]

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 2019-10-22, 20:00 London time. chair: kees, backup: mdeslaur The agenda will include the following:

  • Apologies:
  • Action review:
    • ACTION: vorlon to follow up w/ DMB on request to require 6-month expiry policy for flavor developer teams

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

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

    • ACTION: formal ratification of third party seeded snap security policy, depends on:

    • ACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.

    • ACTION: vorlon to reply to seeded snap upload permissions question on list

    • ACTION: vorlon to chase up what's needed for a new TB election to happen

    • ACTION: xnox to start a draft summarizing the OEM archive portion of the meeting which vorlon, infinity, and mdeslaur will review, edit, and ratify before we move on to figuring out the next step ([2/3 subquorum required if one of us slacks, to avoid holding up the process])

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)