18:00:03 <nirik> #startmeeting Infrastructure (2015-10-29)
18:00:03 <zodbot> Meeting started Thu Oct 29 18:00:03 2015 UTC.  The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <nirik> #meetingname infrastructure
18:00:03 <zodbot> The meeting name has been set to 'infrastructure'
18:00:03 <nirik> #topic aloha
18:00:03 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
18:00:03 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:04 <nirik> #topic New folks introductions / Apprentice feedback
18:00:23 * kushal is here
18:00:28 * pingou 
18:00:29 * sayan is here
18:00:32 * danielbruno is here
18:00:43 <nirik> any new folks like to introduce themselves?
18:00:52 <nirik> or apprentices with questions/comments/feedback?
18:00:52 <smdeep> .hellomynameis smdeep
18:00:53 <zodbot> smdeep: smdeep 'Sudeep Mukherjee' <smdeep@gmail.com>
18:01:13 <janslow> Yes please
18:01:37 <nirik> janslow: fire away when ready. ;)
18:02:21 <smooge> nirik, sorry got distracted. if you need me to run this
18:02:43 <nirik> smooge: no worries. I'm (mostly) here today. ;)
18:02:53 <janslow> nirik - sure. I'm new around here. I'm a developer from the United Kingdom, who's interested in getting involved in the fedora-noc team. I've sent my introduction to the mailing list and have followed the getting started steps. So, Hello! My name's James
18:03:25 <nirik> janslow: welcome! you are more interested in sysadmin side of things than development right?
18:03:53 * dotEast2015 here
18:04:06 <janslow> Yes that's right nirik. I use the term 'developer' widely. My day to day work is about 50:50 development and sysadmin work. I'm interested in learning more about managing infrastructure at scale, because that's where I'd like to go in the future
18:04:39 <janslow> And I thought that Fedora has a pretty good example of infrastructure at scale and I could learn a lot and contribute a lot here to the sysadmin team
18:04:49 <nirik> cool. well do chime in with questions as you hit them... and see me after the meeting over in #fedora-admin and I can get you started in our apprentice group
18:04:55 <puffi> Sorry I'm late
18:04:59 <janslow> Cheers nirik
18:05:18 <nirik> puffi: no worries. we just started. ;)
18:05:47 * relrod here late, too
18:05:59 <nirik> ok, shall we move on to status/info?
18:06:25 <nirik> #topic announcements and information
18:06:25 <nirik> #info Still in f23 final freeze - everyone
18:06:25 <nirik> #info FAS3 status update - pingou - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/YZIAYVJDQF427A6FGPKFX5BU6AWTS7QG/
18:06:25 <nirik> #info [release] anitya: 0.7.0 - pingou - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/PXFQ5PG2D7FHRRP366GWQ27CGUAW7FAZ/
18:06:26 <nirik> #info some questions about mdapi deployment - pingou - http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/UPI4ZOS3PQ2WS7EADMGQ2VCEVSH4XF45/
18:06:29 <nirik> #info mdapi development progressing, growing fedmsg repo-diff support - pingou & threebean - https://pagure.io/mdapi
18:06:32 <nirik> #info got developer.fedoraproject.org working in staging, need to push into production soon - kevin
18:06:34 <nirik> #info
18:06:55 <pingou> #info we are NO-GO for F23 next week, I repeat NO-GO
18:06:57 <pingou> :(
18:07:06 <nirik> pingou: you didn't read far enough.
18:07:14 <nirik> we are meeting again tomorrow and may be go for next week then
18:07:40 <pingou> nirik: indeed, missed the second email
18:07:42 <pingou> #undo
18:07:42 <zodbot> Removing item from minutes: INFO by pingou at 18:06:55 : we are NO-GO for F23 next week, I repeat NO-GO
18:07:52 * pingou fingers crossed :)
18:07:53 <nirik> but we will see what happens tomorrow. ;)
18:08:12 <nirik> we actually don't have anything listed for discussion or learn about today. :(
18:08:20 <nirik> Perhaps we could come up with a few for coming weeks now?
18:09:02 <nirik> I'm happy to teach about most anything, but there's so many to choose from and I have already done a bunch that I am not sure what would be good.
18:09:08 <nirik> anything people would like to know more about?
18:09:44 <threebean> pingou or I could probably do a session on mdapi.
18:09:48 <kushal> nirik, may be how to start working (or becoming an apprentice) for the infra group?
18:09:48 <threebean> it is pretty neat :)
18:09:53 <aikidouke> squid?
18:10:13 * tflink could do one one buildbot if there's interest
18:10:16 <pingou> threebean: I quite like aiohttp :)
18:10:36 <nirik> kushal: sure. we are actually planning a apprentice work day on nov 18th... might be good after that so we have docs fixed up and suck
18:10:38 <nirik> such
18:10:50 <pingou> nirik: btw, is the day on fedocal?
18:11:02 <aikidouke> i dont think it is
18:11:08 <nirik> we should add it. Not sure it is
18:11:11 <aikidouke> i didnt get much response to my email
18:11:28 * aikidouke will add it if I can
18:11:32 <nirik> I thought about replying, but I agreed with everything and thought it looked good, so I didnt :)
18:11:38 <aikidouke> :)
18:11:44 <dotEast2015> same here
18:11:45 <pingou> aikidouke: +1 do it :)
18:11:53 <aikidouke> kk...on my list
18:12:21 <aikidouke> think we could get a blurb on the magazine?
18:12:57 <nirik> so, how about: nov 5th - pingou on mdapi, nov 12 - tflink on buildbot, nov 19th - me / aikidouke on apprentice onramp and recap the apprentice day, dec 3rd me on squid?
18:13:17 <pingou> oh the 5th won't work for me
18:13:26 <pingou> I'll most likely be offline that evening
18:13:37 <nirik> ok. which ones might work?
18:13:47 <pingou> tflink: would the 5th work for you?
18:13:57 <tflink> it can
18:14:18 <nirik> cool.
18:14:18 <pingou> nirik: then let's switch tflink and I :)
18:14:23 <nirik> ok, sounds good.
18:14:23 <tflink> puts more pressure on me to poke more at buildbot nine soon but that's not necessarily a bad thing :)
18:15:58 <nirik> ok, added to gobby
18:16:11 <nirik> so, is everyone still liking the meeting format?
18:16:50 <dotEast2015> nirik, does gobby interate with calendar?
18:17:00 <dotEast2015> sorry, integrate
18:17:00 <nirik> dotEast2015: nope. It's it's own thing completely
18:17:12 <dotEast2015> I see
18:17:35 <nirik> It would be really cool to build a web client for it tho (then it could more easily replace things like etherpad/etc)
18:18:05 <janslow> I'd be interested in looking at that nirik
18:18:30 <nirik> sure, but it's not likely a small project... :(
18:18:52 <nirik> Someone did build some javascript library to interface with it...
18:19:10 <nirik> https://github.com/sveith/jinfinote
18:19:18 <nirik> but it's old and no idea if it's complete or works
18:19:28 <janslow> I'd be happy to take it on as a side project, even just to do some initial scoping/research
18:19:46 <nirik> sure, if you like that would be great.
18:20:16 <nirik> #topic Open Floor
18:20:34 <nirik> ok, any items for open floor? questions, comments, ideas, favorate potato chip flavors?
18:20:51 <aikidouke> salt and vinegar
18:21:00 <janslow> +1 aikidouke
18:21:34 <aikidouke> ah reminder
18:21:35 <nirik> I just had some "new york ruben" flavored ones... and wow... they really did taste like a ruben. ;)
18:21:42 <nessa_> hey, I can use some open source advice
18:21:51 <aikidouke> someone was looking for budget ideas for 2016
18:22:00 <aikidouke> whoever led last week, sorry
18:22:23 <aikidouke> just throwing that out there in case anyone had any ideas/requests
18:22:28 <pingou> smooge: ^
18:22:38 <aikidouke> thanks pingou
18:22:45 <nirik> nessa_: we can try...
18:22:52 <nessa_> I am having to deal with sort of unresponsive maintainer and I am not sure if I should say anything to them.
18:23:10 <pingou> nirik: an idea: if freeze is extended, could we have a 2 days global-warming period?
18:23:52 <smooge> sorry I am working on a broken system.. what did I miss?
18:24:08 <smooge> aikidouke, oh yes thanks
18:24:09 <nessa_> Sometimes it just irritating that I can't work ahead because they are no responding on time. However, I feel like they are people and trying their best, may be just having a busy month
18:24:13 <nirik> nessa_: well, thats kind of outside our scope here... I'd say trying to communicate is better than not. If there is a problem you can't oevercome bring it to fesco
18:24:33 <nirik> pingou: what do you mean exactly?
18:24:44 <pingou> nirik: I want to push a new pagure and a new pkgdb2 :)
18:24:52 <pingou> but the updates will likely be too large for a FBR
18:25:13 <nessa_> @nirik Thanks. I will give it more thought
18:26:27 <nirik> pingou: ok, so you mean a break in the middle of the freeze break for things? or ? not sure...
18:26:43 <pingou> nirik: yes
18:26:55 <nirik> nessa_: happy to provide more feedback if you want to send me more details. :) I'd also err on the side of being forgiving... lots of people busy around release time. ;(
18:27:00 <pingou> nirik: like a two days off-freeze before we freeze again
18:27:24 <nirik> pingou: well, the danger is that we land a bunch of stuff and we think it's ok, but a day later we find a bunch of issues and it interferes with release.
18:27:34 <pingou> true
18:27:52 <nirik> but perhaps it could be workable... not sure.
18:28:45 <nirik> might be more pondering required. ;)
18:28:49 <nirik> anythng else for open floor?
18:29:38 <nessa_> @nirik I am just not sure if I should be demanding their time. Something along the lines of "I would appreciate it if you kept 30 min per week to respond." It is open source after all.
18:30:20 <nirik> sure. hard to say... also many people have many open source communities they work in... so it might be the one you want the answers for is just lower on their list. ;)
18:30:34 <nirik> Anyhow, thanks for coming everyone!
18:30:37 <nirik> #endmeeting