01:00:19 #startmeeting fc_sig 01:00:20 Meeting started Wed Jun 5 01:00:19 2019 UTC and is due to finish in 60 minutes. The chair is mattoliverau. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:23 \o 01:00:24 The meeting name has been set to 'fc_sig' 01:00:42 hey tonyb 01:00:53 anyone else here for the meeting? 01:01:12 Agenda 01:01:29 #link https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda 01:01:33 well diablo_rojo_phon and cmurphy are "slacking off" 01:01:54 so it may just be the Aussie (and Aussie++) ;P 01:02:02 yeah, I thought diablo_rojo_phon was around but not able to run the meeting 01:02:15 why not. then this will go really quick 01:02:26 I'm sure if we keep saying diablo_rojo_phon she'll arrive 01:02:58 I'll ping the others on the ping list (minus tonyb, cmurphy and myself) 01:03:23 Meeting ping: gmann, spotz 01:03:53 I guess we'll just get started 01:04:13 mattoliverau: go for it 01:04:22 #topic Update UTC offsets 01:04:49 wassisdas? 01:04:53 I did send off an email to PTLs before the summit/PTG. 01:05:01 * diablo_rojo_phon waves 01:05:16 I still see a bunch of liasions with no UTC data, so that obviously went well :P 01:06:05 mattoliverau: not too many 01:06:11 So. . Time to start pinging directly? 01:06:25 Yeah, maybe 01:06:39 Maybe I'll send another "reminder" email. 01:06:50 then we can get out the big stick 01:06:52 Works for me 01:06:57 Lol 01:07:05 you might also be able to get it out of launchpad 01:07:24 #action mattoliverau to send an followup "reminder" email to ptls to update liasion list + UTC times. 01:07:45 https://launchpad.net/~o-tony has mine as Sydney 01:08:00 tonyb: yeah true. Not a bad idea 01:08:16 * tonyb is sure there is a search in the API 01:08:33 * tonyb steps back from writing a tool govel in said API 01:08:52 Well I kinda hoped by getting PTLs to do it, then we might be buy in.. Ie they know who we are. 01:09:22 sure 01:10:08 currently we have some (most?) liasons who are just old PTLs, because they became the default. So do we auto change to the new PTL, remove old users.. which is where PTL and project buy in would be a huge help. 01:10:45 maybe we need to track who are liasons by choice and by default 01:11:02 We could also put this in the cross project liaison list 01:11:17 Since I **thiiink*" that one gets attention? 01:11:28 oh, then yeah, great idea 01:12:05 We should look into that :) 01:12:20 I'll start with the follow up email. 01:12:24 shall we move on? 01:12:36 I think that got rolled into openstack-discuss 01:13:06 Yeah we can move in. 01:13:20 #topic New Contributor Patches 01:13:37 To be honest I only just looked at the list. 01:14:15 mattoliverau: more than I did 01:15:00 I also.. have been bad.. 01:15:32 there are a bunch of sandbox ones and a charms one. But there are a few that should be addressed. One is networking bgp, I know a guy who does that stuff (I think) so i'll see if I can ping him about it. 01:16:01 #action we all need to be better at doing our homework :) 01:16:16 Oh I did see an election one ... but I suecpst that diablo_rojo_phon is the reason behind that 01:16:35 I was 01:16:41 And I merged it yesterday 01:16:42 * tonyb should update the (election) story with more work ;P 01:17:17 nice 01:17:37 I say we move on. 01:17:46 +1 01:17:49 Sounds good 01:17:50 #topic Ask.openstack.org Contribution Questions 01:18:21 I saw fungi answered one of the secret questions: https://ask.openstack.org/en/question/120283/is-there-a-mentoring-program-for-openstack/ 01:18:30 nice work fungi 01:19:59 And I saw spotz answered a mentiooring or training one. I've lost the link to confirm the exact question. 01:20:30 Otherwise I didn't see any new questions in ask.o.o 01:20:59 next.. 01:21:11 #topic Sandbox Bot 01:21:45 I used it with one student in Denver. 01:21:52 \o/ 01:21:56 and it worked well 01:22:21 so I (still) need to update the list and get it merged then we can do the hard part of adding it to the training 01:22:23 What are then next steps? push it off your laptop I assume. 01:22:26 mattoliverau: thanks :) 01:23:00 mattoliverau: Yup ... the only small trick is I need to use a zuul secret and stash it in project-config 01:23:39 tonyb: cool, is that something you can progress.. you do have a new employee on your team we can trick into helping ;) 01:24:17 oh the zuul secret stuff. We used that to add docker building and pushing to docker hub in swift. So I might actually be able to help 01:24:21 mattoliverau: I've tricked them into all sorts of things (like joining RH ;P) so I'll keep this one for me 01:24:32 lol 01:24:38 mattoliverau: cool beans 01:25:26 Cool, so sounds like we have a rough plan of what needs to happen. 01:25:51 We'll see what progress we can make, if any, by next meeting. 01:26:04 mattoliverau: I've had https://zuul-ci.org/docs/zuul/user/encryption.html open in chrome for months now ;P 01:26:12 lol 01:26:50 Do we need to make a #action for that? 01:27:06 yeah you just need the script to generate the secret hash. It outputs the required yaml code, which makes it easy. 01:27:46 diablo_rojo_phon: sure :) 01:27:57 #action mattoliverau to bug tonyb at 0900 (UTC+1000) in 2 weeks to upload the project-config change 01:28:04 lol 01:28:10 ... see what I did there 01:28:13 ..and.. 01:28:19 now if nothign happens it isn't my problem ;P 01:28:24 #action tonyb to update the list re:sandbox bot 01:28:31 :P 01:28:45 it's an #action battle :P 01:28:46 which depends on the first one 01:28:52 doh 01:28:56 Lol 01:29:04 LOL 01:29:26 * tonyb feels like I may be working late tonight ;p 01:30:06 ok so the next topic is summit and forum planning.. which might be too early for shanghai? 01:30:15 So I think we'll skip it. 01:30:19 good plan 01:30:40 Yeah that is old 01:30:50 Definitely early for Shanghai 01:30:59 the one after is project liasions, which I hijacked and talked about along side the UTC updates, so we can skip that too 01:31:08 I already have an action item for that :) 01:31:17 So.. 01:31:25 #topic People to Reach Out To 01:31:52 I'll be honest, I've done nothing here, and haven't even looked at the ethercalc 01:32:04 * tonyb either 01:32:07 So I don't have anything to report, does anyone else? 01:32:42 diablo_rojo_phon ? 01:33:13 StarlingX started a FC SIG 01:33:20 Oh nice 01:33:25 oh cool 01:33:32 Lol was saving that for open discussion 01:33:36 Pasted too soon 01:33:42 ok hold on.. 01:33:49 #topic open discussion 01:34:04 diablo_rojo_phon: go 01:34:08 Ha thanks. 01:34:19 StarlingX started their own FC SIG 01:34:26 wow, cool 01:34:52 we should brainstorm together. 01:34:55 So I guess we are doing something right? 01:35:05 Yeah. 01:35:09 That would be cool. 01:35:34 that depends did they use us as 'negative know-how'? 01:35:44 I mean we have the same problems, so solving similar issues with reaching out and onboarding. Do we have any contactS? 01:36:03 Uhh I don't, but I can get them from ildikov 01:36:59 Cool, can you? That would be awesome, if your busy I'm happy to attempt to reach out. I mean if you not travelling and going to places like Cern (/me is jealous). 01:37:51 I definitely can. 01:38:12 I'm done traveling (aside from father's Day weekend in MN) until July. 01:38:28 US father's day that is. 01:39:00 cool 01:39:57 Make an action for me :) 01:40:12 It's a long weekend here in OZ this week and next week I'm taking Thurs - Tues off to head to Melbourne for a locksport conference (OzSecCon). So if I'm not around much next week that's why :) 01:40:23 *this weekend 01:40:59 #action diablo_rojo_phon to get StarlingX fc_sig contact details 01:41:27 \o/ now we're all actioned 01:42:13 Noted :) 01:42:20 I didn't know they had such a thing. 01:42:33 me either. 01:42:44 there is a conference for *everything* 01:43:11 We have 18 minutes left, anything else to bring up? 01:43:34 Or we can have an early mark 01:44:02 It's intl running day so .... if we get an early mark I can go for a run 01:44:46 lol, there seems to be a day for everything. 01:44:55 much like conferences ;P 01:45:19 :) 01:45:26 cool, let's have an early mark. 01:45:41 thanks everyone, see you next meeting 01:45:47 #endmeeting