16:00:05 #startmeeting FESCO (2017-06-16) 16:00:05 Meeting started Fri Jun 16 16:00:05 2017 UTC. The chair is maxamillion. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:05 The meeting name has been set to 'fesco_(2017-06-16)' 16:00:05 #meetingname fesco 16:00:05 The meeting name has been set to 'fesco' 16:00:05 #chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann 16:00:05 Current chairs: Rathann dgilmore jforbes jsmith jwb kalev maxamillion nirik sgallagh 16:00:08 #topic init process 16:00:10 .hello maxamillion 16:00:11 maxamillion: maxamillion 'Adam Miller' 16:00:20 .hello jforbes 16:00:21 jforbes: jforbes 'Justin M. Forbes' 16:01:02 hey 16:01:26 morning 16:01:32 .hello jsmith 16:01:37 jsmith: jsmith 'Jared Smith' 16:02:28 alright, we have enough folks 16:02:35 #topic #1690 Self Contained Changes (Sudo pip safety) 16:02:35 .fesco 1690 16:02:35 https://pagure.io/fesco/issue/1690#comment-444058 16:02:36 maxamillion: Issue #1690: F27 Self Contained Changes - fesco - Pagure - https://pagure.io/fesco/issue/1690 16:05:04 doesn't seem like this really got any movement on the mailing list :/ 16:05:59 * nirik is +1 for it as it affects packages I maintain a fair bit 16:06:37 I'm +1 16:07:04 did the questions get answered? 16:07:28 dgilmore: not that I'm seeing 16:07:39 We approved this for f26 and it got pushed to f27 right? 16:08:23 jforbes: yeah, but they redesigned/reimplemented the solution so things changed since last approval 16:08:31 yeah, they ran into some more problems than that though 16:08:33 thought 16:08:44 Right, just making sure this was the same end goal 16:08:59 I am good with the goal 16:09:16 I would like the open quiestions to be resolved 16:09:18 The number of "I cannot upgrade python*requests, your package is broken" bugs we get is pretty anoying... 16:09:35 (caused by user doing sudo pip install requests) 16:11:06 rgr 16:11:10 on the whole I'm in support 16:11:25 I'm +1 16:12:13 I am +1 as well. They seem more than willing to put things off if the approach doesn't work as intended, I don't see them bulldozing through issues without paying attention 16:12:24 however, we still never got answers to the concerns that caused us to defer last week 16:12:38 so ... I'm not sure what to do there 16:14:15 maxamillion: indeed 16:15:00 thoughts from the group? 16:15:38 what were the questions? 16:15:42 * nirik looks for them 16:16:04 I am good with acking the goal. But i would like to see the outstanding questions answered before acking the implementation 16:16:37 they were on devel@ i believe 16:17:39 yeah, they were on the devel@ thread ... there are concerns that were raised, and then re-raised based on our feedback from last meeting, and still no response 16:18:08 I don't see them 16:18:18 the last thread had some concerns, then a reply by change owner. 16:18:30 I understand the concerns listed there, but it doesn't seem like this is a new issue, and more of a "you are fixing one problem, but not fixing all of the problems" type thing 16:18:46 looks like there was an anwer wednesday 16:18:55 I tend to agree -- getting this fixed (even incompletely) is better than no fix at all... 16:19:10 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/OFPNLIYEVQWH7KHESJFMPDCZGXQVQAJX/ 16:19:11 dgilmore: I think you're the only one who hasn't voted 16:19:30 maxamillion: sorry catching up on devel@ to see whats going on 16:19:34 yes, I think this problem is well worth fixing even if it doesn't solve a bunch of problems 16:19:50 dgilmore: no worries, just pointing it out 16:20:19 i think given the response on list wednesday, i am +1 16:22:01 maxamillion: fin 16:22:09 #agreed FESCo Approves Self Contained Change: Sudo pip safety 16:22:17 #topic #1715 System Wide Change: Rsyslog log format change 16:22:17 .fesco 1715 16:22:17 https://pagure.io/fesco/issue/1715 16:22:19 maxamillion: Issue #1715: F27 System Wide Change: Rsyslog log format change proposal - fesco - Pagure - https://pagure.io/fesco/issue/1715 16:22:30 Any follow-up discussion on this? 16:22:41 maxamillion: what about the java self contained change? 16:22:56 dgilmore: that's new business, we're still doing follow ups 16:23:10 maxamillion: okay 16:23:25 jsmith: doesn't look like it 16:23:45 Yeah, I didn't find anything, and no update to the change page on the wiki :-( 16:24:06 I see no update there 16:24:06 are the change owners aware? perhaps @them in the ticket or mail them directly? 16:24:13 Proposal: Defer for one more week awaiting Change owner updates FESCo requested last week 16:24:21 maxamillion: +1 to your proposal 16:24:31 I'm not really here, but I want to chime in on this 16:24:53 The response I got back from the person proposing it was not encouraging. 16:25:12 They very clearly have no interest in addressing any of the potential fallout around this Change 16:25:27 I'm personally inclined to deny the Change outright, based on this. 16:26:01 sgallagh: if there's no motivation to address fallout, I would also be inclined to deny 16:26:20 thats sad. Not even offers to assist? sheesh 16:26:30 "When some package will break because someone adjusted format of timestamps, the bug is in that package and not in the rsyslog's format." 16:26:50 Yeah, so I'm firmly -1 to this Change 16:26:58 alright 16:27:32 well, that statement seems true to me... but if they offered to help fix things that would be something. 16:27:48 I would have to agree, that is an unpleasant attitude to take on it 16:28:36 Proposal: FESCo Rejects System Wide Change: Rsyslog log format change on the grounds that the Change owner has said they will not address nor help address the impact the Change will have System Wide 16:28:52 What we have is a person with a specific issue that they want fixed, but no indication that they care what happens to anyone else if this changes. 16:28:59 And no, that isn't a bug in the package, it is a lack of support for a change. Yeah, the package needs to be updated, but plowing through without care is a problem 16:29:13 * nirik wonders if this is just not miscommunication/language barrier 16:29:22 nirik: I'm wondering the same thing. 16:29:39 nirik: So I'm still inclined to wait another week, and try to get more communication from the change owner 16:29:41 I would like to give a fair opportunity to them to justify the change 16:29:46 nirik: We made a specific request and they said "no" 16:29:47 * nirik is with jsmith. 16:29:58 sgallagh: where did they say no? 16:30:47 dgilmore: I related our requests that they justify the request by populating the "Benefit to Fedora" with real reasons and also doing some due diligence on the fallout. 16:30:48 they didn't actually say no, they just said it was a bug in the other package... I guess that implys it... 16:30:57 I quoted the entire response above 16:31:29 but that doesn't say "... and we will not help or care about those bugs" 16:31:46 So I think we need to be fair 16:31:52 There are further comments along that 16:31:53 give them a chance 16:32:08 Where Roman's summary is "well, if someone's stuff breaks, they can change the config" 16:32:21 if they ignore or do not give sufficient feedback and update in the next week we reject it then 16:32:54 dgilmore: that seems fair 16:33:32 someone want to make a proposal for a vote? 16:34:03 I think a lot of the gruffness in the responses is likely language and cultural and not at all intended to come across as gruff and dismissive 16:35:29 That's possible, certainly. 16:35:31 proposal: Wait a week for changes. At least populating Benefit and addressing assistance with bugs in packages affected by fallout. 16:35:36 proposal #agreed FESCo asks that in the next week we get some of the benefits to fedora and our users laid out in the change, an outline of docs on how to manage things, and a commitment to help resolve conflicts and problems as they come up in the transistion 16:35:47 or what nirik said 16:35:54 yours is more detailed, thats fine 16:35:58 +1 dgilmore 16:36:01 Yeah, +1 dgilmore 16:36:21 +1 dgilmore 16:36:45 * sgallagh returns to not being here 16:37:08 dgilmore: +1 16:37:40 I will reach out to some folks in Brno to talk to him 16:37:54 to try break down cultural/language issues 16:38:14 maxamillion: I am +1 obviously 16:38:46 +1 dgilmore 16:39:09 #agreed FESCo asks that in the next week we get some of the benefits to fedora and our users laid out in the change, an outline of docs on how to manage things, and a commitment to help resolve conflicts and problems as they come up in the transistion (+1:5, -1:0, +0:0) 16:39:19 alright, onto new business 16:39:20 #topic #1690 Self Contained Changes (Java system/command setting) 16:39:20 .fesco 1690 16:39:20 https://pagure.io/fesco/issue/1690#comment-444058 16:39:21 maxamillion: Issue #1690: F27 Self Contained Changes - fesco - Pagure - https://pagure.io/fesco/issue/1690 16:39:36 I'm not a Java person my any stretch, but this feels a bit like a system-wide change to me 16:39:47 I am a bit confused what this actually is 16:40:28 it seems to be to have a way to change which java an application uses while leaving all others using the standard system java 16:41:04 well, other way... having a java always used by system apps (rpms) and a possibly different one by user installed stuff 16:41:18 I have no idea how they actually intend to solve the problem 16:41:19 right 16:41:45 I guess change the rpm packages to use a different java path/link 16:41:48 there is zero replies on list 16:42:02 well, it seems like it's a built-in virtualenv or rvm for ruby, but for jvm versions .... I just don't have any idea what the plan is on *how* to accomplish this 16:42:17 which makes it hard to decide on since I don't know what the actual change is 16:43:03 shall we punt a week and ask for more details on implementation? 16:43:19 I would prefer that 16:43:25 /usr/some/other/jave foo.jar 16:43:34 thats how I have always done it when need be 16:43:40 nirik: indeed 16:43:56 nirik: +1 16:44:26 +1 16:44:36 Proposal: Defer Self Contained Changes (Java system/command setting) until next week, requesting feedback from Change owners about implementation details and actual impact to Fedora 16:44:41 +1 16:44:45 ack 16:44:45 +1 16:44:52 +1 16:45:16 nirik: safe to assume a +1 from you? 16:45:23 +1 16:45:33 +1 to +1ing +1s 16:45:47 :D 16:45:55 #agreed Defer Self Contained Changes (Java system/command setting) until next week, requesting feedback from Change owners about implementation details and actual impact to Fedora (+1:5, -1:0, +0:0) 16:46:00 #topic #1716 Request to take over NetHack package 16:46:00 .fesco 1716 16:46:01 https://pagure.io/fesco/issue/1716 16:46:04 maxamillion: Issue #1716: Request to take over NetHack package - fesco - Pagure - https://pagure.io/fesco/issue/1716 16:47:00 assigning bugs requires fedorabugs permission I believe 16:47:29 +1 to just making them an admin of the package 16:47:43 I am +1 to giving them admin 16:47:53 nethack is mission critical, so more maintainers the better. 16:47:53 in the BZ comments, it looks like lmacken approved some fedpkg ACLs .... what's missing? 16:47:58 do not think it will solve the problem that had them ask 16:48:23 maxamillion: approveacls 16:48:29 ahhh ok 16:48:32 dgilmore: they likely want to be point of contact. 16:48:34 +1 to giving admin 16:48:53 jsmith: jforbes: ? 16:48:54 nirik: likely 16:48:59 they have fedorabugs 16:49:05 I am +1 to admin 16:49:07 so should be able to assign bugs to themselves 16:49:10 yeah 16:49:19 * dgilmore checked their account 16:49:40 +1 16:50:55 #agreed FESCo grants request to take over NetHack package by tachoknight 16:51:02 #topic #1717 provenpackager request for tdawson 16:51:02 .fesco 1717 16:51:03 https://pagure.io/fesco/issue/1717 16:51:06 maxamillion: Issue #1717: provenpackager request for tdawson - fesco - Pagure - https://pagure.io/fesco/issue/1717 16:51:20 I already did a +1 in the ticket, but I'll +1 again here 16:52:56 I worked with tdawson for about 3 years on the OpenShift Online Team and he's a very skilled packager, also as a side note he was one of the original two founders of Scientific Linux as well as maintaining his own RHEL rebuild for a while (now defunct: http://yorlinux.org/) 16:53:43 +1 16:54:13 +1 16:54:46 +1 here 16:56:11 hum, normally these don't come to meetings. ;) 16:56:25 but I usually handle them and I was out last week I guess. ;) 16:56:36 nirik: oh 16:56:46 You must get at least 3 positive votes with no negative votes, over a one week review period, to be automatically approved. 16:56:58 nirik: yeah, that's my bad 16:57:26 no worries. 16:57:32 * nirik can process it. 16:57:33 #agreed Approved: provenpackager request for tdawson (+1:5, -1:0, +0:0) 16:57:52 #topic Next week's chair 16:58:02 who's up? 16:58:45 I guess I can 16:59:08 when are the next elections? 16:59:53 no idea 17:01:00 should be after f26... 17:01:13 yeah, I just can't seem to find it in the wiki :/ 17:01:35 I'm happy to take next week's meeting if you don't want to, dgilmore 17:02:25 jsmith: all yours 17:02:58 #info jsmith to chair next weeks meeting 17:03:08 #topic Open Floor 17:04:34 I'll give it a few minutes and then close up shop 17:07:14 alright, thanks for coming all! 17:07:16 #endmeeting