15:05:25 #startmeeting FESCO (2018-12-17) 15:05:25 Meeting started Mon Dec 17 15:05:25 2018 UTC. 15:05:25 This meeting is logged and archived in a public location. 15:05:25 The chair is maxamillion. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:05:25 The meeting name has been set to 'fesco_(2018-12-17)' 15:05:25 #meetingname fesco 15:05:25 The meeting name has been set to 'fesco' 15:05:25 #chair nirik, maxamillion, jsmith, jforbes, zbyszek, tyll, sgallagh, contyk, bowlofeggs 15:05:25 Current chairs: bowlofeggs contyk jforbes jsmith maxamillion nirik sgallagh tyll zbyszek 15:05:25 #topic init process 15:05:32 .hello2 15:05:33 jforbes: jforbes 'Justin M. Forbes' 15:05:37 maxamillion: nope 15:05:46 morning 15:05:51 .hello2 15:05:52 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 15:06:09 .hello2 15:06:11 bcotton: bcotton 'Ben Cotton' 15:06:47 .hello2 15:06:48 maxamillion: maxamillion 'Adam Miller' 15:07:30 .hello2 15:07:31 bowlofeggs: bowlofeggs 'Randy Barlow' 15:08:18 .hello2 15:08:19 jsmith: jsmith 'Jared Smith' 15:08:53 alright, unless I miscounted we have quorum 15:09:49 #topic Follow Up Business 15:09:52 #topic #2020 Firefox is switching from gcc to clang/llvm 15:09:52 .fesco 2020 15:09:52 https://pagure.io/fesco/issue/2020 15:09:54 maxamillion: Issue #2020: Firefox is switching from gcc to clang/llvm - fesco - Pagure.io - https://pagure.io/fesco/issue/2020 15:10:06 so it seems this is a highly contentous issue 15:10:10 * nirik was just reading the flurry of comments in this from overnight 15:10:35 i found the linked blog post compelling, though as zbyszek pointed out there were patches required to achieve those numbers (and to get it to work at all?) 15:10:53 but the security claims i found to be the most compelling actually, though i must say i don't know a lot about them 15:11:07 Personally, I think we need to wait at least another week for things to settle a bit. Development is still happening. 15:11:20 yeah... 15:11:29 i would be ok with waiting a bit to see what shakes out 15:11:39 i would love to see a detailed write up of the security angle on this 15:11:45 that performance post was really nice 15:12:18 I would be interested to hear from the GCC folks on the patches there 15:12:20 should we just hold and move on? 15:12:38 bowlofeggs: +1 from me 15:13:23 jforbes: the two patches mentioned are already in gcc-8.2.1-6.fc{28,29,30} 15:13:44 Good to know 15:13:59 one of them was just to improve compile time 15:15:02 alright, anyone have a proposal they want voted on here? 15:15:27 bowlofeggs: +1 from me for moving on too. The decision from last week still stands, and I don't think there's enough new arguments to change it. 15:15:58 well i wonder if the security differences are enough new arguments 15:16:18 when we discussed this, i don't recall security being a consideration 15:16:40 and there are claims that clang doesn't support some security features that we do use from gcc 15:16:54 and of course, the browser is one of the most sensitive components of a desktop computer 15:16:59 proposal: wait until after the new year and revisit then 15:17:07 nirik: +1 15:17:10 nirik: +1 15:17:13 nirik: +1 15:17:24 nirik: +1 15:18:20 nirik: +1 15:19:21 #agreed: Revisit "Firefox is switching from gcc to clang/llvm" after the new year (+1: 6 -1:0, +0:0) 15:19:26 #topic New Business 15:20:14 #topic #2021 F30 Change: Migrate Python-based Nautilus extensions to Python 3 15:20:14 .fesco 2021 15:20:14 https://pagure.io/fesco/issue/2021 15:20:15 maxamillion: Issue #2021: F30 Change: Migrate Python-based Nautilus extensions to Python 3 - fesco - Pagure.io - https://pagure.io/fesco/issue/2021 15:21:18 I'm +1 to till's request for info 15:22:00 * nirik agrees with zbyszek's last comment. 15:22:06 agreed 15:22:42 WORKSFORME 15:23:35 Proposal: Wait until more information is provided as per https://pagure.io/fesco/issue/2021#comment-545919 15:23:40 +1 15:24:05 +1 15:24:18 +1 15:24:20 kalev: you happen to be around? 15:24:51 * zbyszek notes that there was no reply on the fedora-devel announcement, so this doesn't seem to be very controversial. 15:24:54 waiting is fine too... +1 15:25:36 i don't mind waiting, but i also feel like any extension that aren't ported to python 3 by now must not be important 15:25:47 i.e., i would vote +1 even knowing that some weren't ported 15:25:58 #agreed Wait until more information is provided as per https://pagure.io/fesco/issue/2021#comment-545919 (+1:6, -1:0, +0:0) 15:25:59 bowlofeggs: agreed 15:26:02 python2 eols in early 2020 15:26:18 #topic Next week's chair 15:26:30 "next week" isn't for a few weeks ☺ 15:26:35 I also doubt that we'll get much more info from waiting... but it's hard to vote no to a request for more details. 15:26:47 Right, there are eve's the next couple of meetings 15:26:56 bowlofeggs: the wiki page doesn't account for that ;) 15:27:00 is our next meeting jan 7? 15:27:12 That's already after elections right? 15:27:12 bowlofeggs: I think so yes 15:27:15 yes 15:27:20 oh right 15:27:42 So I think we should pick a volunteer from the subset that is certain to be there, to avoid confusion 15:28:15 my seat is good 'till next summer, so i can do it 15:28:44 this is my last meeting then 15:28:59 it's been an honor 15:28:59 oh man, that's sad 15:29:03 maxamillion++ 15:29:11 maxamillion++ 15:29:11 zbyszek: Karma for maxamillion changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:29:47 alright 15:29:47 maxamillion: Thanks for serving 15:30:05 #action bowlofeggs to chair next meeting 15:30:18 #topic Open Floor 15:30:52 thanks for everything maxamillion! 15:31:38 I'll still be around, just need to step back from FESCo so I didn't run again ... my time is even more constrained than it once was 15:33:03 alright, if nothing for open floor I'll light the fuse in about 2 minutes 15:38:12 #endmeeting