22:00:16 #startmeeting app_ecosystem_wg 22:00:17 Meeting started Mon Aug 1 22:00:16 2016 UTC and is due to finish in 60 minutes. The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:00:20 The meeting name has been set to 'app_ecosystem_wg' 22:00:21 Hello everyone! 22:00:23 hi :) 22:00:24 Hi! 22:00:32 Agenda: https://etherpad.openstack.org/p/2016_Aug_1_App_Ecosystem_Workgroup 22:01:09 Hello! 22:01:18 hey 22:01:18 #topic Guadalajara App Hackathon 22:01:58 we are ready for our next training 22:02:01 My First Cloud-Aware App in OpenStack 22:02:03 Judging from the updates to this agenda item, the pre-training is ongoing and going well? 22:02:12 very well 22:02:23 \o/ 22:02:24 the past training was a success 22:02:50 yay1 22:02:52 * shamail sneaks in 22:02:54 hi 22:02:57 josh is ready 22:02:58 we expect the same number of attendes (~30) 22:03:29 hello 22:03:34 hi vic 22:03:59 Excellent :). Patifa, you have a hypothesis you want to test? 22:04:47 Well, Piet needed to depriorize the research unfortunalety 22:05:10 Internal reasons? 22:05:24 o/ 22:05:25 he has other projects. 22:05:32 but I thought we could take a stab at creating a survey to use at the hackathon 22:05:46 Happy to help! 22:05:47 Create a survey target to hackathon participants to help identify pain points in their user journey that we could address in the future. Victor and I drafted the user journey in the hackathon: Architect app > Design/Prototype > Define API/services/SDK > Define language > Gather info/documentation > Prototype (Code>Deploy>Test - repeat) 22:05:47 Main question here is what are our hypothesis we want to confirm. I want to schedule a brainstorming session so that we can come up with some hypotheses to use to create the survey around. 22:06:19 o/ 22:06:20 where do we think devs get stuck.. 22:07:15 We can also target to Point participants to Piet’s survey during the even to help increase Openstack UX project app developer database. Quick and easy. 22:07:39 also, trainings can help us to create hypothesis 22:07:44 Interesting. So this is the journey that the hackathon education is structured around? 22:08:14 There are not mandatory steps... but this are the step we believe they follow 22:08:54 There were others steps, but they were Hackathon specific so l left them out 22:09:07 Like "create biz presentation" 22:09:23 * krotscheck wonders if the process is a little more like: "I have requirements handed to my by a PM" -> "Google Stackoverflow" -> "Follow tutorial", with the language preassumed by the team you're working in. 22:09:51 Either way, you want to brainstorm. At the hackathon? Sometime in the next few weeks? 22:10:06 In real life or hackathon mode? 22:10:23 I want to brainstorm this thrusday ;P 22:10:33 Ok, let's brainstorm this thursday :) 22:10:41 Who would you like to participate? 22:10:46 (real life) 22:11:30 I'm not sure what we're talking about here 22:11:37 The truth is that we wont get "real life data" at the hackathon. But we may still find interesting pain points that might be true in real life too 22:11:41 and I'm not sure what you mean by 'real life' :P 22:11:59 notmars: Two different threads. 22:12:26 So, the goal of this research is to identify the pain points encountered by devs when they try to build on OpenStack? 22:12:44 Yep. 22:13:05 And on thursday you'd like to get people together to brainstorm a testable hypothesis, and then develop tests to check it? 22:13:15 Not sure I can contribute to dev pain points, but can help translate brainstorming items to survey questions 22:13:15 yep 22:13:43 Sure, and we need that skill uxdanielle :D 22:15:06 I'll send the invite to the mailing list. I wanted to check if you think this is a good opportinity too. use ~200 app developers in one place for 2 days playing with OpenStack to gather data. 22:15:29 possibly create a model to be replicated in other hackathons 22:15:34 I think it might be. uxdanielle would know better on the best way to collect data. 22:15:48 Knowing that they may be fairly new to OpenStack 22:15:57 I'd say yes in a more 'passive' capacity (like observing), but if we intervene during their hack...their bound to get frustrating at that activity :P 22:16:17 (frustrated, not frustrating) 22:16:32 exactly 22:16:33 we need to make it so it doesnt get in their way during the hackathon 22:16:37 notmars: due to lack of time 22:16:49 That depends on what you want to know - we might learn more after the brainstorming about what that looks to be 22:17:11 Sounds like there's enough interest. Patifa, how about you organize the call/irc meeting and we'll see what shakes out. 22:17:19 Any disagreements before we move on? 22:17:57 Ok, Any other questions about the Hackathon? 22:18:15 Ok. 22:18:20 #topic Barcelona 22:18:42 action: Patricia to organize brainstoming session around research during hackthon. 22:18:50 mbonell has been in touch with speaker support. It looks like there will be a separate invite for WG-based space, is that correct? 22:18:56 yep 22:19:04 looks like I have to wait 22:19:06 #action: Patricia to organize brainstoming session around research during hackthon. 22:19:09 #action: Patricia to organize brainstoming session around research during hackthon 22:19:10 Oh 22:19:12 :) 22:19:16 but they know about our training proposal 22:19:20 ;) 22:19:22 Just to confirm, is this to see whether we can get space as well? 22:20:06 yep 22:20:13 I'd like to put together a fishbowl session for SDK work during the summit. Given that both shade and the javascript sdk is under the infra banner, we can always request it via fungi, however if it's feasible for us to get space directly from the foundation that'd also be great. 22:20:26 That' sindependent of your training piece though 22:20:53 They will put out the call for WG spaces after the schedule gets published on 8/25 22:21:05 carolbarrett: Ah, excellent. Thank you. 22:21:38 Are there any other WG-related sessions we'd like to propose? 22:21:57 Besides the Birds of a feather and working session? 22:22:12 looks enough for me 22:22:31 +1 22:22:39 Alright, I'll take that down in the notes. 22:23:13 Does anyone think an SDK working session makes sense? 22:23:48 Can you give me more on what you think would come out of it 22:24:02 quality of SDK? Narrowing what SDKs? 22:24:09 Well, I know the Javascript sdk team wants to spend an hour or two hacking together. 22:24:45 I also know that mordred is partial to doing the same with shade, but that'll likely be under the infra banner. 22:24:50 well I think that would be kind of out of scope for us if it's a working session 22:24:52 krotscheck: +1, I'd like to attend that session to discuss how we might be able to provide status information for SDKs in a centralized manner 22:25:12 I'd like that too in fact :P 22:25:23 that's an amazing idea for SDK devs 22:25:34 Right, but it might not be App Eco WG related. 22:25:49 Ya know, this seems like a dev-audience thing that I should take to the dev lsit 22:25:58 something more up to date than https://wiki.openstack.org/wiki/SDKs 22:26:00 shamail, what do you mean by "provide status information for SDKs in a centralized manner"? 22:26:15 #action krotscheck: Start conversation on the dev list about the needs of SDK developers at the summit. 22:26:34 App Eco is the only team I've seen put that info together 22:26:35 krotscheck, or the other way around, reach out to SDK devs 22:26:54 Reed: which services are supported, last update, etc 22:26:55 I think that it's a gap that we should fill, wherever we put it 22:27:15 shamail, so like craigs said, a better wiki page? 22:27:24 Yep! 22:27:27 a better page than the wiki, in other words :) 22:27:41 +1 22:27:43 We would also pull from that page for the operator tag 22:28:17 (Didn't mean to hijack, sorry) 22:28:40 The conversation's getting out of scope for Barcelona. 22:28:56 So let's move on and put this in open discussion 22:29:01 * notmars_ still likes the SDK-dev hack session though :P 22:29:12 One last thing: Voting for sessions is open! Go vote ! https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/ 22:29:29 krotscheck: i'd be comfortable with an infra summit session for that, but cross-project might be even better still? 22:30:11 #topic AppDev User study 22:30:37 From earlier conversation, it sounds like the UX team is no longer focused on this, is that correct uxdanielle? 22:30:49 nope.. that is not correct 22:31:05 Not exactly, in fact it's probably our biggest focus now! 22:31:21 this study is still on going. what got deprioritised was the research AT THE HACKATON ;D 22:31:25 Oh good! 22:31:32 * krotscheck likes clarification 22:31:41 Still no new participants on the schedule. Need to follow up with the qualified participant on scheduling and with Wendy on the progress of the recruit. 22:31:44 :) 22:31:49 Action item: carolbarrett to reach out to walmart and cern contacts. How's that going? 22:31:58 * mordred waves to krotscheck 22:32:16 ah - summit. yeah. happy to lurk/crash other thigns too 22:33:24 did piet send you the ask carolbarrett ? 22:33:58 I saw the ask on the ML 22:34:07 ok 22:35:45 carolbarrett: ping? Any word from the foundation, cern, or walmart? 22:38:15 Shall we move on? 22:38:25 Hrm, ok. Let's table that one for next week. uxdanielle, anything specific remaining on the survey, or can we move on? 22:39:29 Not from my end. I'll regroup with Piet about what we're going to do to find participants tomorrow. We were thinking of using the Foundation's list from the semi-annual survey but that's a big deal for us, so need to be sure once we pull that trigger 22:39:48 Yeah, that would be. Keep us up to date on what you find. 22:39:50 #topic AppDev Centric Ebook 22:39:54 (we can only send out one UX email per cycle so we need to plan to make sure we get everything in) 22:40:14 #link http://lists.openstack.org/pipermail/user-committee/2016-August/001150.html 22:40:41 This is a new ask from the Enterprise WG- they'd like to put together an app-dev focused ebook from now through the summit. 22:41:54 Leong sent an email to the mailing list about it. 22:42:03 They're asking for participants to help write individual sections. 22:42:28 I quite divided about this effort 22:42:34 and participate in the sprint they'll host at the summit 22:42:42 I feel that individual experts on our team have quite a bit to contribute to that, however I don't want to speak on their behalf for the required time commitment. 22:42:58 The sprint will be at the summit but we will be working on outline and get a head start before the summit 22:44:34 I'm worried about content overlap between firstapp and the ebook. 22:44:42 * krotscheck guesses that that overlap could be a strength. 22:44:50 I'm in agreement with that krotscheck 22:45:00 (not the strength part :P) 22:45:07 However if I had to choose one thing to focus on between the two, I'd focus on the one that you can google. 22:45:17 +1M 22:45:54 Does anyone have questions for shamail ?? 22:46:06 The ebook is focused on architecture/design considerations for cloud apps. We could probably point to or re-use firstapp as it makes sense 22:46:06 FirstApp is likely to be in google, but the ebook content not likely 22:46:14 I think it's fine to have both 22:46:19 just make sure they don't conflict 22:46:46 craigs: +1 22:47:11 Well, the initial outline is here: https://docs.google.com/document/d/1mR-M2ufn0lviyGughNdm0zFz9O6AlYFUSr3JKqoaiv4/edit 22:47:22 nice effort! 22:47:31 craigs +1 22:47:43 The target is 20 pages. 22:47:51 So, likely a launching off point. 22:47:59 there is a hugeeee lack about arch/design for cloud apps 22:48:34 those have been covered in previous books 22:48:50 12 minute warning 22:49:13 It doesn't seem like there's anything concrete to talk about on this other than "Hey, if you want to contribute, do!" 22:49:27 The previous eBooks from EWG focused on why to choose cloud and how to get started 22:49:39 That's fair krotscheck :) 22:50:20 Alright, let's move on. shamail, if your team has sepcific asks from us, please don't hesitate to bring them up in the future. 22:50:28 Thanks! 22:50:32 #topic InterOp Challenge 22:50:44 mbonell? DId you manage to get in touch with Brad Topol? 22:51:01 What's the ask here? I can help with this too 22:51:14 he han't response 22:51:20 not sure about his email address 22:51:29 I'll ping rocky 22:51:36 Well, I think his IRC handle is topol. 22:51:46 :o 22:51:48 ok 22:51:49 But yes, reach out to rockyg, :) 22:51:51 mbonell: plz email me, I'll connect you 22:51:57 I'm helping him 22:52:15 shamail: ok! 22:52:20 #action shamail mbonell Get in touch with topol 22:52:27 Next topic. 22:52:34 #topic FirstApp Progress 22:52:49 \o/ to everyone who got shade finished! 22:53:03 \o/ 22:53:06 yeay 22:53:09 yay!!! 22:53:29 fog is next, because is ready for test 22:53:51 * krotscheck did a quick once over on the firstapp content, summarized his thoughts here -> http://lists.openstack.org/pipermail/user-committee/2016-August/001149.html 22:54:35 Heat is still in progress, cleaning up html and need to do an autoscaling page 22:54:47 then I will be ready to publish 22:55:03 craigs++ 22:55:21 javascript is proceeding well, but we're still a few weeks out from landing keystone. 22:55:32 A lot of plumbing to do. 22:55:35 LOL thats kind of Key 22:55:51 craigs-- for the pun. 22:55:53 ;) 22:56:18 Does anyone have any issues they need help with? 22:56:25 Blockers, content, reviews, tests? 22:56:35 nope 22:56:46 no 22:56:52 Alright, next. 22:56:59 #topic What is an App. 22:57:09 Announcement made, patch landed against the app developer persona. 22:57:17 Topic complete. Any questions? 22:57:44 Cool! Last, open discussion! 22:57:49 #topic Open Discussion 22:58:46 shamail, you expressed an interest in having more information on what SDK's are available. 22:58:50 * krotscheck agrees. 22:59:07 * krotscheck will check with the docs team on the best place to put a summary page. 22:59:07 Yes 22:59:42 #action krotscheck: Find a good place to start summarizing SDK info, like a landing page. 22:59:49 Any last topics in our remaining 20 seconds? 22:59:50 There is a Google spreadsheet that was put together by App Eco last year... I wanted to turn that into a rendered page that could be updated by the community 23:00:17 Thanks everyone! 23:00:22 #endmeeting