18:00:02 <smooge> #startmeeting Infrastructure (2017-11-09)
18:00:02 <zodbot> Meeting started Thu Nov  9 18:00:02 2017 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:02 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:02 <zodbot> The meeting name has been set to 'infrastructure_(2017-11-09)'
18:00:02 <smooge> #meetingname infrastructure
18:00:02 <smooge> #topic aloha
18:00:02 <smooge> #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion
18:00:02 <zodbot> The meeting name has been set to 'infrastructure'
18:00:02 <zodbot> Current chairs: dgilmore maxamillion nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:18 <threebean> :)
18:00:22 <marc84> hi everyone
18:00:26 <puiterwijk> .hello2
18:00:29 <nirik> morning
18:00:29 <zodbot> puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' <puiterwijk@redhat.com>
18:00:39 <smooge> hello
18:00:44 <bowlofeggs> .hello2
18:00:44 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
18:00:49 <clime> hi
18:00:57 * cverna waves
18:01:03 <smooge> #topic New folks introductions
18:01:04 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
18:01:13 <benniej> hi
18:01:19 <smooge> hi benniej
18:01:23 * relrod waves
18:02:29 <atrevino> hi, I'm interested to collaborate to fedora-infrastructure.
18:02:41 <bstinson> hi all
18:02:54 <smooge> hello atrevino
18:03:05 <marc84> welcome atrevino
18:03:17 <smooge> what are you looking to work on?
18:03:26 <nirik> welcome atrevino
18:04:34 <smooge> Oh the GO/NO-GO meeting is happening at this time in #fedora-meeting so I am expecting some level of loss of attention :)
18:04:36 <atrevino> was looking to get better in server side things like scripting, or backend development, have some 5+ yoe doing scripting for QA and web dev
18:05:36 <smooge> atrevino, cool. after the meeting we can add you to apprentice if no one has yet
18:05:46 <smooge> #topic announcements and information
18:05:46 <smooge> #info PHX2 Colo Trip, Dec 4th - 9th
18:05:46 <smooge> #info Final freeze has started. PLEASE TEST ANY RCs.
18:05:46 <smooge> #info new notifs in staging, please test!
18:05:47 <smooge> #info bodhi-3.1.0-0.1.beta in staging for post-freeze: https://bodhi.stg.fedoraproject.org/docs/release_notes.html#v3-1-0
18:05:48 <nirik> what did you say smooge ? :)
18:05:58 <atrevino> thanks
18:06:35 <smooge> So we are in Freeze. No major changes to frozen system until after the release
18:08:03 <smooge> #topic Ticket cleanup
18:08:03 <smooge> #info none this week.
18:09:05 <smooge> nirik, you are listed as the person to talk about the next couple of itmes.. can you do that now or just use them as info until next week?
18:10:08 <nirik> can do
18:10:10 <nirik> now
18:10:27 <nirik> so fire away.
18:10:32 <smooge> #topic Apprentice work day - 2017-11-29 - kevin
18:10:51 <nirik> yeah, just wanted to confirm with everyone that that would work and perhaps toss out ideas on what we could work on...
18:11:11 <nirik> there's lots of good things... docs, ansible cleanup, just learning how things are setup, etc
18:11:17 <marc84> +1 nirik
18:12:16 <nirik> Perhaps we should also advertise some? perhaps a post in the community blog?
18:12:26 <nirik> and/or other blogs/devel-announce?
18:12:58 <dustymabe> .hello2
18:12:59 <zodbot> dustymabe: dustymabe 'Dusty Mabe' <dustymabe@redhat.com>
18:14:24 <nirik> anyhow, I'll try and do those things soon. Hopefully we can help a lot of folks onboard to later help us. ;)
18:14:36 <smooge> we need to advertise some and explain what it is. I am not sure myself
18:15:10 <nirik> well, basically just a day where we will plan to be available in #fedora-admin to help apprentices work on things, ask questions, etc.
18:15:20 <cverna> We had a gobby document last time, maybe we can setup one and add ideas to it
18:15:22 <nirik> so they know they can get our attention
18:15:27 <nirik> cverna: +1
18:15:50 <smooge> that sounds like a great idea
18:16:03 <smooge> ok anything else?
18:16:23 <nirik> not on this I don't think
18:17:16 <smooge> #topic What to do about Meetbot redux - kevin
18:17:45 <smooge> is this a recursive problem? we are needing to deal with meetbot in a meeting?
18:18:26 <nirik> lets meet about meetbot. ;)
18:18:52 <nirik> anyhow, we have several tickets decaying in the infra pagure about improvements to meetbot
18:19:03 <nirik> upstream is dead
18:19:28 <nirik> we tried to work with openstack folks, but they said basically sure we would be happy to cooperate and then nothing really happened.
18:19:44 <nirik> we thought about making a new bot, but havent
18:20:08 <smooge> ok time for WDDD question
18:20:09 <nirik> so, I'd like to propose we formally fork it and put it on pagure and move those RFE tickets there and try and get people to help implement them
18:20:13 <smooge> What does debian do?
18:20:19 <nirik> no idea.
18:21:05 <smooge> me either.. I would say your idea is as good as any
18:21:13 <smooge> better than most
18:21:25 <smooge> tries for a ringing endorsement and failing
18:21:33 <nirik> looks like ubuntu has a fork
18:21:40 <nirik> openstack also has a fork
18:21:41 <cverna> is there a fork of meetbot that is maintained ?
18:21:52 <nirik> not really
18:21:54 <cverna> I guess I have my answer :)
18:22:27 <smooge> so job 1
18:22:28 <nirik> actually the launchpad one is just a project, I don't see any content there thats new aside from bugs
18:22:45 <cverna> do we have a stg meetbot ?
18:22:53 <smooge> usra
18:23:03 <smooge> ursabot I think
18:23:08 <nirik> yep.
18:23:12 <cverna> where we could select a new bot and try it
18:23:21 <smooge> nonbot is the dev instance. it doesn't say anything
18:23:36 <nirik> well, we have looked at several, but note that changing bots would require a lot of retooling
18:23:54 <nirik> it's likely a lot easier to just enhance the meetbot plugin
18:24:39 <smooge> I am +1 to nirik's choice of officially putting a maintenance home in pagure. We can import the other forks in as branches and see what can be done there
18:24:47 <nirik> shall I discuss on list? or just make the project and try and get people helping?
18:24:49 <cverna> sounds like something good for the apprentice day :)
18:25:06 <nirik> cverna: indeed, we could set it up then and try and get started on things.
18:25:19 <cverna> +1 to make the project
18:26:06 * cverna waves at vivek_
18:26:16 <nirik> can do. thats all I had on this. ;)
18:28:25 <smooge> #topic How to monitor bastion mail queue - kevin
18:28:25 <smooge> #info https://pagure.io/fedora-infrastructure/issue/5908
18:28:39 <nirik> so, this was filed by puiterwijk a while back...
18:28:50 <nirik> but I am not sure how we can best implement this.
18:28:56 <nirik> open to ideas
18:29:41 <smooge> I am not sure how to implement this either.. the redhat.com queue is very complicated
18:29:42 <puiterwijk> nirik: maybe a queue check for just @redhat.com?
18:29:53 <puiterwijk> That queue should not get too huge at any point in time
18:30:03 <nirik> well, if we send them a bunch of things they may throttle.
18:30:34 <nirik> if we could get them to make us an alias that sends back to us we could do a 'ping' email loop back and forth.
18:30:46 <nirik> but that seems pretty heavy and not sure they would want to do it
18:30:58 <puiterwijk> I think we've been set on the "no-throttle" list
18:31:04 <puiterwijk> Sure.
18:32:33 <smooge> I don't have any good/better ideas at the moment.
18:32:36 <nirik> ok, if so we could try and look at queue for that domain and check it.
18:32:58 <smooge> phone call brb
18:33:13 <nirik> I don't know if any of the existing nagios plugins would do this or need a custom one
18:35:06 <nirik> might be a nice project for an apprentice I suppose... a bit on the complicated side tho
18:35:51 <smooge> we would need a custom one.
18:36:14 <smooge> sounds like an not-so-easy-fix
18:37:32 <smooge> #topic Apprentice Open office hours
18:37:41 <smooge> Any apprentice questions on easy fix problems?
18:37:52 <smooge> or just tickets in general?
18:38:25 <nirik> I added a few easyfix tickets the other day... so do make sure to look.
18:38:27 <netcronin> Do we have a list of projects to work on for the Apprentice Workday?
18:38:34 <nirik> and if any are old, feel free to take them over.
18:38:48 <nirik> netcronin: not yet, we were going to make a gobby document on it.
18:39:02 <netcronin> nirik: sounds good. thanks
18:39:18 <atrevino> I will take a look later today for easy-fix tickets, hoping to participate a bit more in a future.
18:39:50 <smooge> #topic Open Floor
18:40:02 <smooge> OK anything for the open floor part?
18:40:40 * nirik has nothing
18:40:52 <bstinson> is this a good place to ask about getting added to the apprentice group?
18:41:21 <bstinson> i'm looking at helping out with jenkins and perhaps providing some resources for CI testing
18:42:49 <nirik> bstinson: we can add you after the meeting in #fedora-admin. ;)
18:42:52 <puiterwijk> bstinson: just talk to us in #fedora-admin after the meeting
18:43:03 <nirik> and yeah, we should definitely talk about jenkins and come up with a plan. ;)
18:43:07 <bstinson> awesome
18:44:33 <smooge> sounds good
18:44:49 <smooge> in that case I am going to take some migraine medicine and call this a meeting (or vice versa)
18:44:52 <smooge> #endmeeting