15:06 #startmeeting DMB meeting 15:06 Meeting started Mon Jul 27 15:06:05 2020 UTC. The chair is slashd. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:06 15:06 Available commands: action commands idea info link nick 15:06 #topic Review of previous action items 15:06 #subtopic rafaeldtinoco pkgset tooling full documentation (being worked, carried until mentioned) 15:06 these are the long term action items 15:06 still at the same state ? 15:06 right 15:06 yep, just mention those 15:06 and move on 15:07 #subtopic rafaeldtinoco to check edubuntu seed <-> pkgset relationship (generation) and if edubuntu pkgsets can be dropped (carried over) 15:08 #subtopic rafaeldtinoco to create, for now, a small "what-to-do" for pkgset changes in -devel (document exceptions inclusion for DMB team) (carried over) 15:08 git.launchpad.net/~developer-membership-board/+git/packageset 15:08 i still need to finish 15:09 #subtopic rafaeldtinoco link team delegation from dmb kb page when reading ddstreet updates (carried over) 15:10 rafaeldtinoco Any updates on those items ? or all good for now ? 15:11 sorry 15:11 my time in the meeting to talk 15:11 nope, only the documentation 15:12 item is almost finish 15:12 but I still have to create the wiki page 15:12 and link to the dmb wiki pages 15:12 thanks rafaeldtinoco anything we can do to help ? 15:13 yes. please 15:13 How can we help? 15:13 id like help from someone in the edubuntu seed <-> pkgset relationship 15:13 you can get the packageset tool from the git repo I pasted 15:13 and follow the README file and check 15:13 i can take that action item 15:13 edubuntu seed <-> pkgset (from germinate) 15:14 and check if we should add something to exceptions, or any bigger change there 15:14 slashd can you give me action item for that 15:14 thanks a lot @ddstreet 15:14 busy weeks I had 15:14 well you too 15:14 thanks for sharing the burden lol 15:14 yep np, i've wanted to understand the seed/pkgset tooling better so this is a good excuse :) 15:15 nice, its all in Makefile now 15:15 and feel free to push things to the repo 15:15 #action edubuntu seed <-> pkgset (ddstreet) 15:15 * meetingology edubuntu seed <-> pkgset (ddstreet) 15:15 or MR for me to review 15:16 We have no applicant today. Is there anything else we need to discuss or something I missed ? 15:16 are you going thru the mailing list items in the agenda? 15:17 * slashd looking 15:17 #subtopic Request for delagate team for DKMS modules (Francis Ginther) 15:18 seems like the vote went on the ML ^ 15:18 do we want to just vote on it now? 15:18 or keep it on ML? 15:18 Yeah, I think the people that didn't vote could vote now 15:19 We could follow up on the thread for consistency 15:19 i'm fine voting now if we want to queue up a vote for it 15:20 I'm fine with both (ML or proceed with a vote now) 15:20 I think we have quorum today anyway 15:20 let's just vote now, yeah 15:20 i think there are 2 motions https://lists.ubuntu.com/archives/devel-permissions/2020-July/001540.html 15:21 #vote Please vote on: Request for delegate team for DKMS modules 15:21 Please vote on: Please vote on: Request for delegate team for DKMS modules 15:21 Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) 15:21 slashd shouldn't we vote on the 2 motions separately? 15:21 i mean maybe we'll all vote the same for both, but probably should allow for voting separately? 15:22 I guess this is for the first motion I assume? 15:22 #endvote 15:22 Voting ended on: Please vote on: Request for delegate team for DKMS modules 15:22 Votes for:0 Votes against:0 Abstentions:0 15:22 Deadlock, casting vote may be used 15:22 sounds good yep, this roudn is for motion #1, Create a DKMS packageset defined as "Packages that ship DKMS 15:22 modules that need updating to support new kernel versions" 15:23 #vote Please vote on: Motion 1: Create a DKMS packageset defined as "Packages that ship DKMS 15:23 modules that need updating to support new kernel versions" once we have 15:23 further agreed upon at least one uploader to be able to upload to this 15:23 packageset. 15:23 Please vote on: Please vote on: Motion 1: Create a DKMS packageset defined as "Packages that ship DKMS 15:23 Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) 15:23 +1 15:23 +1 received from sil2100 15:24 +1 sounds reasonable to me 15:24 +1 sounds reasonable to me received from ddstreet 15:24 +1 15:24 +1 received from slashd 15:24 +1 15:24 +1 received from rafaeldtinoco 15:24 #voterequired 4 15:26 rbasak also +1'd in the ML 15:26 #endvote 15:26 Voting ended on: Please vote on: Motion 1: Create a DKMS packageset defined as "Packages that ship DKMS 15:26 Votes for:4 Votes against:0 Abstentions:0 15:26 Motion carried 15:27 #vote Please vote on: Motion 2: Create a DKMS packageset uploading team once we have further 15:27 Please vote on: Please vote on: Motion 2: Create a DKMS packageset uploading team once we have further 15:27 Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) 15:27 agreed upon at least one uploader to be added to this team. 15:27 #voterequired 4 15:28 +1 on this one as well 15:28 +1 on this one as well received from sil2100 15:29 +1 the stated restrictions appear to limit this team to just the dkms modules, which i believe is the intention/goal of the original request, so seems reasonable and appropriate 15:29 +1 the stated restrictions appear to limit this team to just the dkms modules, which i believe is the intention/goal of the original request, so seems reasonable and appropriate received from ddstreet 15:29 +1 15:29 +1 received from slashd 15:29 slashd is the directive '#votesrequired' (with an s, not r)? 15:30 oh actually just missing the s, maybe 15:30 #votesrequired 4 15:30 votes now need 4 to be passed 15:31 is this the same motion ? 15:31 motion 2 15:31 Same as the one I emailed? 15:31 ah ok 15:31 +1 15:31 +1 received from rafaeldtinoco 15:31 yes 15:31 i was going to say that 15:31 +1 15:31 +1 received from rbasak 15:31 #endvote 15:31 Voting ended on: Please vote on: Motion 2: Create a DKMS packageset uploading team once we have further 15:31 Votes for:5 Votes against:0 Abstentions:0 15:31 Motion carried 15:32 Who wants to take action on these 2 motions ? 15:32 There are no actions yet 15:32 we got nothing from them yet 15:32 Until we have an uploader approved 15:32 all good then 15:33 next topic.... 15:33 #subtopic Adding Yaru to the desktop set for focal (Marco Trevisan) 15:34 do we need to vote for that ? 15:35 probably not, it seems simple enough, it's already in g, i can take action item for it unless anyone else wants it 15:35 ddstreet: I'll take care of it if no one has it yet 15:36 sounds good, thnx 15:36 #action Adding Yaru to the desktop set for focal (slashd) 15:36 * meetingology Adding Yaru to the desktop set for focal (slashd) 15:36 #subtopic RFC: auto-generated packageset for Canonical OEM enablement metapackages (Iain Lane) 15:37 Something to mention here ? 15:37 not sure if Laney is around? 15:38 this request seemed, to me, very reasonable, but i think i would prefer to have the mentioned script already created before voting on the new packageset 15:39 also it wasn't clear to me who would be running the script, and if there would be any human review of its updates (e.g. if it's run on a crontab) 15:39 maybe preferable to then addresse those point to the ML and vote when we have all the infos in next DMB mtg(s) 15:39 i'm here 15:39 what up 15:40 re: oem packageset 15:40 I mean the script is like 15:40 for pkg in all_packages: 15:40 if fnmatch.fnmatch(pkg, 'oem-*'meta'): 15:40 packageset.add(pkg) 15:41 i assume it would need to be run regularly by a DMB member? or via cron somewhere? 15:41 ya something like that, or the oem team can poke you to run it 15:42 can be integrated in the packageset repo 15:42 or I guess one option would be to make the set owned by another team 15:42 and run in crontab or manually 15:42 like ~ubuntu-archive or ~ubuntu-sru 15:42 then they can run it themseves 15:43 sil2100 ^ Any thoughts on that ? since you are in both group 15:43 probably -archive since we're talking about uploading to NEW here 15:44 then the dmb's role will be handling applications for new uploaders, but not managing the actual packages in the set 15:44 I'm going to have to disappear, sorry. Back in about an hour. 15:45 Laney: I guess we will need to make sure ~archive is agree with that, I don't think dmb has authority on that 15:46 sure 15:46 i would also want to make sure the ppa is access-controlled too, since it essentially opens a self-service hole to upload new packages 15:47 but as long as the packageset team owns the ppa that should be enough 15:47 but maybe you can agree that you are ok in principle with it being ubuntu-archive (i.e. not the dmb) 15:47 nod 15:47 yes i'm fine with the dmb only managing membership in the team 15:47 same here 15:48 not sure if we have enough detail to vote on this right now? and probably would need agreement from -sru and/or -archive teams also; should we take it back to the list to continue? 15:49 Sorry, I have a standup now, let me read the backlog 15:49 sil2100: take your time I think your input will be valuable here 15:49 can come back to it next meeting if you want, I don't think anyone is ready for the rights yet anyway 15:49 just want to have it all in place for when they are 15:49 i think a reply to the email 15:49 with the proposal we have right now 15:50 would be better for voting next meeting 15:50 Yeah, I think this should be safe and doable, since the OEM meta package generation is very strictly defined and controlled 15:50 if needed, im +1 on the change (to only control the membership of the team) 15:52 should we open a vote ? rbasak just left the meeting, maybe we should reconvene next DMB about this topic 15:52 just to clarify, we'd need a specific action item to vote on right? 15:52 which i assume for the dmb would only be 'create packageset and owning team' right? 15:53 the motion would be either we manage the packageset OR we manage permissions of who could change the packageset (by adding or removing people to a team) 15:53 yep 15:54 #action vote at next mtg(s) on controlling the membership access for the OEM enablement metapackages. 15:54 * meetingology vote at next mtg(s) on controlling the membership access for the OEM enablement metapackages. 15:54 anything else on this topic ? 15:55 I don't have preferences, but I think it would make sense for ubuntu-archive to be able to control this 15:56 thanks sil2100 15:56 #subtopic Verify ubuntu-budgie packages, possibly remove fossfreedom personal packageset if no longer needed (Open TB bugs) 15:57 i added this item as i noticed the still-open tb bug 15:57 ack so all good then 15:57 added this comment to the bug for clarification https://bugs.launchpad.net/ubuntu-community/+bug/1716770/comments/9 15:57 Launchpad bug 1716770 in ubuntu-community "[TB/DMB] New packageset ~personal-fossfreedom in Artful" [Undecided,New] 15:57 i haven't seen any reply from fossfreedom, so we could just close this out 15:58 ack 15:58 I think that cover everything in the agenda. Anything else before we call it a day ? 16:00 I guess we are done then. 16:00 #endmeeting