16:00:07 #startmeeting FESCO (2017-08-25) 16:00:07 Meeting started Fri Aug 25 16:00:07 2017 UTC. The chair is maxamillion. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:07 The meeting name has been set to 'fesco_(2017-08-25)' 16:00:07 #meetingname fesco 16:00:07 The meeting name has been set to 'fesco' 16:00:07 #chair maxamillion dgilmore jwb nirik jforbes jsmith kalev sgallagh Rathann 16:00:07 Current chairs: Rathann dgilmore jforbes jsmith jwb kalev maxamillion nirik sgallagh 16:00:10 #topic init process 16:00:11 .hello maxamillion 16:00:13 maxamillion: maxamillion 'Adam Miller' 16:00:15 .hello jforbes 16:00:16 jforbes: jforbes 'Justin M. Forbes' 16:00:22 .hello kalev 16:00:23 kalev: kalev 'Kalev Lember' 16:00:26 .hello sgallagh 16:00:27 sgallagh: sgallagh 'Stephen Gallagher' 16:00:28 the election is over and i am no longer on fesco. the wiki page needs to be updated. 16:00:55 jwb: noted 16:01:49 morning. 16:01:53 .hello jsmith 16:01:54 jsmith_work: jsmith 'Jared Smith' 16:03:20 I think bowlofeggs is the only FESCo member who's never been in FESCo before and he's on PTO to the best of my knowledge 16:03:36 yes he is. 16:04:06 alright, well we have good attendance so let's get rolling 16:04:14 #topic Follow Up Items 16:04:19 We should send out a whenisgood for meeting time 16:04:37 #topic #1763 Fedora Modules Guidelines and Process 16:04:37 .fesco 1763 16:04:38 https://pagure.io/fesco/issue/1763 16:04:41 maxamillion: Issue #1763: Fedora Modules Guidelines and Process - fesco - Pagure - https://pagure.io/fesco/issue/1763 16:04:45 sgallagh: oh? 16:05:08 Every time membership changes, we need to reconfirmed that the meeting time is still acceptable 16:05:12 ah ok 16:05:13 +1 16:05:31 sgallagh: are we aiming to keep it on a Friday or should it open for more days? 16:05:41 All days are open 16:05:57 sgallagh: alrilght, I'll send out a whenisgood 16:06:15 Ah ok. I was going to volunteer but you're welcome to it :-) 16:06:15 #action maxamillion to send out a whenisgood now that FESCo elections are over 16:06:16 Thanks maxamillion 16:06:21 sgallagh: oh, you an 16:06:23 can* 16:06:25 #undo 16:06:25 Removing item from minutes: ACTION by maxamillion at 16:06:15 : maxamillion to send out a whenisgood now that FESCo elections are over 16:06:31 sgallagh: who's taking it? :) 16:06:33 * langdon lurks 16:06:49 langdon: yeah, you're up as soon as we start talking the actual topic ;) 16:06:57 I've got it 16:07:00 hola amigos 16:07:08 #action sgallagh to send out a whenisgood now that FESCo elections are over 16:07:13 sgallagh: thanks :) 16:07:20 alright, so on to Modules Guidelines 16:07:25 langdon: what's the word? 16:08:32 Sent, got feedback, incorporated 16:08:41 langdon: cool 16:08:58 has everyone had a chance to read the guidelines and review process proposed documents? 16:09:16 I think it's an ok start. ;) 16:09:37 I've read through them, and also think it's a good start 16:09:50 I don't have any immediate concerns 16:10:02 same, I'm happy with them as they stand 16:10:07 Well.. No one, especially me, thinks they won't change :) 16:10:17 Just, a solid start :) 16:10:31 Proposal: Approve Fedora Modules Guidelines and Review Process 16:10:35 * maxamillion is +1 16:10:49 I don't have any blocking reservations. 16:11:03 I have a few thoughts on enhancements which I'll discuss offline with langdon 16:11:10 +1 16:11:20 +1 16:11:36 +1 16:11:49 +1+1 16:11:57 +1 I mean :) 16:12:00 :) 16:12:00 +1 16:12:33 dgilmore: what say you? 16:14:29 dgilmore: ping? 16:14:29 maxamillion: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings 16:14:35 shut up zodbot 16:15:48 alright, we'll assume dgilmore is afk 16:15:59 #agreed Approve Fedora Modules Guidelines and Review Process (+1:6, -1:0, +0:0) 16:16:06 moving on 16:16:07 We've got +6 by my count (or +7 if kalev's multiple personalities count separately) 16:16:08 :) 16:16:12 #topic #1765 Proposed Fedora 28 schedule 16:16:12 .fesco 1765 16:16:13 https://pagure.io/fesco/issue/1765 16:16:14 maxamillion: Issue #1765: Proposed Fedora 28 schedule - fesco - Pagure - https://pagure.io/fesco/issue/1765 16:16:18 sgallagh: :) 16:17:17 the submission deadline is really early... thats my only complaint. 16:17:45 hard to move them too much without moving everything though 16:17:48 yeah, it really is especially considering people are going to be on vacation for the winter holiday season 16:17:55 right 16:18:05 maybe move them out just one week? 16:18:34 so that way people who forget to get it in before the holidays have a chance to do so after vacation time 16:18:57 well, that leaves not much time for them to actually do them and get them merged before mass rebuild. 16:19:14 yeah, fair ... that time table is already pretty slim as it is 16:19:20 we could also just be lax and let late proposals in if someone submits them a week later 16:19:22 I guess I'm ok with it as is... since we can take f28 features anytime... people could get them in before the holidays... 16:19:24 Well, it just means that they have to be finished with the prep before they propose it 16:19:30 Which... is not a bad idea 16:19:35 sgallagh: also that 16:19:51 maxamillion: sorry someone was at the door 16:20:05 dgilmore: no worries, you can get in on this one :) 16:20:55 my only concern with the schedule as proposed is that submission deadlines 16:21:18 particullary mass rebuild and systemwide 16:21:23 I'm good with the current plan, but cautious that F27 may slip and cause friction 16:21:37 being so close to christmas people will be distracted nad forget 16:21:51 yeah, although they can get stuff in before that. ;) 16:21:52 sgallagh: I'm not one to bet on things, but I'd imagine f27 slipping is safe bet 16:21:56 and I am not sure of how the tools schedules and mass rebuild line up 16:22:26 dgilmore: The tools folks replied that it works for them 16:22:32 dgilmore: nirik does point out that there's time before the holidays to get things in, 1.5 months ... which I'd like to think is sufficient 16:22:35 See the comments in the ticket 16:22:39 glibc said they are good with it 16:22:42 no word from gcc 16:22:47 ah 16:22:51 I'll ping them. 16:22:53 sgallagh: glibc did not gcc 16:23:32 dgilmore: Understood. I'm asking them now 16:23:50 Please ping if u need me again.. And \o/ (sorry for the aside) 16:24:07 langdon: +1 16:25:13 sgallagh: though loks like we will likely have gcc 7.3 for f28 16:25:43 which should be released in December this year 16:26:21 and get gcc 8 in april 16:27:04 I can't speak for the gcc team, but I suspect they might want to go for a gcc 8 prerelease in F28 16:27:06 which hopefully means 28 doesn't need to wait any on gcc's account 16:27:37 yeah, I was kind of wondering if we were going to make a play for gcc8 early or hold it off until f29 16:28:05 kalev: which may make things tight 16:28:22 kalev: https://fedoraproject.org/wiki/Changes/GCC7 16:28:31 basedf on what they did for gcc7 16:28:34 * kalev nods. 16:28:43 they likely will try get gcc8 in 16:29:34 rgr 16:29:41 so we could just revisit this next meeting... 16:29:48 or is there presure to decide it now? 16:29:59 alright, so any concerns with the schedule that need to be proposed in ticket so we can revisit next week or do we want to vote on it? 16:30:16 nirik: not that I know of, it was just said that we'd revisit so I put it on the schedule 16:30:27 * nirik would like to hear back from gcc folks. 16:30:36 nb: I would also 16:30:51 I concur, we should get confirmation from gcc folks 16:30:58 That works 16:31:01 They aren't replying to me at the moment 16:31:06 I also would kinda like to see the systemwide and mass rebuild deadlines being shifted a week later 16:31:07 but at the same time, I don't think we should let that significantly affect the schedule 16:31:15 tjust to make sure people get them in on time 16:31:17 either they are ready or gcc 8 gets postponed to f29 16:32:30 alright, can folks with concerns/comments around the gcc8 and mass rebuild points put comments in the ticket? 16:32:31 maybe 16:33:09 Proposal: Revisit next week as there are concerns to be addressed around mass rebuild. 16:33:12 * maxamillion is +1 16:33:18 +1 16:33:28 +1 16:33:53 maxamillion: I have one other thing I wanted to bring up 16:34:03 2018-03-06 Software Translation Deadline 16:34:11 +1 16:34:26 years ago we were super strict about it 16:34:48 +1 16:34:51 when we had transifex inhouse we had a big push to translate comps, anaconda, etc 16:35:27 its been a long time now since we have made a concerted effort to make sure things were translated and we did not break sting freeze 16:35:43 I wonder if we still need to keep the deadline in there 16:35:59 we also used to do special composes for translators 16:36:12 which are no longer needed due to full composes nightly 16:37:17 nirik: sgallagh: ? 16:37:24 +1 16:37:28 Sorry, attention split 16:37:45 +1 16:38:01 dgilmore: perhaps post to devel about that and if no objections we just remove it? 16:39:05 #agreed Revisit next week as there are concerns to be addressed about the schedule (+1:7, -1:0, +0:0) 16:39:21 #topic New Business 16:39:25 nirik: sure 16:39:29 #topic #1761 Update of "Fedora Release Live Cycle" and "Changes / Policy" 16:39:32 .fesco 1761 16:39:33 maxamillion: Issue #1761: Update of "Fedora Release Live Cycle" and "Changes / Policy" - fesco - Pagure - https://pagure.io/fesco/issue/1761 16:39:35 https://pagure.io/fesco/issue/1761 16:41:58 I just got feedback from Jeff Law on GCC: they give the schedule the thumbs-up 16:42:01 I am not sure how much this changes from what we have now. I mean after just removing alpha 16:42:09 nirik: right 16:42:12 I do think that we need to re look at the life cycle 16:42:27 law is having trouble accessing his FAS account so he can't comment directly 16:42:39 then there is the bigger question of life cycles for streams, modules, etc. 16:42:57 let's go back to the previous ticket and approve the schedule then now that we have gcc confirmation too? 16:43:06 sure we can 16:43:16 WORKSFORME 16:44:16 #topic #1765 Proposed Fedora 28 schedule 16:44:17 .fesco 1765 16:44:17 https://pagure.io/fesco/issue/1765 16:44:19 maxamillion: Issue #1765: Proposed Fedora 28 schedule - fesco - Pagure - https://pagure.io/fesco/issue/1765 16:44:37 I do not see any answers on gcc 16:44:39 #info Jeff Law states "that schedule looks good from the GCC side, no problem if you say so on my behalf" 16:44:43 based on the GCC approval, I am +1 16:44:46 Proposal: Approve Fedora 28 Schedule 16:44:50 * maxamillion is +1 16:44:53 +1 16:44:57 dgilmore: mattn and law messaged me directly 16:45:02 I am relaying their approval 16:45:16 sgallagh: I do not like that form of feedback 16:45:34 +1 16:45:40 dgilmore: As I said above, he's trying to comment on the ticket but can't get into his FAS account 16:45:47 I can ask him to join this channel 16:45:49 One moment 16:48:55 And he's not responding at the moment... 16:49:33 :/ 16:51:28 How do we want to proceed? 16:51:38 I quoted him exactly above. 16:52:41 I need to step away in 2 minutes, but still +1 here now that glibc/gcc/FPL have all +1'd the schedule 16:53:07 * nirik is fine with +1 and he can add to the ticket when he can. 16:53:30 I agree -- let's +1 this and he can add to the ticket later once he gets his FAS problems solved 16:53:37 mass rebuild is the week after devconf 16:54:49 assuming that gcc is okay with it (I would rather hear it directly) then I am good with the schedule 16:55:53 sgallagh: I don't have a +/-1 from you (for posterity) 16:55:57 +1 16:56:34 dgilmore: +/-1? 16:56:57 +1 assuming gcc is okay 16:57:01 rgr 16:57:03 #agreed Approve Fedora 28 Schedule (+1:7, -1:0, +0:0) 16:57:12 #topic #1761 Update of "Fedora Release Live Cycle" and "Changes / Policy" 16:57:15 .fesco 1761 16:57:16 maxamillion: Issue #1761: Update of "Fedora Release Live Cycle" and "Changes / Policy" - fesco - Pagure - https://pagure.io/fesco/issue/1761 16:57:18 https://pagure.io/fesco/issue/1761 16:58:10 * dgilmore would like us to take a bigger look at the schedule 16:58:22 remove things that are no longer relevant 16:58:32 add things that have become tribal knowledge 17:00:10 dgilmore: +1 17:00:13 I think we should defer this until after flock, because there's a lot more changes than just removing alpha from our traditional cyclee 17:00:23 nirik: sounds good 17:00:28 +1 to defer until after Flock 17:00:34 works for me 17:00:38 +1 to defer until after Flock 17:00:58 agreed 17:01:18 dgilmore: OK, jlaw just turned up. If you want to ask him to repeat his OK for GCC, go ahead 17:01:51 (BTW, that "agreed" == +1 to defer to after Flock) 17:02:07 or I can just say, the schedule is OK for GCC rather than repeating the question :-) 17:02:14 jlaw: for posterity of the FESCo meeting, would you mind providing the stance of the gcc team on the Fedora 28 Schedule 17:02:19 jlaw: bah! beat me to it, thanks :) 17:02:55 alright, kalev is afk .... dgilmore, thoughts on defering #1761 until after Flock? 17:03:02 np. FWIW, I would have responded on the page last week, but couldn't get my FAS creds to work 17:03:20 jlaw: bummer :( 17:03:35 sure it's a problem on my side, it always is... then it fell off my radar 17:04:42 jlaw: +1 - thank you for commented in channel 17:06:23 jlaw: if there is anything we can do to assist on the fas creds, let us know in #fedora-admin... happy to help 17:06:51 dgilmore: +/-1 about postponing #1761 until after Flock? 17:07:07 jlaw: okay thanks 17:07:19 maxamillion: +1 to defering 17:07:41 #agreed Defer #1761 until after Flock, there are a lot of changes that need discussion/review (+1:7, -1:0, +0:0) 17:07:44 errr 17:07:45 #undo 17:07:45 Removing item from minutes: AGREED by maxamillion at 17:07:41 : Defer #1761 until after Flock, there are a lot of changes that need discussion/review (+1:7, -1:0, +0:0) 17:07:48 #agreed Defer #1761 until after Flock, there are a lot of changes that need discussion/review (+1:6, -1:0, +0:0) 17:07:56 kalev is still afk ... I had the vote count wrong 17:07:57 alright 17:08:05 #topic Next week's chair 17:08:18 question, are we going to hold a meeting during Flock? 17:08:27 I'm fine either way... 17:08:31 same 17:08:40 Either way works for me 17:08:49 (but there may be other activities/talks at our normal time) 17:08:51 I think many of us will be there 17:09:04 is anyone in FESCo not goign to be at Flock? 17:09:12 The conference ends at noon EST on Friday 17:09:30 Also known as "this time slot" 17:09:36 Good timing, then :-) 17:09:38 and if we change times... who knows. ;) 17:09:42 Err, EDT 17:09:51 * dgilmore will be at flock 17:10:14 * jsmith_work has to run to another meeting -- catch y'all later 17:10:33 alright, so it looks like we'll have a normally scheduled meeting unless the time changes, but bowlofeggs will be at flock so I imagine this time will work again for at least next week 17:10:42 who's chair next week? 17:10:56 I will 17:11:38 * dgilmore will not be available the week after flock 17:12:23 jforbes: wait, you will be at flock or you'll chair the meeting? 17:12:32 jforbes: or both? :) 17:12:39 maxamillion: both 17:12:43 jforbes: rocking, thanks 17:12:44 :D 17:12:52 #info jforbes to Chair next FESCo Meeting 17:12:59 #topic Open Floor 17:13:14 should we have a whenisgood? 17:13:46 dgilmore: You missed the beginning. I volunteered to send one out 17:13:53 It will apply to the week after Flock 17:15:03 anyone have anything for open floor? 17:18:08 I'll give it another minute or two and then shut it down for the day 17:19:38 sgallagh: okay 17:19:46 alright, thanks everyone! 17:19:47 #endmeeting