Correct the positioning of my agenda item to the designated location.
|Deletions are marked like this.||Additions are marked like this.|
|Line 7:||Line 7:|
|The next meeting is set for 2018-04-10, 20:00 London time. chair: kees, backup: slangasek||The next meeting is set for 2018-04-24, 20:00 London time. chair: kees, backup: slangasek|
|Line 13:||Line 13:|
|* ''ACTION:'' tsimonq2 to propose patches to maintenance-check regarding Lubuntu Next (done in https://code.launchpad.net/~tsimonq2/ubuntu-archive-publishing/lubuntu-next-support-cycle-adjustment/+merge/342475 )|
|Line 16:||Line 15:|
| * ''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)
|Line 17:||Line 18:|
|* [tsimonq2] - The rationale for snapd being in the platform seed when flavors weren't polled first.|
If you have a question to raise with the Board, you can reach the Technical Board members directly by e-mailing email@example.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-04-24, 20:00 London time. chair: kees, backup: slangasek The agenda will include the following:
- Action review:
ACTION: flexiondotorg To follow-up on-list with design review to address MATE Boutique security/consent concerns.
ACTION: infinity to call for confirmation of LTS status from all flavours.
ACTION: infinity to ask maas team to prepare SRU exception policy à la CurtinUpdates
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 seeded snaps policy
- [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.