16:02:56 #startmeeting FESCO (2017-04-28) 16:02:56 Meeting started Fri Apr 28 16:02:56 2017 UTC. The chair is maxamillion. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:56 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:56 The meeting name has been set to 'fesco_(2017-04-28)' 16:02:56 #meetingname fesco 16:02:56 The meeting name has been set to 'fesco' 16:02:56 #chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann 16:02:56 Current chairs: Rathann dgilmore jforbes jsmith jwb kalev maxamillion nirik sgallagh 16:02:59 #topic init process 16:02:59 nirik: sorry 16:03:05 no worries. :) 16:03:10 morning 16:03:17 .hello sgallagh 16:03:18 sgallagh: sgallagh 'Stephen Gallagher' 16:03:18 .hello jforbes 16:03:21 jforbes: jforbes 'Justin M. Forbes' 16:03:39 .hello maxamillion 16:03:40 maxamillion: maxamillion 'Adam Miller' 16:06:38 how long to we wait? 16:07:22 maxamillion: We have quorum, so up to you 16:07:31 oh wait, we do have quorum 16:07:32 * maxamillion derp 16:07:37 I counted 4 at first 16:07:41 #topic #1699 xml-security-c new maintainer 16:07:41 .fesco 1699 16:07:42 https://pagure.io/fesco/issue/1699 16:07:42 maxamillion: Issue #1699: meeting: xml-security-c new maintainer request - fesco - Pagure - https://pagure.io/fesco/issue/1699 16:07:58 this is a follow up from last week that was still on the agenda 16:08:23 Right, we couldn't look at anything because bz/pkgdb/etc were down 16:08:32 correct 16:09:18 I remember a mailing list discussion about this which basically went along the lines that 16:09:50 "Hi, I talked to anttix and he is ok with someone working on xml-security-c to bring it up to date, is anyone interested?" 16:10:24 and no one was? ;) 16:10:25 and then someone showed up and said that the maintainer doesn't respond in bugzilla 16:10:39 no, someone was interested, I think that's the person who filed the fesco ticket now 16:10:53 https://admin.fedoraproject.org/pkgdb/packager/anttix/ shows they are point of contact for 3 packages 16:11:46 * dgilmore is here 16:12:06 But I do see them listed on the package in question now 16:12:16 aha, found the original discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NUGEJ5SYOT2LKURY4P33YHMWNNDVX52L/ 16:12:30 https://admin.fedoraproject.org/pkgdb/package/rpms/xml-security-c/ shows kloczek as an administrator 16:12:55 Which tells me there is nothing else to do here. 16:13:12 ohh, indeed 16:13:40 jforbes: +1 16:13:47 yeah. nothing to do unless we want to orphand the others... which sounds like we don't 16:14:00 They didn't follow the non-responsive maintainer policy, even after being asked to 16:14:12 jforbes: correct 16:14:27 So I recommend that we leave as is and close the ticket 16:14:33 +1 16:14:34 jforbes: +1 16:14:50 +1 16:15:04 +1 16:15:24 +1 16:16:47 #agreed - xml-security-c new maintainer request - leave as is, administrator already updated (+1:6, -1:0, +0:0) 16:16:55 #topic #1653 Better communicating roles and responsibilities of FESCo for elections 16:16:58 .fesco 1653 16:16:59 maxamillion: Issue #1653: [Meta] Better communicating roles and responsibilities of FESCo for elections - fesco - Pagure - https://pagure.io/fesco/issue/1653 16:17:00 https://pagure.io/fesco/issue/1653 16:18:08 oh this just needs adding. 16:18:10 I can do that 16:18:15 nirik: +1 thanks 16:18:20 Oh, that was left open because the wiki was down 16:18:24 thanks nirik 16:18:34 #info nirik to update the wiki 16:18:42 #topic #1690 F27 Self Contained Changes - Java 9 16:18:43 .fesco 1690 16:18:43 https://pagure.io/fesco/issue/1690#comment-438338 16:18:44 maxamillion: Issue #1690: F27 Self Contained Changes - fesco - Pagure - https://pagure.io/fesco/issue/1690 16:19:14 ack to java9 16:19:41 +1 to java9 16:19:42 +1 java9 16:19:45 +1 to java9 16:20:35 nirik: sgallagh: ? 16:20:44 +1 16:21:52 sgallagh: ? :) 16:22:19 +1 16:22:26 Sorry, got disconnected. 16:22:40 -1 internet 16:22:49 heh 16:23:32 #agreed - APPROVED: F27 Self Contained Changes - Java 9 (+1:6, -1:0, +0:0) 16:23:40 #topic #1702 Fedora support_url 16:23:40 .fesco 1702 16:23:40 https://pagure.io/fesco/issue/1702 16:23:41 maxamillion: Issue #1702: Fedora support_url - fesco - Pagure - https://pagure.io/fesco/issue/1702 16:24:18 I do think it is a bug in the desktop that it requires an optional field in /etc/os-release 16:24:43 and I think we really do not have a support url 16:25:02 I am a big fan of the Getting Help link if we do need something 16:25:09 but i figured that FESCo should decide if we have one and if we do what it is 16:25:37 jforbes: +1 16:25:39 jforbes: I do not think we have to have one 16:25:52 but I can go with that 16:26:00 I like the idea of having one, it's difficult for people who are brand new to know where to go without some guideance 16:26:09 If we have one, I think the wiki I posted is the closest. 16:27:10 https://fedoraproject.org/wiki/Communicating_and_getting_help 16:27:13 for the record 16:27:34 indeed 16:28:04 so while not really a support url. its a good pointer 16:28:38 Well, I don't actually see any downside of having one, particularly when it is a "help you help yourself" reference such as this. 16:28:51 jforbes: right 16:29:37 proposal #agreed FESCo has agreed that https://fedoraproject.org/wiki/Communicating_and_getting_help is the official support url 16:29:45 dgilmore: +1 16:29:56 +1 16:30:23 +1 16:30:35 +1 16:31:37 sure, +1 16:31:42 #agreed FESCo has agreed that https://fedoraproject.org/wiki/Communicating_and_getting_help is the official support url (+1:6, -1:0, +0:0) 16:31:48 we might want to make a pass over it and make sure it's all up to date. ;) 16:32:08 +1 16:32:10 probably should yeah 16:32:16 I'll do that this afternoon 16:32:23 maxamillion++ 16:32:26 sgallagh: Karma for maxamillion changed to 17 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:32:46 #info maxamillion to check https://fedoraproject.org/wiki/Communicating_and_getting_help is up to date 16:32:55 #topic Next week's chair 16:33:31 who's up? 16:33:45 I haven't done this in a while, happy to be the chair next week 16:33:55 gracias kalev 16:35:34 #info kalev to chair next week's meeting 16:35:43 #topic Open Floor 16:35:50 I'll be on an airplane during the meeting next week so there's a reasonable chance I won't make it 16:35:54 I will try though :) 16:36:56 I have one quick thing 16:37:12 planning to enable s390x in primary koji this weekend 16:37:18 rocking 16:37:26 there has been a few queries if we should do f26 also 16:37:38 * Pharaoh_Atem pops in 16:37:52 * nirik would like that, but I know it's late in the f26 cycle 16:37:53 it'd be cool if s390x was enabled in primary koji for f26, too 16:38:02 I feel like it is too late in f26 to make the change, but if FESCo felt we should I would support it 16:38:10 dgilmore: I'd vote yes unless there are any real show stoppers ... I can't think of a reason not to other than it's kind of late in the cycle 16:38:12 I think it's a bit too late for f26 16:38:16 why? 16:38:31 other than "lateness", why can't it be moved to primary koji? 16:38:35 I do think its too late 16:38:52 because of the possibility of unkown bugs to cause a slip 16:39:06 right, if some release blocking thing broke only on s390 it would be a pain to try and scramble to fix it now. 16:39:07 we are already quite delayefd 16:39:13 Pharaoh_Atem: being this late in the cycle leaves a shorter runway to fix unforseen/unkonwn issues 16:40:06 as much as I would love to kill off all the alt arch hubs sooner. I think we should wait 16:40:12 but a big +1 to enabling it in rawhide 16:40:20 dgilmore: well, we do have a bit until beta tho... 16:40:21 nice to get everything together into primary koji 16:40:36 it will be the last step in the alt arch redefinition change 16:40:56 how about this: 16:41:21 see how the rawhide merge goes and if it's smooth do f26? 16:41:31 but I am not sure we can easily quantify smooth 16:41:48 maxamillion: what could go wrong? 16:41:59 the process has been pretty well-ironed for all the other arches right? 16:42:06 Pharaoh_Atem: bugs in software 16:42:15 a lot 16:42:29 we have not to date built s390x insallers in a long time 16:42:43 :/ 16:42:43 they may be completely broken 16:42:57 it is very risky 16:43:20 I'm with nirik here. I would rather defer this decision until we see how badly it goes for Rawhide. 16:43:39 we still wait for a firewall change to re-enable f26 composes in the s390 koji setup ... 16:43:40 but that would also leave us even less time. ;) 16:44:05 nirik: indeed 16:44:20 I would say we will know how good s390x is in a week or 2 16:44:31 at which point we are right on top of beta freeze 16:44:34 which takes us to beta freeze. So yeah. 16:44:48 :/ 16:45:42 dgilmore: would it be possible to merge f26 at GA point? do release in old setup, but build updates in merged koji? 16:45:43 OK, so formal proposal: Enable s390x support in Rawhide only. 16:45:51 +1 16:45:55 +1 16:46:02 +1 16:46:05 sharkcz: maybe 16:46:22 +1 16:46:24 +1 16:46:30 ok I guess. makes me sad to miss f26, but such is life. 16:47:07 nirik: is that a +1? 16:47:25 sure 16:49:52 #agreed Enable s390x support in Rawhide only - (+1:6, -1:0, +0:0) 16:50:13 alright, anything else for Open Floor? 16:50:19 nada 16:50:24 nothing from me 16:50:55 nothing here 16:52:33 alright, thanks all! 16:52:36 #endmeeting