16:01:09 #startmeeting uc 16:01:10 Meeting started Mon Mar 18 16:01:09 2019 UTC and is due to finish in 60 minutes. The chair is VW_. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:13 The meeting name has been set to 'uc' 16:01:22 #chair studarus spotz belmoreira 16:01:23 Current chairs: VW_ belmoreira spotz studarus 16:01:27 #topic roll call 16:01:30 o/ 16:01:32 o/ 16:01:37 o/ 16:01:53 o/ 16:02:33 #chair josephrsandoval 16:02:34 Current chairs: VW_ belmoreira josephrsandoval spotz studarus 16:02:41 woo hoo! Looks like we are all here 16:02:56 yes. im no longer challenged by time change. 16:03:29 #topic Follow up from Ops Meetup 16:03:39 did anyone make it to the meeting with those folks last Tuesday 16:03:42 I was not able to 16:03:51 I wasn't home yet:( 16:04:32 unfortunately not... 16:05:18 OK - sounds like we need to catch them tomorrow then. The main thing is trying to get content from the discussions there into the forum 16:05:29 feedback loops FTW! 16:05:53 Yeah they're on the schedule with 3 holders 16:06:03 ^ this 16:06:37 yep - Just curious what they topics might be 16:07:14 I know there were ceph topics at the meetup but not sure what else 16:07:27 yeah - will follow up with them 16:07:42 just wanted to make sure none of us had already 16:08:02 anyway - we'll keep the ball rolling 16:08:34 #topic Formalizing the Ambassador Role 16:08:43 #link https://etherpad.openstack.org/p/uc-ambassador-governance 16:08:53 we had some good discussion on this last week 16:08:55 I put up there my thoughts on requirements 16:09:09 requirements for both Ambassadors and User Groups 16:09:49 yeah - I really like what we have so far 16:09:56 has everyone had some time to review it? 16:09:58 main thing is requirement for inward presentations (within the OSF community) and outward promotion of OSF projects to the at-large non-OpenStack community 16:10:07 I just posted it this AM... 16:10:37 two year term - confirmed by the UC 16:11:28 the role would be less about supporting user groups and more about getting out and talking about OSF projects and community 16:11:33 Are we saying they're going to need to do any travelling? If so I can see 2 year terms if not every other position is yearly or by release 16:12:15 no travel required or stated - someone could do it all online - webinars, blog posts, articles... 16:13:03 why two years? 16:13:37 trying to cut down on the UC workload of having to confirm people... 16:13:59 In my mind, the 2 years is OK because there is still a relationship between the Ambassadors and the user groups 16:14:04 so some consistency would be good 16:14:39 we need some sort of timeframe so that inactives get timed-out... 16:14:54 we need some sort of time limit before a renewal so that inactives get timed-out... 16:14:57 Same could be said for PTLs and most do re-run and are elected 16:15:39 this isn't an election contest - they don't need to win over someone else... 16:15:54 true 16:16:33 I also removed any geographic requirement 16:17:18 so if we get four people qualified people from one region - there is no reason they all can't be Ambassadors 16:18:32 the key would be making sure their body of work is quality and we're not just going for quantity. 16:18:46 agreed 16:18:57 yeah - they'll need to submit links to the content 16:19:26 agreed 16:19:53 anything from OSF staff? 16:20:05 They're in another meeting 16:20:13 k 16:20:54 how the application format would like? we may need to have a template for the candidates 16:21:18 there's a Google form online already - we just need to add the links to the content 16:21:28 and have the form go to the UC 16:22:08 yeah - I would say that this group needs to add comments etc to the doc and we can hopefully review with OSF staff next week when we shift the meeting time 16:22:21 https://docs.google.com/forms/d/e/1FAIpQLSc0TWAPr32S5CNh0mvYyYH4vZY-rEF6bWUZ9KhwMbXjq3jovw/viewform 16:24:18 so we table until next week! 16:24:33 yes 16:24:44 but action - everyone spend some quality time with studarus's document :) 16:25:12 and think how best to compensate ambassadors... 16:25:30 #topic Joint Leadership Meeting in Denver 16:26:02 so, for those who haven't been before, there is usually a joint leadership meeting the day before the summit between the board, the UC and the TC 16:26:16 typically in the afternoon as there is a regular board meeting first 16:27:33 so Sunday 28th? 16:29:07 yes 16:29:26 it's not a hard requirement to have everyone there, but it's nice to get as many of us as we can 16:29:37 I am planning on attending, but will come in Sunday morning 16:29:52 so I will likely miss the board session and join the combined meeting 16:29:52 what time does it start? 16:30:07 I haven't seen a schedule yet 16:30:12 i was scheduled to get in Sunday afternoon. but could probably shift my arrival 16:30:19 My flight arrives into DEN Sunday morning ~11am so I can be there in the PM 16:30:34 traditionally, it's after lunch, but will try to get some guidance from Alan 16:31:02 I arrive in the morning so will be attending 16:31:42 During the joint meeting, we'll have some time to present 16:32:12 I'll dig up the last summit's slides and we can use those as a starting point to work on what we want to talk about this time 16:32:21 I wont be there. Unfortunately this will be the first Summit that I will miss since San Francisco. 16:32:34 I'd be happy to help with the slides 16:32:37 boo :( 16:32:44 you'll be missed belmoreira 16:33:09 yeah studarus - we'll all work on them 16:33:22 and likely share the presentation of them depending on who all is at the meeting 16:34:02 #action VW_ Get the slides for Denver joint leadership meeting started 16:34:31 I think that's all I had for this right now. Just wanted to get you all thinking about it 16:34:40 anyone have anything else related to the joint leadership meeting? 16:34:43 https://docs.google.com/presentation/d/1dE6_TWR24lwtWYXckF78M0tT4DF66NFUJmVecX2Fa2s/edit?usp=sharing 16:34:50 Thanks spotz! 16:34:55 NP 16:36:36 Alright - moving along 16:36:50 #topic UC Forum Sessions 16:37:03 If I recall, we have a couple of sessions set aside for our use? 16:37:46 ou need to ask for them on the WG/BoF spreadsheet 16:37:59 grr lost half of that retyping 16:38:22 The staff would know what's been set aside (and they aren't here)... 16:38:27 They're usually under Ashlee or you need to ask for them on the WG/BoF sheet 16:38:36 Ok - will that 16:38:47 im looking through the track chair app 16:39:03 Look on the real schedule most stuff is gthere 16:39:03 #action VW_ follow up with Ashlee on BoF/WG space 16:39:44 forum selection was ongoing lastt week 16:40:14 operators had placeholders. i didn't see UC. but shouldn't be a problem. the forum submissions wasn't too heavy 16:40:43 I think spotz is right - "our" sessions actually get allocated in the BoF/WG space 16:40:49 kk 16:41:01 I'll follow up with staff and we can revisit here - hopefully with some of them present 16:41:25 Just want to get us thinking about how best to use the time we have :) 16:42:21 #topic Meeting time shift next week 16:42:41 1500Z? +1 16:42:57 so, just a reminder, that we will roll to 15:00 UTC next week. This will free up the staff and put the meeting back at 8:00am Pacific 16:43:20 it's not great for belmoreira next week, but will be fine after his timezone adjusts the following weekend 16:43:23 https://review.openstack.org/644280 moving time up with US daylight savings time change 16:44:12 next week I will be in PDT in a conference. Not sure if I can make it 16:44:31 no worries 16:45:11 the good news is, that once we make the switch, we'll be able to keep it that way all the way through the next election 16:45:37 #topic Any Other Business 16:45:40 Ok, that's all I had 16:45:50 anything else that any of you need to bring up? 16:45:53 best ways for people to contact the UC? 16:46:21 is the email list the "official" best way for people to reach us? If so, I'd like to make sure the email address is better promoted across the Wiki et al other pages 16:46:34 we are kinda hard to find (outside of IRC) 16:46:50 +1 16:46:59 yes - I would say that is the primary method 16:47:11 I agree that other methods are useful too, though 16:47:21 but yeah - if we need to get that published more places, let's do 16:47:35 what about people's email addresses? Are those acceptable to post? 16:48:07 The idea is for the group to be contacted not indivduals unless it needs to be private 16:48:07 or does that just invite screen scraping spam? 16:48:17 i was going to say that 16:48:44 ok - I'll see about getting the group email better promoted on the governance pages 16:49:04 same thing with links to this meeting and the agenda - those are both hard to find from the governance page 16:49:49 yeah - we used to manage all that on the old wiki page, but things shifted more towards the governance one 16:49:56 there are likely some things we need to add 16:50:44 e.g - the meeting info dropped off of https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee 16:50:55 but didn't show up on the other page 16:51:02 in brief - no Twitter, no private email addresses, and do a better job of promoting the group email addr 16:51:51 is that wiki page editable by us? 16:52:38 Doesn't look like I can. :( 16:53:50 I would say lets focus on getting relevant info on the governance page 16:54:13 ok! 16:54:15 I'm not sure what the long term plan is for the wiki stuff 16:54:35 now that I've looked it the page above is actually a redirect from what used to be our page 16:55:26 4 minutes left - anything else? 16:58:27 Ok, we'll wrap up 16:58:39 be sure to spend some time with studarus's document 16:58:49 and we'll meet back here at 15:00 UTC next week 16:59:50 #endmeeting