#ubuntu-meeting-2 2016-05-24
 * slangasek waves
<mdeslaur> \o
 * stgraber waves
<mdeslaur> hrm, no kees, no infinity
<mdeslaur> ok, let's get this started anyway
<mdeslaur> #startmeeting
<meetingology> Meeting started Tue May 24 16:02:23 2016 UTC.  The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<mdeslaur> [topic] Action review
<mdeslaur> slangasek to chase the juju team about creating https://wiki.ubuntu.com/JujuUpdates
<slangasek> that wiki page exists now :)
<slangasek> needs some iteration, which I'll take up with the Juju QA team by email
<slangasek> but maybe can come off the nag list now
<mdeslaur> ok, cool
<mdeslaur> I'll carry forward infinity's actions
<mdeslaur> mdeslaur to look into flavour CVE tracking
<mdeslaur> haven't had time to poke at that, carry forward
<mdeslaur> hi kees!
<kees> hola!
<slangasek> shoot, we didn't go fast enough to give kees all the action items before he got here
<mdeslaur> we've started already
<mdeslaur> hehe
<mdeslaur> [topic] Mailing list archive
<mdeslaur> doesn't look like there's anything on the list
<mdeslaur> besides the last post, which I'll respond to
<mdeslaur> [topic] Community bugs
<mdeslaur> no community bugs
<mdeslaur> does anyone have AOB?
<slangasek> I do not
<stgraber> nothing here
<mdeslaur> [topic] Next chair
<mdeslaur> slangasek, with stgraber as backup
 * slangasek nods
<mdeslaur> ok, looks like we're done
<mdeslaur> #endmeeting
<meetingology> Meeting ended Tue May 24 16:08:45 2016 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-05-24-16.02.moin.txt
<mdeslaur> thanks everyone
<slangasek> short and sweet
<slangasek> thanks, mdeslaur
<stgraber> thanks
#ubuntu-meeting-2 2017-05-23
 * stgraber waves
<mdeslaur> o/
 * slangasek waves
<infinity> \o
<mdeslaur> looks like kees is MIA
<mdeslaur> let's get started
<mdeslaur> #startmeeting
<meetingology> Meeting started Tue May 23 16:00:05 2017 UTC.  The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<mdeslaur> [topic] Action review
<mdeslaur> infinity, slangasek: any progress on your items?
<slangasek> none
<slangasek> but my guilt levels are rising appropriately
<infinity> As usual, I reminded myself of action items 5 minutes before the meeting.  I've pinged roaksoax to get the MaaS thing finally sorted.
<mdeslaur> heh, ok
<infinity> The other item, I did a ninja wiki edit of s/16.04.2/16.04.3/ :P
<slangasek> heh
<mdeslaur> infinity: perhaps just bump it to 16.04.5 right away? :)
<infinity> Shush you.
<mdeslaur> hehe
<mdeslaur> #topic Mailing list archive
<mdeslaur> doesn't look like there's anything new
<mdeslaur> #topic Community bugs
<mdeslaur> no open bugs
<mdeslaur> #topic AOB
<mdeslaur> anyone have anything to discuss?
<slangasek> not I
<stgraber> nothing here
<infinity> Can we drop Go from the archive?
<infinity> If not, then I have nothing to discuss. :P
<mdeslaur> heh
<mdeslaur> #topic Next chair
<mdeslaur> slangasek with stgraber as backup
 * slangasek nods
