/srv/irclogs.ubuntu.com/2020/08/10/#ubuntu-meeting.txt

=== simonquigley is now known as tsimonq2
=== paride is now known as paride|off
ddstreeto/18:58
sil2100o/18:58
rbasako/18:58
rafaeldtinocoo/18:59
sil2100Guess that's a quorum, I think it's my  time to chair, right?19:01
rafaeldtinocoUpcoming: Ɓukasz, Teward, Rafael, Dan, Robie, Eric <wrap>19:01
rafaeldtinocoyep19:01
sil2100#startmeeting DMB meeting19:01
meetingologyMeeting started Mon Aug 10 19:01:50 2020 UTC.  The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:01
meetingologyAvailable commands: action commands idea info link nick19:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic:
sil2100#topic Review of previous action items19:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: Review of previous action items
sil2100#subtopic rafaeldtinoco to check edubuntu seed <-> pkgset relationship (generation) and if edubuntu pkgsets can be dropped (carried over)19:02
rafaeldtinocoI think this is duplicated19:02
rafaeldtinocoddstreet: ^ did you have this also ?19:02
rafaeldtinoco(last item)19:02
sil2100Ah, indeed19:03
ddstreetrafaeldtinoco yeah i think that's a new one on my action list19:03
sil2100ddstreet: any progress? Or should we carry over?19:03
ddstreetnew from last mtg19:03
ddstreetno progress sorry, plz carry over19:03
sil2100Ok then19:04
sil2100#subtopic rafaeldtinoco to create, for now, a small "what-to-do" for pkgset changes in -devel (document exceptions inclusion for DMB team) (carried over)19:04
rafaeldtinocohttps://wiki.ubuntu.com/UbuntuDevelopers/SeedsAndAutomatedPkgsets19:04
rafaeldtinocoand its a Makefile now19:04
rafaeldtinocothis is the "quick what to do"19:04
rafaeldtinocoit will get better (as the long standing item)19:04
rafaeldtinocofor now you can consider done19:05
sil2100Ok, thanks! I'll have to read that up - today I quickly wanted to use it but it errored out when I tried running `make fetch`19:05
rafaeldtinocojust ping me19:05
sil2100But I didn't look into the details, need to try again19:05
rafaeldtinocosure thing19:05
sil2100I was too busy with pointy-release stuff19:05
sil2100#subtopic rafaeldtinoco link team delegation from dmb kb page when reading ddstreet updates (carried over)19:06
rbasakrafaeldtinoco: nicely done - thanks!19:06
rbasakIs that linked to from anywhere?19:06
rafaeldtinocothat is this item ^19:06
rafaeldtinocoand no, where should I like it ?19:06
rafaeldtinoco(it will get bigger and more detailed)19:06
rbasakhttps://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase is the general starting point for DMB-internal docs19:06
rafaeldtinocook19:06
rbasak(internal as in not relevant to anyone but active DMB members, but public of course)19:06
rafaeldtinocosil2100: mark this as carried over then., it will be done next meeting19:07
rafaeldtinocorbasak: tku19:07
sil2100Sure o/19:07
ItzSwirlzo/19:07
sil2100#subtopic DMB to vote at next mtg(s) on controlling the membership access for the OEM enablement metapackages19:07
rbasakI was distracted during the previous meeting, sorry.19:08
rbasakBut AIUI, there's nothing being done here yet, except to define a packageset?19:08
sil2100Yeah, so I'm reading the previous meeting logs now19:08
sil2100I think we agreed that we would just be creating a packageset and delegating the management of those permissions to ubuntu-archive, correct?19:09
rafaeldtinocoAs a first step towards making this self service for that team, I'd like19:09
rafaeldtinocoto ask the DMB to consider making a packageset for this purpose.19:09
rafaeldtinocoInitially it'll have no uploaders apart from ~ubuntu-core-dev, so we're19:09
rafaeldtinococonsidering the set itself only right now.19:09
sil2100Is this something we should vote on?19:09
rafaeldtinocothis is the core part for now19:09
rafaeldtinocowe will have people applying for upload rights later19:10
rafaeldtinocoiirc19:10
sil2100Ok, so only voting on creating the packageset for now with core-dev as members, without team delegation?19:10
rafaeldtinocoi would set the team ready19:10
rafaeldtinocojust so we dont need AA later19:10
rafaeldtinocothis way we can manage permissions as they apply19:11
rbasakCreate a team maybe, and add only ~ubuntu-core-dev to it initially19:11
rafaeldtinocoyep19:11
rafaeldtinocothen we are good to go for applications19:11
sil2100Do we want to define the initial packageset contents formally?19:12
rbasakhttps://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Personal_packagesets_and_glob_expansions is prior art for "glob-based" packagesets19:12
rbasakThere, the formal packageset contents was defined in the packageset description using the glob pattern19:12
rafaeldtinocoyep19:12
rafaeldtinocom tells me19:13
rafaeldtinocothat packageset permissions can be added if a source package exists19:13
rafaeldtinoco*anywhere* (i.e. in a PPA), not just in Ubuntu. So there would be a19:13
rafaeldtinocoscript which enumerates a staging PPA and adds packages found there19:13
rafaeldtinocowhich match the glob 'oem-*-meta' to the packageset.19:13
sil2100Yeah, so the glob here would be oem-*-meta19:13
rafaeldtinocothey want source packages to come automatically from a staging ppa19:13
sil2100Ok, so let me formulate the vote then19:13
rbasakrafaeldtinoco: I would prefer to require the glob to be driven from the archive, not from a PPA19:13
rbasakI'm not sure a packageset containing a package not in the archive would work anyway19:14
rafaeldtinocorbasak: what are the cons ?19:14
rafaeldtinocoah i see19:14
ddstreetthat was a concern for me also rbasak, driving the packageset from a ppa is essentially opening a backdoor into the archive19:14
rbasakIt's confusing, because the DMB's remit relates to the archive only19:14
rafaeldtinocoyou mean an upload for a source that we dont have19:14
rafaeldtinocoyep19:14
rbasakAnd also what ddstreet says19:14
rbasakThe process would be:19:14
rbasakGet a core dev or MOTU sponsored upload into the archive19:15
rbasakGet an AA to do the NEW review19:15
rbasakAsk the DMB to run the script to update the packageset using the glob pattern19:15
rbasakIn that order19:15
sil2100Are we ready to vote on the base part?19:15
rafaeldtinocowhat is the NEW review ?19:16
rafaeldtinocorbasak: ^19:16
ddstreetsil2100 is there specific wording that we're voting on now?19:16
rafaeldtinocosil2100: I think we are all +1 on this, currently discussing the implementation19:16
sil2100#vote Creation of a new canonical-oem-metapackages packageset and owning team for the glob expansion of oem-*-meta, initially having ~ubuntu-core-dev as the only member19:17
meetingologyPlease vote on: Creation of a new canonical-oem-metapackages packageset and owning team for the glob expansion of oem-*-meta, initially having ~ubuntu-core-dev as the only member19:17
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)19:17
sil2100(we need a formal vote)19:17
sil2100Did I  get this right?19:17
rbasak+1 assuming that the glob expansion will be performed from archive packages only19:18
meetingology+1 assuming that the glob expansion will be performed from archive packages only received from rbasak19:18
ddstreet+1 for pkgset and team creation19:18
meetingology+1 for pkgset and team creation received from ddstreet19:18
sil2100+119:18
meetingology+1 received from sil210019:18
rafaeldtinoco+1 for both19:18
meetingology+1 for both received from rafaeldtinoco19:18
sil2100#endvote19:18
meetingologyVoting ended on: Creation of a new canonical-oem-metapackages packageset and owning team for the glob expansion of oem-*-meta, initially having ~ubuntu-core-dev as the only member19:18
meetingologyVotes for:4 Votes against:0 Abstentions:019:18
meetingologyMotion carried19:18
sil2100Ok, motion carried, yes, we can proceed with implementation details19:18
sil2100;)19:18
rafaeldtinocosorry, had in my head this was already voted previously19:19
rafaeldtinocothanks19:19
ddstreeti think at the last mtg we said it would be better to defer the specific pkgset operation to ubuntu-archive or ubuntu-sru team, is that right? and dmb would only manage team membership?19:19
sil2100I don't think it was, as the action item was to vote on it now19:19
rafaeldtinocoddstreet: we did say that19:20
rafaeldtinocobut never agreed19:20
sil2100Yeah19:20
rafaeldtinocoim thinking if that would be easier for them19:20
ddstreeti do agree with rbasak on the concerns around the implementation, but maybe that's best for a different team to work out?19:20
rbasakAIUI then, we'd define the glob expansion (ie. define the script that does the glob expansion) but ~ubuntu-archive or ~ubuntu-sru would actually run it?19:21
rbasakIf that's considered useful, then sure19:21
rafaeldtinocoim ok with that19:21
ddstreeti'm ok either way19:21
rafaeldtinocorbasak: would that be a burden for the sru team ?19:21
rafaeldtinocothinking on what would be best for all (SRU team and this new team)19:21
sil2100Same here, I don't think it's that much of a deal to actually need to be delegated though19:22
rafaeldtinocoif its just running a script19:22
rafaeldtinocoi can do it with the weekly pkgset19:22
rbasakThe SRU team aren't used to managing packagesets or running recognising weird edge cases to run appropriate scripts19:22
rafaeldtinocopkgset <-> seed sync19:22
rafaeldtinocoi can run both together19:22
rafaeldtinocodo we have a "production"  place19:22
rafaeldtinocoto land those things ?19:23
rbasakI'm not refusing to do it on behalf of the SRU team or anything, but I'm not sure it's going to be helpful. In practice it'll end up getting missed I think19:23
sil2100I'd say let's leave it under our control for now19:23
ddstreetsounds like rafaeldtinoco is taking an action item to add it to the tooling then? :)19:23
rafaeldtinocorbasak: that is understood19:23
rafaeldtinocoddstreet: its ok for me.. i was just wondering19:23
rafaeldtinocois my home the best place to run cron jobs ?19:23
rbasakI'm with sil2100. Let's leave it under our control for now.19:23
rafaeldtinocoshould I deploy it somewhere ?19:23
rbasakWe don't have a good place to cron it from19:23
rafaeldtinocook, it will continue here then19:24
rbasakWe could start by just responding to a ping from an uploader who is stuck19:24
rbasakAnd then go from there19:24
sil2100Ok, let's put some action items19:24
sil2100Who wants to take the actual team and packageset creation?19:24
rbasakI'll take it19:24
rafaeldtinococool. i can do the scripting19:24
rafaeldtinocoand crontabing19:24
rafaeldtinocoif needed (or should we wait applicants first ?)19:25
sil2100#action rbasak to take care of the canonical-oem-metapackages packageset and owning team creation19:25
meetingologyACTION: rbasak to take care of the canonical-oem-metapackages packageset and owning team creation19:25
sil2100rbasak: guess it needs the TB, right?19:25
sil2100(I always forget)19:25
rbasakrafaeldtinoco: personally I'd wait until managing it manually becomes painful19:25
rbasakBut I have no objection if you want to run ahead with it19:25
rafaeldtinocomanually it is19:25
rbasakYes - packageset creation will need the TB. We have a process for requesting that19:25
rafaeldtinocoso we can all get used to it19:25
sil2100I think we all have enough on our plates that it's best not to put additional scripting work ;)19:25
rafaeldtinocosil2100: yes!19:25
sil2100Ok, I think we have this sorted out then19:26
sil2100#subtopic slashd to add Yaru to the desktop set for focal19:26
sil2100I don't think slashd is here with us today?19:26
sil2100Does anyone know if that is done?19:26
ddstreetlooks like it's not done yet19:27
ddstreetand slashd is out today19:27
sil2100Ok, let's carry that one over then19:27
sil2100Last action item is a duplicate, and we discussed it already19:28
sil2100We have no applicants today, so let's move to AOB19:28
sil2100#topic AOB19:28
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: AOB
sil2100Anything to discuss otherwise?19:28
sil2100I take that as a no!19:29
sil2100Ok, I guess we can finish19:30
sil2100#topic Select a chair for the next meeting19:30
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice | DMB meeting | Current topic: Select a chair for the next meeting
sil2100That would be Teward, but I guess he's not here today19:30
sil2100#endmeeting19:30
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | <wxl> be nice
meetingologyMeeting ended Mon Aug 10 19:30:47 2020 UTC.19:30
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-08-10-19.01.moin.txt19:30
sil2100Thanks everyone!19:30
rafaeldtinocosil2100: tku!19:30
ddstreetthanks! o/19:30
sil2100I'll update the Agenda now19:30
rafaeldtinocoo/ everyone19:30
ItzSwirlzhave a gn/good day19:30
ItzSwirlzo/19:31
ItzSwirlzDon't let the thunderstorms kill yall19:31
tewardsil2100: nope not here because Hospital19:49
tewardappendicitis19:49
tewardthey got the thing out but i am in recov until tomorrow19:50
tewardstill 'alive' barely though19:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!