TechnicalBoardAgenda

Differences between revisions 595 and 664 (spanning 69 versions)
⇤ ← Revision 595 as of 2017-03-14 16:52:56 →
Size: 2376
Editor: vorlon
Comment: rotate date/chairs
← Revision 664 as of 2019-03-05 22:21:27 → ⇥
Size: 2435
Editor: vorlon
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page records the Agenda for the next meeting of the [[TechnicalBoard|Ubuntu Technical Board]]. Please see the [[http://www.ubuntu.com/community/processes/governance|Ubuntu Governance]] page for details on participation. This page records the Agenda for the next meeting of the [[TechnicalBoard|Ubuntu Technical Board]]. Please see the [[https://www.ubuntu.com/about/about-ubuntu/governance|Ubuntu Governance]] page for details on participation.
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-03-14, 17:00 London time. chair: slangasek, backup: stgraber The next meeting is set for 2019-02-12, 20:00 London time. chair: kees, backup: stgraber
Line 11: Line 11:
  * none
Line 13: Line 12:
  * ''ACTION:'' infinity to follow up with maas SRU exception
  * ''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.2 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:'' slangasek to follow up to snapd-glib SRU exception request
 * Ask for standing freeze exception for python2.6 and openjdk-9 package updates for xenial and yakkety to match the versions in the most recent development release. Both packages were uploaded as pre-release versions, are in universe, and not used by any package builds. Asking to update these to follow the versions from the most recent development release (doko).		   * ''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
## * [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.
 * [vorlon] discuss how to ensure flavors are continuing to meet certification requirements

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-02-12, 20:00 London time. chair: kees, 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 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

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-04-23 19:10:37 by seb128)