16:00:00 #startmeeting FESCO (2017-05-26) 16:00:00 Meeting started Fri May 26 16:00:00 2017 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:00 The meeting name has been set to 'fesco_(2017-05-26)' 16:00:00 #meetingname fesco 16:00:00 The meeting name has been set to 'fesco' 16:00:00 #chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann 16:00:00 Current chairs: Rathann dgilmore jforbes jsmith jwb kalev maxamillion nirik sgallagh 16:00:00 #topic init process 16:00:13 .hello 16:00:13 mprahl: (hello ) -- Alias for "hellomynameis $1". 16:00:18 .hello mprahl 16:00:19 mprahl: mprahl 'Matt Prahl' 16:00:24 .hello sgallagh 16:00:25 sgallagh: sgallagh 'Stephen Gallagher' 16:00:25 .hello jforbes 16:00:28 jforbes: jforbes 'Justin M. Forbes' 16:01:27 * nirik waits to see if we have quorum. 16:02:10 * threebean 16:04:01 jwb / dgilmore / jsmith ? 16:04:11 (I know maxamillion is out today) 16:04:54 hi 16:05:13 thats 4... we need one more for quorum... 16:07:01 so we could cancel due to lack of quorum, but there's at least the arbitrary branching which is under a very short deadline... 16:07:19 Sorry, out today. Have to get kids for 1/2 day 16:07:27 On my phone right now 16:08:06 jwb: ok, should we consider you not here for quorum purposes? 16:09:01 he said out today 16:09:10 yeah. 16:09:42 mprahl / threebean: how much would another week hurt your plans? perhaps we should discuss and try and gather more votes in ticket? 16:10:05 * threebean thinks 16:10:24 well, our date for pagure on dist-git already got pushed by a few weeks to July 5th 16:10:31 .. for other reasons. 16:10:42 we also slipped a week on beta... 16:11:21 nirik: we were going to submit an FBR to put the banner ad on pkgdb today and send something out to devel-announce. that's the only work items that are really blocked by the fesco decision. 16:11:35 mprahl: is that correct? can we still advance work on other bits in the meantime? 16:11:42 FBR? 16:11:46 freeze-break-request 16:11:49 Ah 16:11:55 for fedora infrastructure. 16:12:02 nirik: Can we talk about it today to make sure there are no additional concerns that come up with our timeline and wiki page please? 16:12:15 #topic #1708 - F27 System Wide Change: Arbitrary Branching 16:12:16 .fesco 1708 16:12:16 https://pagure.io/fesco/issue/1708 16:12:16 threebean: getting it communicated now is a big +1 16:12:16 nirik: Issue #1708: F27 System Wide Change: Arbitrary Branching - fesco - Pagure - https://pagure.io/fesco/issue/1708 16:12:20 I don't think we need an answer today though 16:12:36 mprahl / threebean: can you go over what you added in the last week? 16:12:57 I am still extremely concerned over the removal of pkgdb on such a tight schedule 16:13:09 for one, we tried to list out a more detailed timeline at the bottom of the Change here https://fedoraproject.org/wiki/Changes/ArbitraryBranching#Timeline 16:13:50 dgilmore: We pushed the date back to July 10th. Does that help your comfort level at all? 16:13:51 dgilmore: yeah, it is tight for sure. ;( But less stuff to maintain is good... 16:14:13 mprahl: not at all 16:14:34 mprahl: I would like at least one full fedora cycle 16:14:42 and for things to be phased in 16:15:37 ok - our takeaway from last week was that the main concern from fesco was over announcement/education. 16:16:00 Well, that was the consensus. 16:16:01 I thought there were reasons it couldn't be phased in... 16:16:13 Right 16:16:19 nirik: yeah, not without going back to the drawing board. 16:16:53 nirik: We'd have to rewrite PkgDB to phase it in and even then I wouldn't really consider that phasing in unfortunately. 16:16:54 right. 16:17:01 (towards education, mprahl started putting together a FAQ on how to use the new bits https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_do_I_give_a_user_commit_access_to_a_dist-git_repo.3F ) 16:18:28 lots of TODO's still. ;) 16:19:41 I think it's a pretty short ramp, but I'm ok with it in general. I think you may get a bunch more feedback from posting to devel-announce... as lots of people I think have just been ignoring modules until they affect them... which this will do. ;) 16:20:09 heh, yeah. 16:20:45 is there any sense of progress on the pagure over dist-git work? I've not seen much going on there... is that going to happen in time? 16:21:11 nirik: Some of those TODOs require policy decisions which I don't feel comfortable asking people to make until FESCo approves the change. 16:21:27 * nirik nods 16:21:54 puiterwijk's re-architecting for performance is part of it. we "OK'd" the July 5th date with pingou. he's been afk this week and I'm assuming it can pick back up next week. 16:22:39 nirik: We also had discussions with pingou and pfrields a couple weeks ago and it seems like it's one of their priorities. 16:23:02 and as threebean mentioned, pingou said July 5th was ok for prod. 16:23:22 dgilmore: in the timeline section, did you see the list of releng scripts we identified to patch? 16:23:46 threebean: yes, can not guarantee we do not have other things using it 16:23:58 threebean: there is also a bunch of releng stuff thats in infra ansible 16:23:58 how about you all mail devel-announce and say this is the proposed not yet approved plan for feedback... and we revisit next week? since we don't have quorum and dgilmore sounds like a -1 anyhow? 16:24:20 nirik: I would say i am 0 16:24:26 ok. 16:24:42 I am extremely concerned over yanking out pkgdb 16:25:02 there is a bunch of places we rely on it, some of which are likely not documented 16:25:37 sure. we will have to be ready to fix those... 16:26:03 threebean: for instance the script that syncs owners from pkgdb to koji is not mentioned 16:26:22 threebean: that is responsible for adding new packages as well 16:26:24 oh, we already have the patch for that one done, right mprahl? 16:26:39 Yes, I patched that script to work in the new world. 16:26:56 "new world" I should say 16:27:31 dgilmore: but, good example. there are lots of things like that scattered around. 16:27:36 doing our best to tick them all off. 16:27:43 heh, not irritate them - but fix them. 16:27:44 threebean: releng will be the central point for dealing with breakages and we do not have anyone spare to deal with the fallout 16:28:21 understandable. please route things to us to fix. 16:28:48 (maybe this is outside the scope of the meeting, but..) we could even join the releng group proper if that makes more sense. 16:28:55 I strongly wouyld like more time to identify as much as we can beforehand 16:29:34 have we looked at the pkgdb logs to identify clients or internal ips hitting it for things to ensure we catch the bulk of use cases? 16:29:41 yeah, we did. 16:29:57 thats when we found the gnome-software looking for active releases for dist upgrade thing 16:30:02 threebean: it likely would make sense 16:30:10 s/found/realized it/ 16:30:27 right, because they wanted us to manually maintain a file and we said no use pkgdb 16:30:57 yeah - for the transition, we're going to auto-generate that file via cron and put it on the proxies for gnome-software 16:31:34 whats the input data for that? or a human changes it? 16:31:57 nirik: for the data it uses? 16:32:04 yeah 16:32:10 its the release state inside of pkgdb 16:32:20 yes, now... I meant, what will it be. 16:32:33 when we change the state of the release at GA time it changes automatically 16:32:43 oh who knows 16:32:47 well, no, it needs a human to switch it. ;) 16:32:56 in the end it comes back down to fragile humans. 16:33:16 it should come from something in pdc 16:33:17 we don't (yet) have a fedmsg for 'Fedora 26 is released' 16:33:28 but to date we have not correctly set up PDC at all 16:33:53 yeah, this will make us have to. 16:34:16 we also have noone outside of threebean that knows pdc 16:34:25 well, mboddu got an introduction to it. 16:34:33 we sat down and poked at the API together. 16:34:42 threebean: he has not shown to me he understands any of it yet 16:34:46 mboddu was talking to ahills about it yesterday. 16:34:49 but that is good to know 16:34:57 yeah, getting there. will take more time/work. 16:34:57 It seems like he is trying to learn it 16:35:17 mprahl: sure, but there is a difference between learning and knowing 16:35:48 anyhow... so would it work to do a devel-announce post today and revist next week while moving along on anything else you can without a concrete approval? 16:36:25 only other option would be to ask folks to vote in ticket... but we have had poor luck getting people to do that over the years. 16:36:25 yeah - that sounds good to me. 16:36:53 mprahl and I can write it up. nirik, dgilmore: would you guys mind proof-reading it out of band before we hit send? 16:36:57 I am comfortable with things moving along over the next week until we can get a vote. I don't see any concerns that have not already been raised, and are being addressed 16:37:09 sure, happy to help look over anything... 16:37:35 * nirik is ok with the plan in general... its going to be a lot of work in a short window, but I think we can do it. :) 16:37:56 :) 16:38:58 #info devel-announce post will go out soon with the proposed plan and timeline 16:39:13 #info will revisit next week 16:39:26 thanks for being here threebean and mprahl. Appreciated. 16:39:34 #topic Next week chair 16:39:35 thanks guys 16:39:39 anyone want to take it next week? 16:39:45 Thanks for your feedback :) 16:40:28 There aren't many of us here, I guess i will take it again 16:40:30 (thanks!) 16:40:37 jforbes: thanks. 16:40:42 #info jforbes to chair next week 16:40:46 #topic Open Floor 16:40:50 anything for open floor? 16:41:02 One item 16:41:16 I just wanted to reconfirm my memory, since I couldn't find evidence one way or another: 16:41:58 FESCo granted the WGs the privilege to declare certain tickets blockers irrespective of criteria if they deem it sufficiently important. Is that correct? 16:42:30 I do not remeber that 16:42:36 but does not mean it is not so 16:44:06 I feel like that was one of our early decisions about the WGs as far as granting them autonomy 16:44:22 Would have bene before my time, maybe search the logs? 16:44:23 That within their scope, they had that leeway to hold up the release if it was important enough for their Edition 16:45:02 I can't recall either... 16:45:13 jforbes: too many logs to search :-/ 16:45:52 sgallagh: https://pagure.io/fesco/issue/1202 16:46:06 that is the only thing I am getting when using google 16:46:58 Yeah, I'm not coming up with it either, but I swear we discussed it. I have no proof to back that up 16:47:52 It came up recently over a disagreement between the Workstation WG and the blivet-GUI folks. 16:47:57 sgallagh: I am inclined to say we did not agree to that 16:48:49 Essentially they want blivet-GUI to repackage so it doesn't show up as a default app in GNOME because it doesn't meet their guidelines for inclusion. 16:48:51 well, we could look more, and failing that you can add it to next weeks agenda? 16:49:03 But it gets installed via the live installation 16:49:16 And they have their desktop file packaged with their main functionality 16:49:28 sgallagh: I suggest you file a ticket and we can look at it next week 16:49:32 * sgallagh nods 16:49:59 we can discuss in ticket if need ba 16:50:03 need be 16:50:09 Sure 16:50:14 since hopefully by next week the release is go 16:50:22 I mostly brought it up because I was hoping someone else would just remind me where that decision was :) 16:50:41 I think they only wanted it as a Final blocker, so it's not quite that urgent 16:50:46 sgallagh: I honestly do not remeber ever making a decision like that 16:51:06 dgilmore: My memory could be playing tricks on me or conflating it with a similar decision 16:51:25 anyhow, if nothing else will close out in a minute... 16:51:44 WFM 16:52:33 thanks for coming everyone. 16:52:37 #endmeeting