18:03:29 #startmeeting FESCO (2015-05-13) 18:03:29 Meeting started Wed May 13 18:03:29 2015 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:29 #meetingname fesco 18:03:29 #chair ajax dgilmore jwb mitr nirik paragan rishi thozza sgallagh 18:03:30 The meeting name has been set to 'fesco' 18:03:30 Current chairs: ajax dgilmore jwb mitr nirik paragan rishi sgallagh thozza 18:03:30 #topic init process 18:03:35 Hello 18:03:41 hi 18:03:45 Hello 18:03:50 hi there 18:03:50 hi 18:03:52 morning 18:03:56 hi all 18:04:19 lets get started 18:04:20 #topic #1433 provenpackager request - praiskup 18:04:20 .fesco 1433 18:04:21 https://fedorahosted.org/fesco/ticket/1433 18:04:23 dgilmore: #1433 (provenpackager request - praiskup) – FESCo - https://fedorahosted.org/fesco/ticket/1433 18:04:34 * rishi is here 18:04:48 I have no objections 18:04:56 I don't know them, so cannot comment, but others seem ok with it, so happy to go along. 18:05:09 nirik: I am in teh same boat really 18:05:32 +1 18:05:40 * paragan also don't know him so have not commented in the ticket 18:06:18 I trust thozza when he says "Pavel is a skilled packager". 18:06:20 there is 4 +1 in the ticket 18:06:35 I work with praiskup for couple of years, he maintains Autotools and works on databases and tar 18:06:44 with mitr nirik and me. that is 7 18:06:54 sure... seems fine to approve to me 18:07:04 assuming that nirik's happy to go along is a +1 18:07:51 I think those +1's are enough to get him provenpackager status 18:07:52 yes, +1 18:09:02 * nirik can add them. 18:09:26 #agreed praiskup's request to be a provenpackager is approved (+:7,-:0,0:0) 18:09:32 thanks nirik 18:09:47 #topic #1438 F23 System Wide Change: Mono 4 18:09:47 .fesco 1438 18:09:48 https://fedorahosted.org/fesco/ticket/1438 18:09:48 dgilmore: #1438 (F23 System Wide Change: Mono 4) – FESCo - https://fedorahosted.org/fesco/ticket/1438 18:10:01 +1 18:10:11 I think this is a big possitive from where we are now 18:10:13 +1 18:10:14 there were some questions on non-x86 arches 18:10:19 so, do we have actual people working on it? 18:10:21 i don't think they got answered 18:10:22 I've been talking with the maintainers and we've sorted most of the questions. 18:10:24 not just people wanting it done? 18:10:30 nirik: they are working on it 18:10:39 jwb: last I heard, sharkcz was working on the secondary arch support with them 18:10:59 nirik: We’ve had a similar Change request the last release as well IIRC; not sure this will get done but also no reason to stop them 18:11:02 jwb: in talking to them in IRC earlier in the week they are going to do a full bootstrap and not do the bunch of version jumps 18:11:04 ok, I'm +1 as long as there are actual people doing work on it. We had a change in the past where it was someone who wanted it, but they only filed the change and didn't do anything else. 18:11:12 sgallagh, i saw his questions. i didn't see any follow up on the list 18:11:14 that will have the benefit we can add aarch64 and ppc64le 18:11:29 jwb: There was some discussion on #fedora-devel as well 18:11:29 full bootstrap seems completely reasonable 18:11:31 dhorak was looking on sec arches 18:11:38 see his email 18:11:44 but i don't really care if it's ready for non-x86 or not. i was just concerned at the lack of follow up. if that is happening elsewhere, then fine with me 18:11:50 so +1 18:11:55 nirik: it is being worked on, better than teh previous change 18:11:55 So I'm +1 as well 18:12:01 jwb: there was follow up 18:12:02 great. 18:12:06 +1 from me as well 18:12:10 I'm +1 18:12:12 +1 from me 18:12:16 +1 18:12:19 I count that as 7+1 18:13:27 +1 18:13:38 Although I am not sure if we should ask them how they will do the update. 18:13:50 ie. the step by step vs. direct jump to 4. 18:13:56 Don't know if that matters. 18:14:03 proposed #agreed Mono 4 change is accpeted (+:8,-:0,0:0) 18:14:04 rishi: That's been sorted out on an FPC ticket 18:14:14 They're going to do a bootstrap using monolite from Mono 4 18:14:23 sgallagh: Ok, that's great then. I didn't know about that. 18:14:26 rishi: the direct jump to 4 is best 18:14:56 I guess it also requires less effort 18:14:59 less churn and we can add some new arches 18:15:09 dgilmore: Ok. 18:15:14 thozza: a little yeah 18:15:29 it will give us a documented bootstrap process 18:15:48 The "new arches" bit is a solid point. 18:15:52 anything else? or do the accepted and move on? 18:16:04 moveon 18:16:06 #agreed Mono 4 change is accpeted (+:8,-:0,0:0) 18:16:24 #topic #1440 New Spins process 18:16:24 .fesco 1440 18:16:25 https://fedorahosted.org/fesco/ticket/1440 18:16:26 dgilmore: #1440 (New Spins process) – FESCo - https://fedorahosted.org/fesco/ticket/1440 18:16:31 I am clearly +1 18:16:51 especially once mattdm sorts out the trademark portion 18:17:24 short summary is: treat new spins like any other changes. 18:17:25 right? 18:17:31 nirik: yep 18:17:36 +1 18:17:39 dgilmore: I think that even just saying "go to the council at this step in the process" will work for that, because the council _should_ at this point be functional and responsive 18:17:45 the old process is dead and burried. 18:18:09 mattdm: yeah, it will still be much better that the disfunction of today 18:18:38 +1 to change Spins process to Changes process 18:18:40 /me nods. I'm +1 to this. 18:18:41 FESCo can approve the spin. if the council doesnt give trademark approval contingencies kick in 18:19:00 Makes sense to me. +1 18:19:05 so there will be one more step after FESCo approves ? 18:19:08 * rishi continues reading about the trademark issue 18:19:31 jkurik, yes 18:19:39 jkurik: there are many steps after for implementation 18:19:54 he meant for approval 18:19:55 jkurik: trademark approval is one of the implementation steps 18:19:55 dgilmore: of course, I mean during the approval process 18:20:05 dgilmore: ah, ok 18:20:12 jkurik: I suggested adding "If the Change may require trademark approval (for example, if it is a new Spin)..." to the general change process 18:20:34 mattdm: ok, will do 18:20:35 but yeah, we could make the trademark approval a dependent step of the Change being accepted 18:20:51 dgilmore: that what I was on my mind 18:20:52 https://lists.fedoraproject.org/pipermail/spins/2015-May/004211.html 18:21:14 mattdm: Did we hear anything from legal@ about a blanket allowance? 18:21:31 There are plenty of non-spin changes which could benefit from approval 18:21:46 rishi: not officially but general sense was that it's better to keep the council oversight 18:21:49 Or are we going with the SIG == FESCo thing: https://lists.fedoraproject.org/pipermail/spins/2015-May/004208.html 18:21:56 mattdm: ok 18:22:11 rishi: that was a misreading with not enough coffee because that process still says "check with the council" :) 18:22:39 Ok. 18:22:57 we do have one new spin coming 18:23:06 dgilmore: Cinnamon? 18:23:09 yes 18:23:21 mattdm: yep 18:23:34 so we will have a test 18:23:49 I expect that teh change will come up next week 18:24:23 I am counting 4+1 18:24:47 sorry i did not count me that is 5+1 18:24:48 + 18:24:50 er 18:24:51 +1 18:24:57 +1 18:25:29 is there any extra details people feel we need to sort out? 18:25:49 dgilmore: WRT this ticket? 18:25:58 thozza: yes 18:26:41 Is this implicitly punting on the proposal to do the process in a dedicated trac instance? 18:26:54 proposed #agreed Spins to be treated as any other change accepted (+:7,-:0,0:0) 18:27:12 mitr: I guess so yes 18:27:14 mitr, i really hope so 18:27:29 question: should we treat Spins as System wide changes ? 18:27:33 since they would file a Change in teh wiki and track progress in a bug 18:27:36 OK, just wanted to make sure there is nothing outstanding in the ticket. 18:28:00 jkurik: ehh, they just effect themselves 18:28:19 dgilmore: ok, thanks 18:29:00 jkurik: they do need to work with releng to have it built, but that should be covered by it being a new deliverable 18:29:35 if no one has anything else. I will accept it 18:29:42 dgilmore: clear 18:29:46 #agreed Spins to be treated as any other change accepted (+:7,-:0,0:0) 18:30:02 #topic Next week's chair 18:30:14 who wants to run the meeting next week? 18:30:37 i will 18:30:48 ajax: thanks 18:31:14 #info ajax to chair next week's meeting 18:31:24 #topic Open Floor 18:31:37 Does anyone have anything they want to raise? 18:31:51 not i 18:32:11 I would like to ask if there was any previous discussion on FESCo WRT presets being moved from systemd package? 18:32:48 thozza: not that I remeber 18:32:49 or if there is any real opposition to this? 18:33:07 thozza: Once or twice, yes, and the general consensus was that it would make sense. 18:33:09 thozza: where would we put them? fedora-release? 18:33:17 and in fact, i gotta run 18:33:18 Not sure what the exact keywords to look that up would be 18:33:34 dgilmore: that is one of the candidates I think 18:33:35 I think the systemd folks actually have asked and would be happy to have them moved... 18:33:37 I am not opposed 18:33:41 but I can't recall when that was 18:34:01 nirik: yes 18:34:04 nirik: they did, I talked with them and they are fine with it 18:34:07 thozza: we do have some preset files in the -server and -workstation subpackages 18:34:35 thozza: so i guess given that it makes sense to move it into fedora-release 18:35:05 If the systemd people are OK with it and the general consensus matches that, then I don't see a reason not to do this. 18:35:17 they are 18:35:24 I can create a bug for it 18:35:58 sounds fine 18:36:00 thozza: okay. we can get it implemented in rawhide 18:36:08 great 18:37:26 I have one more topic to discuss, regarding timer units, but I can create a ticket for it 18:37:41 thozza: sounds good thanks 18:37:53 if there is nothing else I will close up the meeting 18:39:14 Nothing from me. 18:39:32 #endmeeting