TechnicalBoardAgenda

Differences between revisions 659 and 661 (spanning 2 versions)
⇤ ← Revision 659 as of 2018-10-09 18:00:37 →
Size: 2449
Editor: tsimonq2
Comment: I can comment.
← Revision 661 as of 2018-10-09 20:08:29 → ⇥
Size: 2226
Editor: adconrad
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
The next meeting is set for 2018-10-09, 20:00 London time. chair: infinity, backup: kees The next meeting is set for 2018-10-23, 20:00 London time. chair: kees, backup: mdeslaur
Line 14: Line 14:
  * formal ratification of third party seeded snap security 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).		   * ''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.

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-10-23, 20:00 London time. chair: kees, backup: mdeslaur 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)

    • 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.

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)