17:01:38 <smooge> #startmeeting EPEL (2018-09-26)
17:01:38 <zodbot> Meeting started Wed Sep 26 17:01:38 2018 UTC.
17:01:38 <zodbot> This meeting is logged and archived in a public location.
17:01:38 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:38 <zodbot> The meeting name has been set to 'epel_(2018-09-26)'
17:01:38 <smooge> #meetingname epel
17:01:38 <zodbot> The meeting name has been set to 'epel'
17:01:38 <smooge> #topic Chair and Introductions
17:01:38 <smooge> #chair avij bstinson Evolution nirik smooge
17:01:38 <zodbot> Current chairs: Evolution avij bstinson nirik smooge
17:01:43 <avij> hello
17:01:54 <bstinson> suddenly wednesday
17:01:59 <smooge> yep.
17:04:05 <smooge> This weeks meetings are pretty short
17:04:13 <smooge> we have 3 items:
17:04:34 <smooge> #topic python36 VFAD
17:05:01 <smooge> I talked with the Fedora Python people and they let me know I was wrong and python36 is what they would like to support for a while
17:05:23 <smooge> so we will be aiming this for Python36 and putting together a VFAD in October
17:05:50 <Evolution> sorry I'm late. fires.
17:05:55 <smooge> understood
17:06:40 <smooge> so I will put out an announcement to the list for review and then put in whatever changes to the wiki etc needed to make it happen
17:06:45 * carlwgeorge pokes his head in after the python36 highlight word
17:07:34 <smooge> so the proposed date is 2018-10-16 and we will need to work out a process for what is needed
17:08:39 <smooge> my guess is to get a bunch of spec files 'lined' up and then reviewed and built during the vfad but that may be off base. I will need input from nirik or some other people on this
17:09:26 <smooge> other than that I do not have much else on this. Evolution bstinson avij?
17:09:53 <avij> I don't have anything to add at this stage
17:09:56 <bstinson> nothing from me
17:10:42 <smooge> #info will be done on 2018-10-16
17:10:42 <smooge> #info need to work with nirik on steps needed to do during
17:10:42 <smooge> #info need to work with bcotten/bex? on setting up VFAD messaging?
17:10:58 <nirik> ugh...sorry, got sidetracked
17:11:03 * nirik reads back
17:12:11 <nirik> basically we need to write up some plan and try and get people to do the various parts... write PR's, merge PR's, test builds, etc
17:12:30 <smooge> carlwgeorge, does that day look good to you to help out on this?
17:13:29 <smooge> so I am not sure how PRs will work. Do these go against python-foo or do we say we want a python36-foo?
17:14:23 <nirik> against python-foo normally, but I am sure there will be special cases where we need new packages.
17:14:40 <nirik> just python3-foo (because we may move to 3.7 later, etc)
17:14:52 <carlwgeorge> smooge: i'm occupied from 1-2 central that day, but the rest of the day is free
17:15:18 <smooge> ok thanks we can work out a schedule over email
17:16:05 <nirik> I think churchyard had a outline of packages in one of the devel list posts.
17:16:15 <smooge> ok will talk with him
17:16:58 <smooge> ok anything else from anyone on this?
17:17:37 <smooge> #topic awscli back in EPEL
17:18:09 * nirik really doesn't like the precident here.
17:18:54 <smooge> OK this is a weird thing. I got a request from Red Hat PM about putting awscli back into EPEL
17:19:43 <nirik> we could grant an exception, but I worry more things will do that... but perhaps it's not a big deal
17:19:54 <smooge> The package was pulled into the HA channel which we have said we won't conflict with but people are complaining because HA is not generally available
17:20:54 <smooge> It is confusing to me because it is in base CentOS instead of extras
17:21:24 <nirik> CentOS might do the ha channel in base?
17:21:34 <smooge> I expect it does
17:22:21 <avij> if it shows up in https://git.centos.org/summary/?r=rpms/awscli.git it'll get built, generally
17:23:02 <smooge> bstinson, avij Evolution I would like some ideas from the CentOS side on this because putting it in EPEL is going to cause install questions
17:23:32 <avij> smooge: putting awscli in some generally available RHEL channel is not an option?
17:24:04 <nirik> seems like it might be a good one for extras... but dunno whats involved there
17:24:21 <smooge> I don't understand the rules for doing that at all
17:24:50 <smooge> I can ask them about that themselves. The next thing is that I need to ask them to make a formal ticket versus me just bringing this blind
17:25:39 * nirik nods
17:25:53 <smooge> personally I am of the opinion we change our rules that we don't conflict with any package which shoes up at that URL avij listed
17:25:55 * bexelbie heard his nick
17:26:22 <smooge> hi bexelbie I am not sure I needed to mention it and will bring it up after the meeting with you
17:26:34 <bexelbie> +1
17:27:37 <smooge> #info smooge will request that a formal ticket is opened
17:28:07 <smooge> #info smooge will ask if the item can be put into Extras if it is going to be in RHEL
17:28:50 <bstinson> tying our guidelines to what's published in CentOS does have the advantage of better public visibility
17:29:35 <smooge> I think it also makes it clearer when we can conflict and how we can deal with package rebuilds
17:29:40 <nirik> I think changing things in 7 now might be... confusing
17:30:08 <smooge> ok I can just go for 8 onward
17:30:18 <smooge> if there is an 8
17:30:52 <smooge> any case not for this discussion item
17:30:59 <nirik> yeah, we will have to revamp everything then anyhow. ;)
17:31:58 <smooge> and with the way that 7 has been majorly updated in parts.. if they were to add modularity or something.. we may need to revisit things anyway
17:32:05 <smooge> #topic pagure 5.0 update request ( https://pagure.io/epel/issue/46 )
17:32:53 <nirik> I'm fine with this... as long as they mail epel-announce and give people a heads up.
17:33:06 <nirik> since the old version is no longer maintained and has security issues
17:33:13 <bstinson> +1, especially with security updates
17:33:18 <bstinson> yeah
17:33:26 <smooge> +1, due to the reasons listed
17:34:25 <smooge> I think we lost Evolution to smoke inhalation
17:34:30 <smooge> avij, ?
17:34:37 <avij> +1
17:35:04 <avij> sorry, I had to step away for a moment.. my washing machine started jumping around and I needed to check what's going on.
17:35:06 <Evolution> yeah. I'm here
17:36:21 <Evolution> pagure 5 going into epel, yeah.
17:36:32 <smooge> #agreed Allow pagure to update to 5.0 with announcement to epel-devel and epel-announce ( 5 +1, 0 +0, 0 -1).
17:36:35 <bexelbie> !
17:36:46 <smooge> #agree Allow pagure to update to 5.0 with announcement to epel-devel and epel-announce ( 5 +1, 0 +0, 0 -1).
17:36:49 <smooge> or something
17:36:59 <bexelbie> this meeting isn't scheduled properly in fedocal - please update it.  Right now this room is actually blocked but we've moved Mindshare to #fedora-mindshare
17:37:37 <smooge> urgh sorry
17:37:47 <smooge> I will see how i messed that up
17:37:50 <nirik> I think we moved back an hour and didnt change the calendar...
17:38:00 <smooge> no I went and changed the calendar
17:38:03 <nirik> huh
17:38:17 <smooge> but I probably missed something
17:38:26 <smooge> ok next week #fedora-meeting-2 probably
17:38:44 <smooge> #topic Open Floor
17:39:00 <smooge> #info Next weeks meeting will probably be in #fedora-meeting-2
17:39:12 <smooge> #info Smooge apologizes to mindshare group
17:39:32 <smooge> nirik, can you help me after this to see what I moofed?
17:40:06 <bstinson> had to check to be sure we weren't starting DST early or something :P
17:40:24 <bstinson> s/starting/ending/
17:41:15 <smooge> no we agreed last week.. right before we all went out for a bunch of drinks
17:41:29 <smooge> ok I am going to call this a meeting
17:41:52 <smooge> Thank you all for coming. See you next week at THIS EPEL-TIME, A DIFFERENT EPEL-CHANNEL
17:41:59 <smooge> #endmeeting