/srv/irclogs.ubuntu.com/2022/01/18/#ubuntu-meeting.txt

=== Kamilion|ZNC is now known as Kamilion
=== not_phunyguy is now known as phunyguy
=== unixlab is now known as nicoz
cpaelzero/15:31
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:31
meetingologyMeeting started at 15:31:09 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:31
meetingologyAvailable commands: action, commands, idea, info, link, nick15:31
cpaelzerping slyon, didrocks, sarnold, joalif, jamespage for MIR meeting15:31
sarnoldgood morning15:31
joalifo/15:31
slyono/15:31
cpaelzeras I promised last time I'll be distracted by othe rmeetings, so i beg your pardon for my latency15:31
cpaelzer#topic Review of previous action items15:32
cpaelzernone15:32
cpaelzer#topic current component mismatches15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:32
cpaelzerlet us check what new entries we have that need to be adressed15:32
cpaelzernew info on llvm-toolchain-13 foundations confirmed to take it15:32
cpaelzerdoko was tasked to resolve15:33
slyoncups-filters seems new?15:33
cpaelzerso that will be gone in a bit since it is just needing an AA being a new version15:33
cpaelzerI agree slyon15:33
cpaelzerI was not seeing cups-filters -> lync before15:33
cpaelzercups ~-> Desktop15:33
cpaelzerdidrocks: are you around?15:33
cpaelzerwhile we wait for that another FYI15:34
sarnoldsigh "Firefox has just been updated in the background. Click Restart Firefox to complete the update"15:34
cpaelzerthe suitesparse case was solved, that will be gone with the next run15:34
cpaelzerwithout an MIR actually by auto-excluding -doc and -dev 8suitesparse)15:35
cpaelzerok, it really leaves cups-filters -> lynx as the one to act on15:35
slyonside question about that: how often are those SVGs generated? Would it be possible to add a timestamp to it? (maybe we can discuss this in the AOB section)15:35
cpaelzerI'll ping Desktop in their channel15:35
cpaelzerslyon: you can watch them as html with .html suffix15:36
cpaelzerslyon: https://people.canonical.com/~ubuntu-archive/component-mismatches.html15:36
cpaelzerthere they have a timestamp15:36
cpaelzerupdated as often as update-excuses15:36
slyonok, nice15:36
sarnoldhow nice that it's generated 1.5 minutes before the meeting :)15:36
cpaelzermessage sent to desktop15:37
cpaelzer#topic New MIRs15:37
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir15:37
cpaelzerprotobuf here does NOT need a review yet, it needs an owning team first15:37
cpaelzerfoundations was suggested, slyon would you carry that to the team to say yes/no ?15:38
cpaelzerfrom there it can go into review15:38
slyonwill do15:38
cpaelzerthanks15:38
cpaelzer#topic Incomplete bugs / questions15:38
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir15:38
cpaelzerlibio-prompt-tiny-perl has a todo for foundations, once solved either the MIR isn't needed or it is approved15:39
cpaelzerno action needed15:39
cpaelzerrustc opened, but yet incomplete15:39
cpaelzerI wonder if we need to carry our needs from our "preliminary rust MIR rules" work into that MIR bug15:39
cpaelzermaybe when we do the review to not mess with whatever this was hled back as incomplete for now15:40
cpaelzer#topic Any other business?15:40
cpaelzerthe mismatch timestamp was solved15:40
slyonack15:40
cpaelzerI wanted to ask how the joint review of joalif + slyon worked out?15:41
cpaelzeranything out of that we want to change in our templates?15:41
slyonjoalif did the initial work15:41
slyonI still need to find some time for a review and filling of gaps15:41
joalifI did some stuff, the only thing that caught my eye15:41
cpaelzerok, both please do eventually speak up if you think there are docs or processes to change15:41
joalifis that this package runs a daemon as root15:41
slyonjoalif: was there anthing confusing with the process/wiki page that you'd like to improve?15:42
cpaelzerjoalif: which is ok as a finding, we have recently changed the reporter templates to explain why such (daemon as root) should be ok. Did the reporter explain something in that regard?15:42
joalifthe one thing that confused me a bit was what to do with seeded-in-ubuntu15:43
cpaelzeryou are right joalif15:44
cpaelzerwith our new style where we split RULES and TODO this part clearly would be a  RULE15:44
cpaelzeras it is not meant to stay around in the final post15:44
cpaelzerAnd more like a hint how you could check15:44
joalifyes I understand, my problem is not knowing how I'm supposed to use the tool :p15:46
joalifother than that the review process seems straight forward15:47
cpaelzerhttps://github.com/cpaelzer/ubuntu-mir/pull/615:48
ubottuPull 6 in cpaelzer/ubuntu-mir "Clarify check-mir and such are not to stay in the post" [Open]15:48
cpaelzerCreated for what we can improve here15:48
cpaelzerthe rest to understand "how to do it" really is either mana-page study or co-reviewing with one of us15:48
cpaelzereveryone please have a look at the PR, if accepted until next week we can merge that as improvement15:48
didrockscpaelzer: back, sorry, I thought we told we would skip this week, scrollbacking15:48
cpaelzerwe are about to close didrocks, no problem15:49
cpaelzerunless cups->lynx is a problem to you15:49
sarnoldhow is lynx in the daily-live and daily-preinstalled seeds if it is in universe now?15:50
didrockscpaelzer: no, I’ll follow up with Till15:50
cpaelzerthanks15:50
cpaelzersarnold: magic15:51
sarnold:)15:51
didrocksnot really liking this kind of magic :p15:51
cpaelzersarnold: chances are that is another binary of src:lynx showing up here15:51
cpaelzerbut yeah it is in universe15:51
cpaelzerafaics15:51
cpaelzera kind of magic worth a quick look by didrocks when sorting out the above maybe15:52
cpaelzernever the less I'd be closing out for today15:52
didrocksyeah, it can bit us another time without noticing, hence not linking not understanding what’s going on, but that’s a topic for later :)15:52
cpaelzerok, thank you all then15:56
cpaelzersee you next week15:56
slyonsee you, thanks!15:56
cpaelzer#endmeeting15:56
meetingologyMeeting ended at 15:56:26 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-01-18-15.31.moin.txt15:56
sarnoldthanks cpaelzer, all :)15:56
joalifo/15:56
didrocksthanks!15:56
sarnoldlynx spent some time in main in the old days .. https://launchpad.net/ubuntu/+source/lynx/+publishinghistory?batch=75&memo=75&start=75 .. I wonder if it's been in the seeds ever since? heh15:57
didrockswaow, until Jaunty, not that long ago15:58
didrocks… well, a little bit :)15:59
didrocksI wonder about the come back in main in Xenial…15:59
=== genii-core is now known as genii
rbasako/20:00
sil2100o/20:00
rbasakvorlon, mdeslaur: o/20:00
mdeslaurhi rbasak sil2100 vorlon20:00
rbasakcyphermox doesn't seem to be online20:00
rbasakBut three is enough I think?20:01
rbasakAnd I guess I'm chairing then20:01
rbasak#startmeeting Technical Board20:01
meetingologyMeeting started at 20:01:28 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:01
meetingologyAvailable commands: action, commands, idea, info, link, nick20:01
rbasak#topic Action Review20:01
sil2100I think so, thanks!20:01
rbasakACTION: formal ratification of third party seeded snap security policy, depends on: (rbasak, 19:06)20:01
rbasakACTION: 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)20:01
rbasakACTION: vorlon to reply to seeded snap upload permissions question on list (rbasak, 19:06)20:01
rbasakACTION: 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)20:01
rbasakACTION: all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements (rbasak, 19:11)20:02
sil2100o/20:02
sil2100I started the draft a while ago and did some modifications recently20:02
sil2100(for the OEM archive)20:02
sil2100There are things however that I didn't yet manage to get enough knowledge to fill in the gaps, so maybe one of you could help - if you know20:02
sil2100If not, I'll reach out to people working on it20:02
sil2100Because I was wondering: who has upload rights to the OEM archive?20:03
sil2100Since the Canonical OEM metapackage PPA is governed by the team for the PPU20:03
sil2100But I was actually wondering if it's the same team that gives power over the OEM archive itself?20:03
sil2100The still in-progress draft of the OEM scenario is done here: https://wiki.ubuntu.com/OEMArchive20:04
rbasakALso https://lists.ubuntu.com/archives/technical-board/2020-January/002478.html for some discussion I think20:04
sil2100This was all before my time so I only wrote of the things that I knew about, might need to poke around to get all the other missing bits20:05
sil2100Yeah, this I remember20:05
sil2100But it doesn't directly say who besides the 'Canonical Teams' that got given access to the OEM private PPA are20:06
sil2100If no one remembers, I'll follow up on that since I think we need to have this clarified in the documentation, so that we know exactly how the ACLs for this is managed. Since if the OEM archive is enabled for our main Ubuntu certified machines, I'd like to know that who can upload packages for them20:07
rbasakWas there any explicit approval for the TB for Ubuntu to enable the OEM archive through the Ubuntu archive?20:07
rbasak*by* the TB I mean20:07
mdeslaurSorry, I don't remember the OEM discussions20:07
mdeslaurpretty sure they were enabled before it was brought up to the tech board20:08
sil2100I was not part of the TB so I don't really know, the e-mail seems to say it was. Maybe this is worth revisiting? Should I investigate and we check back next meeting?20:08
rbasakI think you're raising good questions. So yes, that sounds good.20:08
sil2100Since I think it would be clear by checking the IRC logs and maybe poking Dimitri and Iain for some context20:08
sil2100Could you add an additional action item just so that I don't forget? Would be helpful!20:09
mdeslauryeah, I think we need to make sure we're ok with how that works, and how people get upload rights to it20:09
rbasakhttps://lists.ubuntu.com/archives/technical-board/2019-August/002456.html might be relevant20:09
rbasakThere's followup in October and January.20:10
rbasakAFAICT, it was already being done on "preinstalled Ubuntu" without any explicit involvement of the TB.20:10
sil2100True20:10
rbasakSo I suspect it's "Canonical" that can upload to the OEM archive with no further governance rules.20:10
rbasakhttps://lists.ubuntu.com/archives/technical-board/2020-January/002478.html has a summary20:11
sil2100Still, since we were involved in getting it done 'properly', I think we should at least have clear information about ownership here, and maybe also get to know a bit better about what policies such OEM archive uploads follow20:12
mdeslaur+120:12
rbasakYes please. And thank you for getting into this.20:13
sil2100Will try to gather as much info for the next meeting then o/20:14
rbasakOn the third party repository requirements thing, I think it's time I converted the pad into a written draft, now that we've got input from everyone.20:14
rbasakI'll do that next, and present that for further discussion.20:15
rbasakSo everything needs carrying over then, I guess?20:15
rbasak#topic Scan the mailing list archive for anything we missed (standing item)20:15
rbasakThere's "Setting NotAutomatic for hirsute+1-proposed" - do we have a decision on this?20:16
sil2100Let me take a look at that one again20:17
sil2100hm, ok, so I sadly missed some TB meetings, but was this brought up here or only on the ML?20:18
rbasakOnly on the ML so far20:18
mdeslaurwas anyone opposed to that? do we need to make a decision on it?20:19
rbasakBut we're on the IRC agenda topic that makes us look for open things on the ML :)20:19
rbasakI think we need to decide if/when to switch it on, and on which series20:19
rbasakEg. retrospectively for all releases now, or only for Jammy onwards now, or after Knotty opens and then retrospectively for previous releases after it's proven there, etc.20:21
sil2100I have no strong opinions regarding this, since I personally didn't have and didn't see anyone I know have problems with -proposed enabled20:21
rbasakIt'll immediately break pbuilder/sbuild users I think to make the change right now. They'll end up not picking up packages from -proposed I think.20:21
sil2100So I don't really know how much of an impact this has on users right now20:21
mdeslaurbesides vorlon mentioning he'd like it enabled in stable releases, was that really being considered?20:21
rbasakI don't think anything was considered except that it's now possible because Launchpad supports it. The details have been left to us.20:22
sil2100I know this sounds a bit lazy, but maybe we could bring this up again on the next meeting when vorlon is around? As he certainly has an opinion here20:23
rbasakSure, we can defer it20:23
mdeslauryeah, I don't mind turning it on on the dev release20:23
rbasakAlso it's only next week with the phase change20:23
mdeslaurbut I'd rather discuss it with vorlon around if it affects stable releases20:24
rbasakI don't see any other open ML posts, so I think that's it for this topic.20:24
rbasak#topic Check up on community bugs (standing item)20:24
rbasakThere are none.20:24
rbasak#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:25
rbasakNext chair will still be cyphermox, with I guess vorlon as backup.20:25
sil2100+1 o/20:25
rbasak#topic AOB20:25
mdeslaursounds good20:25
rbasakAnything else to raise?20:26
rbasak#endmeeting20:26
meetingologyMeeting ended at 20:26:22 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-01-18-20.01.moin.txt20:26
rbasakThanks all!20:26
mdeslaurthanks rbasak, sil210020:26
sil2100Thank you guys!20:26
xnoxrbasak:  sil2100: i don't think TB has ratify OEM archive implementation; beyond me sending two update emails; and like having a couple of IRC chats with TB; and DBM sorting out delegation / package set for the oem-metas uploads.21:09
xnox*has ratified21:09
rbasakxnox: thanks (and for your previous email summaries of the status!)21:14
=== mwhudson_ is now known as mwhudson
laneyPlease make sure to involve the wider dev community in the discussion, if the TB is taking responsibility for the NotAutomatic change (to be honest, I think it could be an archive/SRU team decision but...)22:18

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