<mdeslaur> #endmeeting
<meetingology> Meeting ended Tue May 23 16:04:37 2017 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2017/ubuntu-meeting-2.2017-05-23-16.00.moin.txt
<mdeslaur> thanks!
<slangasek> kees: LATE
<infinity> kees: You missed it.
<kees> whoops, late
<kees> haha
<slangasek> :)
<kees> saw the "thanks" and started laughing
<slangasek> fwiw in 2 weeks time our team is sprinting, so I may be an unreliable meeting narrator
<infinity> kees: You have AOB before we all /part?
<kees> infinity: nope, all good.
<mdeslaur> slangasek: I'll handle it if you don't show up
<infinity> kees: You might be happy to know that we're finally PIE on all arches.
<slangasek> mdeslaur: isn't stgraber supposed to? :)
<kees> infinity: \o/ \o/
<slangasek> infinity: has that flip been switched?
<slangasek> (and I never got an answer to my email asking who would coordinate rebuilds)
<infinity> slangasek: Yeah, doko got all keen and did it on Saturday, I followed up with a dpkg so the world didn't explode.
<kees> https://outflux.net/ubuntu/hardening/ubuntu-hardening-5years.png
<slangasek> ok
<stgraber> slangasek: I'll be sprinting too :)
<mdeslaur> slangasek: won't he be at the same sprint?
<slangasek> mdeslaur: not the same one no
<mdeslaur> oh, heh
<stgraber> different sprints, same week
<mdeslaur> well, we'll figure it out
<stgraber> it was supposed to be the same sprint originally, but that didn't quite happen
<kees> I changed how my PIE-analysis tool credited PIE packages, so there was quite a bump recently (if package is all .so's and no binaries, count as PIE. If a single ET_EXEC exists, no PIE for you)
<slangasek> yeah, conference bookings went a bit sideways across the reorg
<infinity> stgraber: Sadness.  I don't think we've hung out in a long while.
<slangasek> kees: ahh ok
<stgraber> infinity: been a while indeed, Seville was the last one I think
<slangasek> I was going to say, I know I didn't have *that* many in my mass-rebuild
<kees> slangasek: this is only amd64, so it'll likely not show much change
<slangasek> kees: I mean the mass-rebuild we did right around 17.04 release
<slangasek> which is probably the second smaller tick on your graph
<kees> oh! that likely did help, yes.
<slangasek> (main-only)
<infinity> kees: Any urge to run stats for i386, so we can see where we need to apply abuse?
<infinity> (or armhf or arm64, they should all be in the same state)
<kees> I would suspect the two steps here are rebuild and script-adjust: https://outflux.net/ubuntu/hardening/ubuntu-hardening-month.png
<kees> infinity: In theory I should be able to do i386, just requires some script-bashing
<infinity> slangasek: I admit to being somewhat ignorant about the bits that need staged rebuilds.  Something to do with static linked bits?
<slangasek> or some bash scripting?
<kees> https://outflux.net/ubuntu/hardening/main/ had some unreliable data that I didn't try fixing
<slangasek> infinity: yes
<infinity> I don't think I was involved in that part for the previous arches.
<kees> but the _current_ result is accurate, I think, for amd64 main
<slangasek> infinity: basically, when we turned on PIE, we had a long tail of opaque build failures that required tracking down and rebuilding static libs in order to fix
<kees> i.e. 96% PIE
<slangasek> and nobody really took systematic notes on this
<infinity> kees: Nice.  I, too, am 96% pie.
<slangasek> hahaha
<kees> haha
<slangasek> so while we could just say "if it has a static lib that's not PIE, rebuild it", that's going to hit pretty much every library package in the archive instead of the ones that actually have static revdeps
<infinity> slangasek: So, I guess maybe the next step, if we have no notes, is a rebuild test that we can unwind.
<slangasek> infinity: I was going to suggest doing archive analysis for -dev build-deps that don't translate into runtime deps
<slangasek> should we take this to #-devel? :)
<infinity> slangasek: Sure.
#ubuntu-meeting-2 2018-05-22
<redter53> !ops
<redter53> !op
<redter53> !ops
<redter53> !ops
<re432> !ops
 * slangasek waves
 * jbicha waves back
<infinity> o/
<slangasek> so technically, we do not have a seated TB at the moment
<slangasek> because all of our terms have expired
<slangasek> anyone have anything they want to chat about off the record? :)
<infinity> Oh, did they again?
<slangasek> infinity: oh, did you secure a renewal?
<slangasek> oh ok, we've been extended until June 3
<slangasek> but I haven't seen anyone call for an election yet
<infinity> Might be time for another extension. :P
<infinity> Viva la democracy.
<infinity> Can we just rename this body to the sabtbfl?
<slangasek> ok, well we could in theory have a meeting then
<slangasek> but currently only 2 of us are here
<infinity> We could do, but only with... That.
<slangasek> https://community.ubuntu.com/t/open-discussion-meetings-quorum/5966
<slangasek> :)
 * stgraber waves
