15:01:48 <smooge> #startmeeting Infrastructure (2019-04-25)
15:01:48 <zodbot> Meeting started Thu Apr 25 15:01:48 2019 UTC.
15:01:48 <zodbot> This meeting is logged and archived in a public location.
15:01:48 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:48 <zodbot> The meeting name has been set to 'infrastructure_(2019-04-25)'
15:01:48 <smooge> #meetingname infrastructure
15:01:48 <smooge> #topic aloha
15:01:48 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs
15:01:48 <zodbot> The meeting name has been set to 'infrastructure'
15:01:48 <zodbot> Current chairs: abompard bowlofeggs cverna mizdebsk mkonecny nirik pingou puiterwijk relrod smooge tflink
15:01:58 <nirik> oh, hey smooge
15:02:01 <tflink> .hello2
15:02:02 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com>
15:02:03 <bowlofeggs> .hello2
15:02:05 <smooge> sorry sticky fingers
15:02:07 * nirik was just about to start things in case smooge was traveling
15:02:07 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
15:02:27 <smooge> .hello smooge
15:02:28 <zodbot> smooge: smooge 'Stephen J Smoogen' <smooge@gmail.com>
15:02:50 <puiterwijk> .hello2
15:02:51 <zodbot> puiterwijk: puiterwijk 'Patrick "マルタインアンドレアス" Uiterwijk' <puiterwijk@redhat.com>
15:03:48 * tflink has another meeting at this time today, is likely to be somewhat non-responsive
15:04:15 <bcotton> .hello2
15:04:16 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:04:35 <mkonecny> .hello zlopez
15:04:36 <zodbot> mkonecny: zlopez 'Michal Konečný' <michal.konecny@packetseekers.eu>
15:04:36 <smooge> #topic New folks introductions
15:04:36 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
15:04:36 <smooge> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
15:05:23 <smooge> #topic announcements and information
15:05:23 <smooge> #info Final Freeze Started on 2019-04-16
15:05:23 <smooge> #info Please do not make changes to frozen machines without 2 +1 from sysadmin-main
15:05:23 <smooge> #info Another two blogposts about release-monitoring were published https://communityblog.fedoraproject.org/tag/release-monitoring-org/
15:05:45 <nirik> we have a RC1 now. But go/nogo is later this morning
15:05:57 <smooge> #info RC1 has been composed
15:06:10 <mkonecny> nirik: UTC 17:00
15:06:16 * nirik nods
15:06:42 <smooge> any other announcements?
15:07:21 <smooge> #topic Oncall
15:07:21 <smooge> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
15:07:21 <smooge> #info smooge is on call from 2019-04-18 -> 2019-04-25
15:07:21 <smooge> #info smooge? is on call from 2019-04-25 -> 2019-05-02
15:07:21 <smooge> #info ????? is on call from 2019-05-02 -> 2019-05-09
15:07:22 <smooge> #info Summary of last week: (from smooge )
15:07:38 <smooge> ok who would like to take the 2nd to the 9th?
15:07:38 <nirik> I can take this next week if you like?
15:07:54 <nirik> or someone else can, whatever works. we shouldn't do too many weeks in a row tho
15:07:56 <smooge> nah nirik you did it last week and I can't do the 02/09th :)
15:08:00 <puiterwijk> Or I can take a week again
15:08:14 <nirik> cool. how about puiterwijk now and I take 2nd-9th?
15:08:23 <smooge> puiterwijk, you seemed having a lot of plates in the air and I didn't want to add another one until after Summit
15:08:37 <smooge> nirik, can you take 02->09?
15:08:41 <puiterwijk> smooge: meh. Just sign me up for this week
15:09:01 <bowlofeggs> i can also do 2-9
15:09:07 <bowlofeggs> haven't done it in a bit i don't think
15:09:19 <bowlofeggs> i can't do this week though (or at least, not the weekend)
15:09:52 * nirik was pondering a new way to do oncall, but not sure it would work.
15:10:15 <smooge> bowlofeggs, you are now from 02->09
15:10:20 <puiterwijk> nirik: have a bot do first-line, and write AI to auto-forward and triage tickets? :P
15:10:22 <smooge> puiterwijk, you are on this week
15:10:25 <bowlofeggs> smooge: ack
15:10:28 <nirik> ha.
15:10:35 <smooge> watson
15:10:42 <bowlofeggs> puiterwijk: jcline wrote a chat bot recently that can do that
15:10:58 <puiterwijk> jcline: I hear you're taking over oncall from now on until forever, with help of your bot?
15:11:11 <smooge> but it does it via puns
15:11:14 <nirik> no, my thought was to have a baton/coffee cup/whatever... and whoever has that is on call, someone has to have it all the time, but we could hand it off more often than weekly.
15:11:18 <jcline> What bowlofeggs fails to mention is that the bot doesn't work very well
15:11:31 <nirik> like perhaps per timezones/day/night, or weekend/non weekend, or whatever.
15:11:32 <bowlofeggs> haha that's actually kinda true
15:11:47 <puiterwijk> nirik: sure, that sounds reasonable. We'll just have to figure out shipping
15:12:05 <nirik> :) well, a virtual thing I mean that zodbot keeps track of who has.
15:12:13 <smooge> sorry baton lost in transit.. you are on call FOREVER
15:12:14 <nirik> but dunno, was just a thought.
15:12:15 <puiterwijk> jcline: I bet it'll do better than me! :)
15:12:35 <bowlofeggs> smooge: no, when it's in transit the carrier is on call
15:12:40 <nirik> a week sometimes seems long, but if we try and change it too often we can't get thigns done.
15:13:09 <smooge> #info oncall summary: usual tickets but higher number due to s390 being slow and centos/fedora network connection items
15:13:16 <puiterwijk> nirik: yeah, Ii'd say it's a reasonable idea.
15:13:28 <nirik> perhaps we make it only when someone is actively awake and online.
15:13:36 <nirik> and when no one is... please file a ticket.
15:13:57 <puiterwijk> smooge: okay. Anything critical that is currently in the air and needs transferring?
15:14:02 <smooge> well that is what my message is meant to convey
15:14:08 <smooge> .batsignal
15:14:08 <zodbot> smooge (Stephen Smoogen) is oncall. My normal hours are 1000 UTC to 1800 UTC Monday through Friday. If I do not answer or it is outside those hours, please file a ticket ( https://pagure.io/fedora-infrastructure/issues )
15:14:29 <smooge> puiterwijk, nothing in the air that I know of
15:14:52 <puiterwijk> okay, thanks
15:15:20 <nirik> sure, but I was thinking if there was someone around the times you were not and was not involved in a project that needed their full attention, they could take it then
15:15:30 <smooge> if zodbot is a bit smarter and we just check in/out during those times then it just says "X is currently on call during this time and day." or "No one is on call right now. File a ticket or shutup"
15:15:34 <nirik> but all just random pondering
15:15:47 <nirik> yeah, thats the kind of thing I was thinking of...
15:15:54 <smooge> personally I just assume my oncall week is just doing oncall
15:15:58 <nirik> "the doctor is: OUT"
15:16:05 <smooge> I don't assign anything else until it is over
15:16:35 <smooge> that way I can really get on people's cases when they ping you
15:17:00 <puiterwijk> smooge: I can probably add some aliases to zodbot to make it simpler to take/relinquish oncall
15:17:02 <nirik> I've been trying to ignore people more. ;) it's not easy, but I'm sure I can get the hang of it someday
15:17:33 <smooge> We need personal zodbots which turn off highlights when we need to concentrate
15:17:35 <smooge> ok anyway
15:18:07 <smooge> #topic Oncall
15:18:07 <smooge> #info https://fedoraproject.org/wiki/Infrastructure/Oncall
15:18:07 <smooge> #info smooge is on call from 2019-04-18 -> 2019-04-25
15:18:07 <smooge> #info smooge? is on call from 2019-04-25 -> 2019-05-02
15:18:08 <smooge> #info ????? is on call from 2019-05-02 -> 2019-05-09
15:18:09 <smooge> #info Summary of last week: (from smooge )
15:18:34 <smooge> no.. that is the wrong thing
15:18:46 <smooge> #topic Monitoring discussion
15:18:46 <smooge> #info https://nagios.fedoraproject.org/nagios
15:18:46 <smooge> #info Go over existing out items and fix
15:19:33 <nirik> there's a check thats not working that was added recently...
15:19:42 <smooge> yeah.. I need anothe r+1
15:19:42 <nirik> otherwise things are about the same.
15:19:54 <smooge> or if I got one .. I missed it
15:20:00 <nirik> and kudos to cverna for tracking down the greenwave problem which was really a taskotron problem
15:20:11 * nirik looks
15:20:41 <nirik> I +1ed, someone else needs to. ;)
15:21:56 <smooge> #topic Tickets discussion
15:21:56 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
15:21:56 <smooge> https://pagure.io/fedora-infrastructure/issue/7704
15:22:17 <smooge> woops
15:22:23 <smooge> forgot to remove something last meeting
15:22:25 <nirik> just geoip from relrod...
15:22:42 <smooge> and gobby @$#$@ me
15:23:32 <relrod_cld> I'll get to that discussion some day. Skip it this week :)
15:25:22 * nirik nods
15:25:35 <smooge> ok my gobby changes yesterday never got committed
15:25:42 <smooge> so the next item on the agenda was
15:25:53 <smooge> #topic What do you want from these meetings?
15:26:22 <smooge> We have a lot of meetings these days and I want to make sure this meeting only covers what isn't done in all the others
15:26:50 <smooge> Do any of the weekly discussion items need to be trimmed or something added?
15:27:07 <nirik> I think with all the pondering on workflow and teams and such going on we may have to adjust this meeting, but I think it's usefull right now until we do.
15:27:11 <smooge> or need ot be focuses
15:27:28 <smooge> ok we will revisit and consider this something tabled until then
15:27:31 <nirik> we have used this meeting for lots of things over the years. ;)
15:27:49 <smooge> #info table discussion on what this meeting needs until we have more meetings about workflow meetings
15:28:03 <nirik> lets schedule a meeting on that!
15:28:11 <bcotton> yo dawg, i heard you like meetings
15:28:12 <smooge> yeah I am not looking to end the meeting.. just if it needs to be a shorter meeting
15:28:32 <smooge> ok that is all we have for thsi week..
15:28:36 <smooge> #topic Open Floor
15:28:41 <smooge> yay I spelled it right
15:29:07 <nirik> I think it's a good discussion to have... we should definitely evaluate this meeting once we figure out our new devsecopsagile workflow
15:29:14 <bowlofeggs> we need a meeting about meetings
15:29:20 <smooge> you forgot qa
15:29:29 <bowlofeggs> and if there are too many meetings like that, we'll need a meeting about meetings about meetings…
15:29:45 <smooge> devqasecopsdocs
15:30:01 <mkonecny> Meeting about organizing meetings?
15:30:05 <smooge> ok enough
15:30:06 <bowlofeggs> smooge: lol
15:30:15 <smooge> i forgot one more
15:30:25 <smooge> devqasecopsdocsmarketing
15:30:56 <smooge> alright folks.. it was good to see you all
15:30:58 <smooge> #endmeeting