== Meeting information == * #ubuntu-meeting: Technical Board meeting, started by rbasak, 12 Oct at 19:04 — 19:28 UTC. * Full logs at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-10-12-19.04.log.html == Meeting summary == === Apologies === Discussion started by rbasak at 19:05. * mdeslaur sends his apologies (rbasak, 19:05) * sil2100 may be unavailable due to the imminent Ubuntu release (rbasak, 19:05) === Action review === Discussion started by rbasak at 19:05. * ''ACTION:'' formal ratification of third party seeded snap security policy, depends on: (rbasak, 19:06) * ''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. (rbasak, 19:06) * ''ACTION:'' vorlon to reply to seeded snap upload permissions question on list (rbasak, 19:06) * ''ACTION:'' vorlon to reply to seeded snap upload permissions question on list (rbasak, 19:07) * ''ACTION:'' sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step (rbasak, 19:08) * ''ACTION:'' all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements (rbasak, 19:11) === Erich Eickmeyer via the mailing list: DisplayCAL in the archive as a deb that pulls in a Flatpak, and its inclusion in Ubuntu Studio by default. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements === Discussion started by rbasak at 19:15. * ''AGREED:'' We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway (rbasak, 19:24) === Scan the mailing list archive for anything we missed (standing item) === Discussion started by rbasak at 19:25. * No recent communication on the public mailing list (rbasak, 19:26) === Check up on community bugs (standing item) === Discussion started by rbasak at 19:27. * No open community bugs (rbasak, 19:27) === Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) === Discussion started by rbasak at 19:27. * Next chair will be sil2100 with mdeslaur as backup (rbasak, 19:28) == Action items, by person == * sil2100 * sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step * vorlon * 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. * vorlon to reply to seeded snap upload permissions question on list * vorlon to reply to seeded snap upload permissions question on list * **UNASSIGNED** * formal ratification of third party seeded snap security policy, depends on: * all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements == People present (lines said) == * rbasak (49) * meetingology (9) * vorlon (8) * sil2100 (8) * Eickmeyer (6) * cyphermox (2) == Full log == 19:04 #startmeeting Technical Board 19:04 Meeting started at 19:04:53 UTC. The chair is rbasak. Information about MeetBot at https://wiki.ubuntu.com/meetingology 19:04 Available commands: action, commands, idea, info, link, nick 19:05 #topic Apologies 19:05 #info mdeslaur sends his apologies 19:05 #info sil2100 may be unavailable due to the imminent Ubuntu release 19:05 #topic Action review 19:05 * rbasak rbasak to communicate the TB's MATE resolution to the MATE flavour leads. 19:06 I just did this, and Wimpy said to expect a response in a couple of weeks. Thanks Wimpy! 19:06 * rbasak formal ratification of third party seeded snap security policy, depends on: 19:06 * rbasak 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. 19:06 carry-over 19:06 #action formal ratification of third party seeded snap security policy, depends on: 19:06 * meetingology formal ratification of third party seeded snap security policy, depends on: 19:06 #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. 19:06 * meetingology 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. 19:06 #action vorlon to reply to seeded snap upload permissions question on list 19:06 * meetingology vorlon to reply to seeded snap upload permissions question on list 19:07 carry-over 19:07 #action vorlon to reply to seeded snap upload permissions question on list 19:07 * meetingology vorlon to reply to seeded snap upload permissions question on list 19:07 FWIW, I'm not sure what that item is referring to exactly 19:07 * rbasak sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step 19:08 I assume we will carry this as sil2100 isn't here. 19:08 #action sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step 19:08 * meetingology sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step 19:08 * rbasak all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements 19:09 Does everyone consider their input on this complete? 19:10 I see there's an ongoing discussion at the bottom of the document 19:10 I've given feedback on everything up to that point 19:10 I have an answer for the next related action item, so let's carry this I guess. 19:11 #action all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements 19:11 * meetingology all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements 19:11 * rbasak rbasak to draft refined rules for the proposed "stability" requirement for third-party software repositories 19:11 o/ 19:11 I just drafted this 19:11 o/ 19:11 Let me paste it into the pad 19:11 Sorry everyone, got distracted 19:12 * vorlon finds it, look for --BEGIN--- 19:13 rbasak: thanks. I think we should take some time to digest this rather than trying to decide on it this meeting (at least, I need time to digest :) 19:14 Sure. 19:15 I think the next agenda item will suffice to track the general goal of sorting this out. 19:15 #topic Erich Eickmeyer via the mailing list: DisplayCAL in the archive as a deb that pulls in a Flatpak, and its inclusion in Ubuntu Studio by default. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements 19:15 Any specific next steps here? Is everyone happy to continue digesting/feedbacking? 19:17 I don't want to crash the meeting, but can I say something about this (got a ping)? 19:18 Sure, please do 19:18 Ok, well, considering the feedback I got from vorlon, I'm willing to drop this and have been working on a snap. 19:18 Unfortunately, that has been quite the struggle, so I'm going to be enlisting some help on this. 19:19 At the appropriate time, I hope to make it a seeded snap 19:19 \o/ 19:20 However, I agree that the technicality of being able to include a flatpak of *something* has merit, but I'm no longer pursuing it for this particular application. 19:20 OK. Thank you for the update! 19:20 No problem. I hope that helps. :) 19:20 Where do we want to go from here then? 19:20 I think it's still good to work out an official policy for such cases 19:21 +1 19:21 Should we archive the current discussion until/unless it's raised again by someone else with a similarly credible request? Or as sil2100 says, should we carry on anyway? 19:21 well, aren't we with the third party repo requirements pad? 19:22 I think archiving it carries the risk of retread the next time it comes up :) 19:22 Personally I'm in favour of solidifying this anyway, as we are continuing with seeded snaps which would I think be expected to comply with these generic requirements anyway 19:22 OK, so I think we're agreed that we carry on? 19:22 My apologies for not finishing my comments for that one, but I think we should be continuuing, especially that I feel it's 'close' to being all properly defined 19:24 #agreed We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway 19:24 AGREED: We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway 19:25 So there remains an action item for everyone to continue working on the pad, so I'll leave that there, and I'll adjust the agenda item to make this request generic 19:25 +1 19:25 Anything else for this topic for now? 19:25 #topic Scan the mailing list archive for anything we missed (standing item) 19:26 #info No recent communication on the public mailing list 19:26 However there was a private communication that needs a response I think, but should probably remain private for now. 19:26 Is there somewhere private the TB can go to discuss this now? Or do we need to use private email or something? 19:26 private email is pretty much it 19:27 OK. I'll start that thread after the meeting. 19:27 #topic Check up on community bugs (standing item) 19:27 #info No open community bugs 19:27 #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) 19:27 Me o/ 19:28 Since I was supposed to be chairing today, right? 19:28 #info Next chair will be sil2100 with mdeslaur as backup 19:28 Yup, makes sense. 19:28 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)