<slangasek> ok now there's 3 of us, I guess we might have to gavel in
<slangasek> #startmeeting
<meetingology> Meeting started Tue May 22 19:07:27 2018 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
<meetingology> Available commands: action commands idea info link nick
<stgraber> sorry :)
<slangasek> (I'll go ahead and chair; I think I ran the last one I attended, but also there were no logs because of someone vandalizing the bot, and no one updated the wiki page, so...)
<slangasek> [TOPIC] Apologies
<slangasek> none recorded
<infinity> stgraber beat that topic.
<slangasek> [TOPIC] Action review
<slangasek> infinity: heh
<slangasek> ACTION: flexiondotorg To follow-up on-list with design review to address MATE Boutique security/consent concerns.
<slangasek> oops, that needs amended
<infinity> That action seems old.
<slangasek> ACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
<slangasek> there I fixed it
<mdeslaur> sorry
<slangasek> infinity: it's old but there still hasn't been any on-list follow-up
<slangasek> Wimpress said there is work in progress, but given that this was driven by TB concerns about security UX, I don't think it should fall off our nag list
<infinity> Check.
<slangasek> ACTION: infinity to call for confirmation of LTS status from all flavours.
<infinity> Done.
<slangasek> I'm hoping we can consider that done
<slangasek> ACTION: infinity to ask maas team to prepare SRU exception policy Ã  la CurtinUpdates
<infinity> Carry.
<slangasek> infinity: ok.  while sprinting earlier this month, there was a MAAS SRU referencing https://wiki.ubuntu.com/MAASUpdates; so it would be good to have that formalized
<slangasek> ACTION: slangasek and mdeslaur to more clearly define third party seeded snap security policy
<slangasek> mdeslaur: did you do this when I wasn't looking? ;)
<mdeslaur> uh, no ;(
<slangasek> ok ;)
<slangasek> so, carry
<slangasek> ACTION: tsimonq2 to email proposed policy for flavor-notification of daemons being added to all flavors (e.g. snapd into desktop-common)
<tsimonq2> Darn it.
<slangasek> tsimonq2: ^^ I don't recall seeing an email about this, so here's a formal TB nag
<tsimonq2> To be fair, flavor relationships have changed.
<tsimonq2> I'll bring it up.
<tsimonq2> Thanks.
<slangasek> tsimonq2: changed how?
<infinity> Was it not discussed when it was added to desktop-common, and maybe lubuntu just opted out of the discussion because they were (incorrectly, IMO) not using -common at the time?
<infinity> I absolutely stand by the assertion that desktop-common should be common to *all* *buntu desktops, so if we're adding things there, concensus should be found.
<tsimonq2> slangasek:
<infinity> (just as minimal and standard are common to all flavours)
<tsimonq2> We communicate a lot more. #ubuntu-flavors among other things is now there, so we talk regularly now. I'll bring it up.
<slangasek> infinity: snapd was not discussed with the flavors before addition to desktop-common, no; we had a conversation at a previous meeting about why that was, and the outcome was for tsimonq2 to propose a policy on how to handle this
<infinity> slangasek: Ahh, kay.  So this is an old action, not a result of my foisting desktop-common on lubuntu with the recent seed shuffle.  Kay.
<tsimonq2> infinity: And with >= Cosmic, I do agree.
<slangasek> tsimonq2: #ubuntu-flavors is not the right venue for such a thing (and though my objection counts for little, I object to creating a new IRC channel for this); the proposal should happen on the existing central mailing lists
<tsimonq2> I would (somewha
<tsimonq2> grr /me returned early
<infinity> I would also (somewha
<tsimonq2> lol
<infinity> For the right price.
<slangasek> I mean, discuss to your heart's content, but the proposed policy should go to techboard and ubuntu-release/ubuntu-devel
<infinity> I definitely don't mind -release being used by flavour leads for inter-flavour policy, and obviously devel/devel-discuss when you want wider input than just fellow leads.
<tsimonq2> I would agree that the IRC channel isn't the right place, but in general, conversation about how exactly to go about this needs to happen in a more formal place. I was just noting the IRC channel as an example of ways flavors are collaborating more nowadays.
<slangasek> yes
<infinity> -release is very low traffic, and I consider that on-topic with those hats on.
<slangasek> moving on
<tsimonq2> slangasek: I'm agreed on where to send the policy.
<tsimonq2> OK, thanks TB.
<slangasek> tsimonq2: ok, grand :)
<slangasek> [TOPIC] Review of the seeded snaps policy
<slangasek> this is a carry-over on the agenda and probably doesn't need any discussion today, given mdeslaur's and my action item
<slangasek> however I'm going to leave it on the agenda page for next time so that I have appropriate levels of guilt about getting that done
<slangasek> [TOPIC]  LP: #1770748: Dropping patches added for main inclusion and delegation of maintainership
<jbicha> doko_: are you around?
<slangasek> this was added to the agenda by doko_, who informed me earlier today that he would not be able to attend the meeting
<slangasek> I don't know that we need to tackle this without all the parties to the discussion present
<slangasek> unless some member of the TB is particularly keen to dive into the topic right now?
<jbicha> I felt it was premature for a TB decision on the issues
<seb128> I don't think there is much for the TB there either
<infinity> I think it could have been settled by two adults in #ubuntu-devel without escalating, but maybe not. :P
<slangasek> jbicha: fwiw I don't necessarily think the TB needs to decide on this; I redirected doko from myself to the TB because doko appeared to have invoked me to throw my weight around on the issue, and I declined to do so in a personal capacity
<jbicha> I phrase the issues a bit differently than do_ko
<slangasek> jbicha: if you and doko come to some sort of agreement that you're both happy with, that's fine.  I think there are also policy questions that are larger than the particular disagreement between you and doko, and we may still want the TB to provide guidance
<jbicha> I see 2 issues: whether C++ libraries in main must have symbols files; and whether Foundations should "own" (or "maintain" or whatever) ilmbase
<infinity> jbicha: FWIW, while I don't agree with his handling (and escalation) of the issue, I do agree that it you were tired of waiting around for him to merge, you probably should have merged with symbols files, not synced.
<jbicha> the symbols file question is being discussed on the ubuntu-devel list
<seb128> jbicha, I don't think the packages "ownership" is a TB matter
<infinity> The secondary question of the usefulness of symbols files in C++ projects (especially ones with questionable symbol visibility policies) is definitely not something I think the TB needs to weigh in on.
<jbicha> I hear that Desktop & Foundations teams are going to have a meeting soon to discuss various issues so the ownership issue can be discussed there
<slangasek> jbicha: the question of what team owns a package for purposes main is indeed not a TB question, since main is a matter of Canonical sponsorship
<slangasek> "for purposes main" oh look I'm accidentally 18th century English
<mdeslaur> heh
<infinity> That construct is back in vogue in 21st century en_GB.
<infinity> You're hip.
<infinity> In the wrong country.
<jbicha> interestingly, acheronuk added a debdiff to the bug to add the symbols. Someone could upload that to resolve some of the issue or lower the urgency
<infinity> jbicha: More importantly than re-adding the symbols files is actually auditing the changes between old and new, since that's the point of symbols files in the first place.
<infinity> If we're just going to effectively delete and regenerate them on each upload, they're entirely useless.
<jbicha> I'm not interested in sponsoring it at this point because I'm interested in resolving the question of whether the symbols file is mandatory (for future uploads)
<mdeslaur> being mandatory and removing them is two different things
<slangasek> so I'm shying away from that question for the moment because I don't think we should have a partial discussion without all parties present
<infinity> jbicha: I'm not deeply interested in diving into the list discussion, but I think making symbols files truly useful in Debian/Ubuntu C++ packages might first need some Debian library policy surrounding best practices for symbol visibility.
<jbicha> mdeslaur: it was Debian that removed the symbols file and do_ko added it back without discussion
<slangasek> I mean, I can opine, but in the context of the current TB meeting I think we should postpone
<infinity> jbicha: C++ symbols files can be quite clean if your project doesn't export a ton of pointless cruft it shouldn't.
<jbicha> https://launchpadlibrarian.net/371130484/restoresymbols.debdiff
<slangasek> point of order ;)
<slangasek> if we want to argue this as individual core devs instead of as the TB, could we defer it until after we close out this meeting?  or if you're disagreeing with me about postponing, then I'll dive full in
<jbicha> +1 from me for postponing
<infinity> Right, I'll shut up. ;)
<slangasek> ok :)
<slangasek> [TOPIC] Scan the mailing list archive for anything we missed (standing item)
<slangasek> [LINK] https://lists.ubuntu.com/archives/technical-board/2018-May/thread.html
<slangasek> DMB members stuff, strictly administrative, has been handled
<slangasek> wxl's request for input on quorum - I followed up, I think my comments uncontroversial but https://community.ubuntu.com/t/open-discussion-meetings-quorum/5966/5 if anyone else wants to weigh in
<slangasek> nothing else on list
<slangasek> [TOPIC] Check up on community bugs (standing item)
<slangasek> [LINK] https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
<slangasek> zarro boogs
<slangasek> [TOPIC] Select a chair for the next meeting
<slangasek> is that stgraber, with infinity backup?
<infinity> +1
<stgraber> fine :)
<slangasek> technically, we all expire the Sunday before that
<infinity> Well, +0.5
<infinity> Because I haven't made a short joke in MONTHS.
<slangasek> who wants to prod about extension + election?
<infinity> slangasek: I'll get us extended again, if you promise to chase down sabdfl about an election.
<mdeslaur> lol
<slangasek> [ACTION] infinity to get TB terms re-extended
<meetingology> ACTION: infinity to get TB terms re-extended
<slangasek> [ACTION] slangasek to chase sabdfl / CC about election
<meetingology> ACTION: slangasek to chase sabdfl / CC about election
<slangasek> [AGREED] next TB meeting, 2018-06-05, 20:00 BST. chair stgraber, backup infinity
<slangasek> [TOPIC] AOB
<slangasek> anything else?
<slangasek> #endmeeting
<meetingology> Meeting ended Tue May 22 19:34:29 2018 UTC.
<meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2018/ubuntu-meeting-2.2018-05-22-19.07.moin.txt
<mdeslaur> thanks everyone
<slangasek> stgraber, infinity, mdeslaur, jbicha, seb128, tsimonq2: thanks!
<seb128> thanks!
<infinity> slangasek: Re-extension in progress.
<tsimonq2> Thanks!
<tsimonq2> slangasek: I forget, what was the rationale for defining the policy I'm drafting as daemons, not packages in general? I mean, how often is that file *really* updated?
<slangasek> tsimonq2: the reason was that snapd's daemonness was the bit problematic to flavors, and in general I don't think we need to get flavor signoff on individual packages added there
<tsimonq2> slangasek: ACK.
<tsimonq2> slangasek: wxl asked on the community hub post I made, so pinged you. Please elaborate if you could.
<slangasek> tsimonq2: url?
<tsimonq2> slangasek: https://community.ubuntu.com/t/official-policy-for-adding-daemons-to-desktop-common/6086?u=tsimonq2
#ubuntu-meeting-2 2020-05-19
<mdeslaur> \o
 * vorlon waves
<vorlon> mdeslaur: just the two of us again, I think
<mdeslaur> maybe we should get the hint that nobody likes our parties anymore
<Eickmeyer> Well, that's a bummer. I was hoping bug 1878700 would get addressed.
<ddstreet> yeah I'm here to ask about that as well
<ddstreet> also https://bugs.launchpad.net/ubuntu-community/+bug/1873039
<mdeslaur> oh, we can do that
 * genii consults the Fridge to see what meeting this is
<Eickmeyer> genii: It's supposed to be TB
<genii> Eickmeyer: Yes, I see now, thanks :)
<Eickmeyer> (the Fridge was broken for me)
<mdeslaur> Eickmeyer, ddstreet: one sec, I'm doing them
<Eickmeyer> ack
<mdeslaur> Eickmeyer, ddstreet: done
<Eickmeyer> mdeslaur: Thanks!
<ddstreet> thanks!
<mdeslaur> np!
