TechnicalBoardAgenda
|
Size: 2616
Comment: rotate date/chairs
|
Size: 2523
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| The next meeting is set for 2018-060-5, 20:00 London time. chair: stgraber, backup: infinity | The next meeting is set for 2019-08-13, 20:00 London time. chair: kees, backup: vorlon |
| Line 12: | Line 12: |
| * ''ACTION:'' vorlon to ask DMB to require flavor developer teams in LP to have a 6-month expiry policy, thus requiring developers to reaffirm their committment each release cycle | |
| Line 13: | Line 14: |
| * ''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 [[https://wiki.ubuntu.com/UbuntuSeededSnaps|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). |
* ''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. |
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-08-13, 20:00 London time. chair: kees, backup: vorlon The agenda will include the following:
- Apologies:
- Action review:
ACTION: vorlon to ask DMB to require flavor developer teams in LP to have a 6-month expiry policy, thus requiring developers to reaffirm their committment each release cycle
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
- [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.
TechnicalBoardAgenda (last edited 2024-04-23 19:10:37 by seb128)