|Deletions are marked like this.||Additions are marked like this.|
|Line 7:||Line 7:|
|The next meeting is set for 2019-02-12, 20:00 London time. chair: kees, backup: stgraber||The next meeting is set for 2019-07-30, 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 19:||Line 20:|
|* [vorlon] discuss how to ensure flavors are continuing to meet certification requirements|
If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing firstname.lastname@example.org. 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-07-30, 20:00 London time. chair: kees, backup: vorlon The agenda will include the following:
- 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: 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.