*** jamesmcarthur has joined #openstack-uc | 01:03 | |
*** jamesmcarthur has quit IRC | 01:08 | |
*** jamesmcarthur has joined #openstack-uc | 02:03 | |
*** jamesmcarthur has quit IRC | 02:04 | |
*** lbragstad has joined #openstack-uc | 13:49 | |
*** shubjer0 has joined #openstack-uc | 13:56 | |
*** shubjer0 is now known as shubjero | 13:57 | |
*** leong has joined #openstack-uc | 14:02 | |
*** ChanServ sets mode: +o leong | 14:02 | |
leong | 为/ | 14:02 |
---|---|---|
leong | o/ | 14:03 |
aprice | o/ | 14:03 |
shubjero | hi | 14:03 |
aprice | hello | 14:04 |
tobberydberg | o/ | 14:04 |
*** shubjero is now known as Jared | 14:05 | |
*** leong has quit IRC | 14:07 | |
*** leong has joined #openstack-uc | 14:10 | |
*** ChanServ sets mode: +o leong | 14:10 | |
aprice | mrhillsman: are we still meeting now? | 14:14 |
leong | tried to ping but not getting a respone.... | 14:16 |
mrhillsman | Hey, no internet, sorry | 14:18 |
mrhillsman | Having to use my phone now, was trying to get ISP resolved | 14:19 |
mrhillsman | #startmeeting uc | 14:19 |
openstack | Meeting started Mon Jun 11 14:19:17 2018 UTC and is due to finish in 60 minutes. The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:19 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:19 |
*** openstack changes topic to " (Meeting topic: uc)" | 14:19 | |
openstack | The meeting name has been set to 'uc' | 14:19 |
mrhillsman | #topic Roll Call | 14:19 |
leong | hello mrhillsman | 14:19 |
*** openstack changes topic to "Roll Call (Meeting topic: uc)" | 14:19 | |
leong | o/ | 14:19 |
aprice | o/ | 14:20 |
tobberydberg | o/ | 14:20 |
mrhillsman | #chair leong | 14:20 |
openstack | Current chairs: leong mrhillsman | 14:20 |
mrhillsman | #chair zioproto spotz | 14:21 |
openstack | Current chairs: leong mrhillsman spotz zioproto | 14:21 |
spotz | o? | 14:21 |
mrhillsman | #topic Vancouver Summit Recap | 14:23 |
*** openstack changes topic to "Vancouver Summit Recap (Meeting topic: uc)" | 14:23 | |
mrhillsman | Any key takeaways or additional items we should keep on our radar from the summit? | 14:24 |
leong | mrhillsman: good UC summary to the board :) | 14:26 |
spotz | Um for me I need to follow up with the ops meetup folks, there was a really good troubleshooting workshop from SUSE that might be worth redoing at the meetup as at least one of them will already be there and from some of the discussions I'd be willing to offer the git and gerrit training there as well | 14:27 |
aprice | one of the items to keep on the radar is that there are a lot of operators that are still looking for 1:1 content on how to get involved in the ops community. i think it may be a worthwhile lightning talk or pre-Summit Superuser article so folks know where to go / who to meet and how to engage | 14:29 |
mrhillsman | ++ | 14:30 |
leong | aprice: +1 | 14:30 |
Jared | Thats a good idea | 14:30 |
leong | maybe also considering a "UC clinics" :-) | 14:30 |
aprice | love that | 14:31 |
mrhillsman | What do y'all think about a set of videos along with the articles or supplemental to them? | 14:31 |
mrhillsman | Short and to the point | 14:31 |
mrhillsman | Either way we should list what that content is | 14:32 |
aprice | yeah i like that idea. something lightweight and short | 14:32 |
spotz | If we can get them in the ops area of the site, they need to be easily accessible because some of the info is out there just hard to find. | 14:33 |
leong | is that something we can plan for Berlin? | 14:33 |
spotz | Also keep in mind the First Contact SiG is looking to expand into the OPs area but we didn;t have time to continue those conversations | 14:33 |
mrhillsman | agreed, that's why I think a curated list of items would be good | 14:33 |
aprice | yeah, we could figure out a way to incorporate into the contributors portal at openstack.org/community | 14:34 |
spotz | I think there's a start there aprice, it's pretty barebones | 14:34 |
spotz | We didscussed it at the FC Ops session | 14:35 |
aprice | yeah, there definitely needs to be more content there. | 14:36 |
mrhillsman | can we use an etherpad to list some low hanging fruit? | 14:38 |
mrhillsman | i.e. things to record/write | 14:38 |
mrhillsman | say by next meeting, then we can divide and conquer? | 14:38 |
mrhillsman | anything else on this topic? | 14:39 |
aprice | not from me | 14:42 |
mrhillsman | #topic User Survey update | 14:42 |
*** openstack changes topic to "User Survey update (Meeting topic: uc)" | 14:42 | |
aprice | I can provide an update :) | 14:42 |
mrhillsman | thx ;) | 14:43 |
aprice | now that the summit is wrapped, the promotion of the user survey is definitely top of mind. we have not received many submissions and are planning to ramp up promotion. It is currently scheduled to close August 3. | 14:43 |
aprice | we would definitely appreciate any help promoting it to folks who should complete a deployment. since it's a new year / updated survey, this should be completed by anyone - even if they have completed a survey in a previous cycle | 14:43 |
aprice | we are working on comms to previous takers, but maybe next week (or this week) someone from the UC can remind the Mailing Lists? UC, Ops and Community? | 14:44 |
spotz | soory helping a user with a networking issue in PMs, ping if I don't answer something:) | 14:44 |
aprice | otherwise, it's moving along :) | 14:45 |
leong | aprice: let know if anything i can help to promote the survey to PRC | 14:45 |
aprice | thanks leong! are there channels we could promote to? WeChat? to help get it in front of folks? | 14:45 |
tobberydberg | Can we help put from PCWG? | 14:46 |
aprice | I think that making sure all of the Public Clouds take it would be a big win | 14:46 |
aprice | maybe we can remind folks during the meetings and I can also reach out to the contacts that I have? | 14:46 |
Jared | Are we talking about this survey? https://www.openstack.org/user-survey/survey-2018/landing?BackURL=/user-survey/survey-2018/ | 14:47 |
tobberydberg | Is it purely focused on "operators" or end users as well? | 14:47 |
aprice | shubjero: yep! | 14:47 |
leong | aprice: i can find out the wechat channels | 14:47 |
tobberydberg | Yeps, definitely remind PCs at the next meeting | 14:47 |
aprice | tobberydberg: it is just focused on operators of openstack, not end users | 14:47 |
aprice | leong: thanks! | 14:47 |
aprice | tobberydberg: thanks! | 14:48 |
tobberydberg | got it, thanks | 14:48 |
aprice | that's all of the update from me | 14:49 |
mrhillsman | thx aprice | 14:50 |
mrhillsman | #topic financial team | 14:50 |
*** openstack changes topic to "financial team (Meeting topic: uc)" | 14:50 | |
leong | we are working within Financial Team and trying to invite more PRC financial institutions to contribute/share their use case study. | 14:52 |
leong | To make the invitation efficient and "more official", wondering if I can send out the invitation on behalf of UC's name so that this can give Financial Team more credibility? | 14:52 |
leong | somethings like: We at UC are intersted in collecting more use case studies and working with Financial Team to collect information/case-study | 14:53 |
aprice | leong: it would also be great if with that invitation we can encourage them to take the user survey | 14:53 |
leong | aprice: +1 | 14:54 |
spotz | Defintiely | 14:54 |
leong | multi-purpose in one invitation :) | 14:54 |
mrhillsman | I think the only issue was the way some of the emai i'll was worded leong | 14:54 |
leong | the mail/invitation will be in mandarin :) | 14:54 |
mrhillsman | Ugh autocorrect | 14:54 |
mrhillsman | lol | 14:55 |
mrhillsman | worded not language | 14:55 |
mrhillsman | I think everyone was ok with the intent | 14:55 |
leong | i can draft the letter in mandarin, and translated to english.... | 14:55 |
mrhillsman | ++ | 14:56 |
leong | two purpose in the invitation: 1) encourage to participate/contribute use case study (2) user survey | 14:56 |
mrhillsman | I just want us to be careful of any legal ramifications based on the wording | 14:56 |
mrhillsman | You sent a draft previously I thought but maybe that was just an example | 14:57 |
leong | mrhillsman: yup.. something like that.. but i will add the user survey as well | 14:58 |
mrhillsman | #action leong draft email for financial team | 14:58 |
leong | fyi: The OpenStack User Committee (UC) has commissioned to establish a Financial Team with the charter to bridge the gap of Financial Cloud for OpenStack. UC is interested in collecting more use case studies in the financial sector. We would like to invite XXX Bank to participate in this program. If XXX Bank is interested in participating in this program, please contact UC member Dr Yih Leong Sun or Financial Team Co-chair Zu L | 14:58 |
leong | above is what i drafted to mrhillsman email | 14:58 |
leong | will be in "mandarin" | 14:59 |
spotz | I think it's got the needed info leong | 15:00 |
leong | i will add the user survey part | 15:00 |
aprice | thanks leong! | 15:01 |
mrhillsman | I think the 'has commissioned' was the only think I cringed on | 15:01 |
mrhillsman | aprice any issue there? | 15:01 |
spotz | has asked? But considering it's being translated it might be the closest word? | 15:02 |
aprice | yeah - that's a weird wording. maybe "The OpenStack User Committee (UC) has established a Financial Team with the charter to" | 15:04 |
leong | +1 established | 15:04 |
leong | established = 成立 | 15:04 |
mrhillsman | Ok cool | 15:05 |
mrhillsman | So I know we are over, apologies | 15:05 |
mrhillsman | Thx again everyone | 15:06 |
spotz | We also started late | 15:06 |
mrhillsman | True, did not want to impede | 15:06 |
leong | anyway i will draft the letter in chinese, then have it translated to english for UC review | 15:08 |
spotz | Thanks Leong | 15:08 |
mrhillsman | So the last thing was reviewing against the requirements doc teams and wgs | 15:09 |
mrhillsman | #topic WGs/Teams Review | 15:10 |
*** openstack changes topic to "WGs/Teams Review (Meeting topic: uc)" | 15:10 | |
spotz | Last thing I saw on that was the emails going back and forth the week after summit | 15:11 |
mrhillsman | #link https://governance.openstack.org/uc/reference/new-uc-group-requirements.html | 15:11 |
mrhillsman | So we have this which we should check everyone against and I do not think every wg/team adheres to it right now and we need to help them be aligned | 15:12 |
*** leong has quit IRC | 15:13 | |
mrhillsman | That was pretty much it | 15:17 |
tobberydberg | Please let me know if we are failing at some requirements =) | 15:19 |
mrhillsman | #topic Other Business | 15:19 |
*** openstack changes topic to "Other Business (Meeting topic: uc)" | 15:19 | |
mrhillsman | Definitely will tobberydberg | 15:19 |
tobberydberg | ++ | 15:19 |
tobberydberg | Need to drop off. Take care! | 15:24 |
spotz | mrhillsman: I think the 1 IRC meeting in addition to the other meetings might help some of the reluctance | 15:38 |
*** Jared has left #openstack-uc | 15:50 | |
mrhillsman | Sorry, got disconnected | 15:56 |
mrhillsman | #endmeeting | 15:56 |
*** openstack changes topic to "Open Discussion (Meeting topic: uc)" | 15:56 | |
openstack | Meeting ended Mon Jun 11 15:56:57 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:56 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-06-11-14.19.html | 15:57 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-06-11-14.19.txt | 15:57 |
openstack | Log: http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-06-11-14.19.log.html | 15:57 |
aprice | thanks everyone! | 15:58 |
mrhillsman | thx ! | 16:00 |
*** ellopunk has joined #openstack-uc | 16:57 | |
*** ellopunk has quit IRC | 19:13 | |
-openstackstatus- NOTICE: Zuul was restarted for a software upgrade; changes uploaded or approved between 19:30 and 19:50 will need to be rechecked | 19:58 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!