18:00:49 #startmeeting EPEL 18:00:49 Meeting started Wed Sep 28 18:00:49 2016 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:49 The meeting name has been set to 'epel' 18:00:49 #meetingname EPEL 18:00:49 The meeting name has been set to 'epel' 18:00:49 #chair smooge nirik Evolution bstinson avij 18:00:50 Current chairs: Evolution avij bstinson nirik smooge 18:00:50 #topic aloha 18:00:57 .hello smooge 18:00:58 smooge: smooge 'Stephen J Smoogen' 18:01:07 .hello kevin 18:01:08 nirik: kevin 'Kevin Fenzi' 18:01:11 .hello avij 18:01:14 avij: avij 'Anssi Johansson' 18:01:39 .hello bstinson 18:01:44 bstinson: bstinson 'Brian Stinson' 18:02:09 ok we have quorum 18:02:25 #topic Outstanding issues 18:02:51 I said I would bring up a couple of things during the meeting.. but I have lost what I was going to bring up :( 18:03:13 #info Request for python3x in EPEL6 18:03:36 #info SRPM Naming Conventions and rules 18:04:01 #info EL-5 is still alive for 6 more months 18:04:11 #info EL-4 has not been archived yet 18:04:27 #info NodeJS 18:04:34 oh yes now I remember NodeJS 18:05:03 sgallagh, put in a request to push to the epel-test NodeJS because the old version is EOL in a couple of days 18:05:23 Kevin and I gave a tentative approval but I would like to make it 'formal' 18:05:32 we already did I thought. 18:05:33 .hello sgallagh 18:05:34 sgallagh: sgallagh 'Stephen Gallagher' 18:05:35 months ago 18:06:00 nirik: I think you're thinking about my asking for a late Change in F25 for the sam 18:06:02 *same 18:06:04 but I could be misremembering 18:06:05 we did.. but I thought his request was to move it into epel proper before karma 18:06:25 so I am misunderstanding 18:06:31 in any case I'm all for it. We don't want to ship a no longer supported version with known security issues. 18:06:32 I've got a Fedora Magazine draft awaiting editing and release today as well 18:06:49 To give wider notification of the jump in versions 18:07:10 Hello everybody my name is Carlo, this is my first meeting, and I am exited to start contributing to the fedora infrastructure team... 18:07:12 awesome, +1 to getting that pushed 18:07:31 wind85: welcome! 18:07:50 wind85: well, this is the epel meeting, not the infrastructure one, but welcome anyhow. ;) 18:09:05 wind85, the infrastructure meeting will be tomorrow 18:09:32 .hello ttorling 18:09:33 moto-timo: ttorling 'None' 18:09:59 ok I think we are all ok on the nodejs push. 18:10:04 yes indeed 18:10:13 was there anything else on it? 18:10:52 nirik, alright...Wrong day thanks... 18:11:04 On the documents for EPEL in the wiki. This is on me to get done by the next meeting. If it isn't done by then, I will be wanting someone to take it over 18:13:44 On the epel-4 archive.. I need to work on a script to do this in general with the new mirroring tools since archiving is sort of borked at the moment. 18:13:55 Anything else? 18:14:22 bstinson, anything from the CentOS side? 18:14:43 well, there's https://fedorahosted.org/epel/ticket/34 if we want to discuss or comment or whatever 18:15:38 i don't think we have anything on our end except to say thanks for the nodejs work. we'll be consuming some of that i'm sure 18:16:06 my only comment is that koji is a large complex program written by other people. If he would like to work with them to get this fixed we would appreciate it 18:16:33 well, it's sort of a fundmental assumption koji has. 18:16:44 perhaps some of the modularity work will help out with this... 18:16:55 but failing that, there's not really any better answer 18:16:56 +1 18:16:56 smooge: what nirik said 18:16:56 I am not saying it isn't.. :). 18:17:29 its part of explicit design decisions we made when we added external repo support 18:17:31 however no one on EPSCO could 'fix it' 18:17:47 * dgilmore says that with koji dev hat on 18:18:00 smooge: setting a policy will not fix it 18:18:12 I didn't say it would. 18:18:57 :) I know 18:19:31 setting a policy which says "this is the build system we are using and we are stuck with its choices and limitations" would at least clarify why it is the case 18:20:33 #topic Upcoming Opportunities 18:20:52 which is the next thing.. moving epel trac to pagure or somewhere that is better suited 18:21:05 +1 18:21:39 I think nirik got all the bugs worked out of the trac-2-pagure importer so this should be a piece of cake :) 18:21:44 sure. I think so, but we need to fix one issue in pagure before we do more migrations. 18:21:51 well, there's 1 bug left... 18:22:21 you currently cannot turn off fedmsgs for issues... so when you import it sends fedmsgs for every ticket + every comment + every status change of a ticket, etc 18:22:36 :/ 18:22:48 well it looks like we have 34 issues. 18:22:57 which may not be worth moving over? 18:23:40 it should be easy enough once we fix that bug. 18:23:42 or maybe it is for the next poor SOBs who are in our position 18:23:50 nirik, ok we can wait 18:23:53 lol 18:25:48 * nirik had nothing more that he can remember. ;) 18:27:22 #topic Open Floor 18:27:40 OK anything for open floor or I can close out 18:28:22 all good here 18:28:26 same 18:28:35 #endmeeting